Date: Thu, 19 Mar 2009 08:44:29 -0700 From: Sam Leffler <sam@freebsd.org> To: Matthias Apitz <guru@unixarea.de> Cc: freebsd-net@freebsd.org Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work Message-ID: <49C2685D.6040801@freebsd.org> In-Reply-To: <20090319144251.GA13320@rebelion.Sisis.de> References: <20090317103650.GA6156@rebelion.Sisis.de> <49BF7DE4.4010804@incunabulum.net> <20090317104548.GB6182@rebelion.Sisis.de> <alpine.BSF.2.00.0903171148250.51892@thor.farley.org> <49BFF258.4020207@freebsd.org> <20090319144251.GA13320@rebelion.Sisis.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthias Apitz wrote: > El día Tuesday, March 17, 2009 a las 11:56:24AM -0700, Sam Leffler escribió: > > >> His setup is static key wep; not wpa so I don't think wpa_supplicant is >> the issue. >> >> Matthias, your tcpdump of the dhclient packets isn't usable; please try: >> >> tcpdump -i ath0 -n -y IEEE802_11_RADIO >> >> I reviewed the driver to the code in HEAD and the only difference in the >> crypto area should not matter in this case. It's possible wme is >> somehow enabled and causing problems but the ifconfig output doesn't >> indicate that. >> >> If you can find out the model of ap that might be helpful. >> Unfortunately the best thing to try is HEAD. >> > > I will try to collect a better tcpdump of the dhclient packets on the > weekend and as well figure out what kind of model the AP is; > > would it be helpful to connect with a Windows XP laptop (which seems to > work) to gather some information of the Wifi and other network > parameters? how this could be seen in Windows? maybe there is some > special compression of the payload of the packages in place? > Having a packet trace of a working connection to compare would be very helpful. > I have seen such 'options' in another AP (a Netgear WGT624 v3), > the option was called "[ ] Disable Advanced 108Mbps Features" > and this must be checked (i.e. disabled) to make DHCP happy with > the ath0 EeePC; > That controls SuperG support in Atheros-based ap's and is unrelated. There is a known problem with SuperG support that has been fixed in HEAD but not yet backmerged. For reasons unknown your (apparently) simple setup is not working. I do not use RELENG_7 w/ the stock wireless and have no familiarity with it's status so it's more likely there's just some bug fix not back-merged. > unfortunately I can't look into the AP about this problem is :-( > > thx > > matthias >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49C2685D.6040801>