SLAAC config happens when it shouldn't

Rather annoyingly, “Bug Clerk” closed a ticket I raised when I believe it shouldn’t have.

Here is the detail.

Summary:

I have VLAN interfaces, and even with “autoconfigure IPv6” unchecked, SLAAC still occurs on the interfaces. I had to do a tunable for net.ipv6.conf.vlan1.accept_ra to set it to 0 to fix.

I saw Jira PR 16443, my system doesn’t have that PR but accept_ra was still set to 2 – a very bad default!

My further (probably onto deaf ears) response:

With “Autoconfigure IPv6” unticked, the interfaces should not autoconfigure, including listening to RA, and installing SLAAC addressing!

The documentation here clearly states:

Clear the DHCP checkbox, then select Autoconfigure IPv6 if you want to create the IP address using SLAAC. This automatically configures the IPv6 address. You can only use this option one time to configure an IPv6 address for the system.

And as I mentioned, you are setting accept_ra 2 to, and as per here, that means “2 Overrule forwarding behaviour. Accept Router Advertisements even if forwarding is enabled.”

Can the ticket be re-opened? Anyone else experiencing this issue?

1 Like

Same, and have also raised tickets for it but to no avail. IPv6 is broken and seems a low priority to fix.

1 Like

Thanks for your input. So you experience the exact same issue as I describe (re SLAAC), or related to other autoconf stuff like DHCPv6?

Would be nice for an IX person to stick their beak in here; I don’t think IPv6 is broken in TrueNAS, but some small issues need attention.

Several others have confirmed the issue and there has been threads on it, e.g. TrueNAS Scale and IPv6

1 Like