On Thursday 12 June 2003 2:31 am, JC Fulknier wrote:
> sorry it's 230 AM, forgot to turn off html on last post. here it is again.
>
> I'm using an Orinoco AP 2500 to authenticate to a Red Hat 9 server running
> freeradius 0.8.1. When I run radius report on the radius.log file I do not
> get anything. Is this because the AP does not tell the Radius server that
> the client has logged out? If I read the report I just see logins not
> logouts. Also, there are no files in the radacct dir.

I have the same unit -- I've found a case where it doesn't send a "stop" 
packet until the slot is reused [preferrably by the same user/wireless card] 
{which reminds me I need to e-mail them and see if that really is the case}

Also, the ap2500 has TWO radius entries -- one for authentication, and one for 
accounting. [and within that, you can configure two different ones for the 
same feature, so that you have "failover" protection]  You indicate you are 
seeing "start" records, so I presume you do indeed have the accounting set 
correctly.

One thing to do would be to set up a packet sniffer to watch for radius 
traffic -- that would absolutely show whether or not the AP is sending stop 
records -- other than that, you might try logging in via telnet/snmp and 
seeing what the AP says about "connections" [i.e., whether they are "active" 
or "pending"]

Finally, what firmware level do you have in the AP?  Mine needed the 1.0 
update on their site, and yet I still have a strange problem: everything is 
reported as being "on port 0".  proxim's tech support says that isn't correct 
(the AP should be reporting non-zero "port" numbers) and that I should 
"reload" the unit.  If only one person logs on to my network, then logs off, 
everything is OK; however if there is one intervening "logon", my radius.log 
file lists complaints about stop records not matching fully [port 0 appears 
to be "reused" per radius]  However, it still manages to match [to a mysql 
database] the stop record with the correct "accounting" record in the 
database, so I haven't bothered with it.
-- 
Yet another Blog: http://osnut.homelinux.net

Attachment: pgp00000.pgp
Description: signature

Reply via email to