Bug 2311 - dhcpcd client not able to obtain lease in HSRP environment
Summary: dhcpcd client not able to obtain lease in HSRP environment
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: pump   
(Show other bugs)
Version: 6.0
Hardware: i386 Linux
high
medium
Target Milestone: ---
Assignee: Erik Troan
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-04-21 15:59 UTC by stevecs
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-08-31 22:21:31 UTC
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.)

Description stevecs 1999-04-21 15:59:16 UTC 
We have an ISC DHCP server (v2.0b1pl26) running under
Solaris v2.6.  This server is behind two cisco routers
using HSRP with a virtual gateway interface of 1.0.0.250.

The client machine is located behind two other routers
running HSRP w/ a virtual interface of 192.168.208.254.

DHCPDiscover is sent, received twice (due to HSRP all
broadcast packets are duplicated out each phsyical
interface, this is normal).  The server pings the IP
address it's about to assign, then the server sends
DHCPOffer to client which is also duplicated for each HSRP
physical interface.

The dhcpcd client indicates that no DHCP reply is recieved
when it actually IS sent to the mac address from the
router.  All other clients work (HP printers, Sun
workstations, Win95/NT boxes).  Only the linux system has
a problem.

This problem goes away if the linux system is on the same
subnet as the DHCP server.
Comment 1 David Lawrence 1999-06-11 19:44:59 UTC 
Does this problem still occur with the latest errata release of pump
available at ftp://updates.redhat.com/6.0/i386?
Comment 2 Bill Nottingham 1999-08-31 22:21:59 UTC 
closed, lack of input.
Note You need to log in before you can comment on or make changes to this bug.