<div dir="ltr">
<p class="gmail-MsoPlainText">You shouldn’t need a public /64 on your eth1.<span> </span>Routing works via the fe80 local addresses,
so eth1’s local fe80 should be the default route.<span> </span>Otherwise you only need link local
connectivity to your local network on eth1.<span>
</span>Your eth0 needs a public IPv6 address, and I assume it’s getting one.</p>Is there any other reason why you need a public /64 on your eth1? I can't think of any...<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 20, 2017 at 8:56 AM, Michael Cronenworth <span dir="ltr"><<a href="mailto:mike@cchtml.com" target="_blank">mike@cchtml.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I have a x86_64 server acting as a router for my network.<br>
<br>
eth0 - Internet with /64 IPv6 prefix provided through DHCP.<br>
eth1 - Local network<br>
<br>
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.<br>
<br>
How can I get eth1 to configure using a clients list? Is something like I'm trying to do supported?<br>
<br>
Thanks,<br>
Michael<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
radvd-devel-l mailing list : <a href="mailto:radvd-devel-l@lists.litech.org" target="_blank">radvd-devel-l@lists.litech.org</a><br>
<a href="http://lists.litech.org/listinfo/radvd-devel-l" rel="noreferrer" target="_blank">http://lists.litech.org/listin<wbr>fo/radvd-devel-l</a><br>
</font></span></blockquote></div><br></div>