Linux PARISC architecture development
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Parisc List <linux-parisc@vger.kernel.org>
Subject: dhcp problems in cupertino
Date: Wed, 03 Sep 2008 12:35:37 -0500	[thread overview]
Message-ID: <1220463337.3254.23.camel@localhost.localdomain> (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



             reply	other threads:[~2008-09-03 17:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-03 17:35 James Bottomley [this message]
2008-09-04  0:50 ` dhcp problems in cupertino Grant Grundler
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=1220463337.3254.23.camel@localhost.localdomain \
    --to=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