TrueNAS CORE 13.0-U6.1 and DHCPv6

[vlhjkasnkl31]

For the life of me, searching these forums, Google, etc., I can't seem to find a mention of DHCP6 configuration (client) for TrueNAS Core.

I see the autoconf option, but that's not it. For reference, super familiar w/FreeBSD and IPv6, using and contributing to pfSense as an example.

RAs are being sent within the network, other hosts are just fine, etc.

Thanks for your time.

 

[vlhjkasnkl31]

In lieu of an edit above, I suppose the problem is TrueNAS, while having dhclient (that doesn't support IPv6), does not have dual-dhclient (or any other DHCPv6 supporting means?

This seems like a pretty big oversight given https://www.truenas.com/blog/truenas-facilitates-the-transition-to-ipv6-only/

 

[Patrick M. Hausen]

SLAAC does not work for you?

 

[vlhjkasnkl31]

SLAAC does not work for you?

Technically, or by design? By design, no, environment is DHCP-based. Had planned to reserve c/o DUID like other systems.

SLAAC and local .local resolution would be great for now while full DHCP w/managed options got sorted, but as an aside, when I had autoconf enabled, I wasn't able to reach the LLA on the adapter from other hosts. Still hadn't figured that out.

tl;dr, DHCP w/managed settings (route, DNS, NTP, et al.) is what I'm after.

Thanks for your reply.

 

[Patrick M. Hausen]

I'm running SLAAC everywhere without problems. DNS resolution is via v4 only, though. Because I'm lazy.
Also: Avahi in every single jail and VM.

I wasn't able to reach the LLA on the adapter from other hosts. Still hadn't figured that out.

Did you add the scope when pinging from those other hosts? fe80::dead:beef:dead:beef%<interface-name>

 

[vlhjkasnkl31]

I'm running SLAAC everywhere without problems. DNS resolution is via v4 only, though. Because I'm lazy.
Also: Avahi in every single jail and VM.


Did you add the scope when pinging from those other hosts? fe80::dead:beef:dead:beef%<interface-name>

re: scope, yes indeed, but I had fat fingered the interface, oops.

So SLAAC is working fine, although still looking for DHCP for the managed aspects. Speaking of, looks like my problem could have been summed up better as "TrueNAS CORE and IPv6 RA M flag not working, A works fine".

 

[ObiTobi]

I'm using dual stack - IPv4 and IPv6 in my network. All works fine for me with TrueNAS (except IPv6 default router will not be set. I have created small script for this)
I'm running 13.0-U5.3