Hello,
I have a problem with some CH6541 cable modems. When I check the dhcpd.lease file I see that the agent.remote-id field has not a normal value.
lease 10.90.173.101 {
starts 4 2014/10/16 17:37:48;
ends 0 2014/10/19 17:37:48;
tstp 0 2014/10/19 17:37:48;
cltt 4 2014/10/16 17:37:48;
binding state active;
next binding state free;
hardware ethernet 5c:35:3b:22:6e:2a;
uid "\377;\"n*\\5;\"n*";
option agent.remote-id "\\5;\"n*";
option agent.unknown-9 0:0:11:8b:6:1:4:1:2:3:0;
instead OK CH6541 have the following lease file result:
lease 10.90.220.80 {
starts 5 2014/10/17 04:01:20;
ends 6 2014/10/18 04:01:20;
tstp 6 2014/10/18 04:01:20;
cltt 5 2014/10/17 04:01:20;
binding state active;
next binding state free;
hardware ethernet 5c:35:3b:22:ce:56;
uid "\377;\"\316V\\5;\"\316V";
option agent.remote-id 5c:35:3b:22:ce:56;
option agent.unknown-9 0:0:11:8b:6:1:4:1:2:3:0;
}
Do you have any idea what can cause this problem?
Regards,
Dori
l
it is how the the string is being treated,
it is a binary string but because the first octet is an ascii char 5c or "\" so it treats the rest of the string as ascii
the mac address in question is
\ \5 ; \" n *
5c 05 3b 22 6e 2a
or
\\ 5 ; \" n *
5c 35 3b 22 6e 2a
depending on if the first backslash is escaping the backslash or the backslash is escaping the 5
Thank you kwesirunee for the reply.
What can we do to change this in the DHCP?
Regards,
Dori
nothing it is a display issue,
you would need to contact the developers to make it show as hex all the time.
you could write a sed filter to do it also, but been a long time so can't help with that, but basically you would cat the file and pipe it to sed, sed would detect for lines that don't have separated by colon mac addesses in hex and would use regular expressions to reformat them.