RG: Accounting Problems caused by missing NAS-Port
Georg Brandt
I´ve got a problems with accounting from a WLAN AP.
starting wit radiusd -X the freeRadius say ..."rlm_radutmp: No NAS-Port
seen. Cannot do anything"
In RFC 2866 is stated:
...
Either NAS-IP-Address or NAS-Identifier MUST be present in a
RADIUS Accounting-Request. It SHOULD contain a NAS-Port or NAS-
Port-Type attribute or both unless the service does not involve a
port or the NAS does not distinguish among its ports.
....
As the NAS is a WLAN AP with just one WLAN it might be standard compliant
not transmitting the NAS-Port.
Is there a way for the freeRadius to accept those request without NAS-Port
value ?
please see the the log file
####
rad_recv: Accounting-Request packet from host 192.168.0.127:1813, id=78,
length=74
User-Name = "mysql"
NAS-IP-Address = 192.168.1.160
Acct-Status-Type = Start
NAS-Port-Type = Wireless-802.11
Calling-Station-Id = "00-02-72-02-0F-62"
Acct-Session-Id = "0D000006"
Processing the preacct section of radiusd.conf
modcall: entering group preacct for request 9
modcall[preacct]: module "preprocess" returns noop for request 9
rlm_realm: No '@' in User-Name = "mysql", looking up realm NULL
rlm_realm: No such realm "NULL"
modcall[preacct]: module "suffix" returns noop for request 9
modcall[preacct]: module "files" returns noop for request 9
modcall: group preacct returns noop for request 9
Processing the accounting section of radiusd.conf
modcall: entering group accounting for request 9
radius_xlat:
'/usr/local/var/log/radius/radacct/192.168.0.127/detail-20050113'
rlm_detail:
/usr/local/var/log/radius/radacct/%{Client-IP-Address}/detail-%Y%m%d
expands to /usr/local/var/log/radius/radacct/192.168.0.127/detail-20050113
modcall[accounting]: module "detail" returns ok for request 9
modcall[accounting]: module "unix" returns noop for request 9
radius_xlat: '/usr/local/var/log/radius/radutmp'
radius_xlat: 'mysql'
rlm_radutmp: No NAS-Port seen. Cannot do anything.
rlm_radumtp: WARNING: checkrad will probably not work!
modcall[accounting]: module "radutmp" returns noop for request 9
radius_xlat: 'mysql'
rlm_sql (sql): sql_set_user escaped user --> 'mysql'
radius_xlat: 'INSERT into radacct (AcctSessionId, AcctUniqueId, UserName,
Realm, NASIPAddress, NASPortType, AcctStartTime, AcctStopTime,
AcctSessionTime, AcctAuthentic, ConnectInfo_start, ConnectInfo_stop,
AcctInputOctets, AcctOutputOctets, CalledStationId, CallingStationId,
AcctTerminateCause, ServiceType, FramedProtocol, FramedIPAddress,
AcctStartDelay, AcctStopDelay) values('0D000006', '', 'mysql', '',
'192.168.1.160', 'Wireless-802.11', '2005-01-13 15:03:23', '0', '0', '',
'', '', '0', '0', '', '00-02-72-02-0F-62', '', '', '', '', '', '0')'
radius_xlat: '/usr/local/var/log/radius/sqltrace.sql'
rlm_sql (sql): Reserving sql socket id: 1
rlm_sql_mysql: query: INSERT into radacct (AcctSessionId, AcctUniqueId,
UserName, Realm, NASIPAddress, NASPortType, AcctStartTime, AcctStopTime,
AcctSessionTime, AcctAuthentic, ConnectInfo_start, ConnectInfo_stop,
AcctInputOctets, AcctOutputOctets, CalledStationId, CallingStationId,
AcctTerminateCause, ServiceType, FramedProtocol, FramedIPAddress,
AcctStartDelay, AcctStopDelay) values('0D000006', '', 'mysql', '',
'192.168.1.160', 'Wireless-802.11', '2005-01-13 15:03:23', '0', '0', '',
'', '', '0', '0', '', '00-02-72-02-0F-62', '', '', '', '', '', '0')
rlm_sql (sql): Released sql socket id: 1
modcall[accounting]: module "sql" returns ok for request 9
modcall: group accounting returns ok for request 9
Sending Accounting-Response of id 78 to 192.168.0.127:1813
Finished request 9
Going to the next request
####
any help would be highly appreciated
Georg Brandt
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Alan DeKok
> starting wit radiusd -X the freeRadius say ..."rlm_radutmp: No NAS-Port
> seen. Cannot do anything"
That means that the radutmp file will not be updated.
> In RFC 2866 is stated:
> ...
> Either NAS-IP-Address or NAS-Identifier MUST be present in a
> RADIUS Accounting-Request. It SHOULD contain a NAS-Port or NAS-
> Port-Type attribute or both unless the service does not involve a
> port or the NAS does not distinguish among its ports.
> ....
Yes, so?
The server still logs the accounting packet. It just can't update
radutmp.
> As the NAS is a WLAN AP with just one WLAN it might be standard compliant
> not transmitting the NAS-Port.
Yes.
> Is there a way for the freeRadius to accept those request without NAS-Port
> value ?
FreeRADIUS is already accepting the request. See the "detail" file,
where the request is logged.
Alan DeKok.
Georg Brandt
regards
Georg
Am Thu, 13 Jan 2005 10:07:54 -0500 hat Alan DeKok <al...@ox.org>
geschrieben:
right, there are the "start" messages, it seems that the NAS does not send
a "stop" messages
>
> Alan DeKok.
>
>
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
--
Georg Brandt
CTO
InventCon Europe GmbH
Mainzer Landstr. 27-31
60329 Frankfurt am Main
T: +49 (0) 700 INVENTCON
+49 (0) 700 46836826
M: +49 (0)179 6905307
Email: georg....@inventconeurope.de
Web: www.inventconeurope.de
Alan DeKok
> What is radutmp doing (or not) ?
Maintains lists of logged-in users. See "man utmp", which does the
same thing for normal Unix login users.