From 64aeae8c4aee22c1a22dd4bd7a458ff01efa60af Mon Sep 17 00:00:00 2001 From: Gitea Actions Date: Mon, 20 Oct 2025 12:44:14 +0000 Subject: [PATCH] Auto-update blog content from Obsidian: 2025-10-20 12:44:14 --- .../post/13-migration-opnsense-proxmox-highly-available.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/content/post/13-migration-opnsense-proxmox-highly-available.md b/content/post/13-migration-opnsense-proxmox-highly-available.md index d50f28e..9a04d41 100644 --- a/content/post/13-migration-opnsense-proxmox-highly-available.md +++ b/content/post/13-migration-opnsense-proxmox-highly-available.md @@ -435,9 +435,16 @@ Finally, I need to allow connection of these ports on the firewall, one rule for The last service I want to setup in OPNsense is a mDNS repeater. This is useful for some devices to announce themselves on the network, when not on the same VLAN, such as my printer or my Chromecast. The mDNS repeater get the message from an interface to send it to another one. +This service is also not installed by default, on both firewalls, In `System` > `Firmware` > `Plugins`, I tick the box to show community plugins and install `os-mdns-repeater`. +Then in `Services` > `mDNS Repeater`, the configuration is pretty straight forward: +- Enable: Yes +- Enable CARP Failover: Yes +- Listen Interfaces: *IoT*, *User* +### Service Synchronization +The final step is to synchronize all the services between the master and the backup node in the cluster. ## Switch