Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: dhcp problems in cupertino
Date: Wed, 3 Sep 2008 18:50:01 -0600	[thread overview]
Message-ID: <20080904005001.GA22774@colo.lackof.org> (raw)
In-Reply-To: <1220463337.3254.23.camel@localhost.localdomain>

On Wed, Sep 03, 2008 at 12:35:37PM -0500, James Bottomley wrote:
> 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.

> 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

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

  reply	other threads:[~2008-09-04  0:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-03 17:35 dhcp problems in cupertino James Bottomley
2008-09-04  0:50 ` Grant Grundler [this message]
2008-09-04  0:56 ` Grant Grundler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080904005001.GA22774@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-parisc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox