Bug 4922 - IP/MAC address conflict at boot when shapeing windows pc
IP/MAC address conflict at boot when shapeing windows pc
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: shapecfg (Show other bugs)
6.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-09-05 00:50 EDT by d.e.baker
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-08-02 09:56:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description d.e.baker 1999-09-05 00:50:03 EDT
I am running the traffic shaper which comes with RedHat 6.0
and it works great, except that if a windows 98 machine is
being shaped, and that machine reboots while the host shaper
route is defined, then the windows box will detect a
conflict for the IP address.  This then causes the windows
machine to boot up with the network interface disabled.

The machine doing the routing/shaping is a dual processor
system running the smp kernel (of course).  All linux
software is out-of-the-box stock official RedHat, nothing
re-compiled.

The following are the commands to setup traffic shaping.
Everything works OK until the last statement where the host
route is added.  After this point, the problem mentioned
above occurrs.  If that host route is deleted, then the
problem goes away.

/sbin/insmod shaper -o shaper0
/sbin/shapecfg attach shaper0 eth0
/sbin/shapecfg speed shaper0 20000
/sbin/ifconfig shaper0 192.168.110.1 netmask 255.255.255.0
up
/sbin/route add -host 192.168.110.222 dev shaper0

The address 192.168.110.1 is the IP address of the nic in
the linux router, and 192.168.110.222 is the win pc being
shaped.  I am doing something wrong here, or is this a real
bug with shaper?
Comment 1 Trond Eivind Glomsrxd 2000-07-10 14:39:06 EDT
Is this still a problem in 6.2?
Comment 2 Trond Eivind Glomsrxd 2000-08-02 09:56:50 EDT
Or in the pinstripe beta?
Comment 3 Trond Eivind Glomsrxd 2000-08-15 16:53:07 EDT
OK - no information to the contrary, I'll close this as "fixed for Red Hat 6.2"

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