I’m testing setup:
Mikrotik DHCP server Option82 + FreeRadius . Agent-Remote-Id, Agent-Circuit-Id incorrect format.
I mentioned that Agent-Remote-Id and Agent-Circuit-Id sent in some strange format with slashes.
Like :
Agent-Remote-Id = “\000\006\000\r\355!\244\200”
Agent-Circuit-Id = “\000\004\000\002\000”
And it should be like:
Agent-Remote-Id = 0006000ded21a480
Agent-Circuit-Id = 000400020000
How can I fix this issue. Because of that, I’ve to enter in Freeradius this strange string but not normal hex string seen mikrotik (but without columns). Or maybe someone knows what format it is and has rewrite script for FreeRadius policy.conf ? Maybe linux should have some special library for conversion such numbers ? Because there is other radius server “radiator” and it works as charm and shows this agent-IDs in his debug (accepts them) in already correct format, and it works on WinXP.
This I’ve mentioned in both Wireshark capture and FreeRadius debug output.
But view of same capture file in Centos (freeradius host) and win machine (my workstation) are different check screenshots:
packet from FreeRadius debug:
rad_recv: Access-Request packet from host 192.168.1.101 port 50213, id=4, length=143
NAS-Port-Type = Ethernet
NAS-Port = 2210402311
Calling-Station-Id = "1:0:c:42:40:40:38"
Called-Station-Id = "CLIENTS_pool1"
User-Name = "00:0C:42:40:40:38"
User-Password = ""
Agent-Remote-Id = "\000\006\000\r\355!\244\200"
Agent-Circuit-Id = "\000\004\000\002\000"
NAS-Identifier = "R1"
NAS-IP-Address = 192.168.1.101
packet seen by “Radiator” radius server:
Attributes:
NAS-Port-Type = Ethernet
NAS-Port = 2213543991
Calling-Station-Id = "1:0:c:42:40:40:38"
Framed-IP-Address = 192.168.3.156
Called-Station-Id = "CLIENTS_pool1"
User-Name = "00:0C:42:40:40:38"
User-Password = <230><182><134>I<22><196><196><178>\#<8>Uq<251><162><201>
RB-Agent-Remote-Id = 0006000ded21a480
RB-Agent-Circuit-Id = 000400020000
NAS-Identifier = "R1"
NAS-IP-Address = 192.168.0.22
