Request to use the same hostnames assigned for ipv4 addresses with ipv6 addresse
If possible, it would be nice to be able to use the existing hostnames that may already be assigned to ipv4 addresses via static ip address dhcp assignments with the ipv6 dhcp assignments instead of defaulting to blank entries. Currently I have to open two tabs, one for the ipv4 entries and one for the ipv6 entries and match up the mac addresses before I'm able to identify who is who.
I would appreciate this being an option as well.
virgiliomi last edited by
If both forms of DHCP used the same identifier, then this would probably be easy. But since DHCP uses the MAC address and DHCPv6 uses the DUID (which, yes, I know usually contains the MAC address), this gets a bit harder to make possible.
I suppose pfSense could just have one large DHCP reservation table, with spaces for both IPv4 and IPv6 address, MAC address, DUID, and hostname… then split the info up as needed for the appropriate service files... but when you get into things like specifying DNS servers for a particular host, this also gets significantly more complicated (IPv4 vs. IPv6 DNS servers, etc.).
At this point in the process, nothing's going to change for pfSense 2.3. But there's always 2.4, which probably won't be too far off.
Ok. That makes sense.
Thanks for explaining.
It's definitely not anything critical(to me at least), just sounded like a nice-to-have option.
The odd thing is pfsense is already doing this for itself…
If I ping the pfsense hostname from a device that has ipv4 and ipv6 addresses, it pings the ipv6 address of pfsense. This means that pfsense has automatically added an AAAA hostname record for itself.
One question: Status -> DHCPv6 Leases shows the mac addresses of online interfaces. Is it pulling this from a ipv4 SQL table somewhere, or is it keeping separate volatile records purely for this part of the GUI? I'm wondering if I can migrate the hostnames with a SQL query.
Prioritizing ipv6 addresses when resolving hostnames would go a long way to help in the seemingly endless goal of migrating over to ipv6.
The DHCPv6 leases page pulls the MAC data from contents of the NDP table, it isn't found in anything directly from DHCPv6 currently.