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 authentification of my WNDAP660 in conjunction with a FreeRadius server. While analysing the packages which are sent from the Access Point to the radius server I recognised, that the informations are some kind of buggy. For example the "NAS-Identifier" just sends „hello“ instead of a unique id and the "Connect-Info" is set to a loosy string "CONNECT 0Mbps 802.11b" although the client conected to the Access Point uses 802.11n (not b).
While the "Connect-Info" doesn't provide much harm, the "NAS-Identifier" is used, to identify a NAS and using more than one Access Point of the same type doesn't allow to distinguish between the devices when they just sent "hello".
The wrong setting are configured on the Access Point in file /etc/bss*.conf.wifi*
It is possible to fix that via commandline and restarting the service, but at every cold boot the procedure would have to be repeated. Can anyone confim that problem or better know how the problem be reported to the firmware developpers so that it can be fixed?
Kind Regards
SPuch
7 Replies
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
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
