** Changed in: systemd (Ubuntu)
Status: Invalid => 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/1800836
Title:
systemd-networkd doesn't process IPv6 RA
This bug is still present on Ubuntu 18.04.5 LTS with systemd
237-3ubuntu10.50. Please reopen.
--
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/1800836
Title:
please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: Confirmed => 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/1800836
Title:
possibly needs upstream commit
https://github.com/systemd/systemd/commit/f02ba163891bab73a80332b4599a9d73083cb6c2
--
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/1800836
This is still happening with 237-3ubuntu10.42 in Bionic. RA routes
announced with lifetime of 0s are not removed. It is the firewall which
used to be the default router which (continously) announce these 0s
lifetimes to make sure there are no issues with failover.
$ ip -6 route show default
[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: systemd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
> After a failover
can you explain what exactly happens during the failover? What specific
commands are executed on the old system to remove the VIP and/or adjust
anything else?
** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification
fw01/02 have bond0.21 that is setup to have fe80::1 as the VIP used as
the network gateway:
root@fw01:~# ip -6 a show bond0.21
8: bond0.21@bond0: mtu 1500 state UP qlen 1000
inet6 2620:a:b:21::2/64 scope global
valid_lft forever preferred_lft forever
inet6
> For me it looks like the issue is fixed in this pull request:
> https://github.com/systemd/systemd/pull/3242
that's included in Bionic already.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
@sdeziel can you provide more specific simplified steps to reproduce
this? Like, specific networkd (or netplan) config file(s), and steps to
reproduce?
** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of
We are also affected by this issue. networkd does not expire routes
which causes issues with active-passive router configurations.
For me it looks like the issue is fixed in this pull request:
https://github.com/systemd/systemd/pull/3242
--
You received this bug notification because you are a
I can confirm the same issues with `systemd-networkd` in Xenial (and
Debian Stretch). Do you know if there is a patch from a modern `systemd`
that can be used to backport a fix to older versions?
When not using `systemd-networkd` (like older dists or "vanilla" Xenial)
it is possible to see when
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
systemd from Cosmic is not affected by this bug:
# apt-cache policy systemd
systemd:
Installed: 239-7ubuntu10.3
Candidate: 239-7ubuntu10.3
Version table:
*** 239-7ubuntu10.3 500
500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages
500
14 matches
Mail list logo
