Hello Eric, tis 2008-02-19 klockan 22:32 +0100 skrev Eric Spakman: > Hello Mats Erik, > > This default only works for setups which uses dhcp, not for statically > adresses or ppp(oe/oatm). So a default setting is difficult to give. > This is true, but since Bering is delivered with a setting that has dhcp active, I find it backwards not to let Openntpd use that setting from the very start. Hence it is mostly a matter of forcing _every_ user to make the necessary configuration changes, or to let about every second user (those with static/ppp networks) do a major reconfiguration! Anyway, thanks to the question of Matt Cartter, we got this opportunity to mention this matter on the forum, so other users will be more likely to find their own solution.
Regards Mats E A > http://leaf.sourceforge.net/doc/buci-dnsmasq3.html > > Eric > > > Hello Matt Cartter, > > > > > > your problem is due to the fact that Openntpd is using /etc/resolv.conf, > > which in the default setting is pointing to the interior address > > 192.168.1.254. Unfortunately, Dnsmasq is in its > > default setting (of Bering) not propagating the external nameserver from > > /etc/dhcp/resolv.conf, > > so Openntpd has no access to any external time server, and thus produces > > those error messages. The simplest remedy is to activate name resolution: > > > > > > resolv-file=/etc/dhcpc/resolv.conf > > > > in /etc/dnsmasq.conf. Then Openntpd will be operational from boot time. I > > have suggested this default value to KP Kirchdörfer. We will have to wait > > and see whether it does get implemented. > > > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ ------------------------------------------------------------------------ leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
