I am running freeradius-1.1.3. I am using freeradius to authenticate users logging into Cisco switches and routers. I am trying to use radrelay to send the radius accounting data to our syslog server. When I run radrelay in debug mode, it gives this error: Record Rate since startup: 42.57 Packet Rate since startup: 0.00 read_one: No Acct-Status-Type attribute present. Rejecting record. read_one: No Acct-Status-Type attribute present. Rejecting record. radrelay: Running and Processing Records. Seconds since startup: 7 Records Read: 299 Packets Sent: 0 When I check the contents of the /var/log/radius/radacct/detail-combined file, it contains the following attributes: Packet-Type = Access-Request Wed Oct 3 15:36:02 2007 NAS-IP-Address = 10.3.51.1 NAS-Port = 1 NAS-Port-Type = Virtual User-Name = "testuser" Calling-Station-Id = "10.3.0.51" Client-IP-Address = 10.3.51.1 Is it possible to have the Acct-Status-Type attribute included in the Access Request that is logged to the /var/log/radius/radacct/detail-combined file? If so - how would I go about achieving this? I have checked the /etc/raddb/dictionary and related files (in /usr/share/freeradius/) and see the Acct-Status-Type attribute listed, but am not sure why it is not being included in the above accounting access-request. Thanks in advance, Walter Gould Auburn University
On Wednesday 03 October 2007 16:44:28 Walter Gould wrote:
I am running freeradius-1.1.3.
* Old version complaints apply *
I am trying to use radrelay to send the radius accounting data to our syslog server. [snip] When I check the contents of the /var/log/radius/radacct/detail-combined file, it contains the following attributes:
Packet-Type = Access-Request Wed Oct 3 15:36:02 2007 NAS-IP-Address = 10.3.51.1 NAS-Port = 1 NAS-Port-Type = Virtual User-Name = "testuser" Calling-Station-Id = "10.3.0.51" Client-IP-Address = 10.3.51.1
Access-Request is not from an accounting packet. You have a detail module listed in your authorize or post-auth section which is adding this data to the detail-combined file. You should have something similar to this in your radiusd.conf file: === modules { ... detail detail-radrelay { detailfile = ${radacctdir}/detail-combined detailperm = 0600 locking = yes } ... } accounting { ... detail-radrelay ... } === If you have the detail-radrelay name listed in a config section other than accounting, that is probably where the Access-Request packets are coming from. Kevin Bonner
Kevin Bonner wrote:
Access-Request is not from an accounting packet. You have a detail module listed in your authorize or post-auth section which is adding this data to the detail-combined file. You should have something similar to this in your radiusd.conf file:
Thanks for your reply. You were right about this.
=== modules { ... detail detail-radrelay { detailfile = ${radacctdir}/detail-combined detailperm = 0600 locking = yes } ... } accounting { ... detail-radrelay ... } ===
I have put sections like this in my radiusd.conf file, but now - I am getting no data in the detail-combined file. I have checked permissions on the file and it is owned by user radiusd and group radiusd. Also, there are no related errors in my radius.log file. Why would I not be getting any accounting data written to this file? Seems like something is still mis-configured. Below are my config sections related to this: modules { ... detail detail-combined { detailfile = ${radacctdir}/detail-combined detailperm = 0600 dirperm = 0755 locking = yes } ... } accounting { ... detail-combined ... } Also, I have run radiusd in debug mode and it loads the above module fine. Thanks for any assistance, Walter
Alan DeKok wrote:
Walter Gould wrote:
Why would I not be getting any accounting data written to this file?
This is in the FAQ.
Alan DeKok.
Alan, You were right - thanks for pointing me there. http://wiki.freeradius.org/index.php/FAQ#How_do_I_enable_FreeRADIUS_to_log_a... Walter
That packet is used to gain access. It has nothing to do with accounting. Accounting works much better when you have (only) accounting packets to work with. Use detail not detail-combined. Ivan Kalik Kalik Informatika ISP Dana 3/10/2007, "Walter Gould" <gouldwp@auburn.edu> piše:
I am running freeradius-1.1.3. I am using freeradius to authenticate users logging into Cisco switches and routers. I am trying to use radrelay to send the radius accounting data to our syslog server. When I run radrelay in debug mode, it gives this error:
Record Rate since startup: 42.57 Packet Rate since startup: 0.00 read_one: No Acct-Status-Type attribute present. Rejecting record. read_one: No Acct-Status-Type attribute present. Rejecting record. radrelay: Running and Processing Records. Seconds since startup: 7 Records Read: 299 Packets Sent: 0
When I check the contents of the /var/log/radius/radacct/detail-combined file, it contains the following attributes:
Packet-Type = Access-Request Wed Oct 3 15:36:02 2007 NAS-IP-Address = 10.3.51.1 NAS-Port = 1 NAS-Port-Type = Virtual User-Name = "testuser" Calling-Station-Id = "10.3.0.51" Client-IP-Address = 10.3.51.1
Is it possible to have the Acct-Status-Type attribute included in the Access Request that is logged to the /var/log/radius/radacct/detail-combined file? If so - how would I go about achieving this?
I have checked the /etc/raddb/dictionary and related files (in /usr/share/freeradius/) and see the Acct-Status-Type attribute listed, but am not sure why it is not being included in the above accounting access-request.
Thanks in advance,
Walter Gould Auburn University - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
participants (4)
-
Alan DeKok -
Kevin Bonner -
tnt＠kalik.co.yu -
Walter Gould