radtest is an authetication testing tool. It doesn't do accounting. Send a request from a NAS. You sent an access request with radclient to the accounting port. To no surprise it did not respond. You have to send an accounting packet to the accounting port. Ivan Kalik Kalik Informatika ISP Dana 1/2/2008, "Julian Stöver" <julian_st@gmx.de> piše:
I just tried radtest and radclient, with no result, but I think i found my fault. I used the authentication port for accounting. Now I tried it with the accounting port, with this result:
# echo "User-Name = julian,Password=blabla" | /usr/bin/radclient localhost:1813 acct somesecret # radclient: no response from server for ID 39
radiusd -X:
Cleaning up request 24 ID 46 with timestamp 47a35841 Nothing to do. Sleeping until we see a request. rad_recv: Accounting-Request packet from host 127.0.0.1:32780, id=46, length=46 User-Name = "julian" User-Password = "\266\266q\037"\231\246\222\0047>\027\357v\233\334" rad_lowerpair: User-Name now 'julian' rad_lowerpair: User-Password now 'śśq?"???7>?ďv?Ü' Processing the preacct section of radiusd.conf modcall: entering group preacct for request 25 modcall[preacct]: module "preprocess" returns noop for request 25 rlm_acct_unique: WARNING: Attribute NAS-Port was not found in request, unique ID MAY be inconsistent rlm_acct_unique: WARNING: Attribute Acct-Session-Id was not found in request, unique ID MAY be inconsistent rlm_acct_unique: Hashing ',Client-IP-Address = 127.0.0.1,NAS-IP- Address = 127.0.0.1,,User-Name = "julian"' rlm_acct_unique: Acct-Unique-Session-ID = "de9b5588c70f985c". modcall[preacct]: module "acct_unique" returns ok for request 25 rlm_realm: No '@' in User-Name = "julian", looking up realm NULL rlm_realm: No such realm "NULL" modcall[preacct]: module "suffix" returns noop for request 25 modcall[preacct]: module "files" returns noop for request 25 modcall: leaving group preacct (returns ok) for request 25 Processing the accounting section of radiusd.conf modcall: entering group accounting for request 25 radius_xlat: '/var/log/freeradius/radacct/127.0.0.1/detail-20080201' rlm_detail: /var/log/freeradius/radacct/%{Client-IP-Address}/detail- %Y%m%d expands to /var/log/freeradius/radacct/127.0.0.1/ detail-20080201 modcall[accounting]: module "detail" returns ok for request 25 radius_xlat: 'packet has no accounting status type. [user 'julian', nas '127.0.0.1']' rlm_sql (sql) in sql_accounting: packet has no accounting status type. [user 'julian', nas '127.0.0.1'] modcall[accounting]: module "sql" returns invalid for request 25 modcall: leaving group accounting (returns invalid) for request 25 Finished request 25 Going to the next request --- Walking the entire request list --- Cleaning up request 25 ID 46 with timestamp 47a35844 Nothing to do. Sleeping until we see a request.
Bye Julian
Am 01.02.2008 um 16:27 schrieb Ivan Kalik:
rad_recv: Access-Request packet from host 127.0.0.1:32780, id=232, length=46 .. Sending Access-Accept of id 232 to 127.0.0.1 port 32780
And where is the accounting request that should come right after it? Did NAS send one?
Ivan Kalik Kalik Informatika ISP
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html