Unable to connect to SMB from a running VM inside Truenas

[groenator]

I built a new VM inside my TrueNas scale running Fedora KDE.

When I try to connect to my SMB share, the VM won't connect to my truenas share because the destination is unreachable.

Inside the VM I can ping anything from my local network, except I cannot ping my TrueNas Server.

Truenas server ip: 192.168.1.10

Code:

ARP table:

[titan@fedora ~]$ arp -n
Address                  HWtype  HWaddress           Flags Mask            Iface
192.168.1.253            ether   52:54:00:d5:79:4c   C                     ens3
192.168.1.254            ether   00:a0:98:67:35:ff   C                     ens3
192.168.1.10                     (incomplete)                              ens3
192.168.1.60             ether   00:e0:4c:98:25:a4   C                     ens3
192.168.1.191            ether   f0:18:98:48:e1:5e   C                     ens3
192.168.1.1              ether   14:3c:c3:fd:b9:89   C                     ens3
[titan@fedora ~]$

Route INFO:
[titan@fedora ~]$ ip route show
default via 192.168.1.1 dev ens3
default via 192.168.1.1 dev ens3 proto dhcp metric 100
192.168.1.0/24 dev ens3 proto kernel scope link src 192.168.1.203 metric 100

Running a traceroute to my Truenas:
traceroute 192.168.1.10
traceroute to 192.168.1.10 (192.168.1.10), 30 hops max, 60 byte packets
1  fedora (192.168.1.203)  1105.561 ms !H  1105.521 ms !H  1105.512 ms !H


Running a tracerout to my pihole:
[titan@fedora ~]$ traceroute 192.168.1.254
traceroute to 192.168.1.254 (192.168.1.254), 30 hops max, 60 byte packets
 1  192.168.1.254 (192.168.1.254)  0.907 ms  0.791 ms  0.637 ms

Someone, please explain what is happening here? I did choose the network to be bridge between the NAS and the VM.

Regards,

 

[morganL]

You'll need to document your bridge set up. I assume there is an external IP address on the bridge.

there are a few other threads on the same topic.... it good to refer to the one you are following.

 

[groenator]

Can you share the topics?

The vm IP is 192.168.1.203. What do you mean by documenting the bridge?

 

[morganL]

One of the earliest threads was this:

SOLVED - VMs can't see host

Hey, so I'm currently switching from TrueNAS 12.1 Nightlies to SCALE Nightlies. So far I only saw a few bugs here and there. But It does work. The only problem that I have right now is that my VMs can't see my host aka. TrueNAS. For example, my pihole-vm has the IP 192.168.188.21 and my...

www.truenas.com

Search for the terms and you will find others. Please note how the networking setup was described. Its only if you describe your actions in setting it up, can someone workout what should be done differently. We do plan to improve documentation in this area.

 

[groenator]

Thanks for your help!

 

[morganL]

Let us know if it worked and what the resolution was for you.

 

[groenator]

Yeah! I looked it but I wasn't keen to apply those settings. I need to investigate more.

 

[groenator]

Let us know if it worked and what the resolution was for you.

Someone tried the same settings and it broke the bond0 interface. Now the VMs can't connect to each other. See the reply in the post you sent me.

 

[morganL]

There's a few other threads to search through... you'll have to see if any match your config.
Its on the list for improved documentation.... but we're still at BETA phase.

 

[groenator]

Thats one of the reason I won't spend much time and waiting to get out of beta. Hopefully, this would improve sooner. The next release is next Tuesday. I am really looking forward for that.

 

[morganL]

The documentation on this issue is now available: https://www.truenas.com/docs/scale/virtualization/accessingnasfromvm/

 

[teg]

When following the guide, I will lost connection when activating settings. It seems not to be working?

 

[morganL]

When following the guide, I will lost connection when activating settings. It seems not to be working?

Sorry ro hear. if you could write up the steps you took...and how it breaks, it would be very useful to see if its a documentation issue, configuration issue or bug.

Has anyone elee had issues with this?

 

[teg]

Sorry ro hear. if you could write up the steps you took...and how it breaks, it would be very useful to see if its a documentation issue, configuration issue or bug.

I removed IP address from VM's parent interface (eno1). It has a static IP and . This interface is only physical interface which is in use in my TrueNAS . I added a br0 interface and set IP address for it and added eno1 to bridge members. When I test changes, I will lost connection to my TrueNAS.

 

[teg]

This seems to be similar issue: https://www.truenas.com/community/threads/bridge-connections-not-working.96555/

 

[teg]

If I connect another physical ethernet to the bridge and add to the VM another NIC connected to the bridge, I'm unable to access SMB shares in TrueNAS. The problem exists only if I try to bridge the only physical interface which my TrueNAS uses for normal operation.