Hello, FreeRadius v3.0.19 Ready to process requests (0) Received Accounting-Request Id 205 from 112.112.166.34:1812 to 112.112.176.1:1813 length 610 (0) User-Name = "desclinz@XXXXX" (0) Acct-Status-Type = Interim-Update ... (0) Acct-Session-Time = 26401 (0) Acct-Input-Packets = 2241 (0) Acct-Output-Packets = 3514 (0) Acct-Input-Octets = 91936 (0) Acct-Output-Octets = 192756 (0) Acct-Input-Gigawords = 0 (0) Acct-Output-Gigawords = 0 (0) Acct-Input-Packets-64 = 2241 (0) Acct-Output-Packets-64 = 3514 (0) Acct-Input-Octets-64 = 91936 (0) Acct-Output-Octets-64 = 192756 (0) Acct-Mcast-In-Packets = 0 (0) Acct-Mcast-Out-Packets = 0 (0) Acct-Mcast-In-Octets = 0 (0) Acct-Mcast-Out-Octets = 0 (0) Acct-Mcast-In-Packets-64 = 0 I see the Input Octets 64 is decoded by freeradius, is it expected ? The same Accounting packet on Freeradius v2.2 Acct-Session-Time = 464417 Acct-Input-Packets = 3691542 Acct-Output-Packets = 3156045 Acct-Input-Octets = 822225356 Acct-Output-Octets = 709539148 Acct-Input-Gigawords = 0 Acct-Output-Gigawords = 0 Acct-Input-Packets-64 = 0x0000000000385416 Acct-Output-Packets-64 = 0x000000000030284d Acct-Input-Octets-64 = 0x00000000310229cc Acct-Output-Octets-64 = 0x000000002a4ab54c Acct-Mcast-In-Packets = 0 Acct-Mcast-Out-Packets = 0 Acct-Mcast-In-Octets = 0 Acct-Mcast-Out-Octets = 0 On 2.2, the Input Packets 64 is in Hexadecimal. Thanks
On May 9, 2019, at 4:18 AM, Nicolas Breuer <Nicolas.Breuer@belcenter.biz> wrote:
I see the Input Octets 64 is decoded by freeradius, is it expected ?
Decoding attributes from a packet? No, it's completely unexpected. Why would the server do that?
The same Accounting packet on Freeradius v2.2 ... On 2.2, the Input Packets 64 is in Hexadecimal.
v2 doesn't support 64-bit integers. Alan DeKok.
participants (2)
-
Alan DeKok -
Nicolas Breuer