[Users] Multicast issue with openvz VMs and CTs

jjs - mainphrame jjs at mainphrame.com
Sun Jan 15 03:44:28 MSK 2023


I find it a bit puzzling that keepalived works while ucarp doesn't, since
they both use vrrp multicast (224.0.0.18)

Maybe some rainy day I'll try to figure out why vrrp mc from keepalived
gets through but vrrp mc from ucarp doesn't, but for now I'm happy to have
something that works.

Jake

On Sat, Jan 14, 2023 at 3:16 PM jjs - mainphrame <jjs at mainphrame.com> wrote:

> Success -
>
> I've found that keepalived, which is in the standard debian repos, works
> well to provide a highly available virtual IP using openvz containers, and
> is easy to set up.
>
> I'll now move my default gateway IP from the proxmox CTs to the openvz
> CTs, and breathe a sigh of relief.
>
> Jake
>
>
>
>
>
> On Sun, Jan 8, 2023 at 5:08 PM jjs - mainphrame <jjs at mainphrame.com>
> wrote:
>
>> I've been doing some testing with ucarp, in debian VMs and containers.
>>
>> (ucarp is an implementation of VRRP, a means of providing a highly
>> available floating virtual IP within a cluster of machines)
>>
>> It works fine on proxmox VMs and CTs, and I was hoping to get it working
>> on openvz, but so far my attempts to get it fully up and running have
>> failed.
>>
>> Basically, both nodes become master, because neither node is seeing the
>> multicast traffic from the other.
>>
>> What is the secret of allowing multicast traffic to pass from openvz VMs
>> and CTs, onto the lan?
>>
>> Jake
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/users/attachments/20230114/521f8cf5/attachment-0001.html>


More information about the Users mailing list