pfSense

ok, wow, I think those DUID values we show are straight from the dhcp leases file. Could be a bug in dhcpd.
Needs more research.

Where is this file? I'll check the DUIDs in it.

It's in /var/dhcp/var/db/dhcpd6.leases - but it's encoded.

It's possible there is a buglet in the parsing code, DHCP's encoding of that field is not something I am fond of at all.

It works for me on my Windows 7 box though, I added the DUID from the leases view and it does pick up and use that IP.

Got bored at work... don't tell the boss. Found the issue.

The awk clean pattern in status_dhcpv6_leases.php removes semi colons - gsub(";", "")

The encoded DUID has a semi colon in it - \333\272\244\016\000\001\000\001\023>\337;\244\272\333\003\177\272

Running the real DUID through parse_duid() works so I think this is the only issue. I assume someone removed semi colons for a valid reason?

Having thought about it a little more, it's probably to strip the ; from the end of the lines. Suggested fix is to add a $ to make gsub(";$", "")

Phil

Did you make and test that change? Did that make it show the proper DUID for you?

It does. Also had a look around and nothing appears broken as a result. To clarify, line 152ish of status_dhcpv6_leases.php changed to:

$cleanpattern = "'{ gsub(\"^#.*\", \"\");} { gsub(\"^server-duid.*\", \"\");} { gsub(\";$\", \"\"); print;}'";

Shouldn't need to escape the newly added $ unless you want to do so for clarity that it's not part of a variable.

I tried it on mine as well with a somewhat lengthy dhcpv6.leases file and it appears to have parsed everything OK still.

I committed the change, it should show up here momentarily.