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