David Howells via networkmanager-list <[email protected]>
writes:

> Andrei Borzenkov <[email protected]> wrote:
>
>> The same effect can probably be achieved by setting /128 local address
>> and adding /128 route to peer address.
>
> Any suggestion as to what address I should set?  My address block is
> 2001:8b0:194::/48 if that helps.  I've tried setting a random one from that,
> but it causes an error ("cif6addr: ioctl(SIOCDIFADDR): No such address" I
> think - I can't try it just now).



> I've also tried setting a route, but that didn't seem to work either
> ("sif6addr: ioctl(SIOCADDRT): Permission denied (line 2646)" I think was the
> error).
>
> Further, NM doesn't allow me to specify a peer address ("ipv6 ," is the only
> parameter that it will specify, with both addresses omitted), and I don't know
> how to automatically retrieve the peer address from within the NM framework.

Note that you don't specify the peer address in your ifcfg file either.
pppd(8) documents it as

  ipv6 <local_interface_identifier>,<remote_interface_identifier>

and that's what it is.  These are input values for IPV6CP, which doesn't
negotiate addresses or routing. That's supposed to be configured the
same way as for any other IPv6 link: Using SLAAC and DHCPv6.  Which
makes IPv6 over PPP pretty different from IPv4 over PPP, but exactly the
same as IPv6 over anything else.

The negotiated interface identifiers will be combined with fe80::/64 to
create link local addresses and with any on-link prefixes advertised in
RAs.

There is no IPv6 default route option either AFAIK.  But I believe it
would make sense to offer this as an alternatve in NM for cases where
the peer doesn't send any RA.  It is a pretty common use case.


Bjørn
_______________________________________________
networkmanager-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Reply via email to