severity -1 important
fixed -1 1:2.2.7-1~bpo11+1
thanks
❦ 24 March 2022 17:24 +01, Arturo Borrero Gonzalez:
> This exact same setup was previously working, and actually, the next version
> works just fine.
> Not sure if this has anything to do with the kernel version warning at the
> beginning.
>
> In summary:
>
> | keepalived version | Debian | Works? |
> | --------------------|--------------|--------|
> | 1:2.0.10-1 | buster | yes |
> | 1:2.1.5-0.2+deb11u1 | bullseye | no |
> | 1:2.2.7-1~bpo11+1 | bullseye-bpo | yes |
>
> I'm opeining this bug report mostly so others can find it.
> Raelly appreciated the bpo package is ready to use.
Glad that the backport solves this issue. Unfortunately, I don't think
it's worth reporting the issue upstream as they don't like us lagging so
many versions late. I have used it myself with unicast_src, so it is not
broken for everyone.
After looking twice, I notice the VIP is in the same subnet as the peer.
If you don't have any other address on the subnet, I don't see how this
could work. If you have, maybe it would be better to use a /32 for the
VIP.
--
If one cannot enjoy reading a book over and over again, there is no use
in reading it at all.
-- Oscar Wilde
