Bad communication

Holger Schurig holgerschurig
Fri Jan 22 01:34:59 PST 2010

> How to troubleshoot this? Where could be the problem?

Maybe with a better trace, either in the libpcap format 
("tcpdump ... -w error.pcap") or, since I render tcpdump as 
outdated, with wireshark. For text text version of it, tshark, 
you could do something like "tshark ... -V".

And ideally, you'd sniff the traffic from a third WLAN card, so 
that you can see what is "on the air". You'd need to set that 
interface into monitor mode, e.g. with a cfg80211 controlled 

ifconfig wlan0 down
(and be sure that no wicd/networkmanager disturbs you)
iw wlan0 set type monitor
ifconfig wlan0 up
iw set channel XX / iw set freq YYYY
tshark -i wlan0 -V


More information about the Hostap mailing list