RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1038344 - changes to gateway not picked up by ifup or network
Summary: changes to gateway not picked up by ifup or network
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: arpwatch
Version: 6.5
Hardware: All
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Jan Synacek
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-05 00:21 UTC by Todd
Modified: 2015-10-12 13:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-12 13:57:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Todd 2013-12-05 00:21:57 UTC 
Hi All,

Scietific Linux 6.5, 64 bit.

Would one of our intrepid heroes at Red Hat please fix this for me?

I had to manually configure a Tread Net TEW-638PAP as a wireless bridge yesterday.  In the process, I had to change my default router (a.k.a. gateway) three times.  (Networking too, but that worked.) The TEW-638PAP was hooked to my second Ethernet port (eth1).

Problem, I had to reboot to get the new default route to stick.

Now I know of two places I can put my default router:

   /etc/sysconfig/network     <--- where I put it
   GATEWAY=192.168.10.100   and

   /etc/sysconfig/network-scripts/ifcfg-eth1
   GATEWAY=192.168.10.100

I am using /etc/sysconfig/network and the "vi" method.

To check my default router setting, I used "netstat -rn" and looked for the tags "UG".  (It is at the bottom of the list.)

To try to get the new default router setting to take, I used:

    service network restart; netstat -rn
and
    ifdown eth1; ifup eth1; netstat -rn

No joy with either method.  Whatever gateway I had when I booted, was the one I was stuck with.  Reboot was the only way to make the change.  I even tried manually configuring it with "route".  No joy there either.  

The workaround is to manually delete and add with "ip route"
    ip route delete default via xxx.xxx.xxx.xxx dev eth0
    ip route add default via yyy.yyy.yyy.yyy dev eth0
 
    replace xxx.xxx.xxx.xxx with your current router and yyy.yyy.yyy.yyy with the new one 

And the bug is, both  "/etc/rc.d/init.d/network restart" and "ifup ethx" should do pick up a default router (gateway) change on their own and not require manual intervention or a reboot.

Many thanks,
-T
Comment 2 Todd 2014-02-14 20:24:54 UTC 
Hi,

  Two days ago, one of my workstations upgrade a ton of packages.  It is not on SL 6.5.

  Two things showed up that concern this bug report.

1)  My "GATEWAY=" setting was removed from /etc/sysconfig/network and moved to
/etc/sysconfig/network-scripts/ifcfg-eth1

"ifup eth1" will now read the "GATEWAY=" from ifcfg-eth1.  If moved back to /etc/sysconfig/network, ifup will no longer read it.

Has "GATEWAY" in /etc/sysconfig/network been depreciated?

2)  in /etc/sysconfig/network-scripts/ifcfg-eth1, "BOOTPROTO=" got changed from "static" to "none".

Has this also been depreciated?

Both of the above freaked out my firewall script as it reads and uses the values above.

Many thanks,
-T
Comment 3 Todd 2014-02-14 20:35:20 UTC 
"It is not on SL" should have been " It is now on SL"

Be nice if we had an "edit" function for the typos
Note You need to log in before you can comment on or make changes to this bug.