On 11/9/05, <b class="gmail_sendername">Jouni Malinen</b> <<a href="mailto:jkmaline@cc.hut.fi">jkmaline@cc.hut.fi</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Wed, Nov 09, 2005 at 12:09:35PM -0600, Tony Jarnigan wrote:<br><br>> My Linux box (A) is using wpa_supplicant(v4.4) to do WPA-PSK to a Proxim AP.<br>> It connects fine but when another machine(B) on the network tries to ping
<br>> it, there's no response; no ssh or vnc either although the daemons are<br>> running. It's not iptables or any other firewall software, nothing is<br>> running.<br>><br>> Oddly enough, if A pings B, B can connect no problem. If I discontinue the
<br>> ping, the problem seems to come up again within 2 minutes. If I turn off<br>> WPA-PSK and not run wpa_supplicant, everything works as expected.<br><br>That sounds like issues with multicast/broadcast receive on the host
<br>(A). Pinging A->B allows (B) to update its ARP table without (A) having<br>to receive broadcast arp who-has request and that 2 minutes would be a<br>timeout for the ARP cache.<br><br>What card and driver (including version) are you using on (A)?
</blockquote><div><br></div></div>Proxim 8470 using madwifi checked out 8/14/05: ath_pci=0.9.6, ath_hal=<a href="http://0.9.14.9">0.9.14.9</a><br><br>I've just recently learned the new madwifi is out but haven't had a chance to compile it. I'll investigate broadcast issues but it also seems to be some interaction with wpa_supplicant since without wpa_supplicant, B can get to A without A pinging B.
<br><br>Tony<br>