RFC 3442 support in networkd

Asked by Frank Steinberg on 2018-09-12

When using netplan and systemd-networkd my client' network configuration is incomplete. Before, with the ISC dhcp client, I received my IPv4 configuration including an additional route according the RFC 3442 (Status: Proposed Standard!). With networkd, the additional route seems to be ignored.

E.g. the DHCP server serves this:

option rfc3442-classless-static-routes code 121 = array of integer 8;
subnet 134.169.35.0 netmask 255.255.255.0 {
    option subnet-mask 255.255.255.0;
    option broadcast-address 134.169.35.255;
    option routers 134.169.35.2;
    option domain-name-servers 134.169.35.2;
    # RFC 3442: additional route for 10.1/16 which is on the same VLAN:
    # 10.1/16 via 0.0.0.0 (local link)
    option rfc3442-classless-static-routes 16, 10, 1, 0, 0, 0, 0, 0, 134, 169, 35, 2;
}
host test1 {
    hardware ethernet de:ad:be:ef:00:07;
    fixed-address 134.169.35.218;
    option host-name "test1";
}

With networkd on the client host "test" I get this routing:

root@test1:~# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 134.169.35.2 0.0.0.0 UG 0 0 0 ens3
134.169.35.0 0.0.0.0 255.255.255.0 U 0 0 0 ens3

While I would expect (and in fact with ISC dhcp client I get):

root@test1:~# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 134.169.35.2 0.0.0.0 UG 0 0 0 ens3
10.1.0.0 0.0.0.0 255.255.0.0 U 0 0 0 ens3
134.169.35.0 0.0.0.0 255.255.255.0 U 0 0 0 ens3

Am I right, that networkd does not implement RFC 3442?

Question information

Language:
English Edit question
Status:
Open
For:
Ubuntu systemd Edit question
Assignee:
No assignee Edit question
Last query:
2018-09-12
Last reply:

Can you help with this problem?

Provide an answer of your own, or ask Frank Steinberg for more information if necessary.

To post a message you must log in.