-1

in my network at home, driving some ubuntu-pc's one of them is dhcp-server running dhcp3-server. If i reboot this pc all the clients are going offline with a ahavi-ip-address (169.254...). what is going on during the short downtime of the dhcp-server, what is wrong on which side: client or server?

Peace Ice

raven
  • 18,004
  • 16
  • 81
  • 112
Ice
  • 1,162
  • 3
  • 14
  • 27

2 Answers2

1

Have a look at the lease time concepts of DHCP server.

Whenever I restarted the DHCP server, I never expect client to behave nicely.

Manish Sinha
  • 2,092
  • 2
  • 22
  • 33
  • Is it a good idea to set the lease time to a very high value, e.g. default-lease-time 600; max-lease-time 7200; What do you think? – Ice Oct 23 '09 at 17:48
  • I think the best deal would be to keep it a day. By default most DHCP servers are set to 24 hrs IIRC – Manish Sinha Oct 24 '09 at 18:53
  • Thanks, this is the best solution. i wonder why i got a lease-time of 600 in the default configuration... Now it is fixed, thx. Ice – Ice Oct 30 '09 at 20:53
  • 1
    @Ice the default lease time is usually low so configuration errors can be addressed quickly (i.e. if I change the server config, all the clients will update within 10 minutes). You'd typically increase it when you are satisfied with the configuration. – Simon Richter Jul 18 '13 at 07:29
0

well when ever you are running DHCP server you have to disable DHCP in your router. if you do not do this it will overtake your DHCP box. this strange IPs comes form there.

Artemis
  • 141
  • 4
  • 10
  • i do not have a router with a dhcp-service and if it would not set this kind of avahi-ip-addresses (IPv4 uses the special block 169.254.0.0/16 as described in RFC 3927 while IPv6 hosts use the prefix fe80::/10.). Have a look at [http://wiki.ubuntuusers.de/Avahi] and [http://en.wikipedia.org/wiki/Zero-configuration_networking] – Ice Aug 20 '13 at 06:40