Open Drizzt321 opened 3 years ago
I'm having similar issues. After some digging through the forum, I think it's down to the untagged bridge somehow interfering with ARP traffic on the tagged bridge: https://forums.freebsd.org/threads/bridge-epair-not-passing-through-tagged-vlan-traffic-between-host-and-vnet-jail.71646/#post-437147
A quick test I did:
ifconfig bridge0 destroy
ping begins succeeding@BlueSpaceCanary what's your interface configurations? Are you talking about a bridge on the untagged interface, and a 2nd bridge on the tagged interface, and when you turn off the bridge on the untagged interface the tagged bridge starts working?
@BlueSpaceCanary so I think I reproduced what you're seeing. Bridge on igb0 and igb0.30, the VM doesn't connect with it. If I remove bridge on igb0, suddenly it works. Put the bridge back on igb0, and stops working.
@Drizzt321 Yeah, that's the exact setup I had, one on igb0 and one on igb0.100
@BlueSpaceCanary as per https://genneko.github.io/playing-with-bsd/networking/freebsd-vlan/#do-not-bridge-the-parent-interface-of-the-vlans, looks like indeed, there's just problems running a bridge on both untagged (default VLAN, id 1) interface as well as on a VLAN interface. Might just have to re-architect my network somewhat, or at least put my other VMs on a VLAN that most of the rest of my stuff is on as well. This is annoying.
This should be in bold right atop of the networking page of the wiki and in the man page. Maybe print it 10 times on the console every time you create a switch... All kidding aside, I just spent days troubleshooting this on and off, and without reading this I don't think I every would have suspected bridging the untagged interface was breaking the tagged ones. I made the port on the cisco switch tagged only now, and created all individual vlans interfaces off off lagg0. Finally everything is working as it should
And I don't care this is from 2020 =), it is still very relevant on 13.1.
Unfortunate to see it's still an issue in FreeBSD, but happy you found this issue and got things working.
I am having the same issue, any workaround to have tagged and untagged bridges using the same interface?
I'm trying to dual-home HomeAssistant I have running as a VM. I'm running 12.2-RELEASE with the latest vm-bhyve.
Router is running opnSense, switches are Ubiquiti 8-port managed switches. I have my laptop hardwired into one of the switch ports with the VLAN and it's getting a DHCP address just fine.
When I try using
tcpdump -i em0.30 port 67 or port 68 -e -n -vv
I get the following which appears to be from the VM, and the correct interface MAC, however I don't see any response/reply and the VM still doesn't show the IP on that interface.
When in HA I statically set a IP address on the interface, I can ping back and forth just fine to the router and my laptop, when it's on the VLAN.
Here's my configuration. Anything further I can check? Any alternatives to try? I've done a bunch of searches, so far haven't seen anything that's worked or seems to indicate my problem.
Switches
VM configuration
EDIT: Upon further investigation from the router, using tcpdump, I'm seeing that the response IS being sent, or at least attempting to be.
EDIT2: I don't think I have any firewall issues, my current firewall on the host machine