Accounting Data?

I am trying to get the PMP450's to use the username/calling-station-id as the username in the accounting data. 

According to RFC 2865 Section 5.1 the device should use the username I send back in the Access-Accept, however, this does not appear to be functioning as it should. 

Access-Accept Attributes:

	Service-Type = Framed-User
	Framed-Protocol = PPP
	Framed-Routing = None
	Motorola-Canopy-DLBR = 1024
	Motorola-Canopy-DLBL = 2120
	Motorola-Canopy-ULBR = 384
	Motorola-Canopy-ULBL = 768
	User-Name = "0a-00-3e-d2-aa-xx"
	MS-MPPE-Send-Key = "T]<175>F<13><5><189><148><16>F<130><229><205><254><201>(<30><160>T<153><194>+<198><194>-<244>E<216><132>Jz2"
	MS-MPPE-Recv-Key = "H<148><143><151>o<136><214>m<175><12><31><155><243>\H<188>O<16><223><144><189><210><245><28><14><153><251><161><181><148><6><224>"
	EAP-Message = <3><6><0><4>
	Message-Authenticator = <0><0><0><0><0><0><0><0><0><0><0><0><0><0><0><0>

Accounting-Request Attributes:

	User-Name = "anonymous@domain.com"
	NAS-Port = 2
	NAS-Port-Type = Wireless-Other
	NAS-IP-Address = 192.168.123.239
	Calling-Station-Id = "0A-00-3E-D2-AA-xx"
	Acct-Authentic = RADIUS
	Connect-Info = "1024/384/2X/1X"
	Acct-Session-Id = "0a003ed2aaxx01000002"
	Acct-Input-Octets = 2538
	Acct-Output-Octets = 2961
	Acct-Input-Packets = 9
	Acct-Output-Packets = 7
	Acct-Input-Gigawords = 0
	Acct-Output-Gigawords = 0
	Acct-Session-Time = 1799
	Acct-Status-Type = Alive
	NNS-NAS-Type = "DSL"
	NNS-User-Type = "ppp"
	Timestamp = 1493649474
	Acct-Delay-Time = 0
	Signature = "domain"
	Token = "domain.com"

Any ideas why it is not doing as it should? Any ideas on how to resolve this?

Thanks!

I am not sure on this one, but working to find an answer for you...

I appreciate any insight and your time!

Hi,

What software version you are using on PMP 450?

Are you using PEAP or TTLS ?

Thanks,

Chitrang

Software Version :
CANOPY 13.4.1 AP-DES
Software Boot Version :
CANOPYBOOT 4.1

We are using TTLS. 

Please upgrade to latest 15.0.3 and try

What Chitrang means is that we believe this was corrected in a later software version, and R15.0.3 includes this fix...

(not just try it and see) 

Let us know, thanks!

Looks like I was working with a PMP100 which does not support the latest firmware. However my client is upgrading to PMP450s with the latest firmware. Once I am able to test, I will let everyone know my results!

For the PMP100s I ended up doing a lot of manipulation at the packet level. 

1 Like