No access TrueNAS from VM

[truefriend-cz]

Hello,

i have TrueNAS on HW connected to router. I can't connect to IP hardware running TrueNAS.
TrueNAS (have IP 192.168.55.4) and on TrueNAS is installed Virtual Machine with Windows (have IP 192.168.55.17) and all settinghs is in default configurations.
If i opening file Explorer in VM Windows and add "\\192.168.88.4" not a show any shares on TrueNAS. But from other hosts in LAN it is not a problems with access to share.

Ping to 192.168.55.4 from VM Windows same problem (not accessible)

Where is problem? How i can fix this?

Tested on:
TrueNAS 12 Core
TrueNAS 22 Scale

 

[Patrick M. Hausen]

Post the output of ifconfig of your TrueNAS host and of ipconfig /all of your Windows VM, please.

 

[truefriend-cz]

Post the output of ifconfig of your TrueNAS host and of ipconfig /all of your Windows VM, please.

ifconfig from TrueNAS:

Code:

root@truenas[~]# ifconfig
igb0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=a520b9<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6>
        ether 5c:ba:2c:22:bd:9c
        inet 192.168.55.4 netmask 0xffffff00 broadcast 192.168.55.255
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
        nd6 options=1<PERFORMNUD>
igb1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=e527bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
        ether 5c:ba:2c:22:bd:9d
        media: Ethernet autoselect
        status: no carrier
        nd6 options=1<PERFORMNUD>
igb2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=e527bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
        ether 5c:ba:2c:22:bd:9e
        media: Ethernet autoselect
        status: no carrier
        nd6 options=1<PERFORMNUD>
igb3: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=e527bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
        ether 5c:ba:2c:22:bd:9f
        media: Ethernet autoselect
        status: no carrier
        nd6 options=1<PERFORMNUD>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
        inet 127.0.0.1 netmask 0xff000000
        groups: lo
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
pflog0: flags=0<> metric 0 mtu 33160
        groups: pflog
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 02:0d:ee:1d:d3:00
        id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
        maxage 20 holdcnt 6 proto stp-rstp maxaddr 2000 timeout 1200
        root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
        member: vnet4 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 8 priority 128 path cost 2000000
        member: vnet0.3 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 9 priority 128 path cost 2000
        member: igb0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 1 priority 128 path cost 20000
        groups: bridge
        nd6 options=1<PERFORMNUD>
vnet0.3: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        description: associated with jail: Plex as nic: epair0b
        options=8<VLAN_MTU>
        ether 5e:ba:2c:31:41:ea
        hwaddr 02:83:2f:45:85:0a
        groups: epair
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
        nd6 options=1<PERFORMNUD>
vnet4: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=80000<LINKSTATE>
        ether fe:a0:98:61:8f:

ipconfig /all (image only)

 

[Patrick M. Hausen]

• disable auto boot for your jail and your VM
• reboot your TrueNAS
• navigate to Network > Interfaces, click "ADD"
• add an interface of type bridge, name it "bridge0"
• remove the IP address from igb0
• disable "hardware offloading" for igb0
• add "up" to the "Options" field of igb0
• add the IP address to the bridge0 interface
• click "TEST"
• click "SAVE"
• change the settings of your jail and your VM to connect to the "bridge0" interface
• start your jail and your VM

 

[truefriend-cz]

• disable auto boot for your jail and your VM
• reboot your TrueNAS
• navigate to Network > Interfaces, click "ADD"
• add an interface of type bridge, name it "bridge0"
• remove the IP address from igb0
• disable "hardware offloading" for igb0
• add "up" to the "Options" field of igb0
• add the IP address to the bridge0 interface
• click "TEST"
• click "SAVE"
• change the settings of your jail and your VM to connect to the "bridge0" interface
• start your jail and your VM

After this procedure show "Connecting to TrueNAS ... Make sure the TrueNAS system is powered on and connected to the network." and ended in complete unavailability of the server. Necessary reinstallation of the whole TrueNAS, failed to restore even from "Console setup" (option "1"), because the interface "bridge0" is not displayed (even after restarting the server) - only the hardware interfaces are displayed.

And bug: After click on TEST button and waiting "60" seconds is not reverted state network before changes.

Furthermore, I would not want the IP to be static but to be allocated dynamically by a DHCP server.

EDIT:

I am adding this step - after this is network ok:

• disable auto boot for your jail and your VM
• reboot your TrueNAS
• navigate to Network > Interfaces, click "ADD"
• add an interface of type bridge, name it "bridge0"
• in Bridge Settings in Bridge Members must select adapter "igb0"
• remove the IP address from igb0
• disable "hardware offloading" for igb0
• add "up" to the "Options" field of igb0
• add the IP address to the bridge0 interface
• click "TEST"
• click "SAVE"
• change the settings of your jail and your VM to connect to the "bridge0" interface
• start your jail and your VM

 

[Patrick M. Hausen]

I'm sorry, I missed that step, yes.

 

[truefriend-cz]

I am installed TrueNAS Scale. There aren't as many problems there as on TrueNAS Core.

I want to ask a would you know how I could set up for Bridge not to enter a static IP address but to assign an IP address from a router via DHCP the way it works before this change?

I'm sorry, I missed that step, yes.

 

[Patrick M. Hausen]

Of course - just enable DHCP for the bridge0 interface. In CORE - I have no idea how to setup all of this in SCALE. Which problems specifically do you mean? I run half a dozen of CORE systems with jails, VMs, all without problems. It's important to get the network configuration correct, though.

 

[truefriend-cz]

Of course - just enable DHCP for the bridge0 interface. In CORE - I have no idea how to setup all of this in SCALE. Which problems specifically do you mean? I run half a dozen of CORE systems with jails, VMs, all without problems. It's important to get the network configuration correct, though.

1. problem (BIG): Remote VNC and RDP freezing after xx seconds

Remote VNC freezing after xx seconds

On TrueNAS Core (only Core... on Scale is not problem) in VM machine (Windows) after runnin in VNC tab in browser after xx (20-90 sec.) freezing all mouse and keyboards access. If enabling RDP on VM OS and connected to RDP IP+PORT i have problem... disconnected from remote deskotop. And...

www.truenas.com

2. After create new VM with default config width UEFI boot for OS Windows
No booting from selected ISO... stucked on show only text console with startup.sh ... i must type "exit" and select manually "CDROM" from this. After booting from ISO ok. In TrueNAS Scala is booting from ISO automatically - no any text console.

3. TrueNAS Scala have a Docker - ideal for microservicess for "virtualy" microservers.... use minimal system resources (RAM, CPU, etc.)

4. Samba Server ... in TrueNAS Scale have a newver version, etc.

5. Active development. TrueNAS Scala has an active nightly channel. TrueNAS Core 12 has not released anything for a two years and is releasing new versions for version 13 only.

6. And a new problem that I have already mentioned. After clicking on the "TEST" button to test the network changes, it will not return to the original configuration after the specified time (60 seconds).
In TrueNAS Scala, the settings return OK and you can continue working.

 

[Patrick M. Hausen]

1. You must use VirtIO drivers for networking and disk. I run Windows 10 and server 2016 in production - absolutely no problems.
3. CORE has jails. Low overhead, ideal for virtual microservices.
5. SCALE nightly is the same development model as CORE 13 nightly. The equivalent to CORE 12 is the last SCALE release.
6. Worked for me every time.