Hi! Just wondering if I could get a hand with my new TrueNas Scale install that I am deploying as I seem to have run into a hiccup or two. I set up a new TrueNas scale install and after installing my first VM onto it (Kubuntu) I found that the VM could not see the host system in the network, even though it had full access to the entire LAN. After doing some research this seemed to be a common occurance for TrueNas Scale, and the solution was to create a network bridge, assign a static IP to it, and the assign the NIC on the host system as a member of the bridge.
I did this and everything appears to be working fine, however it now seems that anything I install within dockers/VMs inside TrueNas scale is npt acting as expected. My main issue is with my Plex install (inside a docker) as if I can fix that then I believe I will have a solution for everything. After installing plex, it is appearing that it has major issues being accessed outside of my local network. On the local network I can use the IP of the host system at the given port 32400 to access plex, however Plex is not directly accessible outside my network.
I believe this is because Plex has been assigned an IP by the network bridge of the host and the router doesnt know about this virtual network so it cannot route traffic to it. My solution is to set up a static route from the 192.168.0.1/24 network (my router's LAN) to the 172.16.0.1/24 network which I believe to be the LAN that the bridge is assigning addresses from.
Is my approach correct? Also is there any way from the terminal of the host nas that I would be able to explicitly check what the IP address range the bridge is assigning to my applications. the 'ip a' command gives me alot of info but it is very hard to decipher.
I did this and everything appears to be working fine, however it now seems that anything I install within dockers/VMs inside TrueNas scale is npt acting as expected. My main issue is with my Plex install (inside a docker) as if I can fix that then I believe I will have a solution for everything. After installing plex, it is appearing that it has major issues being accessed outside of my local network. On the local network I can use the IP of the host system at the given port 32400 to access plex, however Plex is not directly accessible outside my network.
I believe this is because Plex has been assigned an IP by the network bridge of the host and the router doesnt know about this virtual network so it cannot route traffic to it. My solution is to set up a static route from the 192.168.0.1/24 network (my router's LAN) to the 172.16.0.1/24 network which I believe to be the LAN that the bridge is assigning addresses from.
Is my approach correct? Also is there any way from the terminal of the host nas that I would be able to explicitly check what the IP address range the bridge is assigning to my applications. the 'ip a' command gives me alot of info but it is very hard to decipher.
Code:
root@truenas[~]# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP group default qlen 1000 link/ether 00:e0:4c:bc:09:13 brd ff:ff:ff:ff:ff:ff inet6 fe80::2e0:4cff:febc:913/64 scope link valid_lft forever preferred_lft forever 3: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 9a:a8:73:47:85:bd brd ff:ff:ff:ff:ff:ff inet 192.168.0.100/24 brd 192.168.0.255 scope global br0 valid_lft forever preferred_lft forever inet6 fe80::98a8:73ff:fe47:85bd/64 scope link valid_lft forever preferred_lft forever 4: kube-bridge: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 7e:fd:4e:da:21:09 brd ff:ff:ff:ff:ff:ff inet 172.16.0.1/16 brd 172.16.255.255 scope global kube-bridge valid_lft forever preferred_lft forever inet6 fe80::bc41:d1ff:fefe:8ae6/64 scope link valid_lft forever preferred_lft forever 5: kube-dummy-if: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default link/ether 62:74:18:9e:9f:68 brd ff:ff:ff:ff:ff:ff inet 172.17.209.86/32 scope link kube-dummy-if valid_lft forever preferred_lft forever inet 172.17.0.1/32 scope link kube-dummy-if valid_lft forever preferred_lft forever inet 172.17.212.61/32 scope link kube-dummy-if valid_lft forever preferred_lft forever inet 172.17.0.10/32 scope link kube-dummy-if valid_lft forever preferred_lft forever inet 172.17.237.241/32 scope link kube-dummy-if valid_lft forever preferred_lft forever inet 172.17.73.180/32 scope link kube-dummy-if valid_lft forever preferred_lft forever inet 172.17.19.203/32 scope link kube-dummy-if valid_lft forever preferred_lft forever inet 192.168.0.100/32 scope link kube-dummy-if valid_lft forever preferred_lft forever inet6 fe80::70dc:94ff:fee1:5c66/64 scope link valid_lft forever preferred_lft forever 6: veth489673ed@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master kube-bridge state UP group default link/ether 36:0d:aa:5f:cf:5b brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet6 fe80::f028:9ff:fe24:666c/64 scope link valid_lft forever preferred_lft forever 7: veth5b6c7a59@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master kube-bridge state UP group default link/ether 06:02:2c:bb:e8:19 brd ff:ff:ff:ff:ff:ff link-netnsid 1 inet6 fe80::f03a:a5ff:fe71:c408/64 scope link valid_lft forever preferred_lft forever 8: vethb0fc7f9b@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master kube-bridge state UP group default link/ether fe:5e:61:f9:6d:c8 brd ff:ff:ff:ff:ff:ff link-netnsid 2 inet6 fe80::dc44:85ff:fef0:7791/64 scope link valid_lft forever preferred_lft forever 9: veth00984b0a@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master kube-bridge state UP group default link/ether be:4d:35:34:81:e6 brd ff:ff:ff:ff:ff:ff link-netnsid 3 inet6 fe80::6498:9dff:fe9d:1906/64 scope link valid_lft forever preferred_lft forever 11: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UNKNOWN group default qlen 1000 link/ether fe:a0:98:0c:1a:fa brd ff:ff:ff:ff:ff:ff inet6 fe80::fca0:98ff:fe0c:1afa/64 scope link valid_lft forever preferred_lft forever 12: veth01c1a9c1@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master kube-bridge state UP group default link/ether 2e:6d:6e:cd:9e:7d brd ff:ff:ff:ff:ff:ff link-netnsid 4 inet6 fe80::3c0e:78ff:fe4b:62da/64 scope link valid_lft forever preferred_lft forever 13: vethc0c0c9bd@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master kube-bridge state UP group default link/ether 3a:97:38:3e:80:85 brd ff:ff:ff:ff:ff:ff link-netnsid 5 inet6 fe80::ac14:16ff:fe76:99d0/64 scope link valid_lft forever preferred_lft forever 14: veth0006ef9e@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master kube-bridge state UP group default link/ether 46:c1:d1:65:31:4f brd ff:ff:ff:ff:ff:ff link-netnsid 6 inet6 fe80::5cea:14ff:fead:44be/64 scope link valid_lft forever preferred_lft forever 15: vetha74baa83@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master kube-bridge state UP group default link/ether 2a:4a:a2:d9:db:c4 brd ff:ff:ff:ff:ff:ff link-netnsid 7 inet6 fe80::2c57:d5ff:fe96:bc2c/64 scope link valid_lft forever preferred_lft forever