Tsaukpaetra
Patron
- Joined
- Jan 7, 2014
- Messages
- 215
Build FreeNAS-11-MASTER-201704280408 (83eff7b)
I have a Windows VM all set up and configured, and it seems to work well accessing the network and the internet in general, but when I try to access network services on the host FreeNAS server, it inexplicably fails. Basically, it can find it (by virtue of DNS), but any connections don't connect, as if the box were unplugged (note, not refused, TCP connections just timeout).
I'm thinking this might be an issue with how the host side complains about setting link properties:
If that's the case, I think I could get away with forcing the VM in question (at the moment I only have one) to use one of the unused ethernet ports on the server instead, but I can't try this because there's no such configuration option in the FreeNAS 11 UI...
Any hints?
I have a Windows VM all set up and configured, and it seems to work well accessing the network and the internet in general, but when I try to access network services on the host FreeNAS server, it inexplicably fails. Basically, it can find it (by virtue of DNS), but any connections don't connect, as if the box were unplugged (note, not refused, TCP connections just timeout).
I'm thinking this might be an issue with how the host side complains about setting link properties:
Code:
root@bob:~ # tail /var/log/messages Apr 29 14:41:06 bob kernel: bridge0: link state changed to DOWN Apr 29 14:41:06 bob kernel: bridge0: link state changed to DOWN Apr 29 14:41:06 bob bridge0: error setting interface capabilities on lagg0 Apr 29 14:41:06 bob kernel: bridge0: link state changed to UP Apr 29 14:41:06 bob kernel: bridge0: link state changed to UP Apr 29 14:41:06 bob kernel: cxl0: promiscuous mode enabled Apr 29 14:41:06 bob kernel: cxl1: promiscuous mode enabled Apr 29 14:41:06 bob kernel: lagg0: promiscuous mode enabled Apr 29 14:41:07 bob kernel: tap0: link state changed to UP Apr 29 14:41:07 bob kernel: tap0: link state changed to UP
If that's the case, I think I could get away with forcing the VM in question (at the moment I only have one) to use one of the unused ethernet ports on the server instead, but I can't try this because there's no such configuration option in the FreeNAS 11 UI...
Any hints?