<div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Tue, Jul 31, 2018 at 8:50 PM Thad Phetteplace <<a href="mailto:tdphette@gmail.com">tdphette@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><p>I've got a pull request for this almost ready to go. I just need to
clean it up a bit and update the man pages with the new config options.
They are as follows:</p>
<p>Within the [Network] section I've added a LinkLocalFallback option
that takes the same parameters as LinkLocalAddressing
(yes,no,ipv4,ipv6). This will allow IPv4 and IPv6 to be configured
independently. Selecting LinkLocalFallback assumes LinkLocalAddressing
is turned on for that protocol family, so there is no need to select
both. Thus if you do LinkLocalFallback=ipv4, there is no need to do
LinkLocalAddressing=ipv4... that is assumed. If you do both, it is
fine... but the fallback feature will take precedence. Note that I've
only implemented ipv4 so far. It will let you set ipv6 in the config,
but I don't have the plumbing in place to support it yet, so it will
just be ignored.</p></div></blockquote><div>Disabling IPv6 link-locals might be a very bad idea though. (You need a link-local to run SLAAC or DHCPv6, to begin with...)</div></div><div><br></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Mantas Mikulėnas</div></div></div>