Disabling DHCP and not setting an IPv4 static address while leaving auto configure IPv6 enabled results in no networking
You can set IPv6 name servers under System→Network→Network Configuration, but if you try to do the above change to disable DHCP you will be taken to another screen that marks IPv6 name servers as incorrect syntax
You can’t remove the IPv4 default route from the GUI
Not having an IPv4 default route causes Apps to fail initialisation
DHCP option 108 (IPv6-Only Preferred) is ignored
Is anyone running TrueNAS in an IPv6-only/IPv6-mostly network?
AFAIK, TrueNAS uses storj.io for their ISOs and updates. storj.io does not support IPv6.
So my guess is that you would have to manually uplaod the update files.
I’m running TrueNAS CORE in IPv6 environment and it seems to work fine. I do not use Apps, obviously.
Something I still am trying to figure out though that I do not think it supports is DHCPv6, so right now it’s just using SLAAC, which is kind of annoying.
Semi offtopic: Both points you guys described are IMHO just once again begging the question:
“Why don’t we just use normal netplan or networks and put a nice webGUI that generates the config file over it?”
You can’t do autoconfig on multiple interfaces, you can’t to mutliple DHCPv4, there is no DHCPv6 support and I don’t if and how it uses privacy extension.
Indeed, I was recently thinking of filing a feature request for that, and would happily upvote if someone else beats me to it.
I myself like systemd-networkd, as the configs are simple by but flexible. netplan might be a better fit for TrueNAS, as you noted, since perhaps they could more easily generate it the existing TrueNAS network configs. It doesn’t really matter which, IMO, so long as it’s something standard.
But in general, especially for IPv6, networking benefits from flexibility, and it’d be really nice to have a simple “just let me edit the network config manually” checkbox in the UI.
