Bug 75956 - No "bind to MAC address" in neat for wireless, wrong HWADDR binding
No "bind to MAC address" in neat for wireless, wrong HWADDR binding
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-network (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
Depends On:
Blocks: 75958 81720
  Show dependency treegraph
Reported: 2002-10-15 04:41 EDT by diego.santacruz
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-02-10 07:11:20 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 diego.santacruz 2002-10-15 04:41:34 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020809

Description of problem:
There is no "bind to MAC address" field in neat for wireless devices (in the
hardware tab), like there is one for Ethernet devices. However, neat
automatically binds it to the MAC address of whatever device is present without
telling the user, which can be wrong in the case of pluggable PCMCIA cards.

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

How reproducible:

Steps to Reproduce:
1. Insert a PCMCIA ethernet card
2. Start up neat
3. Configure a wireless device as eth0 (nicknamed wireless) in a new profile

Actual Results:  In the file /etc/sysconfig/networking/devices/ifcfg-wireless
HWADDR is set to the MAC address of the ethernet card (not the wireless card,
which is not currently inserted).

Expected Results:  neat should not automatically bind to the MAC address of the
present card without telling the user. A "bind to MAC address" field just like
the one for Ethernet cards should be presentr for wireless cards too. This would
let the user specify if the device should be bound to a particular HWADDR and
probe for it.

Additional info:
Comment 1 Harald Hoyer 2003-02-04 11:55:23 EST
fixed in CVS

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