Re: FreeBSD-8.0 802.11n support with ath/mwl
Jim Pingle wrote: On 2/28/2010 10:16 PM, Rui Paulo wrote: On 1 Mar 2010, at 03:05, Jim Pingle wrote: On 2/28/2010 9:41 PM, Rui Paulo wrote: On 1 Mar 2010, at 02:26, Jim Pingle wrote: Ah, I wasn't aware of wlandebug(8). However, it doesn't seem to operate on this mwl(4) card. It sets the value of the sysctl net.wlan.0.debug and that doesn't show up on my system. Another system with a ral(4) card does have that sysctl. Judging by the information in the wlandebug(8) man page it appears as though this may be a side effect of mwl doing much of the work in firmware. wlandebug takes an -i argument. I seem to recall you created your wlan interface named mwl_wlan0, so you need to type wlandebug -i mwl_wlan0. I saw that, but that is hardcoded to expect wlanx (wlan0, wlan1, etc) for an interface name. Having seen that, I recompiled wlandebug without the hardcoded interface name check and it didn't work either, but it did toss an error for the sysctl it was trying to tweak. The whole system was designed for the interfaces to start with wlan and be named wlansomething. It does certainly seem to lean that way. Personally I prefer to keep the hardware name in there, but I wasn't aware that would cause other issues. Especially when VAPs come into play, I'd rather have, for example, mwl0_wlan1, mwl0_wlan2, ath0_wlan0, etc, so I can better tie what goes where. But that's more of a bikeshed of personal preference. :-) Not following the wlanX naming convention will cause confusion for things like rc config files (I believe). Definitely any tool I touched expects vap's to be named wlanX. sysctl net.wlan.X.%parent gives the parent ifnet of a vap; I've considered many times including this in the ifconfig status. Feel free to offer a patch that does this. That made me look deeper at the code and see it was really just setting the debug sysctl based on flags that wlandebug was aware of. Handy, but the same thing could be done by hand with sysctl and some bitwise math in a pinch, assuming the interface has the right oids. (Which mine doesn't, for some reason...) The purpose of wlandebug is to not do any math by hand. Indeed, You're 110% right on that. I was just trying to work around the other issues I was seeing to get to the root of the issue, which seems to be the missing sysctl oid. I need to run some more tests and straighten my antenna issues out, but I'll report what I find back to the list in a few days. mwl 11n support broke sometime near the last firmware update and I never fixed it. I know in particular there are issues with AMPDU and seq#'s but possible other things too. The fw is rather finicky in how state is managed and it's likely the host is not in sync causing problems w/ the ampdu support and rate control algorithm that both operate in the fw. You should be able to get 100 Mb/s througput on an HT40 channel but I think I was seeing more like 35-40. Turning off ampdu is usually helpful to stabilize operation. 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: FreeBSD-8.0 802.11n support with ath/mwl
On 3/7/2010 3:34 PM, Sam Leffler wrote: Not following the wlanX naming convention will cause confusion for things like rc config files (I believe). Definitely any tool I touched expects vap's to be named wlanX. Duly noted. I wasn't aware of just how many issues would arise from straying from that convention. sysctl net.wlan.X.%parent gives the parent ifnet of a vap; I've considered many times including this in the ifconfig status. Feel free to offer a patch that does this. That may be handy in the future. My C skills are a bit rusty but if I decide to go down that road I'll surely share any patches I might come up with. mwl 11n support broke sometime near the last firmware update and I never fixed it. I know in particular there are issues with AMPDU and seq#'s but possible other things too. The fw is rather finicky in how state is managed and it's likely the host is not in sync causing problems w/ the ampdu support and rate control algorithm that both operate in the fw. You should be able to get 100 Mb/s througput on an HT40 channel but I think I was seeing more like 35-40. Turning off ampdu is usually helpful to stabilize operation. I'll have to try that next chance I get. I did manage to get more antenna pigtails and now have a total of three attached, but it didn't make a difference. A colleague was able to get an N rate association on his mwl card (108Mbps) with similar settings to mine, but with a different client card. It would seem that the problem may lie in the client card in my case, so I'm also investigating options there at the moment. It's an Intel ABGN 5100 card, in case anyone wonders. I also found the mwlstats and mwldebug programs which are in the src tree but not built with the system. A simple cd /usr/src/tools/tools/mwl; make all install built them, but mwldebug didn't seem to work for me. Looking at the code I just need to build a kernel or module while having MWL_DEBUG defined to get the sysctls to show up, but I have not yet tried that as I've had a fairly busy week. I'll see if changing the ampdu settings make any difference and report back, and hopefully the rebuild with MWL_DEBUG might also help me get a lead if tweaking ampdu doesn't help. Thanks for the reply, Sam. I appreciate the insight. Jim ___ 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: FreeBSD-8.0 802.11n support with ath/mwl
On 28 Feb 2010, at 03:22, Jim Pingle wrote: On 2/27/2010 9:09 PM, Rui Paulo wrote: On 27 Feb 2010, at 20:29, Robert Watson wrote: Progress on supporting 11n with atheros cards is on going. There's much more to it than adapting the rate control algorithm. Please stay tuned. Are you aware if similar work ongoing for the mwl(4) based 802.11n cards? I picked up a couple cheap this past week and have them working with hostapd but, as with the OP in the thread, only with G rates. The ifconfig[1] output suggests that it is using 40MHz wide ht channels but devices only associate at 54Mbps[2]. Jim [1] ifconfig mwl0_wlan1 mwl0_wlan1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:01:36:17:96:0e inet6 fe80::201:36ff:fe17:960e%mwl0_wlan1 prefixlen 64 scopeid 0x9 inet 192.168.15.1 netmask 0xff00 broadcast 192.168.15.255 nd6 options=3PERFORMNUD,ACCEPT_RTADV media: IEEE 802.11 Wireless Ethernet autoselect mode 11na hostap status: running ssid WatchTower channel 100 (5500 MHz 11a ht/40+) bssid 00:01:36:17:96:0e regdomain DEBUG indoor authmode WPA2/802.11i privacy MIXED deftxkey 3 AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 14 scanvalid 60 ampdulimit 64k ampdudensity 4 shortgi smps burst dtimperiod 1 [2] ifconfig mwl0_wlan1 list sta (w/addr removed) AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 1 120 54M 33.00 1537 25952 EP A RSN (rssi 68:20:20 nf 0:0:0) mwl supports HT rates, but it looks like your AP is not sending HT rates to you. -- Rui Paulo ___ 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: FreeBSD-8.0 802.11n support with ath/mwl
On 2/28/2010 7:54 AM, Rui Paulo wrote: On 28 Feb 2010, at 03:22, Jim Pingle wrote: Are you aware if similar work ongoing for the mwl(4) based 802.11n cards? I picked up a couple cheap this past week and have them working with hostapd but, as with the OP in the thread, only with G rates. The ifconfig[1] output suggests that it is using 40MHz wide ht channels but devices only associate at 54Mbps[2]. Jim [1] ifconfig mwl0_wlan1 mwl0_wlan1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:01:36:17:96:0e inet6 fe80::201:36ff:fe17:960e%mwl0_wlan1 prefixlen 64 scopeid 0x9 inet 192.168.15.1 netmask 0xff00 broadcast 192.168.15.255 nd6 options=3PERFORMNUD,ACCEPT_RTADV media: IEEE 802.11 Wireless Ethernet autoselect mode 11na hostap status: running ssid WatchTower channel 100 (5500 MHz 11a ht/40+) bssid 00:01:36:17:96:0e regdomain DEBUG indoor authmode WPA2/802.11i privacy MIXED deftxkey 3 AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 14 scanvalid 60 ampdulimit 64k ampdudensity 4 shortgi smps burst dtimperiod 1 [2] ifconfig mwl0_wlan1 list sta (w/addr removed) AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 1 120 54M 33.00 1537 25952 EP A RSN (rssi 68:20:20 nf 0:0:0) mwl supports HT rates, but it looks like your AP is not sending HT rates to you. Thanks for the quick clarification, that's very encouraging to find out! In this case, the mwl card is the AP. The client line is from an associated Windows 7 laptop with an Intel 5100abgn card which does show the AP as 802.11n in the AP list. I'm connected and sending this message through it right now, actually. Are there some other bits that need set in order to have clients associate with HT rates? Or some other prerequisite conditions such as number of attached antennae? I do only have one antenna attached as I didn't have a second pigtail for this test unit's case. The card actually has three connectors. I didn't see hints in the mwl(4), wlan(4), hostapd(8), hostapd.conf(5), or ifconfig(8) man pages about troubleshooting rates. I see plenty of talk in ifconfig(8) about use and control of HT rates, but given what I'm seeing in ifconfig, it should be set to use them. I've tried several combinations of channels and standards (e.g. 11ng, 11na) but always end up with a 54Mbps link. I'd appreciate any more pointers that you (or anyone else reading) may have. I'd like to write up something on the topic once I get it fully operational. Thanks, Jim ___ 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: FreeBSD-8.0 802.11n support with ath/mwl
On Sun, Feb 28, 2010 at 12:38:19PM -0500, Jim Pingle wrote: On 2/28/2010 7:54 AM, Rui Paulo wrote: On 28 Feb 2010, at 03:22, Jim Pingle wrote: Are you aware if similar work ongoing for the mwl(4) based 802.11n cards? I picked up a couple cheap this past week and have them working with hostapd but, as with the OP in the thread, only with G rates. The ifconfig[1] output suggests that it is using 40MHz wide ht channels but devices only associate at 54Mbps[2]. Jim [1] ifconfig mwl0_wlan1 mwl0_wlan1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:01:36:17:96:0e inet6 fe80::201:36ff:fe17:960e%mwl0_wlan1 prefixlen 64 scopeid 0x9 inet 192.168.15.1 netmask 0xff00 broadcast 192.168.15.255 nd6 options=3PERFORMNUD,ACCEPT_RTADV media: IEEE 802.11 Wireless Ethernet autoselect mode 11na hostap status: running ssid WatchTower channel 100 (5500 MHz 11a ht/40+) bssid 00:01:36:17:96:0e regdomain DEBUG indoor authmode WPA2/802.11i privacy MIXED deftxkey 3 AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 14 scanvalid 60 ampdulimit 64k ampdudensity 4 shortgi smps burst dtimperiod 1 [2] ifconfig mwl0_wlan1 list sta (w/addr removed) AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 1 120 54M 33.00 1537 25952 EP A RSN (rssi 68:20:20 nf 0:0:0) mwl supports HT rates, but it looks like your AP is not sending HT rates to you. Thanks for the quick clarification, that's very encouraging to find out! In this case, the mwl card is the AP. The client line is from an associated Windows 7 laptop with an Intel 5100abgn card which does show the AP as 802.11n in the AP list. I'm connected and sending this message through it right now, actually. Are there some other bits that need set in order to have clients associate with HT rates? Or some other prerequisite conditions such as number of attached antennae? I do only have one antenna attached as I didn't have a second pigtail for this test unit's case. The card actually has three connectors. I didn't see hints in the mwl(4), wlan(4), hostapd(8), hostapd.conf(5), or ifconfig(8) man pages about troubleshooting rates. I see plenty of talk in ifconfig(8) about use and control of HT rates, but given what I'm seeing in ifconfig, it should be set to use them. I've tried several combinations of channels and standards (e.g. 11ng, 11na) but always end up with a 54Mbps link. I'd appreciate any more pointers that you (or anyone else reading) may have. I'd like to write up something on the topic once I get it fully operational. Did you measure the actual bandwidth you get? Changes are high that you are actually using HT rates, the rate information is just no accurate. -- Bernhard ___ 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: FreeBSD-8.0 802.11n support with ath/mwl
On 28 Feb 2010, at 17:38, Jim Pingle wrote: On 2/28/2010 7:54 AM, Rui Paulo wrote: On 28 Feb 2010, at 03:22, Jim Pingle wrote: Are you aware if similar work ongoing for the mwl(4) based 802.11n cards? I picked up a couple cheap this past week and have them working with hostapd but, as with the OP in the thread, only with G rates. The ifconfig[1] output suggests that it is using 40MHz wide ht channels but devices only associate at 54Mbps[2]. Jim [1] ifconfig mwl0_wlan1 mwl0_wlan1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:01:36:17:96:0e inet6 fe80::201:36ff:fe17:960e%mwl0_wlan1 prefixlen 64 scopeid 0x9 inet 192.168.15.1 netmask 0xff00 broadcast 192.168.15.255 nd6 options=3PERFORMNUD,ACCEPT_RTADV media: IEEE 802.11 Wireless Ethernet autoselect mode 11na hostap status: running ssid WatchTower channel 100 (5500 MHz 11a ht/40+) bssid 00:01:36:17:96:0e regdomain DEBUG indoor authmode WPA2/802.11i privacy MIXED deftxkey 3 AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 14 scanvalid 60 ampdulimit 64k ampdudensity 4 shortgi smps burst dtimperiod 1 [2] ifconfig mwl0_wlan1 list sta (w/addr removed) AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 1 120 54M 33.00 1537 25952 EP A RSN (rssi 68:20:20 nf 0:0:0) mwl supports HT rates, but it looks like your AP is not sending HT rates to you. Thanks for the quick clarification, that's very encouraging to find out! In this case, the mwl card is the AP. The client line is from an associated Windows 7 laptop with an Intel 5100abgn card which does show the AP as 802.11n in the AP list. I'm connected and sending this message through it right now, actually. Are there some other bits that need set in order to have clients associate with HT rates? Or some other prerequisite conditions such as number of attached antennae? I do only have one antenna attached as I didn't have a second pigtail for this test unit's case. The card actually has three connectors. Having only 1 antenna connected will likely impact your connection. I didn't see hints in the mwl(4), wlan(4), hostapd(8), hostapd.conf(5), or ifconfig(8) man pages about troubleshooting rates. I see plenty of talk in ifconfig(8) about use and control of HT rates, but given what I'm seeing in ifconfig, it should be set to use them. I've tried several combinations of channels and standards (e.g. 11ng, 11na) but always end up with a 54Mbps link. I'd appreciate any more pointers that you (or anyone else reading) may have. I'd like to write up something on the topic once I get it fully operational. I don't know what's happening, but I guess your Windows 7 laptop isn't sending the necessary HT rates in the association. Try using wlandebug to see what's happening. -- Rui Paulo ___ 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: FreeBSD-8.0 802.11n support with ath/mwl
On 2/28/2010 2:29 PM, Bernhard Schmidt wrote: On Sun, Feb 28, 2010 at 12:38:19PM -0500, Jim Pingle wrote: [snip] In this case, the mwl card is the AP. The client line is from an associated Windows 7 laptop with an Intel 5100abgn card which does show the AP as 802.11n in the AP list. I'm connected and sending this message through it right now, actually. Are there some other bits that need set in order to have clients associate with HT rates? Or some other prerequisite conditions such as number of attached antennae? I do only have one antenna attached as I didn't have a second pigtail for this test unit's case. The card actually has three connectors. I didn't see hints in the mwl(4), wlan(4), hostapd(8), hostapd.conf(5), or ifconfig(8) man pages about troubleshooting rates. I see plenty of talk in ifconfig(8) about use and control of HT rates, but given what I'm seeing in ifconfig, it should be set to use them. I've tried several combinations of channels and standards (e.g. 11ng, 11na) but always end up with a 54Mbps link. I'd appreciate any more pointers that you (or anyone else reading) may have. I'd like to write up something on the topic once I get it fully operational. Did you measure the actual bandwidth you get? Changes are high that you are actually using HT rates, the rate information is just no accurate. I did some tests and the throughput was quite slow. Enough to make me wonder about the antenna situation again. I'll have to dig up more pigtails and try again. Thanks for the idea. Jim ___ 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: FreeBSD-8.0 802.11n support with ath/mwl
On 2/28/2010 7:03 PM, Rui Paulo wrote: On 28 Feb 2010, at 17:38, Jim Pingle wrote: Are there some other bits that need set in order to have clients associate with HT rates? Or some other prerequisite conditions such as number of attached antennae? I do only have one antenna attached as I didn't have a second pigtail for this test unit's case. The card actually has three connectors. Having only 1 antenna connected will likely impact your connection. I'll hook up two more and try again when I get a chance, I just need to pull them from a working unit that isn't using its wifi currently. I didn't see hints in the mwl(4), wlan(4), hostapd(8), hostapd.conf(5), or ifconfig(8) man pages about troubleshooting rates. I see plenty of talk in ifconfig(8) about use and control of HT rates, but given what I'm seeing in ifconfig, it should be set to use them. I've tried several combinations of channels and standards (e.g. 11ng, 11na) but always end up with a 54Mbps link. I'd appreciate any more pointers that you (or anyone else reading) may have. I'd like to write up something on the topic once I get it fully operational. I don't know what's happening, but I guess your Windows 7 laptop isn't sending the necessary HT rates in the association. Try using wlandebug to see what's happening. Ah, I wasn't aware of wlandebug(8). However, it doesn't seem to operate on this mwl(4) card. It sets the value of the sysctl net.wlan.0.debug and that doesn't show up on my system. Another system with a ral(4) card does have that sysctl. Judging by the information in the wlandebug(8) man page it appears as though this may be a side effect of mwl doing much of the work in firmware. I appreciate the information though, thanks for taking the time to reply. I'll continue to work on this again once I relocate some pigtails from another box. Jim ___ 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: FreeBSD-8.0 802.11n support with ath/mwl
On 1 Mar 2010, at 02:26, Jim Pingle wrote: On 2/28/2010 7:03 PM, Rui Paulo wrote: On 28 Feb 2010, at 17:38, Jim Pingle wrote: Are there some other bits that need set in order to have clients associate with HT rates? Or some other prerequisite conditions such as number of attached antennae? I do only have one antenna attached as I didn't have a second pigtail for this test unit's case. The card actually has three connectors. Having only 1 antenna connected will likely impact your connection. I'll hook up two more and try again when I get a chance, I just need to pull them from a working unit that isn't using its wifi currently. I didn't see hints in the mwl(4), wlan(4), hostapd(8), hostapd.conf(5), or ifconfig(8) man pages about troubleshooting rates. I see plenty of talk in ifconfig(8) about use and control of HT rates, but given what I'm seeing in ifconfig, it should be set to use them. I've tried several combinations of channels and standards (e.g. 11ng, 11na) but always end up with a 54Mbps link. I'd appreciate any more pointers that you (or anyone else reading) may have. I'd like to write up something on the topic once I get it fully operational. I don't know what's happening, but I guess your Windows 7 laptop isn't sending the necessary HT rates in the association. Try using wlandebug to see what's happening. Ah, I wasn't aware of wlandebug(8). However, it doesn't seem to operate on this mwl(4) card. It sets the value of the sysctl net.wlan.0.debug and that doesn't show up on my system. Another system with a ral(4) card does have that sysctl. Judging by the information in the wlandebug(8) man page it appears as though this may be a side effect of mwl doing much of the work in firmware. I appreciate the information though, thanks for taking the time to reply. I'll continue to work on this again once I relocate some pigtails from another box. wlandebug takes an -i argument. I seem to recall you created your wlan interface named mwl_wlan0, so you need to type wlandebug -i mwl_wlan0. -- Rui Paulo ___ 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: FreeBSD-8.0 802.11n support with ath/mwl
On 2/28/2010 9:41 PM, Rui Paulo wrote: On 1 Mar 2010, at 02:26, Jim Pingle wrote: Ah, I wasn't aware of wlandebug(8). However, it doesn't seem to operate on this mwl(4) card. It sets the value of the sysctl net.wlan.0.debug and that doesn't show up on my system. Another system with a ral(4) card does have that sysctl. Judging by the information in the wlandebug(8) man page it appears as though this may be a side effect of mwl doing much of the work in firmware. wlandebug takes an -i argument. I seem to recall you created your wlan interface named mwl_wlan0, so you need to type wlandebug -i mwl_wlan0. I saw that, but that is hardcoded to expect wlanx (wlan0, wlan1, etc) for an interface name. Having seen that, I recompiled wlandebug without the hardcoded interface name check and it didn't work either, but it did toss an error for the sysctl it was trying to tweak. That made me look deeper at the code and see it was really just setting the debug sysctl based on flags that wlandebug was aware of. Handy, but the same thing could be done by hand with sysctl and some bitwise math in a pinch, assuming the interface has the right oids. (Which mine doesn't, for some reason...) Jim ___ 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: FreeBSD-8.0 802.11n support with ath/mwl
On 1 Mar 2010, at 03:05, Jim Pingle wrote: On 2/28/2010 9:41 PM, Rui Paulo wrote: On 1 Mar 2010, at 02:26, Jim Pingle wrote: Ah, I wasn't aware of wlandebug(8). However, it doesn't seem to operate on this mwl(4) card. It sets the value of the sysctl net.wlan.0.debug and that doesn't show up on my system. Another system with a ral(4) card does have that sysctl. Judging by the information in the wlandebug(8) man page it appears as though this may be a side effect of mwl doing much of the work in firmware. wlandebug takes an -i argument. I seem to recall you created your wlan interface named mwl_wlan0, so you need to type wlandebug -i mwl_wlan0. I saw that, but that is hardcoded to expect wlanx (wlan0, wlan1, etc) for an interface name. Having seen that, I recompiled wlandebug without the hardcoded interface name check and it didn't work either, but it did toss an error for the sysctl it was trying to tweak. The whole system was designed for the interfaces to start with wlan and be named wlansomething. That made me look deeper at the code and see it was really just setting the debug sysctl based on flags that wlandebug was aware of. Handy, but the same thing could be done by hand with sysctl and some bitwise math in a pinch, assuming the interface has the right oids. (Which mine doesn't, for some reason...) The purpose of wlandebug is to not do any math by hand. -- Rui Paulo ___ 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: FreeBSD-8.0 802.11n support with ath/mwl
On 2/28/2010 10:16 PM, Rui Paulo wrote: On 1 Mar 2010, at 03:05, Jim Pingle wrote: On 2/28/2010 9:41 PM, Rui Paulo wrote: On 1 Mar 2010, at 02:26, Jim Pingle wrote: Ah, I wasn't aware of wlandebug(8). However, it doesn't seem to operate on this mwl(4) card. It sets the value of the sysctl net.wlan.0.debug and that doesn't show up on my system. Another system with a ral(4) card does have that sysctl. Judging by the information in the wlandebug(8) man page it appears as though this may be a side effect of mwl doing much of the work in firmware. wlandebug takes an -i argument. I seem to recall you created your wlan interface named mwl_wlan0, so you need to type wlandebug -i mwl_wlan0. I saw that, but that is hardcoded to expect wlanx (wlan0, wlan1, etc) for an interface name. Having seen that, I recompiled wlandebug without the hardcoded interface name check and it didn't work either, but it did toss an error for the sysctl it was trying to tweak. The whole system was designed for the interfaces to start with wlan and be named wlansomething. It does certainly seem to lean that way. Personally I prefer to keep the hardware name in there, but I wasn't aware that would cause other issues. Especially when VAPs come into play, I'd rather have, for example, mwl0_wlan1, mwl0_wlan2, ath0_wlan0, etc, so I can better tie what goes where. But that's more of a bikeshed of personal preference. :-) That made me look deeper at the code and see it was really just setting the debug sysctl based on flags that wlandebug was aware of. Handy, but the same thing could be done by hand with sysctl and some bitwise math in a pinch, assuming the interface has the right oids. (Which mine doesn't, for some reason...) The purpose of wlandebug is to not do any math by hand. Indeed, You're 110% right on that. I was just trying to work around the other issues I was seeing to get to the root of the issue, which seems to be the missing sysctl oid. I need to run some more tests and straighten my antenna issues out, but I'll report what I find back to the list in a few days. Thanks again for the information, Jim ___ 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: FreeBSD-8.0 802.11n support with ath/mwl
On 2/27/2010 9:09 PM, Rui Paulo wrote: On 27 Feb 2010, at 20:29, Robert Watson wrote: Progress on supporting 11n with atheros cards is on going. There's much more to it than adapting the rate control algorithm. Please stay tuned. Are you aware if similar work ongoing for the mwl(4) based 802.11n cards? I picked up a couple cheap this past week and have them working with hostapd but, as with the OP in the thread, only with G rates. The ifconfig[1] output suggests that it is using 40MHz wide ht channels but devices only associate at 54Mbps[2]. Jim [1] ifconfig mwl0_wlan1 mwl0_wlan1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:01:36:17:96:0e inet6 fe80::201:36ff:fe17:960e%mwl0_wlan1 prefixlen 64 scopeid 0x9 inet 192.168.15.1 netmask 0xff00 broadcast 192.168.15.255 nd6 options=3PERFORMNUD,ACCEPT_RTADV media: IEEE 802.11 Wireless Ethernet autoselect mode 11na hostap status: running ssid WatchTower channel 100 (5500 MHz 11a ht/40+) bssid 00:01:36:17:96:0e regdomain DEBUG indoor authmode WPA2/802.11i privacy MIXED deftxkey 3 AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 14 scanvalid 60 ampdulimit 64k ampdudensity 4 shortgi smps burst dtimperiod 1 [2] ifconfig mwl0_wlan1 list sta (w/addr removed) AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG 1 120 54M 33.00 1537 25952 EP A RSN (rssi 68:20:20 nf 0:0:0) ___ 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
