Truenas Scale lost internet connectivity after ipv6 enabled on router

TrueNAS General
1

Hello everyone. As per the title I have enabled IPV6 support in my router. I had to do it while installing a crappy ezviz security camera. This allowed me to install the camera but I noticed that my truenas server could no longer send me emails… and then it could no longer see updates and then it could no longer install any applications and finally that all applications and the entire server had lost internet access. The first thing I thought to do was to put things back as they are on the router but nothing changed. I have done several reboots of the server and the router itself but the situation is the same. I also tried to enable IPV6 support in the server and entered a google dns address in ipv6 format but the situation is the same. I absolutely do not understand how this could have happened and I have no idea how to solve it. The ideal would be to be able to keep IPv6 active in the router so I can use the security camera but if it were not possible (and I don’t see the reason but never mind) I am willing to throw the newly purchased camera in the garbage just to restore the functionality of the TrueNAS server.

image
image877×468 14.5 KB

ping doesn’t work, no results, no errors. it stay like this forever even if I ping a local address
If I ping www.google.com this is the result:
image
image828×588 17.9 KB

image
image759×849 17.4 KB

image

image
image973×742 42.2 KB

image
image818×1124 40.5 KB

I’m totally lost here…
Any advice?
Thank you!

2

Do you have IPv6 internet connectivity, or only IPv6 on your LAN?

You appear to have put the Google IPv6 DNS address into the IPv6 default gateway field of the Global Confirguration. This is clearly NOT a default gateway.

If your internet connection has IPv6 connectivity, then you need to put your router IPv6 address in the IPv6 Default Gateway field, otherwise if no IPv6 internet leave it blank.

3

Yes, you are right, that address there was just a desperate test. At the beginning I put there my router ip. Anyway, I tried to test my ipv6 connectivity with an online test and I guess I dont have it. I tried leaving blank the field you told me and repeated the test and the situation didn’t change a bit…

image
image1324×873 76.7 KB

4

I mean: I repetead the tests on the server!

5

After clearing the IPv6 Default Gateway field and saving, did you reboot?

Additional advice, put 1.1.1.1 or 8.8.8.8 or (my personal choice) 9.9.9.9 as the first DNS entry, and your router second.

6

Ok, I changed the order (actually the order was the one you pointed out, I exchanged it during one of many tries). I rebooted and nothing has changed, still zero connectivity :sob:

7

Why would a camera require IPv6 instead of simply supporting it as an option?
The camera requiring it makes me wonder if it’s for nefarious reasons.

8

This thing really surprised me… But the brand is quite well known so I’m not sure.
Anyway I doubt that this thing decided, among all the things to possibly do, just to mess up my truenas server.

9

I think we are going to have to go CLI to diagnose the cause, and I doubt we will work out a fix until we have done that diagnosis.

Can you try the following commands and post the results here please (each command’s output in a separate </> box):

  • ip address show enp8s0
  • ip route list
  • ip route get 33.33.33.33
10

ip address show enp8s0
2: enp8s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 60:45:cb:a0:85:12 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.14/24 brd 192.168.0.255 scope global dynamic enp8s0
valid_lft 73358sec preferred_lft 73358sec
inet6 fe80::6245:cbff:fea0:8512/64 scope link
valid_lft forever preferred_lft forever

admin@truenas[~]$ ip route list
default via 192.168.0.1 dev enp8s0
172.16.0.0/24 dev docker0 proto kernel scope link src 172.16.0.1 linkdown
172.16.1.0/24 dev br-0067789be435 proto kernel scope link src 172.16.1.1
172.16.2.0/24 dev br-2144260d1b65 proto kernel scope link src 172.16.2.1
172.16.3.0/24 dev br-0f4243dd7d43 proto kernel scope link src 172.16.3.1
172.16.4.0/24 dev br-980d281819d5 proto kernel scope link src 172.16.4.1
172.16.5.0/24 dev br-f924e95aceb5 proto kernel scope link src 172.16.5.1 linkdown
172.16.6.0/24 dev br-6b0bc5f21bc4 proto kernel scope link src 172.16.6.1
172.16.7.0/24 dev br-2f3ac66c9b27 proto kernel scope link src 172.16.7.1
172.16.8.0/24 dev br-606665b53b11 proto kernel scope link src 172.16.8.1
172.16.9.0/24 dev br-1970d080f106 proto kernel scope link src 172.16.9.1
172.16.10.0/24 dev br-f6b198554152 proto kernel scope link src 172.16.10.1
172.16.11.0/24 dev br-599ca3b10cdc proto kernel scope link src 172.16.11.1
172.16.12.0/24 dev br-09b3ba80ac72 proto kernel scope link src 172.16.12.1 linkdown
172.16.13.0/24 dev br-2cfab49b6d36 proto kernel scope link src 172.16.13.1
172.16.14.0/24 dev br-ec514ca3af6b proto kernel scope link src 172.16.14.1
192.168.0.0/24 dev enp8s0 proto kernel scope link src 192.168.0.14

admin@truenas[~]$ ip route get 33.33.33.33
33.33.33.33 via 192.168.0.1 dev enp8s0 src 192.168.0.14 uid 950
cache

11

This suggests that packets to internet addresses will indeed be sent to your router and that the internet ping to an ipaddress should work.

If it doesn’t, then I have no idea why.

12

Hi, old problem but I have some updates. Hopefully these will shed some light.

I managed to solve the problem a couple of weeks ago. How? The only thing I did has been disabling dhcp and put in the corresponding windows the ip address that I have reserved in my router for server (192.168.0.14).
As I said everything started to work normally and immediately. This until yesterday when a blackout forced my router and server to reboot (obviously all the changes made were saved, so at the restart nothing should have been changed) and the initial problem was there again. No Internet connection, dns not working. And this time the previous trick didn’t work anymore.
But this time I noted something that I didn’t realize the first time. The server is unable to ping the gateway (192.168.0.1). I can ping everything on my lan, I can access everything on the server from any client on the lan but if I try to ping it from the router it doesn’t work.
I don’t know if this could help here someone diagnosing what is going on or if it makes the entire thing even more absurd… You really are my last hope… :roll_eyes::expressionless::confused: