Switches, Hubs, and Modems
cancel
Showing results for 
Search instead for 
Did you mean: 

2824 Radius Accounting

Schuler, Sebastian
Occasional Visitor

2824 Radius Accounting

Hello,

we are freeradius to autheticate users.
Authentication works fine but we aren't able to use accounting, because we are only getting responses for USER Anonymous. So we can't track user traffic or login/logout times.

Heres a log from freeradius:

Authentication of User "TESTUSER"
>> radius-auth
Thu Nov 20 13:41:24 2006 : Auth: Login OK: [TESTUSER] (from client localhost port 5 cli 00-06-1b-da-33-40) <<

Accounting for this session
>> radius-acct
Thu Nov 23 13:41:24 2006
Acct-Session-Id = "000F00000001"
Acct-Status-Type = Start
Acct-Authentic = RADIUS
Acct-Delay-Time = 0
NAS-Port = 5
Calling-Station-Id = "00-06-1b-da-33-40"
Service-Type = Framed-User
NAS-IP-Address = 192.168.0.1
NAS-Identifier = "ProCurve Switch 2848"
User-Name = "anonymous"
Client-IP-Address = 192.168.0.1
Acct-Unique-Session-Id = "c80dd51a11578c70"
Timestamp = 1164285684

Thu Nov 23 13:41:51 2006
Acct-Session-Id = "000F00000001"
Acct-Status-Type = Stop
Acct-Authentic = RADIUS
Acct-Delay-Time = 0
NAS-Port = 5
Calling-Station-Id = "00-06-1b-da-33-40"
Service-Type = Framed-User
NAS-IP-Address = 192.168.0.1
NAS-Identifier = "ProCurve Switch 2848"
User-Name = "anonymous"
Acct-Terminate-Cause = Port-Reinit
Acct-Session-Time = 28
Acct-Input-Octets = 7344
Acct-Output-Octets = 24165
Acct-Input-Packets = 56
Acct-Output-Packets = 194
Client-IP-Address = 192.168.0.1
Acct-Unique-Session-Id = "c80dd51a11578c70"
Timestamp = 1164285711

Best Regards

Sebastian








2 REPLIES
Mohieddin Kharnoub
Honored Contributor

Re: 2824 Radius Accounting

Hi

I would ask you to attach the configuration of your switch so we can take a look, and remove any sensitive information like IP addresses.

Also what is the firmware version you are using now on this 2800.

Good Luck !!!
Science for Everyone
Schuler, Sebastian
Occasional Visitor

Re: 2824 Radius Accounting

Hi,

thank Your for Your fast answer.
I've got a answer from HP - this behavior is a know Problem and will be solved in the next software release.

Regards

Sebastian