[Bug 1790664] Re: routing policy not always applied on systemd-networkd restart
arash
arash.janzadeh at gmail.com
Wed Sep 5 13:53:40 UTC 2018
** Changed in: systemd (Ubuntu)
Status: Incomplete => In Progress
** Changed in: systemd (Ubuntu)
Status: In Progress => New
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1790664
Title:
routing policy not always applied on systemd-networkd restart
Status in systemd package in Ubuntu:
New
Bug description:
We are using ubuntu 18.04 in an environment with two NIC in the same
subnet.
As part of network configuration we have created a routing table for
each NIC.
Every other time that we restart networkd we lose connectivity to
eth0. After tcpdump we noticed the reason we lose connectivity to eht0
is routing problem. All connection will always go out from eht1.
If we restart netowrkd one more time this will fix the routing issue instantly.
Also on each reboot routing policy applies correctly.
The problem only appears when we restart netwrokd every other time.
We already have raised this issue with Netplan and they suggest this
is a systemd bug.
Please find the debugs in the attachments. Please don't hesitate to
ask if you require any further logs.
Regards
Arash
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1790664/+subscriptions
More information about the foundations-bugs
mailing list