Hide Forgot
Description of problem: The virtual network connections from docker are displayed so it makes it hard to see the real network connections. Version-Release number of selected component (if applicable): 1.2.4.3.fc24 How reproducible: Always Steps to Reproduce: 1. Run docker 2. Click on menu in upper right 3. Observe virtual network connections Actual results: Virtual network connections from docker are displayed. Expected results: Only real network connections are displayed. Additional info: https://github.com/docker/docker/issues/4453 https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1458322
Are you using the GNOME 3 shell or nm-applet? Can you please attach the output of 'ip -d l; nmcli d' and a screenshot of the connections displayed in the UI? Thanks!
I'm just using the default install of Fedora Workstation 24, so I believe that means GNOME 3 shell. I've attached the screenshot and here's the output of the command: [dlj@JohansenDev ~]$ ip -d l; nmcli d 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 promiscuity 0 addrgenmode eui64 2: enp0s25: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000 link/ether 00:21:cc:b8:bb:ba brd ff:ff:ff:ff:ff:ff promiscuity 0 addrgenmode none 3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000 link/ether 10:0b:a9:81:75:bc brd ff:ff:ff:ff:ff:ff promiscuity 0 addrgenmode none 4: br-503e79221197: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default link/ether 02:42:68:66:28:5c brd ff:ff:ff:ff:ff:ff promiscuity 0 bridge forward_delay 1500 hello_time 200 max_age 2000 ageing_time 30000 stp_state 0 priority 32768 vlan_filtering 0 vlan_protocol 802.1Q addrgenmode eui64 5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default link/ether 02:42:2d:f4:47:37 brd ff:ff:ff:ff:ff:ff promiscuity 0 bridge forward_delay 1500 hello_time 200 max_age 2000 ageing_time 30000 stp_state 0 priority 32768 vlan_filtering 0 vlan_protocol 802.1Q addrgenmode eui64 49: veth0d4907d@if48: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-503e79221197 state UP mode DEFAULT group default link/ether 66:57:89:ee:25:90 brd ff:ff:ff:ff:ff:ff link-netnsid 0 promiscuity 1 veth bridge_slave state forwarding priority 32 cost 2 hairpin off guard off root_block off fastleave off learning on flood on addrgenmode eui64 51: vetheaee09f@if50: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-503e79221197 state UP mode DEFAULT group default link/ether 2a:b5:51:78:69:54 brd ff:ff:ff:ff:ff:ff link-netnsid 1 promiscuity 1 veth bridge_slave state forwarding priority 32 cost 2 hairpin off guard off root_block off fastleave off learning on flood on addrgenmode eui64 53: veth8e01ba9@if52: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-503e79221197 state UP mode DEFAULT group default link/ether a2:74:1f:78:85:ed brd ff:ff:ff:ff:ff:ff link-netnsid 2 promiscuity 1 veth bridge_slave state forwarding priority 32 cost 2 hairpin off guard off root_block off fastleave off learning on flood on addrgenmode eui64 55: veth502d00c@if54: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-503e79221197 state UP mode DEFAULT group default link/ether 26:46:9b:fa:0a:45 brd ff:ff:ff:ff:ff:ff link-netnsid 3 promiscuity 1 veth bridge_slave state forwarding priority 32 cost 2 hairpin off guard off root_block off fastleave off learning on flood on addrgenmode eui64 57: veth86e3519@if56: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-503e79221197 state UP mode DEFAULT group default link/ether fe:4b:84:55:34:d0 brd ff:ff:ff:ff:ff:ff link-netnsid 8 promiscuity 1 veth bridge_slave state forwarding priority 32 cost 2 hairpin off guard off root_block off fastleave off learning on flood on addrgenmode eui64 59: veth9f8d1f2@if58: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-503e79221197 state UP mode DEFAULT group default link/ether 5a:33:bd:e5:fe:1b brd ff:ff:ff:ff:ff:ff link-netnsid 4 promiscuity 1 veth bridge_slave state forwarding priority 32 cost 2 hairpin off guard off root_block off fastleave off learning on flood on addrgenmode eui64 61: veth3ac60b3@if60: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-503e79221197 state UP mode DEFAULT group default link/ether e2:fd:50:fe:91:34 brd ff:ff:ff:ff:ff:ff link-netnsid 11 promiscuity 1 veth bridge_slave state forwarding priority 32 cost 2 hairpin off guard off root_block off fastleave off learning on flood on addrgenmode eui64 63: veth650ff7b@if62: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-503e79221197 state UP mode DEFAULT group default link/ether a6:2c:4d:72:0a:3d brd ff:ff:ff:ff:ff:ff link-netnsid 9 promiscuity 1 veth bridge_slave state forwarding priority 32 cost 2 hairpin off guard off root_block off fastleave off learning on flood on addrgenmode eui64 67: vetha805799@if66: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-503e79221197 state UP mode DEFAULT group default link/ether d2:d3:f8:22:6e:67 brd ff:ff:ff:ff:ff:ff link-netnsid 10 promiscuity 1 veth bridge_slave state forwarding priority 32 cost 2 hairpin off guard off root_block off fastleave off learning on flood on addrgenmode eui64 69: vethcf07e44@if68: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-503e79221197 state UP mode DEFAULT group default link/ether 02:95:fc:07:fa:0f brd ff:ff:ff:ff:ff:ff link-netnsid 13 promiscuity 1 veth bridge_slave state forwarding priority 32 cost 2 hairpin off guard off root_block off fastleave off learning on flood on addrgenmode eui64 71: veth7332fee@if70: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-503e79221197 state UP mode DEFAULT group default link/ether 0e:1c:4a:c7:ff:8c brd ff:ff:ff:ff:ff:ff link-netnsid 6 promiscuity 1 veth bridge_slave state forwarding priority 32 cost 2 hairpin off guard off root_block off fastleave off learning on flood on addrgenmode eui64 73: veth7083bec@if72: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-503e79221197 state UP mode DEFAULT group default link/ether 9e:36:d9:f2:7b:49 brd ff:ff:ff:ff:ff:ff link-netnsid 12 promiscuity 1 veth bridge_slave state forwarding priority 32 cost 2 hairpin off guard off root_block off fastleave off learning on flood on addrgenmode eui64 79: veth24866e1@if78: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-503e79221197 state UP mode DEFAULT group default link/ether f6:ee:51:e7:f0:0c brd ff:ff:ff:ff:ff:ff link-netnsid 5 promiscuity 1 veth bridge_slave state forwarding priority 32 cost 2 hairpin off guard off root_block off fastleave off learning on flood on addrgenmode eui64 DEVICE TYPE STATE CONNECTION br-503e79221197 bridge connected br-503e79221197 docker0 bridge connected docker0 wlp3s0 wifi connected Johansen enp0s25 ethernet unavailable -- veth0d4907d ethernet unmanaged -- veth24866e1 ethernet unmanaged -- veth3ac60b3 ethernet unmanaged -- veth502d00c ethernet unmanaged -- veth650ff7b ethernet unmanaged -- veth7083bec ethernet unmanaged -- veth7332fee ethernet unmanaged -- veth86e3519 ethernet unmanaged -- veth8e01ba9 ethernet unmanaged -- veth9f8d1f2 ethernet unmanaged -- vetha805799 ethernet unmanaged -- vethcf07e44 ethernet unmanaged -- vetheaee09f ethernet unmanaged -- lo loopback unmanaged --
Created attachment 1220243 [details] Screenshot of virtual network connections from Docker
Reassigning to gnome-shell...
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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.
This is still happening in Fedora 26 and needs to be fixed.
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.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.