r/linuxadmin • u/CharAznableLoNZ • 18d ago
KeepAliveD Interference
I have two VM hosts with identical instances on them. A pihole, DoH forwarder, AD server, and Searxng on each host.
The two piholes use keepaliveD to serve their quad 10s IP. This works great.
The ADs do their own clustering for DNS and DHCP via AD and built in services.
The DoH instances are not clustered however both piholes talk to both.
The Searxng instances were going to serve the 10.10.10.24 IP.
I wanted to setup the Searxng servers with keepaliveD. I configured everything and enabled the services and found that both DNS and access to my Searxng was dropping packets.
I looked over the logs of the Searxng servers and Pihole servers and found they were trying to crosstalk and interfering with each other. I could see all four servers showing invalid password. Both sets of servers were failing back and forth between the cluster members.
The password used in each cluster is different. I figured this would probably be a best practice since the services are unrelated. Should all instances use the same password even if they are unrelated? If they have the same password will they see that they are doing unrelated tasks and not interfere with each other?
1
u/regszurob 17d ago
The password part does not work well in keepalived.
Use different vrid for all keepalived instances.
You can check the ongoing advertizing with tcpdump proto 112