Bug 53222 - Network access fails after update from RH 7.1 to roswell
Summary: Network access fails after update from RH 7.1 to roswell
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: kernel
Version: roswell
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-09-05 06:23 UTC by Joachim Backes
Modified: 2007-04-18 16:36 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-09-05 15:53:04 UTC
Embargoed:


Attachments (Terms of Use)

Description Joachim Backes 2001-09-05 06:23:54 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.9 i686)

Description of problem:
I made an update installation from RH 7.1 to roswell. MY 7.1 system was
installed with a running network access (3c59x, Kernel 2.4.9). But after
roswell was installed, the network access failed ("Cannot send dump
request" msg during init 3). I found the following solution: Compile a new
Kernel with "NETLINK=Y" and "RTNETLINK=Y". Then roswell will run without
problem.

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


How reproducible:
Didn't try

Steps to Reproduce:
see above.
	

Actual Results:  No network access possible.

Expected Results:  Network reachable.

Additional info:

--

Comment 1 Michael Fulbright 2001-09-05 15:52:59 UTC
Appears to be a kernel related issue, reassigning.

Comment 2 Arjan van de Ven 2001-09-05 15:56:19 UTC
Yes Netlink is required basically to do any real networking; 
David Miller has said that he wants these config options removed and default to
enabled in the TCP/IP stack because the code overhead is low and all non-trivial
network setups require this.

I'd say this is not a real bug; more that 2.4.9 doesn't have the default set
yet.


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