Hi,

On Tue, Jun 18, 2013 at 11:35:41AM +0200, Thomas Bächler wrote:
> Documentation in pppd is incomplete here, at best. While I can define an
> interface identifier using the 'ipv6' option, it doesn't say anything
> about hand-shaking. My impression (from the wording of the
> documentation) is that this is useful if you have a static local and
> remote LL (know a-priori on both ends) and want to omit IPv6CP
> completely (just like specifying a local and remote IP for IPv4).

That interface identifier is used for the IPv6CP handshake - it's what
the client proposes, and the server side can then accept it, or assign
something else.  DSL providers usually accept, 3G providers usually
reject...

[..]
> The point of my patch was that we are not forced to do that. As long as
> we perform DAD (which the kernel does automatically), we do not violate
> RFC 4862 by choosing whatever interface identifier we want (I used the
> term hostid in the patch, but I just noticed that the RFC refers to
> "interface identifier" instead).
> 
> Another point of my patch is that it takes the path of least resistance:
> Instead of messing with the pppd negotiation, it applies its settings at
> a point where there is no negotiation and a large degree of freedom.

I think this change is useful (without having looked at the actual code),
for exactly these reasons.  With the IPv6CP handshake, you'll arrive at
something the provider controls - but then in the /64 that is announced
by RA, you can choose whatever host id / interface identifier you want,
and I can see people wanting to use something easy to type and remember,
like "::1".

(And you can't configure fully static IPv6 addresses here, as the assigned
prefix can - and likely, will - change)

gert

-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             [email protected]
fax: +49-89-35655025                        [email protected]

Attachment: pgpiw7ZUJ1cYA.pgp
Description: PGP signature

_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to