9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Retzki, Sascha [Xplain]" <sascha.retzki@xplain.de>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: RE: [9fans] dhcpd
Date: Thu,  6 Jul 2006 12:15:35 +0200	[thread overview]
Message-ID: <3AF26F5605627543BEC429636A522290235B97@rohrpostix.xplain.local> (raw)

> 
> i read this as explicitly stating that you must have the ethernet
> (mac) address of the machine to be served an ip in ndb.
> although this would mostly defeat the purpose of dhcp, so
> maybe i'm wrong.
> 

Depends - for naming services, this 'the same mac gets the same IP.
Always' thing is way simplier than coupling the dhcp-server with the
naming service 'somehow'. Now, you can name every terminal, every
computer, and still maintain that in one rather central database. I like
that, personally - just my 2 eurocents.

> - erik
> 
> On Wed Jul  5 18:22:50 CDT 2006, steve@quintile.net wrote:
> > A cursory look at the source didn't explain it, and
> > the manual infers this should work:
> >
> > 	 DHCP requests are honored if either:
> >           - there exists an NDB entry containing both the ethernet
> >           address of the requester and an IP address on the
originat-
> >           ing network or subnetwork.
> >           - a free dynamic address exists on the originating network
> >           or subnetwork.


             reply	other threads:[~2006-07-06 10:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-06 10:15 Retzki, Sascha [Xplain] [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-05 23:22 Steve Simon
2006-07-05 23:57 ` quanstro
2006-07-06 13:24 ` Richard Miller
2003-04-24 17:02 David Presotto

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=3AF26F5605627543BEC429636A522290235B97@rohrpostix.xplain.local \
    --to=sascha.retzki@xplain.de \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).