Re: [systemd-devel] F30->F31 systemd-networkd no IPv6 autoconfiguration

2019-11-09 Thread Anthony Joseph Messina
On Saturday, November 9, 2019 1:49:04 PM CST Thomas Haller wrote: > On Fri, 2019-11-08 at 20:30 -0600, Anthony Joseph Messina wrote: > > Thank you for responding Ryan. AFAIK, I don't have both systemd- > > networkd and > > NetworkManager "running" or enabled. In fact, I have had > > NetworkManager

Re: [systemd-devel] F30->F31 systemd-networkd no IPv6 autoconfiguration

2019-11-09 Thread Anthony Joseph Messina
On Saturday, November 9, 2019 1:49:04 PM CST Thomas Haller wrote: > On Fri, 2019-11-08 at 20:30 -0600, Anthony Joseph Messina wrote: > > Thank you for responding Ryan. AFAIK, I don't have both systemd- > > networkd and > > NetworkManager "running" or enabled. In fact, I have had > > NetworkManager

Re: [systemd-devel] F30->F31 systemd-networkd no IPv6 autoconfiguration

2019-11-09 Thread Ryan Gonzalez
Apologies, I didn't realize you had already tried masking the service. Since Fedora uses systemd in the initramfs, I *think* you could instead try booting with systemd.mask=NetworkManager.service, which will should mask it early boot before your rootfs is even mounted. On Fri, Nov 8, 2019 at 8:31

Re: [systemd-devel] F30->F31 systemd-networkd no IPv6 autoconfiguration

2019-11-09 Thread Thomas Haller
On Fri, 2019-11-08 at 20:30 -0600, Anthony Joseph Messina wrote: > Thank you for responding Ryan. AFAIK, I don't have both systemd- > networkd and > NetworkManager "running" or enabled. In fact, I have had > NetworkManager > disabled on these systems for some time (back through F27, I > believe)

Re: [systemd-devel] F30->F31 systemd-networkd no IPv6 autoconfiguration

2019-11-08 Thread Anthony Joseph Messina
Thank you for responding Ryan. AFAIK, I don't have both systemd-networkd and NetworkManager "running" or enabled. In fact, I have had NetworkManager disabled on these systems for some time (back through F27, I believe). Post upgrade (or fresh install) I ensure that NetworkManager is not re-ena

Re: [systemd-devel] F30->F31 systemd-networkd no IPv6 autoconfiguration

2019-11-08 Thread Ryan Gonzalez
Having two networking systems running at once can cause all sorts of problems, not sure if this is the issue here or why NM is still starting but you can try using 'systemctl mask' on it to completely prevent it from running. On Fri, Nov 8, 2019, 7:37 PM Anthony Joseph Messina wrote: > I apologi

[systemd-devel] F30->F31 systemd-networkd no IPv6 autoconfiguration

2019-11-08 Thread Anthony Joseph Messina
I apologize if this isn't the right place to post this request for assistance. I've attempted the Fedora User's list with no luck and would prefer to ask before filing a bug. After a successful "dnf systemd upgrade" F30->F31, I'm finding that a few of my machines which use systemd-networkd ins