unknown timeout using wpa_supplicant

Tony Jarnigan tony at jarnigan.net
Sun Nov 13 21:51:31 EST 2005


On 11/9/05, Jouni Malinen <jkmaline at cc.hut.fi> wrote:
>
> On Wed, Nov 09, 2005 at 12:09:35PM -0600, Tony Jarnigan wrote:
>
> > My Linux box (A) is using wpa_supplicant(v4.4) to do WPA-PSK to a Proxim
> AP.
> > It connects fine but when another machine(B) on the network tries to
> ping
> > it, there's no response; no ssh or vnc either although the daemons are
> > running. It's not iptables or any other firewall software, nothing is
> > running.
> >
> > Oddly enough, if A pings B, B can connect no problem. If I discontinue
> the
> > ping, the problem seems to come up again within 2 minutes. If I turn off
> > WPA-PSK and not run wpa_supplicant, everything works as expected.
>
> That sounds like issues with multicast/broadcast receive on the host
> (A). Pinging A->B allows (B) to update its ARP table without (A) having
> to receive broadcast arp who-has request and that 2 minutes would be a
> timeout for the ARP cache.


I tried compiling the new madwifi-ng drivers and also wpa_supplicant
0.4.6but they didn't seem to work together (I didn't spend much time
debugging).
I went back to my previous madwifi drivers but used the newer wpa_supplicant
and things seem to work now. I'll certainly want madwifi-ng working in the
future but this gets me what I want.

Tony
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20051113/b0609405/attachment.htm 


More information about the HostAP mailing list