Re: [systemd-devel] systemd-networkd quietly ignores DHCPv6 leases

2015-01-15 Thread Barbara Lazarowicz-Steube
On 2015-01-15 09:58, Patrik Flykt wrote:

> Indeed. I so thought I had a patch applied that set the DHCPv6 address
> for the interface. Apparently such functionality has gone into /dev/null
> instead, and as a result you will need the next version of the DHCPv6
> address assignment patch recently posted on the mailing list.
The "DHCPv6 address assignment" patch set from two days ago? I see there
are still some changes for you to make there so I'll keep an eye out for
the final version and once it has been pushed to Git, I'll apply it
locally and let you know whether it has fixed the problem.

> Anyway it is excellent news that DHCPv6 is being used out there!
It is excellent systemd-networkd supports DHCPv6! The fact it only does
so nominally at the moment is a minor thing, teething problems do happen.

-- 
MS
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


[systemd-devel] systemd-networkd quietly ignores DHCPv6 leases

2015-01-14 Thread Barbara Lazarowicz-Steube
Hello everyone,

Having just configured systemd-networkd on my machine, I found myself no
longer assigned global IPv6 addresses. The LAN in question has got fully
operational native IPv6 support and both dhcpcd and connman had no
problems taking advantage of it. Networkd on the other hand picks up
router advertisements but ignores DHCPv6. Observed with systemd version
216 and 218. My network-configuration file is simply

[Match]
Name=en*

[Network]
DHCP=both

Enclosed you will find a debug log I have just obtained from
systemd-networkd, trimmed down to the IPv6 part. As you can see in it,
having received the RA networkd correctly identifies the local network
as managed and fires up the DHCPv6 client. The client then receives a
reply from the server and... does absolutely nothing with it.

Any idea what the problem might be? Thank you in advance - and of course
if you need any more information which might facilitate debugging the
issue, do let me know.

Yours sincerely,
-- 
MS
eno1: flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST
eno1: link 2 added
device 0xdeadbeef7150 has devpath '/devices/pci:00/:00:19.0/net/eno1'
device 0xdeadbeef7150 filled with db file data
eno1: udev initialized link
eno1: saved original MTU: 1500
eno1: added address: fe80::[REDACTED]/64 (valid for ever)
eno1: link state is up-to-date
device 0xdeadbeef47f0 has devpath '/devices/pci:00/:00:19.0'
eno1: found matching network '/etc/systemd/network/80-dhcp.network'
eno1: discovering IPv6 routers
ICMPv6 CLIENT: Start Router Solicitation
ICMPv6 CLIENT: Sent Router Solicitation
ICMPv6 CLIENT: Received Router Advertisement flags MANAGED/OTHER
device 0xdeadbeefa440 has devpath '/devices/pci:00/:00:19.0/net/eno1'
device 0xdeadbeefa440 filled with db file data
DHCPv6 CLIENT: Started in Managed mode
DHCPv6 CLIENT: client state 0 new state 2
DHCPv6 CLIENT: Sent SOLICIT
DHCPv6 CLIENT: Next retransmission in 1.015358s
DHCPv6 CLIENT: Computed IA T1 3888000s and T2 6220800s as both were zero
DHCPv6 CLIENT: client state 2 new state 3
DHCPv6 CLIENT: Recv ADVERTISE
DHCPv6 CLIENT: Sent REQUEST
DHCPv6 CLIENT: Next retransmission in 989.421ms
DHCPv6 CLIENT: client state 3 new state 4
DHCPv6 CLIENT: T1 expires in 1month 1w 3d 9h 5min 27.974400s
DHCPv6 CLIENT: T2 expires in 2month 2w 4d 6h 45min 16.416000s
eno1: DHCPv6 event 12
DHCPv6 CLIENT: Recv REPLY
eno1: link configured
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel