Hey gang -
Here's my server:
1. I have the first tap interface for each VM get added to bridge0 so they can access my internal network here. Each time the VM boots or gets nuked and the tap interface is added or removed from the bridge, the interfaces that make up the lagg flap. Which causes the lagg interface to flap. Which causes the server to drop off the 'net for a few seconds. I read a back-and-forth thread on the kernel bugzilla:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221122
and it looks like there are a list of switches that can be added to the ifconfig line?
Am I misunderstanding that? Because it doesn't seem to matter. VM creation and/or deletion causes the lagg to flap which I just can't have happen. That's massively no bueno and I'm hoping there's a way to keep the lagg (and bridge) up? Any suggestions?
2. Once the VMs boot, they attempt to DHCP out. Nyet. The DHCP server (my FreeBSD router) doesn't see the requests at all, so it never replies. I can statically assign IP addresses to the interfaces and they have full network access. But the DHCP broadcasts aren't getting through. Is the bridge0 interface stomping on them? Or the lagg?
Help?
Thanks!
Here's my server:
- interfaces em0 and em1 bond together into interface lagg1
- interface lagg1 gets added to interface bridge0 to share the network with bhyve VMs
- IP address the server is applied to bridge0, not lagg1
1. I have the first tap interface for each VM get added to bridge0 so they can access my internal network here. Each time the VM boots or gets nuked and the tap interface is added or removed from the bridge, the interfaces that make up the lagg flap. Which causes the lagg interface to flap. Which causes the server to drop off the 'net for a few seconds. I read a back-and-forth thread on the kernel bugzilla:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221122
and it looks like there are a list of switches that can be added to the ifconfig line?
Code:
-tso -lro -toe -txcsum -txcsum6
Am I misunderstanding that? Because it doesn't seem to matter. VM creation and/or deletion causes the lagg to flap which I just can't have happen. That's massively no bueno and I'm hoping there's a way to keep the lagg (and bridge) up? Any suggestions?
2. Once the VMs boot, they attempt to DHCP out. Nyet. The DHCP server (my FreeBSD router) doesn't see the requests at all, so it never replies. I can statically assign IP addresses to the interfaces and they have full network access. But the DHCP broadcasts aren't getting through. Is the bridge0 interface stomping on them? Or the lagg?
Help?
Thanks!