Bug 84504 – RTNETLINK answers: No such device

Bug 84504 - RTNETLINK answers: No such device

Summary:	RTNETLINK answers: No such device

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	kernel (Show other bugs)
Sub Component:
Version:	9
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Arjan van de Ven
QA Contact:	Brian Brock
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-02-17 21:57 EST by Chris Runge
Modified:	2008-01-17 12:49 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2004-09-30 11:40:32 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Chris Runge 2003-02-17 21:57:50 EST

Description of problem:

I realize this is probably the wrong component, so feel free to change it.

I configured my orinoco_pci wireless device with the redhat-config-network
program (after adding the line "alias eth1 orinoco_pci" to /etc/modules.conf).
After bringing up the device, which is successful, I get the following message:

RTNETLINK answers: No such device

I'm not sure if this is related, but dmesg shows the following:

ip_tables: (C) 2000-2002 Netfilter core team
eth1: Channel out of range (0)!
eth1: Error -110 setting multicast list.

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

redhat-config-network-1.1.97-1 (in Phoebe 8.0.94)

Comment 1 Harald Hoyer 2003-02-18 05:22:23 EST

this is more a kernel / driver configuration problem

Comment 2 Bugzilla owner 2004-09-30 11:40:32 EDT

Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/

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