Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
Synopsis: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work Responsible-Changed-From-To: freebsd-net-freebsd-wireless Responsible-Changed-By: adrian Responsible-Changed-When: Mon Apr 11 11:43:53 UTC 2011 Responsible-Changed-Why: punt to freebsd-wiereless http://www.freebsd.org/cgi/query-pr.cgi?pr=132722 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
El día Friday, March 20, 2009 a las 09:06:04AM -0700, Sam Leffler escribió: This looks like a longstanding bug in handling modules loaded by loader that have undefined references (e.g. because your kernel is misconfigured). In general I don't think you're going to get very far booting a HEAD kernel against RELENG_7 world. This will certainly not work for wireless where you need all the changes to ifconfig. If you're trying to test HEAD you will want a separate partition with a fresh install/build of HEAD. Well, I've built an USB key with CURRENT and it boots fine. But there seems to be a problem with the ath0 interface: # uname -a FreeBSD tinyCurrent 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Sun Mar 22 11:47:41 CET 2009 r...@rebelion.sisis.de:/usr/src/myHEAD/obj/usr/src/myHEAD/src/sys/GENERIC i386 # dmesg | fgrep ath ath0: Atheros 5424/2424 mem 0xfbff-0xfbff irq 18 at device 0.0 on pci1 ath0: [ITHREAD] ath0: AR2425 mac 14.2 RF5424 phy 7.0 # ifconfig ath0 ath0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 2290 ether 00:15:af:b2:ae:e6 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier # /usr/sbin/wpa_supplicant -i ath0 -c /etc/wpa_supplicant.conf ioctl[SIOCG80211, op 98, len 32]: Invalid argument Failed to initialize driver interface ELOOP: remaining socket: sock=5 eloop_data=0x28406140 user_data=0x2840d040 handler=0x8069f40 With the RELENG_7 kernel I've collected yesterday a better tcpdump when DHCP starts: http://www.unixarea.de/tcp2.txt Thx for any hint matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e matthias.ap...@oclc.org - w http://www.oclc.org/ http://www.UnixArea.de/ ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
El día Sunday, March 22, 2009 a las 01:14:24PM +0100, Matthias Apitz escribió: Well, I've built an USB key with CURRENT and it boots fine. But there seems to be a problem with the ath0 interface: # uname -a FreeBSD tinyCurrent 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Sun Mar 22 11:47:41 CET 2009 r...@rebelion.sisis.de:/usr/src/myHEAD/obj/usr/src/myHEAD/src/sys/GENERIC i386 # dmesg | fgrep ath ath0: Atheros 5424/2424 mem 0xfbff-0xfbff irq 18 at device 0.0 on pci1 ath0: [ITHREAD] ath0: AR2425 mac 14.2 RF5424 phy 7.0 # ifconfig ath0 ath0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 2290 ether 00:15:af:b2:ae:e6 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier # /usr/sbin/wpa_supplicant -i ath0 -c /etc/wpa_supplicant.conf ioctl[SIOCG80211, op 98, len 32]: Invalid argument Failed to initialize driver interface ELOOP: remaining socket: sock=5 eloop_data=0x28406140 user_data=0x2840d040 handler=0x8069f40 ... Ah, I found the solution with Don Google... I have now in CURRENT to do: # ifconfig wlan0 create wlandev ath0 # /etc/rc.d/wpa_supplicant start wlan0 or via /etc/rc.conf: wlans_ath0=wlan0 ifconfig_wlan0=WPA DHCP and the interface wlan0 comes up fine and get in my home office the IP with DHCP; will test this the other day in the Wifi zone where RELENG_7 does not get IP with DHCP; thx so far; matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e matthias.ap...@oclc.org - w http://www.oclc.org/ http://www.UnixArea.de/ ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
I went today evening with my EeePC and CURRENT on USB key to that Greek restaurant; DHCP does not get IP in CURRENT either; this is somehow good news, isn't it :-) below are some information concerning the AP, ifconfig ... the output of the tcpdump is on my server as http://www.unixarea.de/ath-current.txt let me know if you need more information; HIH matthias info about AP: Siemens Gigaset SE 505 dsl/cable S30853-S1006-R107-3 (handwritten label says: this is no DSL router; IP 192.168.2.1) as DSL-modem some Fritz!Box is connected to this box http://reviews.cnet.com/routers/siemens-gigaset-se505-dsl/1707-3319_7-30799508.html # uname -a FreeBSD tinyCurrent 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Sun Mar 22 11:47:41 CET 2009 r...@rebelion.sisis.de:/usr/src/myHEAD/obj/usr/src/myHEAD/src/sys/GENERIC i386 # ifconfig -a ath0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 2290 ether 00:15:af:b2:ae:e6 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=3RXCSUM,TXCSUM inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 wlan0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:15:af:b2:ae:e6 inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 media: IEEE 802.11 Wireless Ethernet DS/5.5Mbps mode 11g status: associated ssid ConnectionPoint channel 11 (2462 Mhz 11g) bssid 00:01:e3:0e:97:99 regdomain 96 indoor ecm authmode OPEN privacy ON deftxkey 1 wepkey 1:104-bit txpower 20 bmiss 7 scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme burst roaming MANUAL # tcpdump -n -i ath0 -y IEEE802_11_RADIO 17:56:24.647835 436598375373us tsft 1.0 Mb/s -80dB signal -96dB noise antenna 1 [0x0012] Beacon (ConnectionPoint) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] ESS[|802.11] 17:56:24.750225 43659844us tsft 1.0 Mb/s -81dB signal -96dB noise antenna 1 [0x0012] Beacon (ConnectionPoint) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] ESS[|802.11] 17:56:24.852621 436598580174us tsft 1.0 Mb/s -79dB signal -96dB noise antenna 1 [0x0012] Beacon (ConnectionPoint) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] ESS[|802.11] 17:56:24.955019 436598682572us tsft 1.0 Mb/s -80dB signal -96dB noise antenna 1 [0x0012] Beacon (ConnectionPoint) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] ESS[|802.11] ... full log see: http://www.unixarea.de/ath-current.txt ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
Matthias Apitz wrote: I went today evening with my EeePC and CURRENT on USB key to that Greek restaurant; DHCP does not get IP in CURRENT either; this is somehow good news, isn't it :-) This may be orthogonal, but: A lab colleague and I have been seeing a sporadic problem where the ath0 exhibits the symptoms of being disassociated from its AP. We are running RELENG_7 on the EeePC 701 since the open source HAL merge. In the behaviour we're seeing, we don't see any problem with the initial dhclient run, the ath0 just seems to get disassociated within 5-10 minutes of associating. If we leave 'ping ap-ip-address' running in the background, we don't see this problem. We have yet to produce a tcpdump to catch it 'in the act' and observe the DLT_IEEE80211 traffic when it actually happens, I have only seen the symptoms. The AP does not show the EeePC units as being associated any more at this point, but ath0 still shows 'status: associated'. The AP involved is a Netgear WG602 V2, and is running the vendor's firmware. I'll try to get set up with 'tcpdump -y ieee802_11' from initial boot (including dhcp and anything we bump into). cheers BMS ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
The following reply was made to PR kern/132722; it has been noted by GNATS. From: Bruce M Simpson b...@incunabulum.net To: Matthias Apitz g...@unixarea.de Cc: bug-follo...@freebsd.org, Sam Leffler s...@freebsd.org, freebsd-net@freebsd.org, Sean C. Farley s...@freebsd.org Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work Date: Mon, 23 Mar 2009 18:44:42 + Matthias Apitz wrote: I went today evening with my EeePC and CURRENT on USB key to that Greek restaurant; DHCP does not get IP in CURRENT either; this is somehow good news, isn't it :-) This may be orthogonal, but: A lab colleague and I have been seeing a sporadic problem where the ath0 exhibits the symptoms of being disassociated from its AP. We are running RELENG_7 on the EeePC 701 since the open source HAL merge. In the behaviour we're seeing, we don't see any problem with the initial dhclient run, the ath0 just seems to get disassociated within 5-10 minutes of associating. If we leave 'ping ap-ip-address' running in the background, we don't see this problem. We have yet to produce a tcpdump to catch it 'in the act' and observe the DLT_IEEE80211 traffic when it actually happens, I have only seen the symptoms. The AP does not show the EeePC units as being associated any more at this point, but ath0 still shows 'status: associated'. The AP involved is a Netgear WG602 V2, and is running the vendor's firmware. I'll try to get set up with 'tcpdump -y ieee802_11' from initial boot (including dhcp and anything we bump into). cheers BMS ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
El día Monday, March 23, 2009 a las 06:44:42PM +, Bruce M Simpson escribió: Matthias Apitz wrote: I went today evening with my EeePC and CURRENT on USB key to that Greek restaurant; DHCP does not get IP in CURRENT either; this is somehow good news, isn't it :-) This may be orthogonal, but: A lab colleague and I have been seeing a sporadic problem where the ath0 exhibits the symptoms of being disassociated from its AP. We are running RELENG_7 on the EeePC 701 since the open source HAL merge. In the behaviour we're seeing, we don't see any problem with the initial dhclient run, the ath0 just seems to get disassociated within 5-10 minutes of associating. If we leave 'ping ap-ip-address' running in the background, we don't see this problem. ... This must be a complete different problem, because in my case the AP stays (at least what ifconfig shows) always associated, but don't get offered IP addr; matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e matthias.ap...@oclc.org - w http://www.oclc.org/ http://www.UnixArea.de/ ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
Matthias Apitz wrote: I went today evening with my EeePC and CURRENT on USB key to that Greek restaurant; DHCP does not get IP in CURRENT either; this is somehow good news, isn't it :-) below are some information concerning the AP, ifconfig ... the output of the tcpdump is on my server as http://www.unixarea.de/ath-current.txt let me know if you need more information; HIH matthias info about AP: Siemens Gigaset SE 505 dsl/cable S30853-S1006-R107-3 (handwritten label says: this is no DSL router; IP 192.168.2.1) as DSL-modem some Fritz!Box is connected to this box http://reviews.cnet.com/routers/siemens-gigaset-se505-dsl/1707-3319_7-30799508.html # uname -a FreeBSD tinyCurrent 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Sun Mar 22 11:47:41 CET 2009 r...@rebelion.sisis.de:/usr/src/myHEAD/obj/usr/src/myHEAD/src/sys/GENERIC i386 # ifconfig -a ath0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 2290 ether 00:15:af:b2:ae:e6 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=3RXCSUM,TXCSUM inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 wlan0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:15:af:b2:ae:e6 inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 media: IEEE 802.11 Wireless Ethernet DS/5.5Mbps mode 11g status: associated ssid ConnectionPoint channel 11 (2462 Mhz 11g) bssid 00:01:e3:0e:97:99 regdomain 96 indoor ecm authmode OPEN privacy ON deftxkey 1 wepkey 1:104-bit txpower 20 bmiss 7 scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme burst roaming MANUAL # tcpdump -n -i ath0 -y IEEE802_11_RADIO 17:56:24.647835 436598375373us tsft 1.0 Mb/s -80dB signal -96dB noise antenna 1 [0x0012] Beacon (ConnectionPoint) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] ESS[|802.11] 17:56:24.750225 43659844us tsft 1.0 Mb/s -81dB signal -96dB noise antenna 1 [0x0012] Beacon (ConnectionPoint) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] ESS[|802.11] 17:56:24.852621 436598580174us tsft 1.0 Mb/s -79dB signal -96dB noise antenna 1 [0x0012] Beacon (ConnectionPoint) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] ESS[|802.11] 17:56:24.955019 436598682572us tsft 1.0 Mb/s -80dB signal -96dB noise antenna 1 [0x0012] Beacon (ConnectionPoint) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] ESS[|802.11] ... full log see: http://www.unixarea.de/ath-current.txt If you have the raw pcap capture please provide a url to it. From the log it appears you're sending+receiving wep-encrypted frames. They keyid is the same and since you're receiving frames I have to assume the key matter is correct as otherwise the h/w would drop the frame. You can verify this by feeding the key into wireshark to check if the frame contents make sense. I'm out of ideas. About the only thing I can suggest is you setup a different ap w/ the same wep key and see if things work. If so then you know it's something this ap is doing. I can't recall when I last tested wep on HEAD but I'm pretty sure it works. I will re-test that when I get a chance. Sam ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
Bruce M Simpson wrote: Matthias Apitz wrote: I went today evening with my EeePC and CURRENT on USB key to that Greek restaurant; DHCP does not get IP in CURRENT either; this is somehow good news, isn't it :-) This may be orthogonal, but: A lab colleague and I have been seeing a sporadic problem where the ath0 exhibits the symptoms of being disassociated from its AP. We are running RELENG_7 on the EeePC 701 since the open source HAL merge. In the behaviour we're seeing, we don't see any problem with the initial dhclient run, the ath0 just seems to get disassociated within 5-10 minutes of associating. If we leave 'ping ap-ip-address' running in the background, we don't see this problem. We have yet to produce a tcpdump to catch it 'in the act' and observe the DLT_IEEE80211 traffic when it actually happens, I have only seen the symptoms. The AP does not show the EeePC units as being associated any more at this point, but ath0 still shows 'status: associated'. The AP involved is a Netgear WG602 V2, and is running the vendor's firmware. I'll try to get set up with 'tcpdump -y ieee802_11' from initial boot (including dhcp and anything we bump into). There are many issues with the wireless code in RELENG_7. Now that the hal is merged we can try to address them. Unfortunately the 7.2 release has just begun so it's unclear what we can get in. I'm also limited in what I'm willing to commit given that I do not run RELENG_7. Sam ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
The following reply was made to PR kern/132722; it has been noted by GNATS. From: Sam Leffler s...@freebsd.org To: Matthias Apitz g...@unixarea.de Cc: bug-follo...@freebsd.org, freebsd-net@freebsd.org Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work Date: Mon, 23 Mar 2009 12:12:04 -0700 Matthias Apitz wrote: I went today evening with my EeePC and CURRENT on USB key to that Greek restaurant; DHCP does not get IP in CURRENT either; this is somehow good news, isn't it :-) below are some information concerning the AP, ifconfig ... the output of the tcpdump is on my server as http://www.unixarea.de/ath-current.txt let me know if you need more information; HIH matthias info about AP: Siemens Gigaset SE 505 dsl/cable S30853-S1006-R107-3 (handwritten label says: this is no DSL router; IP 192.168.2.1) as DSL-modem some Fritz!Box is connected to this box http://reviews.cnet.com/routers/siemens-gigaset-se505-dsl/1707-3319_7-30799508.html # uname -a FreeBSD tinyCurrent 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Sun Mar 22 11:47:41 CET 2009 r...@rebelion.sisis.de:/usr/src/myHEAD/obj/usr/src/myHEAD/src/sys/GENERIC i386 # ifconfig -a ath0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 2290 ether 00:15:af:b2:ae:e6 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=3RXCSUM,TXCSUM inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 wlan0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:15:af:b2:ae:e6 inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 media: IEEE 802.11 Wireless Ethernet DS/5.5Mbps mode 11g status: associated ssid ConnectionPoint channel 11 (2462 Mhz 11g) bssid 00:01:e3:0e:97:99 regdomain 96 indoor ecm authmode OPEN privacy ON deftxkey 1 wepkey 1:104-bit txpower 20 bmiss 7 scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme burst roaming MANUAL # tcpdump -n -i ath0 -y IEEE802_11_RADIO 17:56:24.647835 436598375373us tsft 1.0 Mb/s -80dB signal -96dB noise antenna 1 [0x0012] Beacon (ConnectionPoint) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] ESS[|802.11] 17:56:24.750225 43659844us tsft 1.0 Mb/s -81dB signal -96dB noise antenna 1 [0x0012] Beacon (ConnectionPoint) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] ESS[|802.11] 17:56:24.852621 436598580174us tsft 1.0 Mb/s -79dB signal -96dB noise antenna 1 [0x0012] Beacon (ConnectionPoint) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] ESS[|802.11] 17:56:24.955019 436598682572us tsft 1.0 Mb/s -80dB signal -96dB noise antenna 1 [0x0012] Beacon (ConnectionPoint) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] ESS[|802.11] ... full log see: http://www.unixarea.de/ath-current.txt If you have the raw pcap capture please provide a url to it. From the log it appears you're sending+receiving wep-encrypted frames. They keyid is the same and since you're receiving frames I have to assume the key matter is correct as otherwise the h/w would drop the frame. You can verify this by feeding the key into wireshark to check if the frame contents make sense. I'm out of ideas. About the only thing I can suggest is you setup a different ap w/ the same wep key and see if things work. If so then you know it's something this ap is doing. I can't recall when I last tested wep on HEAD but I'm pretty sure it works. I will re-test that when I get a chance. Sam ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
The following reply was made to PR kern/132722; it has been noted by GNATS. From: Matthias Apitz g...@unixarea.de To: bug-follo...@freebsd.org Cc: Sam Leffler s...@freebsd.org, freebsd-net@freebsd.org, Bruce Simpson b...@incunabulum.net, Sean C. Farley s...@freebsd.org Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work Date: Mon, 23 Mar 2009 19:23:11 +0100 I went today evening with my EeePC and CURRENT on USB key to that Greek restaurant; DHCP does not get IP in CURRENT either; this is somehow good news, isn't it :-) below are some information concerning the AP, ifconfig ... the output of the tcpdump is on my server as http://www.unixarea.de/ath-current.txt let me know if you need more information; HIH matthias info about AP: Siemens Gigaset SE 505 dsl/cable S30853-S1006-R107-3 (handwritten label says: this is no DSL router; IP 192.168.2.1) as DSL-modem some Fritz!Box is connected to this box http://reviews.cnet.com/routers/siemens-gigaset-se505-dsl/1707-3319_7-30799508.html # uname -a FreeBSD tinyCurrent 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Sun Mar 22 11:47:41 CET 2009 r...@rebelion.sisis.de:/usr/src/myHEAD/obj/usr/src/myHEAD/src/sys/GENERIC i386 # ifconfig -a ath0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 2290 ether 00:15:af:b2:ae:e6 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=3RXCSUM,TXCSUM inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 wlan0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:15:af:b2:ae:e6 inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 media: IEEE 802.11 Wireless Ethernet DS/5.5Mbps mode 11g status: associated ssid ConnectionPoint channel 11 (2462 Mhz 11g) bssid 00:01:e3:0e:97:99 regdomain 96 indoor ecm authmode OPEN privacy ON deftxkey 1 wepkey 1:104-bit txpower 20 bmiss 7 scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme burst roaming MANUAL # tcpdump -n -i ath0 -y IEEE802_11_RADIO 17:56:24.647835 436598375373us tsft 1.0 Mb/s -80dB signal -96dB noise antenna 1 [0x0012] Beacon (ConnectionPoint) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] ESS[|802.11] 17:56:24.750225 43659844us tsft 1.0 Mb/s -81dB signal -96dB noise antenna 1 [0x0012] Beacon (ConnectionPoint) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] ESS[|802.11] 17:56:24.852621 436598580174us tsft 1.0 Mb/s -79dB signal -96dB noise antenna 1 [0x0012] Beacon (ConnectionPoint) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] ESS[|802.11] 17:56:24.955019 436598682572us tsft 1.0 Mb/s -80dB signal -96dB noise antenna 1 [0x0012] Beacon (ConnectionPoint) [1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 Mbit] ESS[|802.11] ... full log see: http://www.unixarea.de/ath-current.txt ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
On Mon, Mar 23, 2009 at 06:44:42PM +, Bruce M Simpson wrote: Matthias Apitz wrote: I went today evening with my EeePC and CURRENT on USB key to that Greek restaurant; DHCP does not get IP in CURRENT either; this is somehow good news, isn't it :-) This may be orthogonal, but: A lab colleague and I have been seeing a sporadic problem where the ath0 exhibits the symptoms of being disassociated from its AP. We are running RELENG_7 on the EeePC 701 since the open source HAL merge. In the behaviour we're seeing, we don't see any problem with the initial dhclient run, the ath0 just seems to get disassociated within 5-10 minutes of associating. If we leave 'ping ap-ip-address' running in the background, we don't see this problem. I found doing a -bgscan before it happens, make it not happen. I now have -bgscan in my rc.conf. John -- John Hay -- john@meraka.csir.co.za / j...@freebsd.org ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
The following reply was made to PR kern/132722; it has been noted by GNATS. From: John Hay j...@meraka.org.za To: Bruce M Simpson b...@incunabulum.net Cc: Matthias Apitz g...@unixarea.de, freebsd-net@freebsd.org, Sam Leffler s...@freebsd.org, Sean C. Farley s...@freebsd.org, bug-follo...@freebsd.org Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work Date: Mon, 23 Mar 2009 22:40:50 +0200 On Mon, Mar 23, 2009 at 06:44:42PM +, Bruce M Simpson wrote: Matthias Apitz wrote: I went today evening with my EeePC and CURRENT on USB key to that Greek restaurant; DHCP does not get IP in CURRENT either; this is somehow good news, isn't it :-) This may be orthogonal, but: A lab colleague and I have been seeing a sporadic problem where the ath0 exhibits the symptoms of being disassociated from its AP. We are running RELENG_7 on the EeePC 701 since the open source HAL merge. In the behaviour we're seeing, we don't see any problem with the initial dhclient run, the ath0 just seems to get disassociated within 5-10 minutes of associating. If we leave 'ping ap-ip-address' running in the background, we don't see this problem. I found doing a -bgscan before it happens, make it not happen. I now have -bgscan in my rc.conf. John -- John Hay -- john@meraka.csir.co.za / j...@freebsd.org ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
El día Monday, March 23, 2009 a las 12:12:04PM -0700, Sam Leffler escribió:
If you have the raw pcap capture please provide a url to it.
I have to capture it and will provide it;
From the log it appears you're sending+receiving wep-encrypted frames.
They keyid is the same and since you're receiving frames I have to
assume the key matter is correct as otherwise the h/w would drop the
frame. You can verify this by feeding the key into wireshark to check
if the frame contents make sense.
I'm out of ideas. About the only thing I can suggest is you setup a
different ap w/ the same wep key and see if things work. If so then you
know it's something this ap is doing. I can't recall when I last tested
wep on HEAD but I'm pretty sure it works. I will re-test that when I
get a chance.
Sam
WEP in general works; my AP at home is configured as WEP and the entries
in wpa_supplicant.conf are nearly the same, only the key differs:
# my home
#
network={
ssid=tarara
scan_ssid=0
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=xx
}
# Restaurante Odyssee (2007-11-18)
#
network={
ssid=ConnectionPoint
scan_ssid=0
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=
}
but I will configure another AP to also use the same wep_key0, if you
think that the problem could depend on the key itself;
and I will check if I could get somewhere this model of AP for a test;
matthias
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
The following reply was made to PR kern/132722; it has been noted by GNATS.
From: Matthias Apitz g...@unixarea.de
To: Sam Leffler s...@freebsd.org
Cc: bug-follo...@freebsd.org, freebsd-net@freebsd.org
Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or
IP does not work
Date: Mon, 23 Mar 2009 22:42:07 +0100
El día Monday, March 23, 2009 a las 12:12:04PM -0700, Sam Leffler escribió:
If you have the raw pcap capture please provide a url to it.
I have to capture it and will provide it;
From the log it appears you're sending+receiving wep-encrypted frames.
They keyid is the same and since you're receiving frames I have to
assume the key matter is correct as otherwise the h/w would drop the
frame. You can verify this by feeding the key into wireshark to check
if the frame contents make sense.
I'm out of ideas. About the only thing I can suggest is you setup a
different ap w/ the same wep key and see if things work. If so then you
know it's something this ap is doing. I can't recall when I last tested
wep on HEAD but I'm pretty sure it works. I will re-test that when I
get a chance.
Sam
WEP in general works; my AP at home is configured as WEP and the entries
in wpa_supplicant.conf are nearly the same, only the key differs:
# my home
#
network={
ssid=tarara
scan_ssid=0
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=xx
}
# Restaurante Odyssee (2007-11-18)
#
network={
ssid=ConnectionPoint
scan_ssid=0
key_mgmt=NONE
wep_tx_keyidx=0
wep_key0=
}
but I will configure another AP to also use the same wep_key0, if you
think that the problem could depend on the key itself;
and I will check if I could get somewhere this model of AP for a test;
matthias
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
John Hay wrote: I found doing a -bgscan before it happens, make it not happen. I now have -bgscan in my rc.conf. That's exactly the workaround I needed. Thanks John. As Sam points out, the root fix is probably already in HEAD; it would be nice to find time to backport, but this works for us for now as a workaround (we are just using ath0 as a STA for testing in the lab at the moment, it is likely we will use hostap later). cheers, BMS ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
The following reply was made to PR kern/132722; it has been noted by GNATS. From: Bruce M Simpson b...@incunabulum.net To: John Hay j...@meraka.org.za Cc: Matthias Apitz g...@unixarea.de, freebsd-net@freebsd.org, Sam Leffler s...@freebsd.org, Sean C. Farley s...@freebsd.org, bug-follo...@freebsd.org Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work Date: Tue, 24 Mar 2009 01:08:33 + John Hay wrote: I found doing a -bgscan before it happens, make it not happen. I now have -bgscan in my rc.conf. That's exactly the workaround I needed. Thanks John. As Sam points out, the root fix is probably already in HEAD; it would be nice to find time to backport, but this works for us for now as a workaround (we are just using ath0 as a STA for testing in the lab at the moment, it is likely we will use hostap later). cheers, BMS ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
El día Thursday, March 19, 2009 a las 08:44:29AM -0700, Sam Leffler escribió: 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'm going to build a HEAD kernel now with # cd /usr # mv src/sys src/sys.RELENG_7 # setenv CVSROOT :pserver:anon...@anoncvs.tw.freebsd.org:/home/ncvs # cvs checkout src/sys ... I've checked the FreeBSD handbook about SVN / CVS and it reads that all changes in SVN are back ported to CVS trees... just to make sure, is that reality? Thx matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e matthias.ap...@oclc.org - w http://www.oclc.org/ http://www.UnixArea.de/ ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
El día Thursday, March 19, 2009 a las 08:44:29AM -0700, Sam Leffler escribió: Matthias Apitz wrote: 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. What would be the best tool in WinXP to log Wifi traffic, like tcpdump does? I see some 'Tcpdump for Windows' as http://microolap.com/products/network/tcpdump/ but it seems that it does not work for wireless adapters; any hints? matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e matthias.ap...@oclc.org - w http://www.oclc.org/ http://www.UnixArea.de/ ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
Matthias Apitz wrote: El día Thursday, March 19, 2009 a las 08:44:29AM -0700, Sam Leffler escribió: Matthias Apitz wrote: 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. What would be the best tool in WinXP to log Wifi traffic, like tcpdump does? I see some 'Tcpdump for Windows' as http://microolap.com/products/network/tcpdump/ but it seems that it does not work for wireless adapters; any hints? matthias http://www.wireshark.org/download.html -Boris ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
El día Thursday, March 19, 2009 a las 08:44:29AM -0700, Sam Leffler escribió: 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've updated /usr/src/sys to HEAD, configured a kernel based on the new GENERIC (without any changes), compiled it and installed it; the kernel crashes on loading (note: on loading, not on booting): http://www.unixarea.de/trap.jpg i.e. without knowing any inconsistency of user land or file system; what I did wrong? Thx matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e matthias.ap...@oclc.org - w http://www.oclc.org/ http://www.UnixArea.de/ ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
Matthias Apitz wrote: El día Thursday, March 19, 2009 a las 08:44:29AM -0700, Sam Leffler escribió: 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've updated /usr/src/sys to HEAD, configured a kernel based on the new GENERIC (without any changes), compiled it and installed it; the kernel crashes on loading (note: on loading, not on booting): http://www.unixarea.de/trap.jpg i.e. without knowing any inconsistency of user land or file system; what I did wrong? This looks like a longstanding bug in handling modules loaded by loader that have undefined references (e.g. because your kernel is misconfigured). In general I don't think you're going to get very far booting a HEAD kernel against RELENG_7 world. This will certainly not work for wireless where you need all the changes to ifconfig. If you're trying to test HEAD you will want a separate partition with a fresh install/build of HEAD. Sam ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
El día Friday, March 20, 2009 a las 09:06:04AM -0700, Sam Leffler escribió: In general I don't think you're going to get very far booting a HEAD kernel against RELENG_7 world. This will certainly not work for wireless where you need all the changes to ifconfig. If you're trying to test HEAD you will want a separate partition with a fresh install/build of HEAD. Ok, I will prepare a complete build of HEAD in some machine and transfer it to an USB key to boot the EeePC from it; this will take some time; thx matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e matthias.ap...@oclc.org - w http://www.oclc.org/ http://www.UnixArea.de/ ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
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? 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; unfortunately I can't look into the AP about this problem is :-( thx matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e matthias.ap...@oclc.org - w http://www.oclc.org/ http://www.UnixArea.de/ ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
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 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
Old Synopsis: Wifi ath0 associates fine with AP, but DHCP or IP does not work New Synopsis: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work Responsible-Changed-From-To: freebsd-bugs-freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Tue Mar 17 08:21:07 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=132722 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
Hi, Can you please try cvsupping RELENG_7 sources to after this date: %%% Date: Thu Mar 12 03:09:11 2009 New Revision: 189720 URL: http://svn.freebsd.org/changeset/base/189720 %%% The Atheros open source HAL from HEAD was MFC'd and this may or may not fix your problem. thanks, BMS ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
The following reply was made to PR kern/132722; it has been noted by GNATS. From: Bruce Simpson b...@incunabulum.net To: freebsd-gnats-sub...@freebsd.org Cc: lini...@freebsd.org, freebsd-b...@freebsd.org, freebsd-net@FreeBSD.org, Matthias Apitz g...@unixarea.de, Sam Leffler s...@freebsd.org Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work Date: Tue, 17 Mar 2009 08:31:38 + Hi, Can you please try cvsupping RELENG_7 sources to after this date: %%% Date: Thu Mar 12 03:09:11 2009 New Revision: 189720 URL: http://svn.freebsd.org/changeset/base/189720 %%% The Atheros open source HAL from HEAD was MFC'd and this may or may not fix your problem. thanks, BMS ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
The following reply was made to PR kern/132722; it has been noted by GNATS. From: Matthias Apitz g...@unixarea.de To: bug-follo...@freebsd.org, g...@unixarea.de Cc: Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work Date: Tue, 17 Mar 2009 09:42:43 +0100 I forgot to mention that I've applied this patch from Sam to my RELENG_7 kernel: http://article.gmane.org/gmane.os.freebsd.stable/60383/match=cft+ath+hal+src I think, updating to Date: Thu Mar 12 03:09:11 2009 New Revision: 189720 URL: http://svn.freebsd.org/changeset/base/189720 as suggested will not change anything, or I'm wrong? matthias ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
Hi, One crucial piece of info missing is exactly which Atheros part you are using, can you please attach this to the PR? you can get this from pciconf -lv and look for the ath0, also please post your boot time dmesg / or when you insert the part. thanks. Matthias Apitz wrote: The following reply was made to PR kern/132722; it has been noted by GNATS. From: Matthias Apitz g...@unixarea.de To: bug-follo...@freebsd.org, g...@unixarea.de Cc: Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work Date: Tue, 17 Mar 2009 09:42:43 +0100 I forgot to mention that I've applied this patch from Sam to my RELENG_7 kernel: http://article.gmane.org/gmane.os.freebsd.stable/60383/match=cft+ath+hal+src I think, updating to Date: Thu Mar 12 03:09:11 2009 New Revision: 189720 URL: http://svn.freebsd.org/changeset/base/189720 as suggested will not change anything, or I'm wrong? I didn't make many changes apart from fixups in a few files for the diff, so if you're running with the updated HAL, then in theory an svn update/cvsup should make no change. Of course the only way to be sure is to look under the hood. I didn't see any issues with the backported HAL, and I don't really know enough about ath(4) to suggest any workarounds at this point other than reversing your application of the patch, and cvsupping to before the date the patch was MFCed, can we be absolutely sure that the regression you observe happens with the new HAL? Sam would know more, but of course one of the reasons I've taken this on is because a project I'm involved with needs working ath(4) on pci-e in 7.x, I don't know about chip specific problems at this point in time, so I'm just as in the dark as you are! thanks, BMS ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
Matthias Apitz wrote: as requested the output of dmesg(1) and the ath0 related part of 'pciconf -lv'; pls note also that the Wifi works fine in general, i.e. with the AP in my office (WPA) and in my home (WEP); Is this an ASUS Eee PC? If so, which model is it? It looks like a 901. I tested OK with the 701. Sam said that there may be models of ath(4) requiring further changes to be back-ported from -CURRENT, this could well be one of them. cheers BMS ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
The following reply was made to PR kern/132722; it has been noted by GNATS. From: Matthias Apitz g...@unixarea.de To: bug-follo...@freebsd.org Cc: freebsd-net@FreeBSD.org, Bruce Simpson b...@incunabulum.net Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work Date: Tue, 17 Mar 2009 11:36:51 +0100 as requested the output of dmesg(1) and the ath0 related part of 'pciconf -lv'; pls note also that the Wifi works fine in general, i.e. with the AP in my office (WPA) and in my home (WEP); Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-STABLE #1: Tue Mar 10 11:42:48 CET 2009 g...@rebelion.sisis.de:/usr/src/sys/i386/compile/REBELION Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Celeron(R) M processor 900MHz (900.10-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6d8 Stepping = 8 Features=0xafe9fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE AMD Features=0x10NX real memory = 1064828928 (1015 MB) avail memory = 1028284416 (980 MB) ACPI APIC Table: A M I OEMAPIC ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: A M I OEMRSDT on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 3f70 (3) failed Timecounter ACPI-safe frequency 3579545 Hz quality 850 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 acpi_ec0: Embedded Controller: GPE 0x18 port 0x62,0x66 on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 vgapci0: VGA-compatible display port 0xec00-0xec07 mem 0xf7f0-0xf7f7,0xd000-0xdfff,0xf7ec-0xf7ef irq 16 at device 2.0 on pci0 agp0: Intel 82915GM (915GM GMCH) SVGA controller on vgapci0 agp0: detected 7932k stolen memory agp0: aperture size is 256M vgapci1: VGA-compatible display mem 0xf7f8-0xf7ff at device 2.1 on pci0 hdac0: Intel 82801F High Definition Audio Controller mem 0xf7eb8000-0xf7ebbfff irq 16 at device 27.0 on pci0 hdac0: HDA Driver Revision: 20090131_0127 hdac0: [ITHREAD] pcib1: ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0 pci3: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge irq 18 at device 28.2 on pci0 pci1: ACPI PCI bus on pcib2 ath0: Atheros 5424/2424 mem 0xfbff-0xfbff irq 18 at device 0.0 on pci1 ath0: [ITHREAD] ath0: WARNING: using obsoleted if_watchdog interface ath0: Ethernet address: 00:15:af:b2:ae:e6 ath0: mac 14.2 phy 7.0 radio 10.2 uhci0: Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-A port 0xe400-0xe41f irq 23 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-B port 0xe480-0xe49f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-C port 0xe800-0xe81f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-C on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb2 uhub2: 2 ports with 2 removable, self powered uhci3: Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-D port 0xe880-0xe89f irq 16 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb3: Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-D on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb3 uhub3: 2 ports with 2 removable, self powered ehci0: Intel 82801FB (ICH6) USB 2.0 controller mem 0xf7eb7c00-0xf7eb7fff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: Intel 82801FB (ICH6) USB 2.0 controller on ehci0 usb4: USB revision 2.0 uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 on usb4 uhub4: 8 ports with 8 removable, self powered umass0: ENE UB6225, class 0/0, rev 2.00/1.00, addr 2 on uhub4 pcib3: ACPI PCI-PCI bridge at device 30.0 on pci0 pci4: ACPI PCI bus on pcib3 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH6M SATA150 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
The following reply was made to PR kern/132722; it has been noted by GNATS. From: Bruce Simpson b...@incunabulum.net To: Matthias Apitz matthias.ap...@oclc.org Cc: bug-follo...@freebsd.org, freebsd-net@FreeBSD.org Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work Date: Tue, 17 Mar 2009 10:39:32 + Matthias Apitz wrote: as requested the output of dmesg(1) and the ath0 related part of 'pciconf -lv'; pls note also that the Wifi works fine in general, i.e. with the AP in my office (WPA) and in my home (WEP); Is this an ASUS Eee PC? If so, which model is it? It looks like a 901. I tested OK with the 701. Sam said that there may be models of ath(4) requiring further changes to be back-ported from -CURRENT, this could well be one of them. cheers BMS ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
El día Tuesday, March 17, 2009 a las 10:39:32AM +, Bruce Simpson escribió: Matthias Apitz wrote: as requested the output of dmesg(1) and the ath0 related part of 'pciconf -lv'; pls note also that the Wifi works fine in general, i.e. with the AP in my office (WPA) and in my home (WEP); Is this an ASUS Eee PC? If so, which model is it? It looks like a 901. It is an Asus EeePC 900, not the 901. I tested OK with the 701. Sam said that there may be models of ath(4) requiring further changes to be back-ported from -CURRENT, this could well be one of them. as I said the Wifi works in all places, but not with this special AP (while a Nokia cellphone can associate and DHCP without problems); let me know if you need more info; Thx matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e matthias.ap...@oclc.org - w http://www.oclc.org/ http://www.UnixArea.de/ ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
as requested the output of dmesg(1) and the ath0 related part of 'pciconf -lv'; pls note also that the Wifi works fine in general, i.e. with the AP in my office (WPA) and in my home (WEP); Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-STABLE #1: Tue Mar 10 11:42:48 CET 2009 g...@rebelion.sisis.de:/usr/src/sys/i386/compile/REBELION Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Celeron(R) M processor 900MHz (900.10-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6d8 Stepping = 8 Features=0xafe9fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE AMD Features=0x10NX real memory = 1064828928 (1015 MB) avail memory = 1028284416 (980 MB) ACPI APIC Table: A M I OEMAPIC ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: A M I OEMRSDT on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 3f70 (3) failed Timecounter ACPI-safe frequency 3579545 Hz quality 850 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 acpi_ec0: Embedded Controller: GPE 0x18 port 0x62,0x66 on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 vgapci0: VGA-compatible display port 0xec00-0xec07 mem 0xf7f0-0xf7f7,0xd000-0xdfff,0xf7ec-0xf7ef irq 16 at device 2.0 on pci0 agp0: Intel 82915GM (915GM GMCH) SVGA controller on vgapci0 agp0: detected 7932k stolen memory agp0: aperture size is 256M vgapci1: VGA-compatible display mem 0xf7f8-0xf7ff at device 2.1 on pci0 hdac0: Intel 82801F High Definition Audio Controller mem 0xf7eb8000-0xf7ebbfff irq 16 at device 27.0 on pci0 hdac0: HDA Driver Revision: 20090131_0127 hdac0: [ITHREAD] pcib1: ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0 pci3: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge irq 18 at device 28.2 on pci0 pci1: ACPI PCI bus on pcib2 ath0: Atheros 5424/2424 mem 0xfbff-0xfbff irq 18 at device 0.0 on pci1 ath0: [ITHREAD] ath0: WARNING: using obsoleted if_watchdog interface ath0: Ethernet address: 00:15:af:b2:ae:e6 ath0: mac 14.2 phy 7.0 radio 10.2 uhci0: Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-A port 0xe400-0xe41f irq 23 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-B port 0xe480-0xe49f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-C port 0xe800-0xe81f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-C on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb2 uhub2: 2 ports with 2 removable, self powered uhci3: Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-D port 0xe880-0xe89f irq 16 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb3: Intel 82801FB/FR/FW/FRW (ICH6) USB controller USB-D on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb3 uhub3: 2 ports with 2 removable, self powered ehci0: Intel 82801FB (ICH6) USB 2.0 controller mem 0xf7eb7c00-0xf7eb7fff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: Intel 82801FB (ICH6) USB 2.0 controller on ehci0 usb4: USB revision 2.0 uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 on usb4 uhub4: 8 ports with 8 removable, self powered umass0: ENE UB6225, class 0/0, rev 2.00/1.00, addr 2 on uhub4 pcib3: ACPI PCI-PCI bridge at device 30.0 on pci0 pci4: ACPI PCI bus on pcib3 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH6M SATA150 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.2 on pci0 ata0: ATA channel 0 on atapci0 ata0: [ITHREAD] ata1: ATA channel 1 on atapci0 ata1: [ITHREAD] pci0: serial bus, SMBus at device 31.3 (no driver attached) acpi_asus0: ASUS EeePC on acpi0 acpi_lid0: Control Method Lid Switch on acpi0 acpi_button0: Sleep Button on acpi0 acpi_button1: Power Button on acpi0 acpi_tz0: Thermal Zone on acpi0 battery0: ACPI Control Method Battery on acpi0 acpi_acad0: AC Adapter on acpi0
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
The following reply was made to PR kern/132722; it has been noted by GNATS. From: Matthias Apitz g...@unixarea.de To: Bruce Simpson b...@incunabulum.net Cc: Matthias Apitz matthias.ap...@oclc.org, freebsd-net@freebsd.org, bug-follo...@freebsd.org Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work Date: Tue, 17 Mar 2009 11:45:48 +0100 El día Tuesday, March 17, 2009 a las 10:39:32AM +, Bruce Simpson escribió: Matthias Apitz wrote: as requested the output of dmesg(1) and the ath0 related part of 'pciconf -lv'; pls note also that the Wifi works fine in general, i.e. with the AP in my office (WPA) and in my home (WEP); Is this an ASUS Eee PC? If so, which model is it? It looks like a 901. It is an Asus EeePC 900, not the 901. I tested OK with the 701. Sam said that there may be models of ath(4) requiring further changes to be back-ported from -CURRENT, this could well be one of them. as I said the Wifi works in all places, but not with this special AP (while a Nokia cellphone can associate and DHCP without problems); let me know if you need more info; Thx matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e matthias.ap...@oclc.org - w http://www.oclc.org/ http://www.UnixArea.de/ ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
On Tue, 17 Mar 2009, Matthias Apitz wrote: El día Tuesday, March 17, 2009 a las 10:39:32AM +, Bruce Simpson escribió: Matthias Apitz wrote: as requested the output of dmesg(1) and the ath0 related part of 'pciconf -lv'; pls note also that the Wifi works fine in general, i.e. with the AP in my office (WPA) and in my home (WEP); Is this an ASUS Eee PC? If so, which model is it? It looks like a 901. It is an Asus EeePC 900, not the 901. I tested OK with the 701. Sam said that there may be models of ath(4) requiring further changes to be back-ported from -CURRENT, this could well be one of them. as I said the Wifi works in all places, but not with this special AP (while a Nokia cellphone can associate and DHCP without problems); let me know if you need more info; Is the AP made by Aruba Networks? On RELENG_7, I needed a newer version (v0.5.11 instead of v0.5.10) of wpa_supplicant for it to associate correctly. With v0.5.10, I could see DHCP requests from my laptop but no responses. This is the patch I am using currently: http://people.freebsd.org/~scf/wpa_supplicant-0.5.11-RELENG_7.patch Note: sam@ updated HEAD to v0.5.11 then to the v0.6.x series. Sean -- s...@freebsd.org___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
The following reply was made to PR kern/132722; it has been noted by GNATS. From: Sean C. Farley s...@freebsd.org To: Matthias Apitz g...@unixarea.de Cc: Bruce Simpson b...@incunabulum.net, freebsd-net@FreeBSD.org, Matthias Apitz matthias.ap...@oclc.org, bug-follo...@freebsd.org Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work Date: Tue, 17 Mar 2009 11:55:32 -0500 (CDT) This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --56599777-302749604-1237308518=:51892 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8BIT Content-ID: alpine.bsf.2.00.0903171149121.51...@thor.farley.org On Tue, 17 Mar 2009, Matthias Apitz wrote: El día Tuesday, March 17, 2009 a las 10:39:32AM +, Bruce Simpson escribió: Matthias Apitz wrote: as requested the output of dmesg(1) and the ath0 related part of 'pciconf -lv'; pls note also that the Wifi works fine in general, i.e. with the AP in my office (WPA) and in my home (WEP); Is this an ASUS Eee PC? If so, which model is it? It looks like a 901. It is an Asus EeePC 900, not the 901. I tested OK with the 701. Sam said that there may be models of ath(4) requiring further changes to be back-ported from -CURRENT, this could well be one of them. as I said the Wifi works in all places, but not with this special AP (while a Nokia cellphone can associate and DHCP without problems); let me know if you need more info; Is the AP made by Aruba Networks? On RELENG_7, I needed a newer version (v0.5.11 instead of v0.5.10) of wpa_supplicant for it to associate correctly. With v0.5.10, I could see DHCP requests from my laptop but no responses. This is the patch I am using currently: http://people.freebsd.org/~scf/wpa_supplicant-0.5.11-RELENG_7.patch Note: sam@ updated HEAD to v0.5.11 then to the v0.6.x series. Sean -- s...@freebsd.org --56599777-302749604-1237308518=:51892-- ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
Sean C. Farley wrote: On Tue, 17 Mar 2009, Matthias Apitz wrote: El día Tuesday, March 17, 2009 a las 10:39:32AM +, Bruce Simpson escribió: Matthias Apitz wrote: as requested the output of dmesg(1) and the ath0 related part of 'pciconf -lv'; pls note also that the Wifi works fine in general, i.e. with the AP in my office (WPA) and in my home (WEP); Is this an ASUS Eee PC? If so, which model is it? It looks like a 901. It is an Asus EeePC 900, not the 901. I tested OK with the 701. Sam said that there may be models of ath(4) requiring further changes to be back-ported from -CURRENT, this could well be one of them. as I said the Wifi works in all places, but not with this special AP (while a Nokia cellphone can associate and DHCP without problems); let me know if you need more info; Is the AP made by Aruba Networks? On RELENG_7, I needed a newer version (v0.5.11 instead of v0.5.10) of wpa_supplicant for it to associate correctly. With v0.5.10, I could see DHCP requests from my laptop but no responses. This is the patch I am using currently: http://people.freebsd.org/~scf/wpa_supplicant-0.5.11-RELENG_7.patch Note: sam@ updated HEAD to v0.5.11 then to the v0.6.x series. 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. Sam ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work
The following reply was made to PR kern/132722; it has been noted by GNATS. From: Sam Leffler s...@freebsd.org To: Sean C. Farley s...@freebsd.org Cc: Matthias Apitz g...@unixarea.de, Matthias Apitz matthias.ap...@oclc.org, freebsd-net@freebsd.org, Bruce Simpson b...@incunabulum.net, bug-follo...@freebsd.org Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work Date: Tue, 17 Mar 2009 11:56:24 -0700 Sean C. Farley wrote: On Tue, 17 Mar 2009, Matthias Apitz wrote: El día Tuesday, March 17, 2009 a las 10:39:32AM +, Bruce Simpson escribió: Matthias Apitz wrote: as requested the output of dmesg(1) and the ath0 related part of 'pciconf -lv'; pls note also that the Wifi works fine in general, i.e. with the AP in my office (WPA) and in my home (WEP); Is this an ASUS Eee PC? If so, which model is it? It looks like a 901. It is an Asus EeePC 900, not the 901. I tested OK with the 701. Sam said that there may be models of ath(4) requiring further changes to be back-ported from -CURRENT, this could well be one of them. as I said the Wifi works in all places, but not with this special AP (while a Nokia cellphone can associate and DHCP without problems); let me know if you need more info; Is the AP made by Aruba Networks? On RELENG_7, I needed a newer version (v0.5.11 instead of v0.5.10) of wpa_supplicant for it to associate correctly. With v0.5.10, I could see DHCP requests from my laptop but no responses. This is the patch I am using currently: http://people.freebsd.org/~scf/wpa_supplicant-0.5.11-RELENG_7.patch Note: sam@ updated HEAD to v0.5.11 then to the v0.6.x series. 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. Sam ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
