Bug 1476430 - nm-applet displays no connection when using a bridge connection
nm-applet displays no connection when using a bridge connection
Status: NEW
Product: Fedora
Classification: Fedora
Component: network-manager-applet (Show other bugs)
All Linux
unspecified Severity medium
: ---
: ---
Assigned To: Lubomir Rintel
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2017-07-28 20:57 EDT by Bond Masuda
Modified: 2018-05-03 04:38 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bond Masuda 2017-07-28 20:57:10 EDT
Description of problem:
I have configured a bridge connection on my laptop named bridge0, and a corresponding bridge slave that is the actual ethernet port. nmcli shows this connection is up, and it works. However, the nm-applet icon in the notification area shows there is no connection.

Version-Release number of selected component (if applicable):
I did not have this problem in Fedora 25. It only started right after the upgrade to Fedora 26.

How reproducible:
Every time. I've deleted and re-created the same bridge connection with same results.

Steps to Reproduce:
1. connect to wired network by creating a bridge connection
2. add real ethernet port as bridge slave to bridge connection.
3. turn bridge connection on (nmcli conn up bridge0)

Actual results:
nm-applet icon shows disconnected state. even though connection is up, and bridge0 has DHCP address and everything works.

Expected results:
nm-applet icon to show connected state.

Additional info:
Comment 1 Fedora End Of Life 2018-05-03 04:38:01 EDT
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Note You need to log in before you can comment on or make changes to this bug.