Re: Wrong prefix delegation assignment on 6.4.{0-2}
Roy Marples
Mon Jul 28 08:54:29 2014
Hi
On 2014-07-28 01:40, Spyros Stathopoulos wrote:
Under 6.4.x I get the same but immediately after
ppp0: adding reject route to (same prefix as the ADV line above) via
::1
ppp0: adding route to (same prefix again)
and my internal interface (int0, lan facing) has the same prefix as
the ADV line but always ends in :1 instead of the MAC-based ipv6 that
is usually assigned.
Is this a bug or are there any route specific changes in 6.4.x that I
have missed? Please tell me if any more information is required. Any
ideas to debug?
From the changeset of 6.4.0 I posted to the list:
http://roy.marples.name/archives/dhcpcd-discuss/2014/0687.html
* If not specified, Delegated Prefixes will get an automatic SLA of
the interface index. If the biggest SLA and the assigned prefix fits
into a /64 then dhcpcd creates a /64 prefix so that SLAAC works. If
bigger than /64 is needed then dhcpcd creates one rounded upto the
nearest multiple of 8. Unless a configured SLA of 0 is assigned, a
reject route for the Delegated Prefix is installed to stop unassigned
addresses trying to be resolved upstream. Addresses added from Delegated
Prefixes now have a default address suffix of 1 instead of using a SLAAC
style address.
The reason why dhcpcd just adds 1 to the prefix is because the prefix we
get may not always be a /64.
As /64 is required for RA/RS and mac based SLAAC, but that isn't a
requirement of Prefix Delegation as a DHCPv6 address could easily be
assigned from a /90 pool if needed.
I suppose the question becomes, how are you advertising the prefix from
your delegation to your LAN?
If it's a fixed configuration file with a fixed default router ip then
it will need changing.
On NetBSD rtadvd works fine with dhcpcd as it stands, and no fixed
config is required.
Thanks
Roy
Archive administrator: postmaster@marples.name