After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 700964 - Do not auto-enable ipv4 on bridge ports (bridge slaves)
Do not auto-enable ipv4 on bridge ports (bridge slaves)
Status: RESOLVED DUPLICATE of bug 747443
Product: gnome-control-center
Classification: Core
Component: Network
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-05-24 16:02 UTC by David Jaša
Modified: 2015-04-07 12:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description David Jaša 2013-05-24 16:02:07 UTC
Steps to reproduce:
set up:
1) disable your wired device
2) delete "Auto ethernet" connection
3) in nm-connection-editor, create a system-wide ethernet connection (tick "... all users ...") with auto-connect and with both ipv4 and ipv6 disabled
4) in nm-connection, create a bridge device with device from 3) used as slave
5) enable eth & bridge connections
reproducer:
6) go to Network panel of g-c-c or "Network Settings" in network top-bar menu
7) select wired device, hit "cogwheel", go to ipv4 config
8) disable ipv4, confirm
9) hit cogwheel again, go to ip4 tab again1

what happens:
7) ipv4 is enabled
9) ipv4 is enabled

what should happen:
g-c-c shouldn't touch bridge port in any of these cases as the IP configuration is specified on the bridge device

versions:
Fedora 19 Beta RC4
control-center-3.8.2-1
NetworkManager-0.9.8.1-1

note:
nm-connection-editor doesn't have this bug
Comment 1 Bastien Nocera 2015-04-07 12:27:47 UTC
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 747443 ***