I know Alan responded to this already, but I'll inject some notes as well.
On Fri, 2004-09-10 at 12:07, Brian Sumpter wrote: > When I first installed FreeRadius, I noticed that my AP2000 units did > not send the Account-Session-Time variable back in the stop packets. > I assume that this is just a “feature” of the Orinoco AP’s to not > report session time. This is indeed true of the screwed up RADIUS implementation on the AP-2000s. They do not report session time with the Account-Session-Time attribute. They expect you to calculate it after-the-fact based on the Start and Stop packet times. Oh well, it's doable. > I assumed a simple modification to the SQL statement to figure (logout > time – login time) would do the trick, but I could be wrong. Like Alan said, this is probably doable. > Also, my radius logs report every user connection on port 0. However, > in the database everyone is coming in on port 2. Would this have > something to do with the Port 2 Wrong ID issue below? This is another "feature" of the APs. For some reason, they do not take the time to report the correct port in the Access Request packets. They simply set it to 0. This is quite annoying. You do, however, get the Called-Station-Id in the Access Request packets. You DON'T get the Called-Station-Id in the ACCOUNTING packets (very annoying), however you *do* get the correct Port ID. FYI, port 2 is the card in slot A, port 9 is the card in slot B, and ports 3-8, 10-15 are any WDS "virtual" ports for repeater-type environments. Anyway, the fact that it does this should not affect anything in the account as autz/auth and accounting are totally seperate functions. It's just a large annoyance. -- --Mike ----------------------------------- Michael Griego Wireless LAN Project Manager The University of Texas at Dallas - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
