Hi, cktan@ocesb.com.my wrote:
OK, I try to setup hostapd in freebsd to be my wireless NAS and configure the accounting server to my radius server. It works. Which mean the my previous NAS do not do the accounting job. Thank for your information. By the way, I do notice the accounting request sent by hostapd is very basic and what should I do if i need to add more attribute? For example, the accounting packet do not include the full username i.e. user@domain. Looking for your advice.
rad_recv: Accounting-Request packet from host 61.4.124.254:56195, id=35, length=155 Acct-Session-Id = "00000000-00000000" Acct-Status-Type = Start Acct-Authentic = RADIUS User-Name = "user" NAS-Identifier = "61test.com" NAS-Port = 0 Called-Station-Id = "00-02-6F-43-8E-E1:61test" Calling-Station-Id = "00-14-A5-D9-09-07" NAS-Port-Type = Wireless-802.11 Connect-Info = "CONNECT 11Mbps 802.11b"
I am also setting up FreeBSD + hostapd + freeRadius and accounting... Did anybody notice, that hostapd *always* sends a NAS-Port with a value of 0 for *any* connected station? This happens for me with the hostapd 0.4.8 included with FreeBSD 6.2, as well as with hostapd 0.5.8. And it is presumably the reason, why I cannot seem to get radwho to function properly. The radutmp module seems to use a combination of NAS-Identifier and NAS-Port to differentiate it's records. When station-B associates to the AP, the radutmp record for station-A gets overwritten :-( Andreas -- Keep it icy man. I don't want to end up a corpse before my time because you were daydreaming.