Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've got a Raspberry Pi arriving any day now, and I intend to use it (amongst other things) as a DHCP server.

Currently we have a few devices on our network to which we would like to assign static IPs, and a router, which is currently the DHCP server (the router can assign static IPs, but is buggy as hell, I've never got the config to stick for more than a few hours).

Having connected the Pi to the network and configured dhcpl-3-server, what do I need to do on the rest of my network so that it works properly (clients get their IPs from the Pi, and use the Router as the default gateway)?

share|improve this question
@Mitch Should I? What's the difference? – fredley May 31 '12 at 16:13
up vote 1 down vote accepted

If your DHCP configuration on the Raspberry Pi is ok and you don't need any other feature, you shouldn't need anything else. But you have to make sure the Raspberry Pi gives the proper default gw address to the clients, as well as a primary and a secondary DNS server (again the router for the primary, I suppose and I suggest a Google Public DNS server or any other OpenDNS server for the secondary).

This is my old DHCPd configuration, maybe you can find it useful.

subnet netmask
    default-lease-time 86400;
    max-lease-time 86400;
    option subnet-mask;
    option broadcast-address;
    option routers;
    option domain-name-servers;
    option domain-name-servers;
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.