lp:~dmitriis/charm-policy-routing

Author: Dmitrii Shcherbakov
Author Date: 2018-10-30 15:01:47 UTC

add bionic series support to the charm

Author: Dmitrii Shcherbakov
Author Date: 2018-09-25 20:22:33 UTC

fix directly connected route handling

The ip rule added by the charm makes all traffic from a given subnet to
be evaluated for forwarding purposes against a secondary routing table.

However, this routing table does not contain directly connected routes
for subnets present in the main routing table which are added by the
kernel based on assigned interface ip addresses. This leads to the fact
that even traffic that is supposed to be forwarded by virtue of ARP
without going through the default gateway still goes to the default
gateway. In some cases the default gateway can filter out traffic going
from a subnet that is directed to the same subnet, e.g.

from 192.0.2.0/24 to 192.0.2.0/24

The expectation is, generally, that end hosts can communicate using
just switches on a single segment/link via ARP and MAC learning.

This change adds a more specific policy rule to have all link-local
traffic evaluated against the main routing table.

https://www.freedesktop.org/software/systemd/man/systemd.service.html#ExecStart=
"this directive may be specified more than once with the same effect"

Author: Dmitrii Shcherbakov
Author Date: 2018-09-25 20:22:33 UTC

fix directly connected route handling

The ip rule added by the charm makes all traffic from a given subnet to
be evaluated for forwarding purposes against a secondary routing table.

However, this routing table does not contain directly connected routes
for subnets present in the main routing table which are added by the
kernel based on assigned interface ip addresses. This leads to the fact
that even traffic that is supposed to be forwarded by virtue of ARP
without going through the default gateway still goes to the default
gateway. In some cases the default gateway can filter out traffic going
from a subnet that is directed to the same subnet, e.g.

from 192.0.2.0/24 to 192.0.2.0/24

The expectation is, generally, that end hosts can communicate using
just switches on a single segment/link via ARP and MAC learning.

This change adds a more specific policy rule to have all link-local
traffic evaluated against the main routing table.

https://www.freedesktop.org/software/systemd/man/systemd.service.html#ExecStart=
"this directive may be specified more than once with the same effect"