Summary: | systemd-networkd: support adding routes without additional addresses & support link-local addresses | ||
---|---|---|---|
Product: | systemd | Reporter: | Shaun Keenan <skeenan> |
Component: | general | Assignee: | Tom Gundersen <teg> |
Status: | RESOLVED FIXED | QA Contact: | systemd-bugs |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Shaun Keenan
2014-12-03 01:04:49 UTC
1) I'm not following. Could you paste the .network file (or equivalent ip(8) script) you would like to use, but which does not work? The code you link to is only about the auto-discovered link-local addresses, where you always will have both a route and an address... 2) Hm, not quite following this either. How do you want to specify link-local addresses? There is no restriction stopping you from using Address=169.254.<...>, but I guess this is not what you want. What do you mean by 'link-local addresses aren't correctly detected'? There is no way IPv4LL assignment can fail (unless there is a bug), but, again, I suppose you have something else in mind? Is the IPv4LLRoute= option related to this? 1) here's the end goal I'm trying to get: core@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@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. another little note on this from my conversation with the coreos devs - see this gist and the comment below it: https://gist.github.com/marineam/e87509ddfc682ca6864a and, more debugging that I did, including log files and systemd configs that I tried: https://gist.github.com/skeenan947 Please use GatewayOnLink=yes. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.