Bug 296591 - Bridge(4) flaps when the first vmnet(4) interface is added
Summary: Bridge(4) flaps when the first vmnet(4) interface is added
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 15.1-RELEASE
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-net (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-07-08 07:01 UTC by Poul-Henning Kamp
Modified: 2026-07-08 08:42 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Poul-Henning Kamp freebsd_committer freebsd_triage 2026-07-08 07:01:07 UTC
I have a bridge(4) here with some epair(4)s and an ix(4) (Intel X520).

When I add or remove the first vmnet(4) member the bridge flaps.

I can see no reason why it should do that.

Once the bridge already has a vmnet member, I can add and delete
as many vmnet interfaces as I want, without it flapping.

My workaround is to add a dummy unused, vmnet999 to the bridge
in /etc/rc.conf to get the flapping over with.

But surely that cannot be right ?

I noticed that vmnet(4) is the only interface with IFCAP_LINKSTATE,
and that bridge_linkcheck() is interested in that bit, but I would
pressume that the other interfaces being LINK_STATE_UP will keep
the bridge up in the hasls==0 case.

I'm not going to be very popular if I muck too much about with this
machine particular, so sticking prinf's in there is not at present
an option for me.