Bug 4922

Summary: IP/MAC address conflict at boot when shapeing windows pc
Product: [Retired] Red Hat Linux Reporter: d.e.baker
Component: shapecfgAssignee: Trond Eivind Glomsrxd <teg>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-08-02 13:56:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description d.e.baker 1999-09-05 04:50:03 UTC
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

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 netmask
/sbin/route add -host dev shaper0

The address is the IP address of the nic in
the linux router, and 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 18:39:06 UTC
Is this still a problem in 6.2?

Comment 2 Trond Eivind Glomsrxd 2000-08-02 13:56:50 UTC
Or in the pinstripe beta?

Comment 3 Trond Eivind Glomsrxd 2000-08-15 20:53:07 UTC
OK - no information to the contrary, I'll close this as "fixed for Red Hat 6.2"