Re: Kismet on FreeBSD 7.0-STABLE

2008-11-06 Thread Paul B. Mahol
On 11/6/08, Ludovit Koren [EMAIL PROTECTED] wrote:


 Hi,

 I am using

 iwi0: Intel(R) PRO/Wireless 2200BG mem 0xfafef000-0xfafe irq 9 at
 device 3.0 on pci2


 # kldload /boot/kernel/if_iwi.ko
 # kldload /boot/kernel/iwi_bss.ko
 # kldload /boot/kernel/iwi_ibss.ko
 # kldload /boot/kernel/iwi_monitor.ko
 # /etc/rc.d/wpa_supplicant start iwi0

 which is working fine when I am using it connecting to WiFi net. When
 I am using wpa_cli scan and scan_results I can see different nets.

 I have the following configuration line in the kismet.conf file:

 source=radiotap_bsd_ab,iwi0,pcapfile

It should be:

source=radiotap_bsd_ab,iwi0,iwi0

More information is required. Can you put iwi0 into monitor mode and
use tcpdump instead?

ifconfig iwi0 monitor
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Kismet on FreeBSD 7.0-STABLE

2008-11-06 Thread Jan Henrik Sylvester

Ludovit wrote:
 iwi0: Intel(R) PRO/Wireless 2200BG mem 0xfafef000-0xfafe irq 9
 at device 3.0 on pci2

Monitor is broken on iwi on FreeBSD 7. I did report it during the 
7.0-BETA, but there was at least one more report in the meantime.


With exactly the same setup, I can use kismet with ural (ok), zyd (many 
broken packages), ral (ok), and ath (good, but see below). I do not 
receive a single package with iwi.


I did replace my iwi miniPCI device by an ath one, which is more 
reliable anyhow. (iwi, as all Intel cards, occasionally dies and cannot 
reload firmware because of too little dma memory. That was reported a 
few times, too.)


ath can monitor, even for longer periods of time, but if I do channel 
hopping in kismet, it often eventually stops receiving packages after a 
few minutes. Restarting kismet always fixes that. (I have had that with 
different ath cards.)


iwi monitoring did work on 6.2, but often the card would not do regular 
networking after that until reboot and the problem with the firmware 
mentioned above was already present, although it was much better than on 
6.1.


For monitoring, you should either get a different card or try 6.X, 
6-STABLE, or maybe 8-CURRENT. (I have no experience with the latter.)


Cheers,
Jan Henrik
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Kismet on FreeBSD 7.0-STABLE

2008-11-06 Thread Ludovit Koren


Hi,

I am using 

iwi0: Intel(R) PRO/Wireless 2200BG mem 0xfafef000-0xfafe irq 9 at device 
3.0 on pci2


# kldload /boot/kernel/if_iwi.ko
# kldload /boot/kernel/iwi_bss.ko
# kldload /boot/kernel/iwi_ibss.ko
# kldload /boot/kernel/iwi_monitor.ko
# /etc/rc.d/wpa_supplicant start iwi0

which is working fine when I am using it connecting to WiFi net. When
I am using wpa_cli scan and scan_results I can see different nets.

I have the following configuration line in the kismet.conf file:

source=radiotap_bsd_ab,iwi0,pcapfile


I am using kismet_server and kismet_client commands but I cannot see
any received data (networks, packets, ...)

I tried 

source=radiotap_bsd_ab,iwi0,ipw2200

as well with no success. Anyone was able to succeed with kismet? Is
the Intel(R) PRO/Wireless 2200BG working with kismet at all? Any hints
greatly appreciated.

Thank you very much in advance.

Regards,

lk
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Kismet on FreeBSD 7.0-STABLE

2008-11-06 Thread Ludovit Koren

 On Thu, 06 Nov 2008 13:12:23 +0100
 [EMAIL PROTECTED](Paul B. Mahol)  said:
 
 On 11/6/08, Ludovit Koren [EMAIL PROTECTED] wrote:
 
 
  Hi,
 
  I am using
 
  iwi0: Intel(R) PRO/Wireless 2200BG mem 0xfafef000-0xfafe irq 9 at
  device 3.0 on pci2
 
 
  # kldload /boot/kernel/if_iwi.ko
  # kldload /boot/kernel/iwi_bss.ko
  # kldload /boot/kernel/iwi_ibss.ko
  # kldload /boot/kernel/iwi_monitor.ko
  # /etc/rc.d/wpa_supplicant start iwi0
 
  which is working fine when I am using it connecting to WiFi net. When
  I am using wpa_cli scan and scan_results I can see different nets.
 
  I have the following configuration line in the kismet.conf file:
 
  source=radiotap_bsd_ab,iwi0,pcapfile
 
 It should be:
 
 source=radiotap_bsd_ab,iwi0,iwi0

I tried it even with this, no success

 
 More information is required. Can you put iwi0 into monitor mode and
 use tcpdump instead?
 
 ifconfig iwi0 monitor
 

I cannot capture any packet.

lk
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Kismet on FreeBSD 7.0-STABLE

2008-11-06 Thread Paul B. Mahol
On 11/6/08, Ludovit Koren [EMAIL PROTECTED] wrote:

 On Thu, 06 Nov 2008 13:12:23 +0100
 [EMAIL PROTECTED](Paul B. Mahol)  said:

 On 11/6/08, Ludovit Koren [EMAIL PROTECTED] wrote:
 
 
  Hi,
 
  I am using
 
  iwi0: Intel(R) PRO/Wireless 2200BG mem 0xfafef000-0xfafe irq 9 at
  device 3.0 on pci2
 
 
  # kldload /boot/kernel/if_iwi.ko
  # kldload /boot/kernel/iwi_bss.ko
  # kldload /boot/kernel/iwi_ibss.ko
  # kldload /boot/kernel/iwi_monitor.ko
  # /etc/rc.d/wpa_supplicant start iwi0
 
  which is working fine when I am using it connecting to WiFi net. When
  I am using wpa_cli scan and scan_results I can see different nets.
 
  I have the following configuration line in the kismet.conf file:
 
  source=radiotap_bsd_ab,iwi0,pcapfile

 It should be:

 source=radiotap_bsd_ab,iwi0,iwi0

 I tried it even with this, no success


 More information is required. Can you put iwi0 into monitor mode and
 use tcpdump instead?

 ifconfig iwi0 monitor


 I cannot capture any packet.

Then it is iwi driver problem.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]