Bug 103042 - Order of network interface shutdown should be reversed
Summary: Order of network interface shutdown should be reversed
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: initscripts
Version: 9
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
Depends On:
Blocks: CambridgeTarget
TreeView+ depends on / blocked
Reported: 2003-08-25 19:48 UTC by Mario Lorenz
Modified: 2014-03-17 02:38 UTC (History)
1 user (show)

Fixed In Version: 7.31-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2003-09-04 03:23:33 UTC

Attachments (Terms of Use)

Description Mario Lorenz 2003-08-25 19:48:40 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
Running etc/init.d/network stop should stop the network interfaces
in the reverse order than they were brought up. Namely,
PPPoE Interfaces should be shut down first, before the underlying
Ethernet interface is shut down. Otherwise, the remote end will deem
the link open and take a while to time it out, which is annoying if you just
wanted to reboot, and afterwards the pppoe doesnt come up.

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

How reproducible:

Steps to Reproduce:
1. /etc/rc.d/init.d/network start   (during bootup)
2. /etc/rc.d/intt.d/network stop    (manually or during shutdown)

Actual Results:  interfaces are brought up in order:
eth0 eth1 ppp0
and are being shut down in order
eth0 eth1 ppp0

Expected Results:  interfaces should be brought up in order
eth0 eth1 ppp0
and be shut down as in
ppp0 eth1 eth0
(so that the pppoe session can be properly terminated)

Additional info:

Comment 1 Bill Nottingham 2003-09-04 03:23:33 UTC
Fixed in 7.31-1, somewhat. The order isn't completely reversed, but xDSL
interfaces are brought up after other interfaces, and brought down before other

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