NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
WNDAP660 Radius information are buggy in FW 3.7.9.0
Hello together, I already posted a similar message in the German community without any solution, so I will try it here in the wider range of the English community again. I'm using radius auth...
Hi spuch
We have a beta firmware for this case. Please reach support team to get the firmware.
Thanks,
Raghu
The provided beta firmware fixes the problem with the same NAS-Identifier for all access points. Now the mac address is given, which should be fine. I've tested that on three devices. Thanks for fixing that issue!
Of couse it would be nice, if the Connect-Info could also be set to some value which ist not misleading (e.g. "CONNECT 0Mbps 802.11b" if having a 300Mbps connection at 802.11ng) but for sure this is more a cosmetic aspect
Kind regards
SPuch
Hi spuch
Thanks for your feedback and confirmation.
On your other point -CONNECT 0Mbps 802.11b" Could you please help us to share with the packet capture where you are seeing this?
Thanks,
Raghu
Hi Raghu,
you can find the string "CONNECT 0Mbps 802.11b" in every radius accounting packet within the Connect-Info Attribute. It is an automatically generated value (implemented in accounting.c from hostapd) which uses the hardware mode (a, b, g) of the accesspoint and the supported supported_rates (Mbps ) of the access point. If nothing or wrong values are specified in the hostapd config file (like in our case) the defaults are used which leads to "0Mbps 802.11b".
I see two solutions if you want to fix that:
1 option)
The "hw_mode" is set to "ng" of "na" in /etc/ap.conf.wifi*
Acccording to the source code and the manual of config file this are not supported values which leads to (valid are a, b, g in version 0.5.7 of hostapd used in the firmware). Newer version like 2.6 can also use ad or any (see https://w1.fi/cgit/hostap/plain/hostapd/hostapd.conf for details). Maybe the Version 'sony_r5.7' is patched for that case, i didn't check that.
Set hw_mode=g in /etc/ap.conf.wifi0 and hw_mode=a in /etc/ap.conf.wifi1 should help and maybe the parameter "supported_rates" must be set as well (see https://w1.fi/cgit/hostap/plain/hostapd/hostapd.conf)
2 option)
Set the parameter "radius_ath_req_attr" in the config file for the hostapd
"this overrides the automatically generated value". You could of cause use something more generall here.
Both solutions would be better than the actual one, because every client connection to the access point is presumably better than 0Mbps.
Please let me know if that helps or if you still need a packet capture?
Kind regards
SPuch
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
