[Bug 1230265] nmcli device - doesn't show correct connection status for a primary device which got unplugged
https://bugzilla.suse.com/show_bug.cgi?id=1230265 https://bugzilla.suse.com/show_bug.cgi?id=1230265#c5 --- Comment #5 from Zaoliang Luo <zluo@suse.com> --- (In reply to Jonathan Kang from comment #4)
(In reply to Zaoliang Luo from comment #3)
Created attachment 877231 [details] yast logs
I just took a look at this and the source code[1] of NetworkManager, and found that this behaviour was done on purpose.
Ports don't deactivate when they lose carrier; for bonds/teams in particular that would be actively counterproductive.
*[1] https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/main/src... core/devices/nm-device.c#L7041
interesting but weird. At least add a line about this 'behavior' into documentation for NetworkerManager if it is not done yet. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com