Klaus Frank

This PR might even address this issue it is open since 2015... https://github.com/docker/libnetwork/pull/826

I'd also suggest an mostly IPv6 only core implementation, most of the codebase does not need IPv4 addresses, using IPv4-mapped IPv6 addresses. Simplifying the codebase and allowing to focus on...

@murphy83 This project and this pending pull request are a good point to start if you'd like. I personally moved away from docker to using the container runtime directly or...

Hi, I was pointed here because of a similar design Issue, so what's now the difference between `-No*` and `-Skip*`? When would I use one over the other? Maybe it's...

@AvogatoWizardWhisker No, UAC also exists on servers.

> > ### DNS response for `ipv4only.arpa` > > This won't work in few specific scenarios: > > 1. where user have changed it's DNS servers to some without DNS64...

Nothing against explicit overwrites. Some people have especially cursed and broken environments and being able to disable autodetect is always good for debugging, even though when it turns out to...

Any update on this? This ticket has been dormant for almost half a year now. I couldn't see any problems with having `ipv6 = true`, esp because almost everywhere in...

The reason was that dhcpcd was changing system configuration that I had explicitely defined otherwise (and it doing so caused service disruptions). So I wasted excessive time trying to understand...

It has been a while, but if I recall correctly, it was an interaction between multiple settings (at least accept_ra and forwarding) that caused the disruption. The system was used...