On 14/10/13 12:03, Vladislav Grishenko wrote:
The problem with that is that RDNSS and DNSSL are per interface, not per-
prefix. Maybe the calculation should the maximum valid time of any prefix
advertised on the interface?
It will not work for several different prefixes and serveral different
global-scope addresses on dnsmasq interface.
Since it's per interface (actually not, per router, but whatever), and
onlink flag is always set, auto-cooked [::] rdnss address should contain
link-local address of that interface, not global.
Seems sensible. I wish I could remember why I changed from doing that 10
months ago:
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=55b42f6de33ab1de695509a053c9fbd38795150b
Cheers,
Simon.
After that, lifetimes can
be max (or 2/3 of max to fit RFC defaults) of any valid ra lifetime.
Also, announcing link-local addres of interface as RDNSS make life easier
while prefix changing, renumbering, etc.
As for user-specified RDNSS addresses, it's up to him to shoot in own foots
and specify static or dynamic servers.
Best Regards, Vladislav Grishenko
_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
