Bug 1004978 - nm-connection-editor misnames "default gateway" as "gateway"
nm-connection-editor misnames "default gateway" as "gateway"
Product: Fedora
Classification: Fedora
Component: network-manager-applet (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-09-05 18:38 EDT by Pavel Roskin
Modified: 2015-02-17 12:05 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-02-17 12:05:14 EST
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 Pavel Roskin 2013-09-05 18:38:07 EDT
Description of problem:

When using manual IPv4 configuration, the "default gateway" column is called "gateway".  The tooltip only talks about the IP addresses.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:

1. Right click on nm-applet
2. Select "Edit connections"
3. Click "Add"
4. Choose "Ethernet"
5. Select "IPv4 Settings" tab.
6. Set "Method" to "Manual".

Actual results:

A table titled "Addresses" appears, with the fields "Address", "Netmask" and "Gateway".

Expected results:

The last column should be called "default gateway".  Better yet, the default gateway should be entered outside the table, next to DNS servers.  Normally, there is just one default gateway per system.  Even if there are many, they can be on the same subnet.  It's pointless to tie default gateways to subnets.  I think handling them like DNS servers (GUI-wise) would be the best approach.

Additional info:

A gateway for a network is where to send packets to reach _that_ network.  A default gateway is where to send packets for networks that are not known to the system.

This is a big deal.  Bugzilla is filled with closed bug reports from users who try and fail to add a default gateway by entering a network.
Comment 1 Fedora End Of Life 2015-01-09 14:44:50 EST
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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.
Comment 2 Fedora End Of Life 2015-02-17 12:05:14 EST
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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

Thank you for reporting this bug and we are sorry it could not be fixed.

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