Date: Tue, 10 Feb 2009 11:25:54 -0800 From: Yuri <yuri@rawbw.com> To: "Sam Leffler" <sam@freebsd.org> Cc: freebsd-hackers@freebsd.org Subject: Re: How to troubleshoot why ath0 can't connect to a passwordless wireless network? Message-ID: <20090210112554.15896t24mpahwggs@webmail.rawbw.com> In-Reply-To: <4991ADB5.9050803@freebsd.org> References: <20090209143642.168421bp9jjvs7i8@webmail.rawbw.com> <4991ADB5.9050803@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting "Sam Leffler" <sam@freebsd.org>: > You seem to say your network is open (no security). If not you need =20 > to show your network configuration. That's right, network is open (no security). > tcpdump can be used to tap traffic at 3 layers: 802.3, 802.11, and =20 > driver. It can be used to identify where packets are lost in the =20 > hierarchy (if at all). 'tcpdump -vv -i ath0' shows nothing when I run 'dhclient ath0' or 'dhcping -s 255.255.255.255'. dhclient always fails, dhcping says "no answer". But tcpdump shows traffic between other hosts on the same network. > Assuming packets are going out but not coming back you can sniff =20 > from a 3rd station to look for traffic in the air but not received. No, now packets don't seem to go out at all. I said before that packets went out when interface in fact was in 'monitor' mode. > Given how little info you posted it's virtually impossible to advise =20 > you what is wrong. When in doubt c&p real output; describing a =20 > problem often causes useful info to be left out. There is no "real output" from tcpdump, this is a problem. How to find out for example why 'sendto' call from dhcping doesn't =20 result in any packets on ath0 interface which is 'UP' and 'associated'? I used this same system to connect to other open WiFi networks without =20 the problem. So it seems to be network-specific. And it fails only for =20 certain networks. Yuri
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090210112554.15896t24mpahwggs>