Bug 150382 - net.agent does not handle removal of wireless card
net.agent does not handle removal of wireless card
Status: CLOSED DUPLICATE of bug 127283
Product: Fedora
Classification: Fedora
Component: hotplug (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2005-03-05 03:58 EST by Richard Levitt
Modified: 2014-03-16 22:52 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 14:08:15 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Richard Levitt 2005-03-05 03:58:02 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6)
Gecko/20050302 Firefox/1.0.1 Fedora/1.0.1-1.3.2

Description of problem:
Upon removal of wireless card (Netgear WG511), net-agent fails to
handle event:


Mar  5 08:09:11 localhost net.agent[5449]: remove event not handled
Mar  5 08:09:12 localhost net.agent[5446]: remove event not handled

As a result, ifdown eth1 is not run when the card is removed.  This
means that the dhclient is not killed.  If the card is reinserted,
there will be two dhclients running, and no IP address will be allocated.

As a brute force fix, I have added "ifdown eth1" to the top of my
/etc/hotplug/net.agent.  It's not elegant, but it works.

In case it's relevant, I have added "alias eth1 islpci_cb" to
/etc/modprobe.conf (as described in some advice somewhere on the
Internet) to get this card recognised by system-config-network. 
Subject to that, the card has been added to the system via
system-config-network in a standard way.


This Bug was previously reported as 127283 for FC2 in July 2004.  That
Bug report contains further history.  Comment 3 says "A call to ifdown
added in 2004_09_23-1. Note that this may very well
not do anything useful without modifying ifdown."  In fact, a call to
ifdown eth1 is exactly what is needed, but net.agent is not making
that call.


Why is the (massively popular) WG511 wireless card (and, I imagine,
any other prism54 card) so poorly supported in every version of FC?

A popup should tell the poor user that firmware needs to be downloaded
to get the card to work.  Isn't that the minimum any half decent
operating system would do?  It's not as if the relevant developers are
unaware of this issue.

Having worked out that firmware must be obtained, why is the poor user
left to amend /etc/modprobe.conf manually in order to get this card
recognised by system-config-network?

In the end, the steps required to get the card to work perfectly well
are trivial (get firmware; add a line to /etc/modprobe.conf; run
system-config-network to add card; brute force fix
/etc/hotplug/net.agent), but the amount of time and effort taken to
figure all of this out is significant and I guess a large percentage
of would be users just give up and return to XP.

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

How reproducible:

Steps to Reproduce:
1.Insert wireless network card.
2.Remove it


Actual Results:  /var/log/messages:

Mar  5 08:09:11 localhost net.agent[5449]: remove event not handled
Mar  5 08:09:12 localhost net.agent[5446]: remove event not handled

Expected Results:  net.agent should have run ifdown eth1

Additional info:
Comment 1 Bill Nottingham 2005-03-07 12:55:18 EST

*** This bug has been marked as a duplicate of 127283 ***
Comment 2 Red Hat Bugzilla 2006-02-21 14:08:15 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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