[GH-ISSUE #2349] DNS Network Routes break masquerading #4994

Open
opened 2026-08-05 01:00:48 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @ndziuba on GitHub (Jul 30, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/2349

When creating a DNS Network Route masquerading is set by default.
This results in the following rule for routing nodes when running: iptables -t nat -S
-A NETBIRD-RT-NAT -j MASQUERADE
-A NETBIRD-RT-NAT -j MASQUERADE

Because of that every traffic trough a routing node that has this route gets masqueraded as no -s or -d flags are set.
Even when masquerading is deactivated for another route.

Deactivating masq for the DNS route fixes this behaviour.
But that means they cant be used with masquerading on a node that has non-masqueraded routes.

NetBird version

0.28.6

Originally created by @ndziuba on GitHub (Jul 30, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/2349 When creating a DNS Network Route masquerading is set by default. This results in the following rule for routing nodes when running: iptables -t nat -S -A NETBIRD-RT-NAT -j MASQUERADE -A NETBIRD-RT-NAT -j MASQUERADE Because of that every traffic trough a routing node that has this route gets masqueraded as no -s or -d flags are set. Even when masquerading is deactivated for another route. Deactivating masq for the DNS route fixes this behaviour. But that means they cant be used with masquerading on a node that has non-masqueraded routes. **NetBird version** 0.28.6
saavagebueno added the waiting-feedbacktriage-needed labels 2026-08-05 01:00:48 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#4994