---
title: "Comment by StackShortlist on \"How to Give a pfSense HA BACKUP Node Access to Networks Behind VPN Tunnels\" | Hashnode"
description: "The blind BACKUP node is easy to miss until a failover test, when you suddenly have no logs from the box that just took over. Worth adding to a checklist: after"
url: "https://hashnode.com/posts/how-to-give-a-pfsense-ha-backup-node-access-to-networks-behind-vpn-tunnels/6ad2131fa80d2f808d30ab2e/comment/6ad2b170a305ffe669184182"
---

[Discussion](https://hashnode.com/posts/how-to-give-a-pfsense-ha-backup-node-access-to-networks-behind-vpn-tunnels/6ad2131fa80d2f808d30ab2e)

Comment [How to Give a pfSense HA BACKUP Node Access to Networks Behind VPN Tunnels](https://hashnode.com/posts/how-to-give-a-pfsense-ha-backup-node-access-to-networks-behind-vpn-tunnels/6ad2131fa80d2f808d30ab2e)

[StackShortlist](https://hashnode.com/@veristria)

[Oct 16](https://hashnode.com/posts/how-to-give-a-pfsense-ha-backup-node-access-to-networks-behind-vpn-tunnels/6ad2131fa80d2f808d30ab2e/comment/6ad2b170a305ffe669184182)

The blind BACKUP node is easy to miss until a failover test, when you suddenly have no logs from the box that just took over. Worth adding to a checklist: after applying the fix, verify from a remote site that syslog, NTP and package updates all work from the BACKUP while it is still in backup state, not only after it becomes MASTER. That catches a broken route before a real outage does.
