RE: [SLE] yast: how to set up static DHCP addresses



-----Original Message-----
From: stephan beal [mailto:stephan@xxxxxxxx]
Sent: Thursday, September 14, 2006 1:12 PM
To: suse-linux-e@xxxxxxxx
Subject: Re: [SLE] yast: how to set up static DHCP addresses

On Thursday 14 September 2006 18:13, Marlier, Ian wrote:
I think I'd be tempted to go a different way; rather than setting
the
DHCP server to always hand the same addresses to those clients, why
not just set the lease time to, oh, a year or something?

Even if the clients leave, come back, and request a new address, the
DHCP server will hand them the one they had before (since that MAC
address still has a lease for that address).

That is true, and my lease time is set to 30 days, but it seems that
one
of my boxes is getting a different IP depending on whether a log in to
Windows or Linux.

Now that's wacky behavior...

Forgot to set the "don't be broken" flag in your Windows install, did
you? :-)

Given that dhcpd seems to think that the requesting computer is a
different machine depending on OS, I'm not sure that a static config
will help; the lease file lookup happens using the exact same piece of
info that the static assignment lookup uses, and so you should end up
with the same behavior post-static-entry.

Which is not to say that the behavior makes sense; nor that it should be
that way; nor that dhcpd actually necessarily acts in the expected
manner...


(It should be noted here that I don't use YaST to manage my DHCP
server; I tried for a while, but the DHCP server config module made
a
real hash of things, and didn't support a whole bunch of the
features
that DHCP offers. Last version I tried was 9.3, though, so it may
be
better now.)

It's suitable for basic use, but doesn't provide access to any
non-basic
features.

Which is why I dropped it, and just roll my own dhcpd.conf file now.
It's easier to maintain 100+ static assignments, along with all kinds of
wacky pxe/tftp/etc related config options, than it is to try to fix the
problems that config tools were causing.

--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@xxxxxxxx

Relevant Pages

  • Client ip address changed without notice
    ... That is IP lease time. ... DHCP server can I use the IP once again. ... >network connection. ...
    (microsoft.public.win2000.networking)
  • Re: Understanding the impact of a DHCP server outage
    ... At 50% of the lease time the DHCP client attempts to renew its lease from the DHCP server that it leased the address from via unicast. ... If this is not successful the DHCP client waits until 87.5% of the lease time has expired and then re-attempts to renew it address, again via unicast to the DHCP server. ...
    (microsoft.public.windows.server.networking)
  • Re: Understanding the impact of a DHCP server outage
    ... At 50% of the lease time the DHCP client attempts to renew its lease from ... from any DHCP server via the standard broadcast method. ...
    (microsoft.public.windows.server.networking)
  • Re: Some issues after DHCP migration
    ... All I ever did to migrate a DHCP Server was to stop the service on the both old ... I just finished transfering a DHCP config and db from an old DC to a new DC ... I got a warning for my new DHCP server with Event ...
    (microsoft.public.windows.server.networking)
  • Re: named sandbox trouble
    ... I assumed this was because of DHCP, but disabling DHCP meant ... it (and it's config file) have a manpage. ... In my case, I disabled the DHCP server on my ADSL-modem/router/switch, ...
    (freebsd-net)