Controller inverting input and oputput data on Radius interim updates?
Hi,
I have an EAP110 connected to a software controller V5.9.31, and a Radius server in the same LAN. The controller is configured to use a portal in the same LAN with authentication to my "External RADIUS Server".
Everything works fine: splash page displayed correctly, authentication on Radius is ok. However, it seems that the controller is sending wrong data in the Interim Update messages to the Radius server: input and Output data are inverted. This is an example of information sent in the Interim Update message for a session where the guest device has downloaded a lot:
(71) Acct-Input-Octets = 1362952
(71) Acct-Output-Octets = 44896400
...
(83) Acct-Input-Octets = 1867873
(83) Acct-Output-Octets = 135510452
I'm not new to this matter, and I use to work with many brands of access points/controllers, but this is the first time I'm facing this kind of problem. The meaning of Acct-Input-Octets is: "the number of incoming octets passed through a specific client port during one session", and vice versa for the output. So, I'm expecting that the 2 values are inverted.
Of course, on the Omada statistics page the Transmitted traffic is much higher than the Received traffic, but that's not the way it should be: in fact in this manual https://static.tp-link.com/2021/202105/20210510/Omada%20SDN%20Software%20Controller%204.3.5%20(windows&linux)_User%20Guide.pdf
you can see at page 336 that the "normal" case is when the Transmitted is lower than the Received.
Has anyone ever had the same problem?
Thank you in advance.