SOLVED No networking Debian bhyve

[HertogArjan]

Hi everyone,

I am trying to install Pi-hole to my freenas server and to do that I am trying to configure a VM to run Debian. I haven't got any experience with bhyve or VM's. I followed the tutorial by The Internet Monkey to set up a VM and got Debian working, although I have no network access at all from within the VM. During the Debian installation DHCP autoconfiguration does not work, the Debian mirrors can not be reached and I cannot ping google.com either. Pinging the network address of my freenas server or my gateway returns "Destination host unreachable".

The network interface used by my freenas system is called igb0, so that is the interface I setup iohyve with as well.

This is my ifconfig output:

Code:

igb0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 9000
		options=2400b9<RXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO,RXCSUM_IPV6>
		ether 0c:c4:7a:64:9c:bc
		inet 192.168.178.52 netmask 0xffffff00 broadcast 192.168.178.255
		nd6 options=9<PERFORMNUD,IFDISABLED>
		media: Ethernet autoselect (1000baseT <full-duplex>)
		status: active
igb1: flags=8c02<BROADCAST,OACTIVE,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 0c:c4:7a:64:9c:bd
		nd6 options=9<PERFORMNUD,IFDISABLED>
		media: Ethernet autoselect
		status: no carrier
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>
tap0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
		description: iohyve-PiHole
		options=80000<LINKSTATE>
		ether 00:bd:63:80:57:00
		nd6 options=9<PERFORMNUD,IFDISABLED>
		media: Ethernet autoselect
		status: active
		Opened by PID 64596
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9000
		description: iohyve-bridge
		ether 02:45:87:96:55:00
		nd6 options=1<PERFORMNUD>
		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: epair5a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
				ifmaxaddr 0 port 11 priority 128 path cost 2000
		member: epair4a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
				ifmaxaddr 0 port 10 priority 128 path cost 2000
		member: epair3a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
				ifmaxaddr 0 port 9 priority 128 path cost 2000
		member: epair2a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
				ifmaxaddr 0 port 8 priority 128 path cost 2000
		member: epair1a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
				ifmaxaddr 0 port 6 priority 128 path cost 2000
		member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
				ifmaxaddr 0 port 5 priority 128 path cost 2000
		member: igb0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
				ifmaxaddr 0 port 1 priority 128 path cost 20000
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 9000
		options=8<VLAN_MTU>
		ether 02:ff:20:00:05:0a
		nd6 options=1<PERFORMNUD>
		media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
		status: active
epair1a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 9000
		options=8<VLAN_MTU>
		ether 02:ff:20:00:06:0a
		nd6 options=1<PERFORMNUD>
		media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
		status: active
epair2a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 9000
		options=8<VLAN_MTU>
		ether 02:ff:20:00:08:0a
		nd6 options=1<PERFORMNUD>
		media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
		status: active
epair3a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 9000
		options=8<VLAN_MTU>
		ether 02:ff:20:00:09:0a
		nd6 options=1<PERFORMNUD>
		media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
		status: active
epair4a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 9000
		options=8<VLAN_MTU>
		ether 02:ff:20:00:0a:0a
		nd6 options=1<PERFORMNUD>
		media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
		status: active
epair5a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 9000
		options=8<VLAN_MTU>
		ether 02:ff:20:00:0b:0a
		nd6 options=1<PERFORMNUD>
		media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
		status: active

Can anyone tell me what I am doing wrong? In another topic someone mentioned he also had trouble connecting to his network and that he was able to fix it with the command 'ifconfig bridge0 addm tap0'. This would make a lot of sense since tap0 is currently not listed as a member of the bridge, however when I run the command the system returns "ifconfig: BRDGADD tap0: Invalid argument".

 

[m0nkey_]

Why does your bridge0 have a description set? It suggests you've tried to modify the interface manually.

Make sure the tuneables are correctly set to bridge the NIC and load the kernel module, then try rebooting your FreeNAS server.

If that's all good, then you may not be getting a DHCP assignment. You should try setting a static IP, route and DNS servers within your VM.

 

[HertogArjan]

I should've mentioned, I already tried setting up a static IP and that didn't work. I can only assume that just like jails the VM does not need to have the same IP as my freenas server. Otherwise getting Pi-hole to work will get difficult anyway. I did use kmod=1 and net=igb0.

I'm not sure what would have caused it to have a description set. I did enter mtu 9000 as an extra option for my igb0 interface to allow jumbo frames. Besides that I tried to add the tap0 interface to the bridge, with no succes. That is all I've done manually.

I'll try rebooting when I get home today and let you know if that worked or not.

EDIT: It did not.

EDIT2: Quite late with the update, but the problem resolved itself I guess. Not entirely sure why unfortunately. Could be because of the MTU, I did change it back to 1500. If anyone comes across the same issue in the future I'd recommend removing custom options like a different MTU and a reboot also never hurt anything. If that does not solve your issue, it is most likely something else.