Unable to connect or ping from Truenas 25.10.4 - Goldeye to external sites

TrueNAS General
1

I rebooted my Truenas system after a long time of it being up and it didn’t come up properly. I tried to restore form a backup and that didn’t help. I think the problem is more with my router than Truenas, but I need some advice on troubleshooting.

I have tried several reboots, etc. I compared the network settings between my production and backup Truenas systems. I can connect to outside sites and ping them from the backup machine, just not the production machine.

Using or pinging internal sites works fine. On external sites it doesn’t matter if I use the FDQN (www.google.com) or the IP address (8.8.8.8) .

truenas_admin@truenas[~]$ ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
From 192.168.1.84 icmp_seq=1 Destination Host Unreachable
From 192.168.1.84 icmp_seq=2 Destination Host Unreachable
From 192.168.1.84 icmp_seq=3 Destination Host Unreachable

I have IPv6 running and before the reboot I could use the IPv6 address to connect to Truenas and pinging a FQDN often used IPv6 instead of IPv4. After this hassle the server doesn’t get a IPv6 address even though it shows a proper IPv6 gateway and the network settings have autoconfigure IPv6 turned on.

Here is a trace

truenas_admin@truenas[~]$ traceroute 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets
1 truenas.endry.net (192.168.1.84) 2817.959 ms !H 2817.922 ms !H 2817.903 ms !H
truenas_admin@truenas[~]$

The firewall rules for the production server match the backup server. The backup server is running the beta 26.0.0-MASTER+20260702-020147, but otherwise settings on the servers and the router match. The backup server does get a IPv6 address. The firewall rules on the router for both devices are the same.

Any troubleshooting advice would be appreciated.

2

Your NAS is missing a default gateway, probably.

3

Thanks for the suggestion. It has both a IPv4 and IPv6 gateway. Both match the gateway addresses on the backup system.

4

Do the netmasks/prefix-lengths match?

5

Additionally can you ping the gateway from the NAS?

6

Thank you. It has the router as both the IPv4 and IPv6 gateway, but it sure acts as if the IPv4 gateway isn’t set. see next reply.

7

Thank you. Yes, I can ping the gateway and all internal addresses. I just changed the IPv6 setting to autoconfigure on the bridge vs the NIC and now I can ping external IPv6 addresses too. That isolates it to not being to ping IPv4 external addresses and that is likely what is causing the app catalog refresh to fail.

8

To restate my problem after some tweaking. I am ok on IPv6, but I can only ping or connect to internal IPv4 addresses, not external ones. The server’s IPv4 address is the same as it has always been, the gateway is 192.168.1.1 which is the router and I can ping 192.168.1.1. I can’t ping external sites with FQDN or the IPv4 address. Traceroute ends at the server’s address .84.

traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets
1 truenas.endry.net (192.168.1.84) 3054.845 ms !H 3054.780 ms !H 3054.752 ms !H

9

The problem is now fixed. I had a bridge setup for a VM and that was causing the issue. I also have 2 NICs on the server and that made it more difficult to diagnose. I was able to focus everything including the VM on one NIC, disable the bridge, unplug the second NIC and that cleared it. It wont let me delete the bridge, but it is disabled.