[systemd-devel] dhcpd fails to negotiate with Cox Cable

[J Decker]

See Subject.

I can grab dumps of both windows and linux attempting to negotiate...

I can probably catch when the IP lease expires (or connection resets?) and
the request is done again.

>From what I can tell 1) when the modme is booting it will grant like a 60
second lease on 192.168.100.11(something)  which can connect to the modem
directly...
then that expires and another is requests a new one, which it gets from a
10.something address , and is fom there given the real IP; but this last
step seems to be ignored; and/or timing sensitive that if the response to
10. isn't soon enough, it fails to send another redirect sort of response...

I've attempted to use DHCP options to make the packets match as much as
possible, but some flags I don't have control of ( Although ATM I don't
recall those).

The last few days it's disconnected at least once per day.  I have a
workaround. I put the router's mac on a window device, renew there, and
then re-plug the cable; which that last negotitation must work since on
disconnect it loses all addresses(?)
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] systemd/hostnamed: setting the hostname and using it in the DHCP Discover

[J Decker]

On Mon, Jul 31, 2017 at 7:38 AM, Andrey Yurovsky  wrote:

> On Mon, Jul 31, 2017 at 7:24 AM, Lennart Poettering
>  wrote:
> > On Fr, 28.07.17 12:08, Andrey Yurovsky (yurov...@gmail.com) wrote:
> >
> >> I have an embedded target where the hostname is expected to be a
> >> string derived in part from the MAC address of an Ethernet interface.
> >> I've been looking at how to properly set the system's hostname and
> >> also have systemd-networkd use it in the DHCP request it sends out,
> >> however there seems to be an order of operations issue.
> >>
> >> 1. in systemd/core/main.c the /etc/hostname contents are
> unconditionally read
> >> 2. I can add a service that uses the special network-pre.target to
> >> override /etc/hostname with my generated string and I see that while
> >> the initial string is pickedup by systemd, the new hostname will in
> >> fact be used
> >> 3. I then have a .network file specifying DHCP on that Ethernet
> interface
> >>
> >> But then on initial boot I see that the DHCP Discover coming out has
> >> option 12 set to the original hostname that systemd picked up in
> >> main.c, even though the network-pre.target caused my unit to run. I
> >> can then reboot the system and this time main.c picks up the "new"
> >> hostname and option 12 is indeed set to this.
> >>
> >> One workaround I found was to have my unit write the Hostname= option
> >> to the .network file but that seems like the wrong approach.
> >>
> >> Is there a correct way to replace or otherwise set the hostname and
> >> have systemd use it from the beginning and ensure that the DHCP client
> >> specifies it in option 12?
> >
> > Hmm, I am not sure I follow. Do you want the hostname to be "sticky"?
> > i.e. if you boot up once, and your special hostname is not initialized
> > yet, you initialize from whatever the MAC address is, and then store
> > it to /etc/hostname, and from that point on and for all future boots
> > it's supposed to stay fixed? Or do you want it to be fully
> > dynamic: as soon as an ethernet device shows up, set the hostname,
> > and when no device has shown up the hostname should remain
> > uninitialized, and on subsequent boot everything starts from fresh,
> > with no previous data?
>
> Sorry, what I mean is the hostname is "sticky" but is always the same
> (there's just the one built-in Ethernet interface, nothing is
> dynamic), the trick is I always want that generated hostname used and
> I never want to see a DHCP Discover go out with a default hostname
> that isn't this generated string (it's a bit off but is meant to
> maintain expected behavior from this device).
>
>
There's an option under [dhcp] section
https://www.freedesktop.org/software/systemd/man/systemd.network.html

SendHostname=
When true (the default), the machine's hostname will be sent to the DHCP
server.

UseHostname=
When true (the default), the hostname received from the DHCP server will be
set as the transient hostname of the system

Hostname=
Use this value for the hostname which is sent to the DHCP server, instead
of machine's hostname.


would think if you set your name there it won't matter what /etc/hostname
is?

>
> > Under the assumption you want the latter: just drop /etc/hostname, so
> > that no static hostname is managed by systemd/hostnamed. In this case
> > the system will boot up with the fallback hostname (which is
> > "localhost" unless your distro overrides that at compile time). Then,
> > add a udev rule that is run when an interface shows up, and that
> > changes the hostname as necessary, maybe by invoking the
> > /usr/bin/hostname binary.
>
> I didn't think of that, thank you! That makes a lot of sense.
>
> > The DHCP client in networkd will query the hostname the instant it
> > starts setting up the DHCP session. It will use whatever is set at
> > that point in time. Hence, if you set the hostname from the udev rule
> > things should be properly race-free as networkd will only take
> > possession of any interface after the udev rule ran, and hence will
> > necessarily initialize its DHCP client at a point in time the hostname
> > is set to what you want it to be set to.
>
> Got it. Thank you for taking the time to answer my weird question, I
> really appreciate it.
> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
>
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] systemd-networkd-wait-online: Wait for specific address family to be online

[J Decker]

goes back to 'can we have a configurable script to run when DHCP assigns
the address?'
Surely it can't be that hard to read a config line, save it, and later
execute a script


On Tue, Sep 6, 2016 at 1:54 PM, Ernst Bammer  wrote:

> Hi,
> sorry to bring this up again, but maybe somebody is back from vacation
> who can answer this? ;-)
> Best regards, Ernst
>
> On Sun, Jul 24, 2016 at 12:31 PM, Ernst Bammer 
> wrote:
> > Hi,
> >
> > I have a service that depends on a non-loopback IPv4 address to be
> > available at start-up. My network configuration is done with networkd,
> > it's very simple and basically just:
> >
> > [Match]
> > Name=eth*
> > [Network]
> > DHCP=v4
> >
> > I've added the following to my service:
> >
> > [Unit]
> > Requires=network-online.target
> > After=network-online.target
> >
> > Unfortunately, there is no IPv4 address when the service tries to
> > start (and then crashes).
> > For debugging purposes, I added this to [Service]:
> >
> > ExecStartPre=/bin/sh -c "/bin/cat /run/systemd/netif/links/*"
> > ExecStartPre=/bin/sh -c "/bin/cat /run/systemd/netif/leases/*"
> >
> > On reboot, I see this in the journal:
> >
> > Jul 24 11:41:59 myhost sh[492]: # This is private data. Do not parse.
> > Jul 24 11:41:59 myhost sh[492]: ADMIN_STATE=configured
> > Jul 24 11:41:59 myhost sh[492]: OPER_STATE=degraded
> > Jul 24 11:41:59 myhost sh[492]: FLAGS=69699
> > Jul 24 11:42:00 myhost sh[529]: /bin/cat: /run/systemd/netif/leases/*:
> > No such file or directory
> > Jul 24 11:42:00 myhost systemd[1]: test.service: control process
> > exited, code=exited status=1
> > Jul 24 11:42:00 myhost systemd[1]: Failed to start Test.
> > Jul 24 11:42:00 myhost systemd[1]: Unit test.service entered failed
> state.
> >
> > I suspect the problem might be that the network interface also gets a
> > link-local IPv6 address, and thus systemd-networkd-wait-online
> > immediately returns. If I disable IPv6 on my system (by blacklisting
> > the ipv6 module), it works as expected (s-n-w-o waiting for DHCPV4
> > address).
> >
> > Is there a way to get s-n-w-o to wait for an address family (in my
> > case IPv4) to be available? Or is there any other workaround?
> >
> > FWIW, I'm using Debian 8 Jessie (systemd version 215).
> >
> > Thank you!
> > Ernst
> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
>
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] tunnel configuration broken

[J Decker]

so is this 'working as designed' so I'm not allowed to make a tunnel
on a DHCP device using systemd networkd configuration files?
I can fall back to configuring it as a .service though I had as many
issues with that as the normal configuration.

1) this again goes back to why I want to run a script on DHCP address
assignment, preferably with the new address given as a parameter to
the script... or 2) if there was a way to specify ${eth0.address} as
the tunnel (netdev? network?) configuration parameter



On Mon, Feb 29, 2016 at 10:44 PM, J Decker <d3c...@gmail.com> wrote:
> Yes; I thnk instead it's a DHCP issue; since the device has no address
> to start, adding the tunnel endpoing to that socket without an address
> seems to be failing.  It has to wait until the DHCP signal, and then
> it really needs the DHCP address to update the tunnel endpoint
> configuration.
>
> On Mon, Feb 29, 2016 at 10:36 PM, Kai Krakow <hurikha...@gmail.com> wrote:
>> Am Mon, 29 Feb 2016 19:12:11 -0800
>> schrieb J Decker <d3c...@gmail.com>:
>>
>>> I would have thought that naming 00-eth0.network; 01-eth1.network or
>>> something would start devices in that order?
>>
>> No... It does say nothing about order in your sense. It's just ordering
>> which configuration overwrites another when options are specified in
>> multiple files.
>>
>> So it's not start order, it just order of precedence for configuration
>> options.
>>
>> --
>> Regards,
>> Kai
>>
>> Replies to list-only preferred.
>>
>> ___
>> systemd-devel mailing list
>> systemd-devel@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] howto systemd restart one network device

[J Decker]

yes restart repeatedly does the same thing and doesn't work



On Tue, Mar 1, 2016 at 10:49 AM, Kai Krakow <hurikha...@gmail.com> wrote:
> Am Mon, 29 Feb 2016 22:59:17 -0800
> schrieb J Decker <d3c...@gmail.com>:
>
>> well that was the search
>>
>> after everything is up how do I restart a single device so it will
>> work in the meantime...
>
> I usually do "systemctl restart systemd-networkd" which probably
> restarts all devices. This worked for me all the time.
>
> Maybe something like:
>
> $ systemctl restart sys-subsystem-net-devices-enp5s0.device
>   ^^
> put your device here
>
> Found by "systemctl | fgrep enp"
>
> However, "systemctl show ..." indicates it doesn't support doing that.
>


 fgrep he   // he is in 'ethernet' but he-tunnel is the .netdev I want to start
[code]
  sys-devices-pci:00-:00:19.0-net-eno1.device
 loaded active plugged   Ethernet Connection
I217-LM
  sys-subsystem-net-devices-eno1.device
 loaded active plugged   Ethernet Connection
I217-LM
  httpd.service
 loaded active running   Apache Web Server
  kmod-static-nodes.service
 loaded active exitedCreate list of required
static device nodes for the current kernel
  
systemd-fsck@dev-disk-by\x2duuid-50a189be\x2d1ec4\x2d4efc\x2db575\x2d7396e7923413.service
loaded active exitedFile System Check on
/dev/disk/by-uuid/50a189be-1ec4-4efc-b575-7396e7923413
  
systemd-fsck@dev-disk-by\x2duuid-d55e3257\x2d76bb\x2d49a5\x2da9ff\x2d076b0559369e.service
loaded active exitedFile System Check on
/dev/disk/by-uuid/d55e3257-76bb-49a5-a9ff-076b0559369e
  
systemd-fsck@dev-disk-by\x2duuid-fec23492\x2d4be8\x2d4c03\x2d9349\x2d9ee06ab2c5ff.service
loaded active exitedFile System Check on
/dev/disk/by-uuid/fec23492-4be8-4c03-9349-9ee06ab2c5ff
  man-db.timer
 loaded active waiting   Daily man-db cache update
LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB= The low-level unit activation state, values depend on unit type.

[/code]


and just blindly trying it...

systemctl restart sys-subsystem-net-devices-he-tunnel.netdev
Failed to restart sys-subsystem-net-devices-he-tunnel.netdev.service:
Unit sys-subsystem-net-devices-he-tunnel.netdev.service not found.



> --
> Regards,
> Kai
>
> Replies to list-only preferred.
>
> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] howto systemd restart one network device

[J Decker]

well that was the search

after everything is up how do I restart a single device so it will
work in the meantime...
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] tunnel configuration broken

[J Decker]

On Mon, Feb 29, 2016 at 7:12 PM, J Decker <d3c...@gmail.com> wrote:
> systemd 229-3
>
> I recently updated my Arch Linux.
>
> https://wiki.archlinux.org/index.php/IPv6_tunnel_broker_setup
>
> using a hurricane electric tunnel...
>
> and now the tunnel device wants to start and add all the static
> addresses that are specified on other physical net devices in fact
> the HE is attached to a bridge that has to wait itself for other
> things to start.
>
> I would have thought that naming 00-eth0.network; 01-eth1.network or
> something would start devices in that order?
>
> How do I specify a dependance order between network configurations?


Sorry I sent to wrong place.  I did recently add a ipv6 to a bridge to
stop another issue.  but after moving the ipv6 to the end of the
bridge it still doesn't wait for eth0 to come up before it starts the
tunnel

[code]

[root@tower2 network]# systemctl start systemd-networkd
[root@tower2 network]# Feb 29 20:15:23 tower2 polkitd[913]: Registered
Authentication Agent for unix-process:3325:15819222 (system bus name
:1.44 [/usr/bin/pkttyagent --notify-fd 4 --fallback], object path
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.utf-8)
Feb 29 20:15:23 tower2 systemd[1]: Starting Network Service...
Feb 29 20:15:23 tower2 systemd-networkd[3331]:
[/etc/systemd/network/he-tunnel.netdev:9] Tunnel addresses
incompatible, ignoring assignment: 
Feb 29 20:15:23 tower2 systemd-networkd[3331]:
[/etc/systemd/network/he-tunnel.netdev:10] Tunnel addresses
incompatible, ignoring assignment: 
Feb 29 20:15:23 tower2 systemd-networkd[3331]: Tunnel with invalid
address family configured in /etc/systemd/network/he-tunnel.netdev.
Ignoring
Feb 29 20:15:23 tower2 systemd-networkd[3331]:
[/etc/systemd/network/he-tunnel.network:7] Route is invalid, ignoring
assignment: 
Feb 29 20:15:23 tower2 systemd-networkd[3331]:
[/etc/systemd/network/01-eth0.network:8] Tunnel is invalid, ignoring
assignment: he-ipv6


[/code]

there's then another started... oh starting started.
eth0 needs to be up already and I can't confirm why it wouldn't be?
it's DHCP so it needs to know when it gets its address before I can
assign the he-tunnel.

[/code]
Feb 29 20:15:23 tower2 systemd-networkd[3331]: br0: netdev ready
Feb 29 20:15:23 tower2 systemd-networkd[3331]: br0: Gained IPv6LL
Feb 29 20:15:23 tower2 systemd-networkd[3331]: eno1: Gained IPv6LL
Feb 29 20:15:23 tower2 systemd-networkd[3331]: eth0: Gained IPv6LL
Feb 29 20:15:23 tower2 systemd-networkd[3331]: Enumeration completed
Feb 29 20:15:23 tower2 systemd[1]: Started Network Service.
Feb 29 20:15:23 tower2 systemd-networkd[3331]: br0: netdev exists, using ex
[/code]
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] tunnel configuration broken

[J Decker]

systemd 229-3

I recently updated my Arch Linux.

https://wiki.archlinux.org/index.php/IPv6_tunnel_broker_setup

using a hurricane electric tunnel...

and now the tunnel device wants to start and add all the static
addresses that are specified on other physical net devices in fact
the HE is attached to a bridge that has to wait itself for other
things to start.

I would have thought that naming 00-eth0.network; 01-eth1.network or
something would start devices in that order?

How do I specify a dependance order between network configurations?
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] dhcp address change callback?

[J Decker]

On Mon, Jan 25, 2016 at 4:43 AM, Lennart Poettering
 wrote:
> On Sat, 23.01.16 14:22, Johannes Ernst (johannes.er...@gmail.com) wrote:
>
>> Is there a way to receive a callback when a dhcp client-side IP address 
>> changes?
>>
>> Use case: dynamic DNS update.
>
> On Linux changes regarding IP configuration are reported via rtnl (aka
> routing netlink). This works regardless how the IP address was
> required, and without any extra API from networkd.
>

that's somewhat more useful information than 'there's hooks in C for
it' Is there some standard daemon that listens and can bind to these
events?
And even so; can't a few lines (configuration defintion, a variable to
store a scriptname, and a call to exec the script like using a systemd
unit to setup a network be added to a single place that already does
the change?  Even if it's a systemd service that's added that in turn
listens to rtnl?

> Lennart
>
> --
> Lennart Poettering, Red Hat
> ___
> 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] dhcp address change callback?

[J Decker]

There isn't.  Arch Linux proposes a cron job that runs every so often.
They say there's support in the C library; but I was unable to
identify where that was so I could add a clone of existing exec(
some_configured_script );  Seems like something really easy to add,
but noone has taken this as a feature request either.

On Sat, Jan 23, 2016 at 2:22 PM, Johannes Ernst
 wrote:
> Is there a way to receive a callback when a dhcp client-side IP address 
> changes?
>
> Use case: dynamic DNS update.
>
> Thanks,
>
>
>
> Johannes.
> ___
> 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

[systemd-devel] Where is DHCP Address stored?

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

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

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

[J Decker]

On Sat, Nov 28, 2015 at 7:36 AM, Tom Gundersen <t...@jklm.no> wrote:
> 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?

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

Re: [systemd-devel] DHCPC Events?

[J Decker]

Should I have not said specifically Arch linux?
Is it something that can't be done?
It is something that should be so obvious it doesn't merit an answer?



On Fri, Nov 6, 2015 at 1:56 PM, J Decker <d3c...@gmail.com> wrote:
> I have Arch Linux setup as my router.
> It's on a connection that can change the IP that I'm given, when that
> happens I need to rerun firewall rules and rebuild my ipv6 tunnel.
> How do I run some script or something when the address changes (or
> when it's initially given in the case of boot?)
>
> Also there seems to be no way to specify default ipv6 route for next
> hop... ie 'ip -6 route replace ::/0 dev he-ipv6'
> It's been a couple months I've been limping along so I forget; I
> vaguely remember that this should have been setup in the configuration
> scripts; but it didn't work unless I did it this way.  The iniital
> method I think was 'add' instead of 'replace' which no longer works (I
> think something changed in the kernel that affected that; but I don't
> know).
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] DHCPC Events?

[J Decker]

I have Arch Linux setup as my router.
It's on a connection that can change the IP that I'm given, when that
happens I need to rerun firewall rules and rebuild my ipv6 tunnel.
How do I run some script or something when the address changes (or
when it's initially given in the case of boot?)

Also there seems to be no way to specify default ipv6 route for next
hop... ie 'ip -6 route replace ::/0 dev he-ipv6'
It's been a couple months I've been limping along so I forget; I
vaguely remember that this should have been setup in the configuration
scripts; but it didn't work unless I did it this way.  The iniital
method I think was 'add' instead of 'replace' which no longer works (I
think something changed in the kernel that affected that; but I don't
know).
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel