| 1 |
On 10/14/2017 12:37 AM, Tom H wrote: |
| 2 |
> On Fri, Oct 13, 2017 at 5:58 PM, Daniel Frey <djqfrey@×××××.com> wrote: |
| 3 |
>> On 10/13/2017 11:05 AM, Canek Peláez Valdés wrote: |
| 4 |
>>> |
| 5 |
>>> Have you tried to boot the systems with the "disable_ipv6=1" kernel |
| 6 |
>>> parameter? |
| 7 |
>> |
| 8 |
>> I just tried this, and it doesn't seem to help. |
| 9 |
>> |
| 10 |
>> # cat /proc/cmdline |
| 11 |
>> disable_ipv6=1 root=/dev/md126p3 rd.auto=1 quiet rootfstype=ext4 |
| 12 |
>> init=/usr/lib/systemd/systemd |
| 13 |
>> |
| 14 |
>> But: |
| 15 |
>> |
| 16 |
>> # dmesg | grep -i ipv6 |
| 17 |
>> [ 22.218113] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready |
| 18 |
>> [ 22.241260] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready |
| 19 |
>> [ 26.421072] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready |
| 20 |
> |
| 21 |
> it's "ipv6.disable_ipv6=1" not "disable_ipv6=1". |
| 22 |
> |
| 23 |
|
| 24 |
Argh, I shouldn't have assumed that it was the full parameter. Oh well, |
| 25 |
on that machine, I managed to switch back to openrc. That didn't go real |
| 26 |
smoothly, portage couldn't figure out how to do it on it's own after |
| 27 |
switching profiles, it was blindly removing and rebuilding some packages |
| 28 |
manually that eventually made it work and not want to pull in systemd again. |
| 29 |
|
| 30 |
After that, I was able to reconfigure the kernel without ipv6 at all... |
| 31 |
rebooted... and openrc Just Worked(tm) with my network issue gone. |
| 32 |
|
| 33 |
For the other two, I'll try again but this time with the proper kernel |
| 34 |
parameter. That could've saved me a lot of time, but oh well. |
| 35 |
|
| 36 |
Dan |
Archives