On 30/10/11 16:21, Tom Metro wrote:
The dhcp-host option has a complex syntax, and the man page doesn't
cover all the rules.
One aspect not mentioned is that the order of the arguments don't have
to match what it is specified. The man page indicates:
--dhcp-host=[][,id:|*][,set:][,][,][,][,ignor
On 30/10/11 18:06, Tom Metro wrote:
Simon Kelley wrote:
Tom Metro wrote:
Simon Kelley wrote:
...the expiry times are 108 and 51 seconds after 1st
of Jan 1970 ie. well in the past. The NTP thing is exactly the problem.
OK, but even if Dnsmasq thinks the current time is 0 (1st Jan 1970), why
w
On 30/10/11 12:59, Olaf Flebbe wrote:
Hi,
in order to compile dnsmasq 2.59 on macosx lion one needs the Define
__APPLE_USE_RFC_2292 in order to get the IPV6_PKTINFO definition.
Thanks for that.
http://seclists.org/nmap-dev/2011/q3/810
implies that there's in alternative: __APPLE_USE_RFC_354
> Web site says:
>
> "For isolated systems, the user can periodically enter the correct time
> by hand (using Chronyc)."
>
> Aside from the ability to manually set the time (is that novel?), how
> does it better handle an intermittently connected node?
>
You are mixing two use cases. 1) you said
Ed W wrote:
> Try using chrony...
http://chrony.tuxfamily.org/
> ...it has much better handling of no internet cases.
Web site says:
"For isolated systems, the user can periodically enter the correct time
by hand (using Chronyc)."
Aside from the ability to manually set the time (is that novel
