[radvd-devel-l] Adding local interface to clients list

Reuben Hawkins reubenhwk at gmail.com
Wed Sep 20 22:58:25 EDT 2017

I don't think an iface should configure itself based on RA sent from
itself.  I recall that being a problem in the past, but not sure now.

Nonetheless, If you have the prefix on that host and you're using it to
configure RADVD, then you have all the info you need to set a public IP on
eth1 if you want one.  I'd recommend not doing that though.  There's no
need for it.

On Wed, Sep 20, 2017 at 10:09 AM, Michael Cronenworth <mike at cchtml.com>

> On 09/20/2017 11:44 AM, Reuben Hawkins wrote:
>> You shouldn’t need a public /64 on your eth1.Routing works via the fe80
>> local addresses, so eth1’s local fe80 should be the default route.Otherwise
>> you only need link local connectivity to your local network on eth1.Your
>> eth0 needs a public IPv6 address, and I assume it’s getting one.
>> Is there any other reason why you need a public /64 on your eth1? I can't
>> think of any...
> Sure, it's not required, but I just noticed that difference when I was
> configuring it.
> I'm coming from a IPv6-to-4 tunnel setup where both ports had addresses.
> --
> radvd-devel-l mailing list  :  radvd-devel-l at lists.litech.org
> http://lists.litech.org/listinfo/radvd-devel-l
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.litech.org/pipermail/radvd-devel-l/attachments/20170920/e297900f/attachment.html>

More information about the radvd-devel-l mailing list