[Dnsmasq-discuss] System tries to get its address by DHCP before dnsmasq starts up - how to stop it?
I have a little server system running dnsmasq version 2.59 under Ubuntu 12.04 (I have just upgraded it from Ubuntu 10.04). While booting it tries to get its network configuration (using DHCP presumably) from the LAN, since *it's* the DHCP server this doesn't work but it wastes a lot of time waiting for things to time out and produces various error messages on the way. How do I configure the system so that it doesn't do this? -- Chris Green ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Can't figure out how to assign static IPv6 addresses to clients
On 04/10/12 00:32, Carlos Laviola wrote: On Tue, Oct 2, 2012 at 4:52 PM, Simon Kelley si...@thekelleys.org.uk wrote: On 02/10/12 14:56, Dan Williams wrote: On Mon, 2012-10-01 at 21:49 +0200, Sean Boran wrote: Perhaps you clients are getting their addresses from router advertisement, and not DHCP. So disable RA first in dnsmasq (and make sure no router or other host is publishing one) You don't want to disable RA, you want to tell clients to use managed configuration in the RA. If you disable RA, then nothing on that link will have a default router and thus no way to get packets to anything that's not in the broadcast domain. DHCPv6 does not have any facility to provide a default gateway like IPv4, since that's precisely the functionality of RAs. So you really want to reconfigure either dnsmasq or radvd to set the M (Managed) flag, which will tell the clients to get their address from DHCPv6, not generate one from the RA prefix option. Dan is right, and the way to do this in dnsmasq is to define a dhcp-range, and set the global enable-ra flag. That will send RA (for the default route) with the M flag set (no SLAAC address). If you want SLAAC addresses _as_well_ as DHCPv6 assigned ones, add the slaac keyword to the dhcp-range. That clears the M flag. I tried all this, yet it still won't work. It used to work when I used radvd + the WIDE DHCP daemon. I'm at a loss here... Thanks for all the help, though. See my later post, which has more details. The best thing to do would be to capture RA packets from the working, radvd system and the non-working dnsmasq one, so that we can analyse the difference. Simon. ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] System tries to get its address by DHCP before dnsmasq starts up - how to stop it?
On Thu, Oct 04, 2012 at 10:23:33AM +0100, Chris Green wrote: I have a little server system running dnsmasq version 2.59 under Ubuntu 12.04 (I have just upgraded it from Ubuntu 10.04). While booting it tries to get its network configuration (using DHCP presumably) from the LAN, since *it's* the DHCP server this doesn't work but it wastes a lot of time waiting for things to time out and produces various error messages on the way. How do I configure the system so that it doesn't do this? Further to this the delay is cause by /etc/init/failsafe.conf, even if I have static IP correctly configured in /etc/network/interfaces the silly init sequence still does all the waits in /etc/init/failsafe.conf waiting for DHCP. Google searches just produce the standard way to set up static IP but no workaround for the delays. -- Chris Green ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] System tries to get its address by DHCP before dnsmasq starts up - how to stop it?
On Thu, 2012-10-04 at 12:20 +0100, Chris Green wrote: On Thu, Oct 04, 2012 at 10:23:33AM +0100, Chris Green wrote: I have a little server system running dnsmasq version 2.59 under Ubuntu 12.04 (I have just upgraded it from Ubuntu 10.04). While booting it tries to get its network configuration (using DHCP presumably) from the LAN, since *it's* the DHCP server this doesn't work but it wastes a lot of time waiting for things to time out and produces various error messages on the way. How do I configure the system so that it doesn't do this? Further to this the delay is cause by /etc/init/failsafe.conf, even if I have static IP correctly configured in /etc/network/interfaces the silly init sequence still does all the waits in /etc/init/failsafe.conf waiting for DHCP. Google searches just produce the standard way to set up static IP but no workaround for the delays. Is the machine running NetworkManager? If so it could be a misconfiguration issue or an Upstart dependency issue. Dan ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
