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

Reuben Hawkins reubenhwk at gmail.com
Wed Sep 20 12:44:13 EDT 2017

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...

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

> Hi,
> I have a x86_64 server acting as a router for my network.
> eth0 - Internet with /64 IPv6 prefix provided through DHCP.
> eth1 - Local network
> I initially had RADVD configured to provide the /64 prefix the ISP
> provided to all clients on my network. However, it turns out that the
> Chromecast device does not support IPv6 and casting will not work with some
> applications. I wanted to use the "clients" block in radvd.conf to specify
> every device except for the Chromecast (aside, it would be nice if an
> option was made to make it a blacklist instead of a whitelist). I found
> that the eth1 device will not obtain/set an IPv6 address if I use a
> "clients" block, even when I list the fe80: address of eth1.
> How can I get eth1 to configure using a clients list? Is something like
> I'm trying to do supported?
> Thanks,
> Michael
> --
> 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/4566b5ca/attachment.html>

More information about the radvd-devel-l mailing list