Problem with networking in bhyve

[Deleted member 86555]

I have a newly installed FreeNAS-11.1-U5, because the usb drive died. The pervious usb was running was running FreeNAS-11.1-U4 and i didn't have this problem then. The problem is that networking doesn't work in my one and only vm, but it's only outbound that's not working. I can reach the vm over ssh and also ping it but i can not access the internet or any computer on the local network from the vm.

My freenas networking setup looks like this:
em0(igb0) < -- connected to lan subnet. ip from dhcp:192.168.1.188
em1(igb1) < -- connected to dmz subnet. has no ip but have tried with ip. subnet:192.168.2.0

bridge0 < -- bridge bettwen igb1 and tap0
tap0 < -- vm

I am relatively sure it's not a problem in the client vm's os because i have check the default rout and also booted in to a live-cd and tried to setup the network there with the same result. Which leads me to believe that the problem is in the setup of the interfaces on the freenas, all of the setup was done in the webui.

This is from freenas:
netstat -rn

Code:

Routing tables

Internet:
Destination		Gateway			Flags	 Netif Expire
default			192.168.1.254	  UGS		igb0
127.0.0.1		  link#3			 UH		  lo0
192.168.1.0/24	 link#1			 U		  igb0
192.168.1.188	  link#1			 UHS		 lo0

Internet6:
Destination					   Gateway					   Flags	 Netif Expire
::/96							 ::1						   UGRS		lo0
::1							   link#3						UH		  lo0
::ffff:0.0.0.0/96				 ::1						   UGRS		lo0
fe80::/10						 ::1						   UGRS		lo0
fe80::%lo0/64					 link#3						U		   lo0
fe80::1%lo0					   link#3						UHS		 lo0
ff02::/16						 ::1						   UGRS		lo0

ifconfig

Code:

igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
   options=6403bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
   ether d0:50:99:c1:88:6b
   hwaddr d0:50:99:c1:88:6b
   inet 192.168.1.188 netmask 0xffffff00 broadcast 192.168.1.255
   nd6 options=9<PERFORMNUD,IFDISABLED>
   media: Ethernet autoselect (100baseTX <full-duplex>)
   status: active
igb1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
   options=2400b9<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO,RXCSUM_IPV6>
   ether d0:50:99:c1:88:6c
   hwaddr d0:50:99:c1:88:6c
   nd6 options=9<PERFORMNUD,IFDISABLED>
   media: Ethernet autoselect (1000baseT <full-duplex>)
   status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
   options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
   inet6 ::1 prefixlen 128
   inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
   inet 127.0.0.1 netmask 0xff000000
   nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
   groups: lo
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
   ether 02:3b:59:e7:eb:00
   nd6 options=1<PERFORMNUD>
   groups: bridge
   id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
   maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
   root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
   member: tap0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
		   ifmaxaddr 0 port 4 priority 128 path cost 2000000
   member: igb1 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
		   ifmaxaddr 0 port 2 priority 128 path cost 20000
tap0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
   options=80000<LINKSTATE>
   ether 00:bd:18:6c:42:00
   hwaddr 00:bd:18:6c:42:00
   nd6 options=1<PERFORMNUD>
   media: Ethernet autoselect
   status: active
   groups: tap
   Opened by PID 33022

 

[Chris Moore]

Do you have MAC filtering on the router? The virtual MAC of the VM will have changed.

Sent from my SAMSUNG-SGH-I537 using Tapatalk

 

[Deleted member 86555]

Do you have MAC filtering on the router? The virtual MAC of the VM will have changed.

Sent from my SAMSUNG-SGH-I537 using Tapatalk

Thanks for the reply Chris. I checked and mac filtering is not turned on but is available. Any other ideas?

 

[dlavigne]

This was a bug that is fixed for U6: https://redmine.ixsystems.com/issues/33054. In the meantime, you could do an install of U4 into another boot environment as U4 was not affected by this bug.

 

[Deleted member 86555]

This was a bug that is fixed for U6: https://redmine.ixsystems.com/issues/33054. In the meantime, you could do an install of U4 into another boot environment as U4 was not affected by this bug.

Thanks