Skip to contentSkip to conversation

dhcp problems in cupertino

DISCUSSION James Bottomley 2 participants 3 messages Sep 3, 2008 – Sep 4, 2008

lore
Share & tools
lore
#0 lore raw

It looks like the old dhcp server was converted to dhcp3 without pulling across all of the dhcp entries. I've added the gig-e network and and entry for ion (which I needed to get it to come up). However, there are evidently still machines out there trying and failing to get IP addresses:

Sep  3 10:24:29 gsyprf11 dhcpd: DHCPDISCOVER from 00:17:08:c8:75:40 via eth11: network 192.168.1/24: no free leases
Sep  3 10:36:29 gsyprf11 dhcpd: DHCPDISCOVER from 00:04:ea:b1:cf:80 via eth10: network 192.168.0/24: no free leases

So whoever's systems these are will need to add an entry for them.

James

#1 lore raw
Quoted 8 lines · James Bottomley

It looks like the old dhcp server was converted to dhcp3 without pulling across all of the dhcp entries. I've added the gig-e network and and entry for ion (which I needed to get it to come up). However, there are evidently still machines out there trying and failing to get IP addresses:

Sep  3 10:24:29 gsyprf11 dhcpd: DHCPDISCOVER from 00:17:08:c8:75:40 via eth11: network 192.168.1/24: no free leases
Sep  3 10:36:29 gsyprf11 dhcpd: DHCPDISCOVER from 00:04:ea:b1:cf:80 via eth10: network 192.168.0/24: no free leases

gsyprf11 intentionally has no free leases. I plan was gsyprf11 should only serve IP's for the systems that can/should netboot from it. ie other parisc systems.

Quoted 1 line

So whoever's systems these are will need to add an entry for them.

I don't know offhand which systems they represent but can probably work that out. I just add those to the dhcp server running on gsyprf10.

I suspect it's a FC switch or something like that.

thanks,
grant

Quoted 8 lines

James

--
To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#2 lore raw
In reply to James Bottomley
Quoted 2 lines · James Bottomley

It looks like the old dhcp server was converted to dhcp3 without pulling across all of the dhcp entries.

I suspect I "upgraded" the switchs and never realized I needed to add the IP to DHCP.

Quoted 6 lines

I've added the gig-e network and
entry for ion (which I needed to get it to come up). However, there are evidently still machines out there trying and failing to get IP addresses:

Sep  3 10:24:29 gsyprf11 dhcpd: DHCPDISCOVER from 00:17:08:c8:75:40 via eth11: network 192.168.1/24: no free leases

ProCurve Switch 2848#

Just "telnet 192.168.1.131".

Quoted 1 line
Sep  3 10:36:29 gsyprf11 dhcpd: DHCPDISCOVER from 00:04:ea:b1:cf:80 via eth10: network 192.168.0/24: no free leases

HP J4813A ProCurve Switch 2524

thanks,
grant