On Sat, Nov 28, 2015 at 4:33 PM, J Decker <d3c...@gmail.com> wrote: > Okay maybe it's not stored anywhere.... > > I was just having a plethora of network issues after updating. > > After finding others were reporting issues with the linux kernel 4.2.5 > I rollback to the prior stable 4.1.6... that resolved some of the > issues; but I was still getting a spam of messages every few seconds. > I reverted to systemd-227 and these stopped.
Distro? > Nov 28 07:18:14 tower2 systemd-networkd[354]: eno1: Starting DHCPv6 > client on NDisc request failed: Invalid argument > Nov 28 07:18:14 tower2 systemd-networkd[354]: br0: Starting DHCPv6 > client on NDisc request failed: Invalid argument > Nov 28 07:18:19 tower2 systemd-networkd[354]: eth0: Starting DHCPv6 > client on NDisc request failed: Invalid argument > Nov 28 07:18:19 tower2 systemd-networkd[354]: he-ipv6: Starting DHCPv6 > client on NDisc request failed: Invalid argument > Nov 28 07:18:19 tower2 systemd-networkd[354]: eno1: Starting DHCPv6 > client on NDisc request failed: Invalid argument > Nov 28 07:18:19 tower2 systemd-networkd[354]: br0: Starting DHCPv6 > client on NDisc request failed: Invalid argument > Nov 28 07:18:25 tower2 systemd-networkd[354]: eth0: Starting DHCPv6 > client on NDisc request failed: Invalid argument > Nov 28 07:18:25 tower2 systemd-networkd[354]: he-ipv6: Starting DHCPv6 > client on NDisc request failed: Invalid argument > Nov 28 07:18:25 tower2 systemd-networkd[354]: eno1: Starting DHCPv6 > client on NDisc request failed: Invalid argument > Nov 28 07:18:25 tower2 systemd-networkd[354]: br0: Starting DHCPv6 > client on NDisc request failed: Invalid argument > Nov 28 07:18:30 tower2 systemd-networkd[354]: eth0: Starting DHCPv6 > client on NDisc request failed: Invalid argument > Nov 28 07:18:30 tower2 systemd-networkd[354]: he-ipv6: Starting DHCPv6 > client on NDisc request failed: Invalid argument > Nov 28 07:18:30 tower2 systemd-networkd[354]: eno1: Starting DHCPv6 > client on NDisc request failed: Invalid argument > Nov 28 07:18:30 tower2 systemd-networkd[354]: br0: Starting DHCPv6 > client on NDisc request failed: Invalid argument > Nov 28 07:18:35 tower2 systemd-networkd[354]: eth0: Starting DHCPv6 > client on NDisc request failed: Invalid argument > Nov 28 07:18:35 tower2 systemd-networkd[354]: he-ipv6: Starting DHCPv6 > client on NDisc request failed: Invalid argument > Nov 28 07:18:35 tower2 systemd-networkd[354]: eno1: Starting DHCPv6 > client on NDisc request failed: Invalid argument > Nov 28 07:18:35 tower2 systemd-networkd[354]: br0: Starting DHCPv6 > client on NDisc request failed: Invalid argument > Nov 28 07:18:41 tower2 systemd-networkd[354]: eth0: Starting DHCPv6 > client on NDisc request failed: Invalid argument > > > > On Sat, Nov 28, 2015 at 4:18 AM, J Decker <d3c...@gmail.com> wrote: >> I recently updated my system, and am probably using systemd-228 >> >> When the network starts, the device I have configured as DHCP >> [Match] >> Name=eth0 >> >> [Network] >> DHCP=ipv4 >> Tunnel=he-ipv6 >> >> comes up with the old address and no default route set. If I disable >> that and manually run dhcpcd eth0 I get a valid IP and a default route >> that is an entirely different network than I get from systemd... so it >> must be saving the old address somewhere; but I cannot find any >> reference to that lease/state file. > _______________________________________________ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/systemd-devel _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel