Bug 1817 - Pump doesn't seem to setup DHCP correctly
Pump doesn't seem to setup DHCP correctly
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: dhcpcd (Show other bugs)
6.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Erik Troan
http://leonardo.sr.unh.edu/arguin/hom...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-03-26 11:09 EST by carguin
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-03-31 15:30:17 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description carguin 1999-03-26 11:09:20 EST
I have a DHCP network activated on system boot. When pump
runs, it does get an IP address and activates the interface,
but I cannot use the network. Attempts to ping tell me the
network is unreachable.

In order to get the network working, I use the
"dhcpcd-rhcn-1.3.17-pl3-1" package, and my own ifup-eth and
ifdown-eth0 scripts.

I am running Linux 2.2.4.
Comment 1 Preston Brown 1999-03-29 12:13:59 EST
We need more information.  What is the output of 'route' after pump
runs?  Are your routes correct? What subnet are you on?
Comment 2 rebel 1999-03-30 10:26:59 EST
Pump is completely unfunctional. Kernel 2.2.5, FreeBSD bootpd.
Comment 3 carguin 1999-03-30 15:06:59 EST
When pump runs it doesn't seem to setup the routes correctly. I get:

132.177.56.0    *          255.255.252.0   U     0   0   0 eth0
127.0.0.0       *          255.0.0.0       U     0   0   0 lo

This seems born out, since I can ping machines on the 132.177.56.0
subnet, but I cannot, for instance, reach my nameservers.

This is using the default ifup and ifdown scripts, BTW.

With dhcdpcd, the route table is:

132.177.56.0    *               255.255.252.0   U   0 0 0 eth0
127.0.0.0       *               255.0.0.0       U   0 0 0 lo
default         student2-56gw.u 0.0.0.0         UG  0 0 0 eth0


While I'm at it, I might also add that dhcpcd tries to reuse to old IP
address is possible (ie, it request that first). This is *very*
nice... I've had the same IP address for the last two semesters :)When pump runs it doesn't seem to setup the routes correctly. I get:

132.177.56.0    *          255.255.252.0   U     0   0   0 eth0
127.0.0.0       *          255.0.0.0       U     0   0   0 lo

This seems born out, since I can ping machines on the 132.177.56.0
subnet, but I cannot, for instance, reach my nameservers.

This is using the default ifup and ifdown scripts, BTW.

With dhcdpcd, the route table is:

132.177.56.0    *               255.255.252.0   U   0 0 0 eth0
127.0.0.0       *               255.0.0.0       U   0 0 0 lo
default         student2-56gw.u 0.0.0.0         UG  0 0 0 eth0


While I'm at it, I might also add that dhcpcd tries to reuse to old IP
address is possible (ie, it request that first). This is *very*
nice... I've had the same IP address for the last two semesters :)
Comment 4 Erik Troan 1999-03-31 15:30:59 EST
this should be fixed in pump 0.3, which will be in the next
starbuck. Please let me know if this is still a problem.

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