Truenas has no connection outside LAN, but kubernetes/apps do

[Mulde]

Hello. Thanks for stopping by :D

First of all, i recently made a FRESH TrueNAS-SCALE-22.02.4 install on a HP proliant microserver gen8 that has been running Truenas CORE for a few years without issues. I have seen a few similar problems to the one i am about to describe, which have been solved, but i find that the solutions do not solve my problem. So here goes.

For a few minutes, maybe an hour, after a reboot of the server everything is fine. I can add catalogs, install/update apps and even update Truenas. My issue is that Truenas looses the ability to communicate with anything outside my LAN shortly after a reboot. Like it forgets its DNS's or something. nslookups times out and ping www.google.com fails because it cannot resolve the host. ping <some ip> hangs until i cancel it, with 100% packet loss.
Weirdly enough the apps still have a connection outside my LAN. Plex is working fine, both playing videos locally and remotely and downloading cover art. Sonarr is able to successfully search for shows. In the containers i am able to make nslookups and ping successfully.
I am able to install new apps. Maybe somehow kubernetes has no problem pulling images etc, while Truenas does not have access to anything outside LAN?
I found similar posts where most issues was solved by configuring the default ipv4 gateway, nameservers and even the /etc/resolv.conf file. I tried configuring these too but no luck.
I have manually set 8.8.8.8 as nameserver, and pointed to DHCP server/router as nameserver (as seen in picture). No difference.

Any ideas??
Thank you in advance!

 

[Mulde]

I am sorry. I am NOT able to install new apps:
Failed to pull image "emby/embyserver:4.7.6.0": rpc error: code = Unknown desc = Error response from daemon: Get "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io: no such host

But apps can ping. Here is an example ping from an esphome container:
# ping www.google.com PING www.google.com (142.250.186.100) 56(84) bytes of data. 64 bytes from fra24s06-in-f4.1e100.net (142.250.186.100): icmp_seq=1 ttl=114 time=20.3 ms 64 bytes from fra24s06-in-f4.1e100.net (142.250.186.100): icmp_seq=2 ttl=114 time=20.6 ms 64 bytes from fra24s06-in-f4.1e100.net (142.250.186.100): icmp_seq=3 ttl=114 time=20.4 ms ^C --- www.google.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 20.348/20.456/20.631/0.124 ms

 

[Mulde]

Yep.. This was of course a me thing. Turns out i had enabled "Host networking" on one of the containers that i run a VPN with. AND i had not specified the kill switch IP ranges to whitelist. I did not need host networking, so i disabled it, and configured the ip ranges to whitelist, and problem solved.