Bug 53531 - Network setup very unflexible
Summary: Network setup very unflexible
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: initscripts   
(Show other bugs)
Version: roswell
Hardware: i386 Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
: 55802 55843 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2001-09-10 23:28 UTC by Chris Chabot
Modified: 2014-03-17 02:23 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-09-11 00:11:52 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Chris Chabot 2001-09-10 23:28:33 UTC
When changing the IP address of a interface, it doesnt always apply when 
doing a ifdown / ifup. even network restart doesnt do the job.

I had this happen to me several times while playing with some new servers 
and RH Roswell beta 2 (+all updates). One eth was configured for the 
external net, one for internal (192...). When changing the 2 
configurations around, doing a ifup/down combo, didnt change the network 
settings of both, instead they both gor the internal address.

Interstingly enough, this seems to occur when the network card is also 
bound to the default gw (router) address. network restart didnt fix this 
situation either.

When doing a 'route' or ip route show, i saw that interface was still 
bound to the local network.

My suspission is that the new routing setup (iproute2) is not un-binding 
the interface from the routing table, thus is not allowing it to be re-
bound to a different network.

This greatly deacreases the flexibility of linux networking (no longer 
can we laugh @ win95 users who need to restart after a network change?!)

Comment 1 Chris Chabot 2001-09-11 00:11:48 UTC
Ps, after playing some more, i noticed chaning the IP within the same network 
range also did not work. When i tried this, the network cable was unplugged.

However the logs didnt show any errors, nor was there any visual output.

Could it be that when arpping fails, it doesnt change the ip?

Comment 2 Bill Nottingham 2001-09-26 20:43:48 UTC
This should be fixed at least somewhat in initscripts-6.40.1-1, or later.

Comment 3 Bill Nottingham 2001-11-06 21:57:22 UTC
*** Bug 55802 has been marked as a duplicate of this bug. ***

Comment 4 Bill Nottingham 2001-11-07 17:34:03 UTC
*** Bug 55843 has been marked as a duplicate of this bug. ***

Comment 5 Need Real Name 2001-11-07 18:38:07 UTC
Could somebody please post a patch or something so we can fix it in the 

Comment 6 Mike McLean 2002-04-17 20:25:17 UTC
I'm still seeing ip addresses persist on an interface after running ifdown. 
This is happening with recent versions of initscipts, but only when the
BOOTPROTO is dhcp.  After ifdown I see:

# ip addr list dev eth0
2: eth0: <BROADCAST> mtu 1500 qdisc pfifo_fast qlen 100
    link/ether 00:50:da:b4:13:fd brd ff:ff:ff:ff:ff:ff
    inet brd scope global eth0

I traced ifdown and it appears that ifdown
  - kills the running dhcpcd process for the interface
  - uses ip link to take the interface down

Neither of these actions seems to remove the ip address from the device.  Is
this a bug in initscripts or in dhcpcd?

Comment 7 Bill Nottingham 2002-04-17 22:12:54 UTC
dhcpcd, I think.

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