Re: Problems with Atheros card and hostpd
Hello Sam, Sunday, December 27, 2009, 4:55:12 PM, you wrote: >> I think I was the only one in thread who used FreeBSD as an AP, also >> that was before 7.x when I made the log. So I'm not saying it's >> FreeBSD specific problem, I don't even think it's a BSD problem, but >> perhaps some kind of incompatibility and I was hoping for some >> workaround. > AP mode power save was broken for a time in 7.x (IIRC the aging of > frames on the PS q was incorrectly calculated causing them to be tossed > prematurely)--but that was unrelated to WME/WMM. Well, it's possible that when I disabled WME/WMM on android it stopped using power save at all... The behavior was similar to the one you described. It was throwing out packets claiming those were too old, but it worked fine with Linux. I think I already provided the link, but in case I didn't, this is the log that I captured when I was looking for the issue (it's power save debug messages that you mentioned): https://supportforums.motorola.com/message/87903#87903 Does it look ok? How long the packets supposed to be hold before being discarded? I think I should still have logs collected using kismet... > Can't even guess w/o a packet trace and/or debug log. WME should be > immaterial to FreeBSD unless crypto was involved in which case you > might've hit a bug w/ h/w crypto+WME that's long since been fixed > (certain ath parts require the MIC be handled in s/w when WME is used). > The best thing to do wrt FreeBSD is run 8.0 or later for much better > wireless support. Well right now, I can't reproduce the issue anymore. I just tried it; I removed the access point completely, restarted the phone, and hostapd but it still works. Anyway, between my initial post and now I actually upgraded to 8.0 so that could be it, though it puzzles me that linux with power saving enabled worked fine with 7.x (I think it was 7.1) Actually, the reason why I even mentioned the WME is that I observed it working at the time I disabled it on the phone, also what made me experiment with it was post of another person who claimed it fixed his issue which seemed identical to mine (he used a hardware AP though). It's also possible that disables WME on android completely disables power savings. It's possible it could be just a coincidence. I updated to 8.0 around the same time (well actually I tried the WME actually before the upgrade), but it's possible that after I switched it back it continued to work because 8.0 doesn't have the issue anymore? One question, any idea if FreeBSD code could be in HP AP 420 and some other APs? This is the post of the guy that actually made me experiment with WME: https://supportforums.motorola.com/message/88983#88983 -- Best regards, Derekmailto:tak...@takeda.tk Men are from Mars. Women are from Venus. Computers are from hell. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problems with Atheros card and hostpd
Derek Kulinski wrote: Hello Sam, Sunday, December 27, 2009, 12:05:34 PM, you wrote: I didn't see anything in the thread to point a finger at freebsd but given the debug msg log shows "ath0" instead of "wlan0" I'm guessing whatever version was being used was pre-8.x. I think I was the only one in thread who used FreeBSD as an AP, also that was before 7.x when I made the log. So I'm not saying it's FreeBSD specific problem, I don't even think it's a BSD problem, but perhaps some kind of incompatibility and I was hoping for some workaround. AP mode power save was broken for a time in 7.x (IIRC the aging of frames on the PS q was incorrectly calculated causing them to be tossed prematurely)--but that was unrelated to WME/WMM. Unlikely. Try collecting a packet trace of a failure w/ wireshark or tcpdump from a 3rd sta and send it to me. Be sure to collect data at the 802.11 layer (e.g. -y IEEE802_11_RADIO). You might also learn something by enabling power save debug msgs on the ap w/ wlandebug. Well, I actually managed it to work. Since the phone was rooted I changed settings and disabled WME on the phone. I associated it and it worked. Now there's a weird thing that I don't really get. After I saw that phone was working with WME disabled, I went back and changed it to the way it originally was, I also restarted the phone. To my surprise the phone continued to work (with WME enabled), and I still don't understand why. Perhaps it stored some information necessary? I think I'll deassociate the phone and make it forget the AP and see if it works. Can't even guess w/o a packet trace and/or debug log. WME should be immaterial to FreeBSD unless crypto was involved in which case you might've hit a bug w/ h/w crypto+WME that's long since been fixed (certain ath parts require the MIC be handled in s/w when WME is used). The best thing to do wrt FreeBSD is run 8.0 or later for much better wireless support. Sam ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problems with Atheros card and hostpd
Hello Sam, Sunday, December 27, 2009, 12:05:34 PM, you wrote: > I didn't see anything in the thread to point a finger at freebsd but > given the debug msg log shows "ath0" instead of "wlan0" I'm guessing > whatever version was being used was pre-8.x. I think I was the only one in thread who used FreeBSD as an AP, also that was before 7.x when I made the log. So I'm not saying it's FreeBSD specific problem, I don't even think it's a BSD problem, but perhaps some kind of incompatibility and I was hoping for some workaround. > Unlikely. Try collecting a packet trace of a failure w/ wireshark or > tcpdump from a 3rd sta and send it to me. Be sure to collect data at > the 802.11 layer (e.g. -y IEEE802_11_RADIO). You might also learn > something by enabling power save debug msgs on the ap w/ wlandebug. Well, I actually managed it to work. Since the phone was rooted I changed settings and disabled WME on the phone. I associated it and it worked. Now there's a weird thing that I don't really get. After I saw that phone was working with WME disabled, I went back and changed it to the way it originally was, I also restarted the phone. To my surprise the phone continued to work (with WME enabled), and I still don't understand why. Perhaps it stored some information necessary? I think I'll deassociate the phone and make it forget the AP and see if it works. -- Best regards, Derekmailto:tak...@takeda.tk You know it's love when you memorize her IP number to skip DNS overhead ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problems with Atheros card and hostpd
Derek Kulinski wrote: > Hello Boris, > > I checked the handbook, UPDATING, and nothing mentioned this thing, > why? I would think I'm not the only one with this problem, or am I? > > Anyway it seems to work, I'm getting: > Starting hostapd. > Configuration file: /etc/hostapd.conf > wlan0: IEEE 802.11 Fetching hardware channel/rate support not supported. > Using interface wlan0 with hwaddr 00:11:95:e5:70:df and ssid 'mayumi-ap' > > Is it something I should worry about? No. hostapd collects channel/rate information for functionality that is linux-specific. On freebsd hostapd is used purely as an authenticator. > Also how to create wlan device by hand? "ifconfig ath0 wlandev wlan0" > doesn't seem to work. > > What initially was worrying me was this: >>> ath0: mem 0xf400-0xf400 irq 3 at device 11.0 on pci0 >>> ath0: [ITHREAD] >>> ath0: AR2413 mac 7.9 RF2413 phy 4.5 > > I thought that ath0 was using a different driver than it supposed to. > > There's one more question, though not related to this problem. > I have an android phone, and it doesn't seem to work with my FreeBSD > AP, while it works on others. After sniffing the traffic, it looks > like it is a power management issue: > https://supportforums.motorola.com/message/87903#87903 I didn't see anything in the thread to point a finger at freebsd but given the debug msg log shows "ath0" instead of "wlan0" I'm guessing whatever version was being used was pre-8.x. > > Someone traced the problem to WME/WMM in his case. I don't know if > that's the case for me yet, I tried to disable/enable wme on the AP > but it doesn't seem to do anything. Is it possible that I might fix it > by enabling some option? Unlikely. Try collecting a packet trace of a failure w/ wireshark or tcpdump from a 3rd sta and send it to me. Be sure to collect data at the 802.11 layer (e.g. -y IEEE802_11_RADIO). You might also learn something by enabling power save debug msgs on the ap w/ wlandebug. > > Anyway, thanks for everyone who helped me fix the initial issue. > > Derek > > > Wednesday, December 16, 2009, 4:28:49 AM, you wrote: > >> Multi-BSS support in 8.0 means that you first need to create a wlan >> pseudo-device, and run hostapd with that. The rc.conf lines look like this: > >> wlans_ath0="wlan0" >> create_args_wlan0="wlanmode hostap" >> ifconfig_wlan0="ssid networkname media autoselect up" > >> -Boris > >> Derek Kulinski wrote: >>> Hello, >>> >>> I just upgraded my access point (from 7.1 to 8.0) and can't make >>> hostapd work (looks like wide-dhcp relay also has a problem with ath0): >>> >>> [mayumi]:/root# hostapd -P /var/run/hostapd.pid -dd /etc/hostapd.conf >>> Configuration file: /etc/hostapd.conf >>> Line 2: DEPRECATED: 'debug' configuration variable is not used anymore >>> ctrl_interface_group=0 (from group name 'wheel') >>> pcap_open_live: >>> ifname='ath0' >>> bsd driver initialization failed. >>> ath0: Unable to setup interface. >>> rmdir[ctrl_interface]: No such file or directory >>> Exit 255 >>> >>> Output from dmesg: >>> ath0: mem 0xf400-0xf400 irq 3 at device 11.0 on pci0 >>> ath0: [ITHREAD] >>> ath0: AR2413 mac 7.9 RF2413 phy 4.5 >>> >>> The interface seems to exist, but seems it lost some of its >>> functionality: >>> [mayumi]:/root# ifconfig ath0 >>> ath0: flags=8843 metric 0 mtu 2290 >>> ether 00:11:95:e5:70:df >>> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) >>> status: no carrier >>> [mayumi]:/root# ifconfig ath0 list cap >>> ifconfig: Don't know how to list cap for ath0 >>> >>> What's going on? The card worked pretty well with 7.1. >>> >>> I tried to compile kernel just with "device ath_ar5212" >>> but I'm only getting this: >>> >>> ah.o(.text+0x212): In function `ath_hal_rfprobe': >>> /usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference to >>> `__start_set_ah_rfs' >>> ah.o(.text+0x21f):/usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined >>> reference to `__stop_set_ah_rfs' >>> ah.o(.text+0x235):/usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined >>> reference to `__stop_set_ah_rfs' >>> >>> > > > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problems with Atheros card and hostpd
Hello Boris, Wednesday, December 16, 2009, 5:18:57 PM, you wrote: > 20080420: > The 802.11 wireless support was redone to enable multi-bss > operation on devices that are capable. The underlying device > is no longer used directly but instead wlanX devices are > cloned with ifconfig. This requires changes to rc.conf files. > For example, change: > ifconfig_ath0="WPA DHCP" > to > wlans_ath0=wlan0 > ifconfig_wlan0="WPA DHCP" > see rc.conf(5) for more details. In addition, mergemaster of > /etc/rc.d is highly recommended. Simultaneous update of userland > and kernel wouldn't hurt either. > As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta > modules were merged into the base wlan module. All references > to these modules (e.g. in kernel config files) must be removed. Ok, now I'm quite embarrassed =) Anyway, thanks for your help. -- Best regards, Derekmailto:tak...@takeda.tk The great thing about Object Oriented code is that it can make small, simple problems look like large, complex ones. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problems with Atheros card and hostpd
Derek Kulinski wrote: Hello Boris, I checked the handbook, UPDATING, and nothing mentioned this thing, why? I would think I'm not the only one with this problem, or am I? Well, I learned about it because I follow the -current@ and -net@ mailing lists, but there is at least some mention of it in /usr/src/UPDATING: 20080420: The 802.11 wireless support was redone to enable multi-bss operation on devices that are capable. The underlying device is no longer used directly but instead wlanX devices are cloned with ifconfig. This requires changes to rc.conf files. For example, change: ifconfig_ath0="WPA DHCP" to wlans_ath0=wlan0 ifconfig_wlan0="WPA DHCP" see rc.conf(5) for more details. In addition, mergemaster of /etc/rc.d is highly recommended. Simultaneous update of userland and kernel wouldn't hurt either. As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta modules were merged into the base wlan module. All references to these modules (e.g. in kernel config files) must be removed. Anyway it seems to work, I'm getting: Starting hostapd. Configuration file: /etc/hostapd.conf wlan0: IEEE 802.11 Fetching hardware channel/rate support not supported. Using interface wlan0 with hwaddr 00:11:95:e5:70:df and ssid 'mayumi-ap' Is it something I should worry about? I don't think so. The same thing happens on my access points. It looks like the channel and rate remain properties of the underlying device, which makes sense, since all wlan pseudo-devices use the same channel and rate. Also how to create wlan device by hand? "ifconfig ath0 wlandev wlan0" doesn't seem to work. What initially was worrying me was this: ath0: mem 0xf400-0xf400 irq 3 at device 11.0 on pci0 ath0: [ITHREAD] ath0: AR2413 mac 7.9 RF2413 phy 4.5 I thought that ath0 was using a different driver than it supposed to. There's one more question, though not related to this problem. I have an android phone, and it doesn't seem to work with my FreeBSD AP, while it works on others. After sniffing the traffic, it looks like it is a power management issue: https://supportforums.motorola.com/message/87903#87903 Someone traced the problem to WME/WMM in his case. I don't know if that's the case for me yet, I tried to disable/enable wme on the AP but it doesn't seem to do anything. Is it possible that I might fix it by enabling some option? Don't know anything about this, I'm afraid. Anyway, thanks for everyone who helped me fix the initial issue. Derek Wednesday, December 16, 2009, 4:28:49 AM, you wrote: Multi-BSS support in 8.0 means that you first need to create a wlan pseudo-device, and run hostapd with that. The rc.conf lines look like this: wlans_ath0="wlan0" create_args_wlan0="wlanmode hostap" ifconfig_wlan0="ssid networkname media autoselect up" -Boris Derek Kulinski wrote: Hello, I just upgraded my access point (from 7.1 to 8.0) and can't make hostapd work (looks like wide-dhcp relay also has a problem with ath0): [mayumi]:/root# hostapd -P /var/run/hostapd.pid -dd /etc/hostapd.conf Configuration file: /etc/hostapd.conf Line 2: DEPRECATED: 'debug' configuration variable is not used anymore ctrl_interface_group=0 (from group name 'wheel') pcap_open_live: ifname='ath0' bsd driver initialization failed. ath0: Unable to setup interface. rmdir[ctrl_interface]: No such file or directory Exit 255 Output from dmesg: ath0: mem 0xf400-0xf400 irq 3 at device 11.0 on pci0 ath0: [ITHREAD] ath0: AR2413 mac 7.9 RF2413 phy 4.5 The interface seems to exist, but seems it lost some of its functionality: [mayumi]:/root# ifconfig ath0 ath0: flags=8843 metric 0 mtu 2290 ether 00:11:95:e5:70:df media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier [mayumi]:/root# ifconfig ath0 list cap ifconfig: Don't know how to list cap for ath0 What's going on? The card worked pretty well with 7.1. I tried to compile kernel just with "device ath_ar5212" but I'm only getting this: ah.o(.text+0x212): In function `ath_hal_rfprobe': /usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference to `__start_set_ah_rfs' ah.o(.text+0x21f):/usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference to `__stop_set_ah_rfs' ah.o(.text+0x235):/usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference to `__stop_set_ah_rfs' ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problems with Atheros card and hostpd
On Wednesday 16 December 2009 01:39:25 pm Derek Kulinski wrote: > Also how to create wlan device by hand? "ifconfig ath0 wlandev wlan0" > doesn't seem to work. You have it backwards. It should be: ifconfig wlan0 create wlandev ath0 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problems with Atheros card and hostpd
Hello Boris, I checked the handbook, UPDATING, and nothing mentioned this thing, why? I would think I'm not the only one with this problem, or am I? Anyway it seems to work, I'm getting: Starting hostapd. Configuration file: /etc/hostapd.conf wlan0: IEEE 802.11 Fetching hardware channel/rate support not supported. Using interface wlan0 with hwaddr 00:11:95:e5:70:df and ssid 'mayumi-ap' Is it something I should worry about? Also how to create wlan device by hand? "ifconfig ath0 wlandev wlan0" doesn't seem to work. What initially was worrying me was this: >> ath0: mem 0xf400-0xf400 irq 3 at device 11.0 on pci0 >> ath0: [ITHREAD] >> ath0: AR2413 mac 7.9 RF2413 phy 4.5 I thought that ath0 was using a different driver than it supposed to. There's one more question, though not related to this problem. I have an android phone, and it doesn't seem to work with my FreeBSD AP, while it works on others. After sniffing the traffic, it looks like it is a power management issue: https://supportforums.motorola.com/message/87903#87903 Someone traced the problem to WME/WMM in his case. I don't know if that's the case for me yet, I tried to disable/enable wme on the AP but it doesn't seem to do anything. Is it possible that I might fix it by enabling some option? Anyway, thanks for everyone who helped me fix the initial issue. Derek Wednesday, December 16, 2009, 4:28:49 AM, you wrote: > Multi-BSS support in 8.0 means that you first need to create a wlan > pseudo-device, and run hostapd with that. The rc.conf lines look like this: > wlans_ath0="wlan0" > create_args_wlan0="wlanmode hostap" > ifconfig_wlan0="ssid networkname media autoselect up" > -Boris > Derek Kulinski wrote: >> Hello, >> >> I just upgraded my access point (from 7.1 to 8.0) and can't make >> hostapd work (looks like wide-dhcp relay also has a problem with ath0): >> >> [mayumi]:/root# hostapd -P /var/run/hostapd.pid -dd /etc/hostapd.conf >> Configuration file: /etc/hostapd.conf >> Line 2: DEPRECATED: 'debug' configuration variable is not used anymore >> ctrl_interface_group=0 (from group name 'wheel') >> pcap_open_live: >> ifname='ath0' >> bsd driver initialization failed. >> ath0: Unable to setup interface. >> rmdir[ctrl_interface]: No such file or directory >> Exit 255 >> >> Output from dmesg: >> ath0: mem 0xf400-0xf400 irq 3 at device 11.0 on pci0 >> ath0: [ITHREAD] >> ath0: AR2413 mac 7.9 RF2413 phy 4.5 >> >> The interface seems to exist, but seems it lost some of its >> functionality: >> [mayumi]:/root# ifconfig ath0 >> ath0: flags=8843 metric 0 mtu 2290 >> ether 00:11:95:e5:70:df >> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) >> status: no carrier >> [mayumi]:/root# ifconfig ath0 list cap >> ifconfig: Don't know how to list cap for ath0 >> >> What's going on? The card worked pretty well with 7.1. >> >> I tried to compile kernel just with "device ath_ar5212" >> but I'm only getting this: >> >> ah.o(.text+0x212): In function `ath_hal_rfprobe': >> /usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference to >> `__start_set_ah_rfs' >> ah.o(.text+0x21f):/usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference >> to `__stop_set_ah_rfs' >> ah.o(.text+0x235):/usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference >> to `__stop_set_ah_rfs' >> >> -- Best regards, Derekmailto:tak...@takeda.tk -- I can see clearly now, the brain is gone... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problems with Atheros card and hostpd
On Wed, 2009-12-16 at 03:19 -0800, Derek Kulinski wrote: > Hello, > > I just upgraded my access point (from 7.1 to 8.0) and can't make > hostapd work (looks like wide-dhcp relay also has a problem with ath0): > The ifconfig usage changed in 8.0 The Handbook is not correct: http://www.freebsd.org/doc/en/books/handbook/network-wireless.html see: http://forums.freebsd.org/showthread.php?t=8784 and a small tutorial from my hand: http://martenvijn.nl/trac/wiki/ap may show usefull command and config for you. Here: http://www.freebsd.org/doc/en/books/handbook/network-wireless.html the Handbook is not correct... I hope this helps, cheers, Marten > [mayumi]:/root# hostapd -P /var/run/hostapd.pid -dd /etc/hostapd.conf > Configuration file: /etc/hostapd.conf > Line 2: DEPRECATED: 'debug' configuration variable is not used anymore > ctrl_interface_group=0 (from group name 'wheel') > pcap_open_live: > ifname='ath0' > bsd driver initialization failed. > ath0: Unable to setup interface. > rmdir[ctrl_interface]: No such file or directory > Exit 255 > > Output from dmesg: > ath0: mem 0xf400-0xf400 irq 3 at device 11.0 on pci0 > ath0: [ITHREAD] > ath0: AR2413 mac 7.9 RF2413 phy 4.5 > > The interface seems to exist, but seems it lost some of its > functionality: > [mayumi]:/root# ifconfig ath0 > ath0: flags=8843 metric 0 mtu 2290 > ether 00:11:95:e5:70:df > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > [mayumi]:/root# ifconfig ath0 list cap > ifconfig: Don't know how to list cap for ath0 > > What's going on? The card worked pretty well with 7.1. > > I tried to compile kernel just with "device ath_ar5212" > but I'm only getting this: > > ah.o(.text+0x212): In function `ath_hal_rfprobe': > /usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference to > `__start_set_ah_rfs' > ah.o(.text+0x21f):/usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference > to `__stop_set_ah_rfs' > ah.o(.text+0x235):/usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference > to `__stop_set_ah_rfs' > -- Marten Vijn linux 2.0.18 OpenBSD 3.6 FreeBSD 4.6 http://martenvijn.nl http://opencommunitycamp.org http://wifisoft.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problems with Atheros card and hostpd
Am 16.12.2009 um 12:19 schrieb Derek Kulinski: Hello, I just upgraded my access point (from 7.1 to 8.0) and can't make hostapd work (looks like wide-dhcp relay also has a problem with ath0): Things got a bit more complicated (and more powerful) with 8.0: you now have to configure a virtual wireless interface, attached to the physical one. Unfortunatly, the handbook has not quite caught up with this change. Stefan -- Stefan BethkeFon +49 151 14070811 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problems with Atheros card and hostpd
Multi-BSS support in 8.0 means that you first need to create a wlan pseudo-device, and run hostapd with that. The rc.conf lines look like this: wlans_ath0="wlan0" create_args_wlan0="wlanmode hostap" ifconfig_wlan0="ssid networkname media autoselect up" -Boris Derek Kulinski wrote: Hello, I just upgraded my access point (from 7.1 to 8.0) and can't make hostapd work (looks like wide-dhcp relay also has a problem with ath0): [mayumi]:/root# hostapd -P /var/run/hostapd.pid -dd /etc/hostapd.conf Configuration file: /etc/hostapd.conf Line 2: DEPRECATED: 'debug' configuration variable is not used anymore ctrl_interface_group=0 (from group name 'wheel') pcap_open_live: ifname='ath0' bsd driver initialization failed. ath0: Unable to setup interface. rmdir[ctrl_interface]: No such file or directory Exit 255 Output from dmesg: ath0: mem 0xf400-0xf400 irq 3 at device 11.0 on pci0 ath0: [ITHREAD] ath0: AR2413 mac 7.9 RF2413 phy 4.5 The interface seems to exist, but seems it lost some of its functionality: [mayumi]:/root# ifconfig ath0 ath0: flags=8843 metric 0 mtu 2290 ether 00:11:95:e5:70:df media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier [mayumi]:/root# ifconfig ath0 list cap ifconfig: Don't know how to list cap for ath0 What's going on? The card worked pretty well with 7.1. I tried to compile kernel just with "device ath_ar5212" but I'm only getting this: ah.o(.text+0x212): In function `ath_hal_rfprobe': /usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference to `__start_set_ah_rfs' ah.o(.text+0x21f):/usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference to `__stop_set_ah_rfs' ah.o(.text+0x235):/usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference to `__stop_set_ah_rfs' ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Problems with Atheros card and hostpd
Hello, I just upgraded my access point (from 7.1 to 8.0) and can't make hostapd work (looks like wide-dhcp relay also has a problem with ath0): [mayumi]:/root# hostapd -P /var/run/hostapd.pid -dd /etc/hostapd.conf Configuration file: /etc/hostapd.conf Line 2: DEPRECATED: 'debug' configuration variable is not used anymore ctrl_interface_group=0 (from group name 'wheel') pcap_open_live: ifname='ath0' bsd driver initialization failed. ath0: Unable to setup interface. rmdir[ctrl_interface]: No such file or directory Exit 255 Output from dmesg: ath0: mem 0xf400-0xf400 irq 3 at device 11.0 on pci0 ath0: [ITHREAD] ath0: AR2413 mac 7.9 RF2413 phy 4.5 The interface seems to exist, but seems it lost some of its functionality: [mayumi]:/root# ifconfig ath0 ath0: flags=8843 metric 0 mtu 2290 ether 00:11:95:e5:70:df media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier [mayumi]:/root# ifconfig ath0 list cap ifconfig: Don't know how to list cap for ath0 What's going on? The card worked pretty well with 7.1. I tried to compile kernel just with "device ath_ar5212" but I'm only getting this: ah.o(.text+0x212): In function `ath_hal_rfprobe': /usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference to `__start_set_ah_rfs' ah.o(.text+0x21f):/usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference to `__stop_set_ah_rfs' ah.o(.text+0x235):/usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference to `__stop_set_ah_rfs' -- Best regards, Derek mailto:tak...@takeda.tk Wear short sleeves! Support your right to bare arms! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
