After the last upgrade to TrueNAS SCALE 23.10.1, my apps have no connection to the internet anymore.
I currently use the NAS un 10.10.10.2 and use a bridge for my VMs, which has the IP addresses 10.10.10.2/24 and 10.10.10.10/24 attached to it.
The apps can ping to 10.10.10.2, but not to 10.10.10.1 for instance, nor anywhere else outside the NAS:
I can also connect to other apps from an app just fine.
Kubernetes settings:
Node IP: 10.10.10.2
Route v4 Interface:
Route v4 Gateway:
I also already tried changing the interface to my bridge and setting the gateway to 10.10.10.1, but without any positive effect.
Especially since it worked before the upgrade to 23.10.1, I’m curious whether that’s a bug in SCALE itself? Or do you have any other suggestion what’s possibly wrong here?
I currently use the NAS un 10.10.10.2 and use a bridge for my VMs, which has the IP addresses 10.10.10.2/24 and 10.10.10.10/24 attached to it.
The apps can ping to 10.10.10.2, but not to 10.10.10.1 for instance, nor anywhere else outside the NAS:
Code:
root@app:/# ping google.de PING google.de (142.250.186.131): 56 data bytes ^C --- google.de ping statistics --- 3 packets transmitted, 0 packets received, 100% packet loss root@app:/# ping 10.10.10.2 PING 10.10.10.2 (10.10.10.2): 56 data bytes 64 bytes from 10.10.10.2: seq=0 ttl=42 time=0.087 ms 64 bytes from 10.10.10.2: seq=1 ttl=42 time=0.066 ms ^C --- 10.10.10.2 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max = 0.066/0.076/0.087 ms root@app:/# ping 10.10.10.1 PING 10.10.10.1 (10.10.10.1): 56 data bytes ^C --- 10.10.10.1 ping statistics --- 4 packets transmitted, 0 packets received, 100% packet loss
I can also connect to other apps from an app just fine.
Kubernetes settings:
Node IP: 10.10.10.2
Route v4 Interface:
Route v4 Gateway:
I also already tried changing the interface to my bridge and setting the gateway to 10.10.10.1, but without any positive effect.
Especially since it worked before the upgrade to 23.10.1, I’m curious whether that’s a bug in SCALE itself? Or do you have any other suggestion what’s possibly wrong here?