Radacct Reused ?

[Alan DeKok]

On Apr 21, 2019, at 4:31 PM, Oscar <oscar at jofre.com> wrote:
> About:

  Copying configuration files to the list isn't helpful.

> Is Class an attribute that should come from the NAS ?

  No.

> I'm using mikroitk as a NAS and I think/hope is not garbage.

  <shrug>  If it's re-using Acct-Session-Id across different sessions, then yes, it's garbage.

> This is what it is sending as accounting
> 
> 	22:14:40 radius,debug sending 3f:41a8 to 18.194.84.153:1813 
> 	22:14:40 radius,debug,packet sending Accounting-Request with id 14 to 18.194.84.153:1813 
> 	22:14:40 radius,debug,packet     Signature = 0x72ab4a619fdecb98eeaefe7322abe9fe 
> 	22:14:40 radius,debug,packet     Acct-Status-Type = 3 
> 	22:14:40 radius,debug,packet     NAS-Port-Type = 19 
> 	22:14:40 radius,debug,packet     Calling-Station-Id = "30:07:4D:50:64:AA" 
> 	22:14:40 radius,debug,packet     Called-Station-Id = "8D0008D14A5D" 
> 	22:14:40 radius,debug,packet     NAS-Port-Id = "bridge-hs" 
> 	22:14:40 radius,debug,packet     User-Name = "SwB_3094873_ins_6971_30:07:4D:50:64:AA" 
> 	22:14:40 radius,debug,packet     NAS-Port = 2148532224 
> 	22:14:40 radius,debug,packet     Acct-Session-Id = "80100000" 

  That's really not a good idea.  The Acct-Session-Id *should* be a long random string.

> Seems than Nas-Port + Acc-Session-id (  2148532224 + 80100000 ) should be unique.

  Except when the same user logs into the same NAS port.

> Is that correct ?

  When I said no amount of poking FreeRADIUS would fix the NAS, I meant it.  Your response should *not* be to poke the FreeRADIUS configuration in an attempt to "fix" the problem.

  Alan DeKok.