[systemd-bugs] [Bug 86947] systemd-networkd: support adding routes without additional addresses & support link-local addresses

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=86947

--- Comment #2 from Shaun Keenan <skeenan at gmail.com> ---
1) here's the end goal I'm trying to get:
core at coreos ~ $ netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
0.0.0.0         10.9.134.1      0.0.0.0         UG        0 0          0 eth0
10.9.134.0      0.0.0.0         255.255.255.0   U         0 0          0 eth0
10.9.134.1      0.0.0.0         255.255.255.255 UH        0 0          0 eth0
169.254.169.254 0.0.0.0         255.255.255.255 UH        0 0          0 eth0
192.168.0.0     0.0.0.0         255.255.0.0     U         0 0          0
flannel0
192.168.65.0    0.0.0.0         255.255.255.0   U         0 0          0
docker0

core at coreos ~ $ ip addr show dev eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP
qlen 1000
    link/ether fa:16:3e:9a:a6:10 brd ff:ff:ff:ff:ff:ff
    inet 10.9.134.192/24 brd 10.9.134.255 scope global dynamic eth0
       valid_lft 1405sec preferred_lft 1405sec
    inet6 fe80::f816:3eff:fe9a:a610/64 scope link 
       valid_lft forever preferred_lft forever

note that there's no ip on the interface.  On a side note, I don't care all
that much about whether or not there's an IP on the int...  but the issue is
that systemd doesn't automatically discover link-local addresses, and adding
IPv4LL=true doesn't change the fact that I don't get a link-local addy on the
interface.

Here's how I was trying to add it:
write_files:
  - path: /etc/systemd/network/00-eth0.network
    owner: root:root
    permissions: 0644
    content: |
      [Match]
      Name=eth*

      [Network]
      IPv4LL=true
      IPv4LLRoute=true
      DHCP=v4

      [DHCP]
      UseRoutes=false

I tried a few different versions of this.  no matter what I do, link-local
addresses never show up unless I statically configure the IP.

2) see #1 - IPv4LL assignment is failing both with and without the
IPv4LLRoute=true attribute turned on.
Note that this is with the latest coreos alpha, which is on 216 I believe.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20141209/34e2a8c0/attachment.html>