On Tue, Jul 31, 2018 at 2:29 PM, Mantas Mikulėnas wrote:
>
> Disabling IPv6 link-locals might be a very bad idea though. (You need a
> link-local to run SLAAC or DHCPv6, to begin with...)
>
Good point. Perhaps I should make it an IPv4 only feature, in which case
the LinkLocalFallback option coul
On Tue, Jul 31, 2018 at 8:50 PM Thad Phetteplace wrote:
> 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:
>
> Within the [Network] section I've added a LinkLocalFallback option tha
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:
Within the [Network] section I've added a LinkLocalFallback option that
takes the same parameters as LinkLocalAddressing (yes,no,ipv4,ipv
I'm currently working with a client that needs LinkLocalAddressing as a
fallback when DHCP resolution fails. Currently with systemd-networkd it
looks like you have both DHCP and LinkLocalAddressing on, but that means
you get a second 169.254.*.* address even when DHCP succeeds. We
investigated usin
