SOLVED VM on bridge network ONLY has access to host

[HaveYourPhil]

Following the various guides and forum posts about setting up a bridge network so that VMs can reach both the network/internet and the TrueNAS host, I have done exactly that, however, my VMs are now able to connect to TrueNAS but NOT anything else on the network. Not even the gateway (192.168.0.1). Any help on this would be really appreciated, I've spent 2 days trying different combinations of setting up bridges etc... I've tried to include all relevant information in the screenshots and descriptions below but happy to share more in-depth details as required.

Hardware​

CPU: Intel i7-8700
Motherboard: Gigabyte Z390i Aorus (mini-ITX)
Memory: 32GB DDR4
Network Controller: Intel I219-V
Storage: Broadcom HBA 9500-8i with 4x Crucial MX500 2TB

Networking Settings​

br0 is setup as a bridge network with a static IP and eno2 as its only member. Default Gateway and Nameservers set manually after following these steps in the "physical" CLI (keyboard & monitor):

1. Create bridge network with eno2 assigned. Restart.
2. Remove IP Alias from eno2 and assign to br0. Restart.
3. Unset the Default Gateway and Nameservers. Restart.
4. Confirm that TrueNAS can ping 192.168.0.1 but not 1.1.1.1.
5. Set Default Gateway and Nameservers (as per screenshot above). Restart.
6. Confirm that TrueNAS can reach internet (by checking for updates and pinging 1.1.1.1)
7. Confirm that Containers can reach internet (curl google.com from container shell)

The resulting network config:

So far everything is working as expected; TrueNAS has full network/internet access, Apps have network/internet access and I have a bridge network, so I can start setting up VMs with access to the TrueNAS host. I have also tried doing all of the above (minus some of the restarting) in the GUI with the same outcome.

VM Settings​

And the result in the Windows 10 VM is that it fails to get an IP:

(Note that the windows VM seems to think my speed is 10Gbps but the physical interface is only 1Gbps)

Assigning the network settings manually gets me this:

So now it looks like I'm receiving packets finally but still no network access. I'm able to ping the TrueNAS host but that's it; not the gateway, nor 1.1.1.1:

Summary​

• Setup bridge network to allow VM<->Host network access
• TrueNAS and Apps working just fine
• VM can ping TrueNAS Host
• VM cannot access rest of network

Thank you so much for any help you're able to give!

 

[DaSnipe]

I'd enable the two sysctl values to reach the rest of your network. You might only need the first one but some Charts/Apps need both

How-To | TrueCharts

This is a quick how-to or setup-guide to have a local Wireguard server using on your TrueNAS box.

truecharts.org

 

[HaveYourPhil]

You're a legend! Thank you so much, that's done the trick.

For anyone else facing the same issue, it only required net.ipv4.ip_forward (but did work with both) and after a reboot, my VM was able to get an IP via DHCP and access the internet.

Show

Thank you again, DaSnipe.