Virtual Machine Networking Issue

[anonymous4519576]

I have been spinning my wheels on this for days, so I'm starting to get annoyed. I have the following config:

10.0.0.15 is the main address TrueNAS uses for the webUI, and 10.0.0.249 is one I attempted to assign to a VM as the NIC. (Also yes, the NICs ID in the device list is not the same as any other ID, so thats not the issue)

I plan to have a VM that runs a webserver that is not the same as the TrueNAS servers IP (tried bridging, ended up forwarding the TrueNAS portal, which was very bad), but for some reason from the VM I can't get it to reach the outer internet. From my home network I can SSH in and use it, but I can't ping anything else.

At this point I don't know what the problem is. My router has the IP set up properly so its not a router issue. Any suggestions?

ZFS configuration: RAID-Z2
System: Dell R710
CPUs: 2 Intel Xeon X5675
RAM: 18 sticks of Hynix Hmt351r7efr4a-h9 4GB
RAID card: Dell H700
Boot Drive: Kingston A400 120GB
Cache Drive: Samsung 980 1TB
Main Drives: Five Seagate Exos X16 14TB
Addon NIC: Intel X540-AT2
TrueNAS version: TrueNAS-SCALE-22.12.0

 

[Basserra]

Try making a 'bridge' interface in TN's network configuation page and link your desired NIC as a member to it. Then use the 'br#' as the NIC in the VM config.

It's been a long time for me so I don't remember what problems I had with it before. But, I do not have an IP set on my physical NIC in TN but I assigned the IP to the bridge interface that is both linked to the NIC and is used for the VMs. If you get into VLANs, it's similar. Make a VLAN interface with the physical as a parent, then a bridge interface with the VLAN as a member, and the host IP set on the bridge not the physical nor vlan.

 

[Basserra]

ended up forwarding the TrueNAS portal

With a bridge interface and the VM having its own IP address, you should not run into this problem. However, you can also change the ports on either the VM's webserver or the TN webUI. It's not necessary for me to, but I have TN using ports 65080/65443, but without a reverse proxy then you have to add the port to the address of whatever is not 80/443 (i.e. https://192.168.1.1:65443)