Bug 65082

Summary:	network up after sleep
Product:	[Retired] Red Hat Linux	Reporter:	Frank Liu <gfrankliu>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED DEFERRED	QA Contact:	Ben Levenson <benl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3	CC:	rvokal
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-09-29 19:55:39 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Frank Liu 2002-05-17 05:36:55 UTC

Description of Problem:
My network interface is configured to use dhcp and ONBOOT=no,
but after my laptop comes back from power save mode, you will
see the dhcpcd is automatically started and trying to setup my
network, even though my ONBOOT=no and my eth0 was down before
the power save mode.

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


How Reproducible:


Steps to Reproduce:
1. 
2. 
3. 

Actual Results:


Expected Results:


Additional Information:

Comment 1 Phil Knirsch 2002-05-21 13:33:10 UTC

Hm. The problem might be that the power up after sleep is not considered a
normal boot and therefore the network will be started just as if you do a
'service network start' while the system is running.

The question is whether there is a way to distinguish between the power up after
sleep and a normal 'service network start'.

This sounds more like a initscripts problem to me, so i reasign it to that
component. I am pretty sure it's not in the net-tools themselves.

(Maybe it's hotplug, not sure)

Comment 2 Frank Liu 2002-05-24 04:40:54 UTC

I didn't have this problem with RedHat 7.2.
You would think if the network was purposely in a "down" state
before "sleep", why would one want it to be up after the "sleep".

another issue with "dhcp" and ONBOOT=no:
sometimes, I need to plug my laptop into a network with no dhcp server,
I can manually bring up the network
ifconfig eth0 192.168.1.11 netmask 255.255.255.0 up
it works for a minutes and then quit. I tracked the problem down finally.
it looks like the "dhcpcd" somehow got started after my "ifconfig" command.
of course, it eventually dies because there is no dhcp server on the server.
Unfortunately, this also brings down my manually up'ed interface.

Again, I didn't have this problem in redhat 7.2.

Frank

Comment 3 Bill Nottingham 2005-09-29 19:55:39 UTC

Closing bugs on older, no longer supported, releases. Apologies for any lack of
response.

If this persists on a current release, such as Fedora Core 4, please open a new bug.