[systemd-devel] Where is DHCP Address stored?

2015-11-28 Thread J Decker 
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

Re: [systemd-devel] Where is DHCP Address stored?

2015-11-28 Thread J Decker 
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.

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  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

Re: [systemd-devel] Where is DHCP Address stored?

2015-11-28 Thread J Decker 
On Sat, Nov 28, 2015 at 7:36 AM, Tom Gundersen  wrote:
> On Sat, Nov 28, 2015 at 4:33 PM, J Decker  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?

Arch; did an update lastnight/this morning when my networking fell apart.

>
>> 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  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

Re: [systemd-devel] Where is DHCP Address stored?

2015-11-28 Thread Tom Gundersen 
On Sat, Nov 28, 2015 at 4:42 PM, J Decker  wrote:
> On Sat, Nov 28, 2015 at 7:36 AM, Tom Gundersen  wrote:
>> On Sat, Nov 28, 2015 at 4:33 PM, J Decker  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?
>
> Arch; did an update lastnight/this morning when my networking fell apart.

As far as I can tell the fixes for these issues are upstream, but not
backported. You could try with current git, or ask downstream to
backport.

>>> 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  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

Re: [systemd-devel] Where is DHCP Address stored?

2015-11-28 Thread Tom Gundersen 
On Sat, Nov 28, 2015 at 4:33 PM, J Decker  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  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