https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240658
--- Comment #9 from Harald Schmalzbauer <bugzilla.free...@omnilan.de> --- Update: The link-state-change issue doesn't affect _configured_ interfaces, so the fix in https://reviews.freebsd.org/D21769 is most likely perfectly valid. I guess the remaining issue is by design. As long as the interface was never configured, state change only works once in one direction -> recorded as active. If I have the interface configured before or afterwards, connection change/loss will be recognized. But not for unconfigured interfaces. So the issue has no production influencing effects. It's might just caus confusion on systems with (cold) standby interfaces, since the admin might assume there's a link active and searches all switches unsuccessfully for that link… During this test I saw that assigning an IP address to an already link-established em(4) or igb(4) interface, causes loss/interruption of the establisehd ethernet link. Don't know if this is desired… Guess these facts are related and as long as the internal steps configuring a em/igb(4) (or probably iflib generic?) NIC stay as they are, it won't be possible to catch the link state loss with unconfigured/cold-stanby interfaces, right? Thanks, -Harry(In reply to John Delano from comment #7) -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
