RE: [SLE] yast: how to set up static DHCP addresses
-----Original Message----- From: stephan beal [mailto:stephan@s11n.net] Sent: Thursday, September 14, 2006 1:12 PM To: suse-linux-e@suse.com 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.
Marlier, Ian wrote:
Forgot to set the "don't be broken" flag in your Windows install, did you? :-)
Damnit, now you tell me! Where is that flag? I've been looking for it for years! Probably hidden somewhere in the bottomless pit of the registry... :)
I think I'd be tempted to go a different way; rather than setting
On Thursday 14 September 2006 18:13, Marlier, Ian wrote: 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...
Hm, if you want to be save, you should get something like 127.0.0.2/31 ;-) But such a long lease time? In test /tryout environment, one hour lets you experiment safely. (I once handed out an address to an unknown machine and it took way too long for the lease to expire, since then we keep it short, and it does not produce any burden on network or the dhcp-server. For work environment, i would suggest 8-24 hours. In your subnet, one can give via dhcp, fixed adresses to known mac-addresses, and a (small) pool for the labtops of road-warriors. Hans -- pgp-id: 926EBB12 pgp-fingerprint: BE97 1CBF FAC4 236C 4A73 F76E EDFC D032 926E BB12 Registered linux user: 75761 (http://counter.li.org)
participants (3)
-
Hans Witvliet -
Marlier, Ian -
suse＠rio.vg