[Touch-packages] [Bug 1768088] Re: can't activate 2 independent reachable interface

2024-01-25 Thread Lukas Märdian 
Please reopen if this is still an issue

** Changed in: netplan.io (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1768088

Title:
  can't activate 2 independent reachable interface

Status in netplan.io package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1768088/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1768088] Re: can't activate 2 independent reachable interface

2021-06-30 Thread Dan Streetman 
please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1768088

Title:
  can't activate 2 independent reachable interface

Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1768088/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1768088] Re: can't activate 2 independent reachable interface

2018-11-20 Thread Joseph Rafferty 
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.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1768088

Title:
  can't activate 2 independent reachable interface

Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1768088/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1768088] Re: can't activate 2 independent reachable interface

2018-11-20 Thread Joseph Rafferty 
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.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1768088

Title:
  can't activate 2 independent reachable interface

Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1768088/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1768088] Re: can't activate 2 independent reachable interface

2018-05-25 Thread Mathieu Trudel-Lapierre 
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.

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1768088

Title:
  can't activate 2 independent reachable interface

Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1768088/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp