| 1 |
On 24 January 2013, at 18:35, Manuel McLure wrote: |
| 2 |
|
| 3 |
> In any case, I did some more debugging and found that the problem |
| 4 |
> seems to be an interaction between dhcpcd and IPv6 configuration. The |
| 5 |
> latest version of dhcpcd now attempts by default to take over IPv6 |
| 6 |
> stateless configuration instead of letting the kernel take care of it |
| 7 |
> as happened before. dhcpcd appears to be getting an IPv6 address set |
| 8 |
> up before the IPv4 configuration is complete, and considers this "good |
| 9 |
> enough" to background itself instead of waiting for the IPv4 |
| 10 |
> configuration to be complete. The workaround was to add "noipv6rs" |
| 11 |
> (Disable solicition of IPv6 Router Advertisements) to the |
| 12 |
> /etc/dhcpcd.conf file so that dhcpcd ignores IPv6 configuration. The |
| 13 |
> kernel still configures IPv6 correctly, and dhcpcd now waits for the |
| 14 |
> IPv4 configuration to be complete before backgrounding itself. |
| 15 |
|
| 16 |
That sounds queer. You should file a bug. |
| 17 |
|
| 18 |
Stroller. |
Archives