This bug is stale, and it remains unclear if there is a systemd bug, so
marking invalid.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
** Changed in: systemd (Ubuntu)
Status: Won't Fix => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
The bug is from 2017 without activity until now, from a desktop
perspective it isn't a rls issue, tagging a notfixing
** Tags removed: rls-kk-incoming
** Tags added: rls-kk-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
We believe the kernel handles RAs itself, adding a task for it.
** Also affects: linux (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.
For the systemd-networkd case, can you set `SYSTEMD_LOG_LEVEL=debug` on
systemd-networkd.service to see if it yields useful information?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
With systemd-networkd on the 20.04 server, the /64 prefix does not
bounce between 0s and 1s, but stays at 0s, but is not removed (nor is
the /128).
** Tags added: rls-kk-incoming
** Changed in: network-manager (Ubuntu)
Status: New => Triaged
** Also affects: systemd (Ubuntu)
I can reproduce this on kinetic. I get sent a 2a02:908:2812:7d20::/64
prefix via RA with "valid lifetime" and ""preferred lifetime" set to 0,
every 3s. Instead of the prefix being deleted from the interface, it's
lifetime is set to 1s and then expires every second, causing regular
"connection
7 matches
Mail list logo
