can't activate 2 independent reachable interface

Bug #1768088 reported by vigilian
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
netplan.io (Ubuntu)
New
Undecided
Unassigned
systemd (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

ubuntu: 18.04
systemd:
Installed: 237-3ubuntu10
Candidate: 237-3ubuntu10
netplan.io:
  Installed: 0.36.1
  Candidate: 0.36.1

network:
  version: 2
  renderer: networkd
  ethernets:
    ens3:
      addresses: [192.168.3.30/25]
      dhcp4: no
      routes:
       - to: 0.0.0.0/0
         via: 192.168.3.1
         metric: 100
         table: 101

      routing-policy:
       - from: 192.168.3.0/25
         table: 101

    ens7:
      addresses: [192.168.5.24/25]
      dhcp4: no
      gateway4: 192.168.5.1
      nameservers:
        addresses: [1.1.1.1]

this doesn't activate a proper rule for table 101:
0: from all lookup local
32766: from all lookup main
32767: from all lookup default

in place of
0: from all lookup local
32765: from 192.168.3.0/25 lookup 101
32766: from all lookup main
32767: from all lookup default

the file in /etc/systemd/network contains the correct information:
[Match]
Name=ens3

[Network]
Address=192.168.3.30/25

[Route]
Destination=0.0.0.0/0
Gateway=192.168.3.1
Metric=100
Table=101

[RoutingPolicyRule]
From=192.168.3.0/25
Table=101

the ens3 is reachable from 3.0 but not from anywhere else

with ifupdown on another system both interfaces would be reachable from everywhere on the private subnets.
up ip route add default table 101 dev enp8s0 via 192.168.3.1
up ip rule add from 192.168.3.0/25 lookup 101
down ip rule del from 192.168.3.0/25
down ip route del default table 101 via 192.168.3.1

Revision history for this message
vigilian (vigilian) wrote :

It has been resolved with a restart of service systemd-network.
still a bug or not? I guess yes since netplan shoulkd apply directly the policy and create them.

description: updated
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Still a bug; if systemd-networkd requires a restart, then systemd-networkd has something that it gets confused about, that we'll need to figure out.

Revision history for this message
Joseph Rafferty (joraff) wrote :

I can duplicate this. Posted my issue to askubuntu before coming across this report. See https://askubuntu.com/questions/1094591/18-04-1-lts-systemd-network-not-applying-routingpolicyrule for details.

Revision history for this message
Joseph Rafferty (joraff) wrote :

Further info: successive restarts of systemd-networkd or netplan apply (which I've since learned simply generates files and restarts networkd) applies the rule, following by the next immediate invocation removing the rule, and so on.

Revision history for this message
Dan Streetman (ddstreet) wrote :

please reopen if this is still an issue

Changed in systemd (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.