Hello, I was on the latest Electric Eel Update (I think 24.10.2.1?) and I just upgraded to Fangtooth, and after doing so it is now telling me that my IP cannot access the UI???
I have SSH access, is there a way I can resolve this?
Edit I managed to regain access by disabling IPv6 on my laptop, so it seems that perhaps something has changed with regards to allowed IPv6 IPs???
I removed all Allowed IPs, I re-added allowed IPs, as soon as I add my IPv6 range again and enable IPv6 on my laptop I loose access again.
It seems to me that Fangtooth has a bug with allowing IPv6 blocks to have access.
I add second picture so you can see my allowed IPs, this was all working fine in Electric Eel
Do you have a second client device you can try, just to eliminate the laptop as the issue?
I’d suggest filing a bug report, but they’re most likely going to ask at some point if you can test it with a different client.
Yessir, bug is reported: Jira
Should not need second device as was working perfectly fine on Electric Eel, seems like a regression. I do have a second device but I think it needs to work on this device 
If they ask i can try but even if it works on a second device it still needs to work on this device so it doesn’t achieve much. The issue is not with my laptop, it did not change, TrueNAS changed.
And of course my IPv6 assigned is within the /48 block allocation I am allowing, so there can be no doubt.
There must not be many people using and allowlisting IPv6 eh?
@farkingjeebus It’s possible a bug in Fangtooth could cause that one specific device to fail at IPv6 communication with the TrueNAS server, which was why I asked. It could be some specific combination of configuration on the server and client that just doesn’t mesh, for instance.
And yeah, I suspect the number of people on this forum trying to allowlist IPv6 to be considerably smaller than the number of people using IPv4. For the small business and home/home office environment, v6 tends not to be worth the hassle LAN-side, IMO.
I have it enabled on my WAN, so my firewall has a public v6 address and can pull websites and other services that are v6 only, but it’s completely deactivated inside my LAN. It doesn’t really add any benefit beyond IPv4 at my scale, AT&T Fiber doesn’t officially support the address block size needed for Ipv6 VLANs (there’s a hack way around this that would put the internet service I use for work in an unsupported state), and devices I depend on in my network are either v4 only, or so old that I don’t trust their undocumented v6 auto-config to work.
It’s just a huge bucket of additional potential failure points for no tangible benefit inside my LAN. For now. 
It was working with Electric Eel. The only combination here is that I upgraded to Fangtooth and it ceased to work from that moment. Unless this is called out in the patch notes as a functional (expected breaking) change, this is what’s known as a regression and it should be fixed, thus the bug report I have lodged.
I have a lot of use for IPv6 on my LAN. I have many servers listening on 443 on my LAN ↔ WAN, and they are bound to an IPv6 address and proxied through Cloudflare which exposes them over dual stack IPv4/IPv6. This is just one great use which I am utilising IPv6 for on my LAN.
I have had literally zero issues or failures with IPv6 except for now this issue upgrading to Fangtooth, it doesn’t cause any problems for me at all the two networking stacks operate side by side and neither fails for me.
@farkingjeebus Check it out: Jira
Looks like a fix has been completed and is in testing to be rolled out in 25.04.1.
Thanks for taking the time to report it.
1 Like
