SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-05-14 12:12:27 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Disabling Masquerding not working #1349

New Issue
Closed
opened 2025-11-20 05:28:49 -05:00 by saavagebueno · 4 comments
saavagebueno commented 2025-11-20 05:28:49 -05:00
Owner
Copy Link

Originally created by @ndziuba on GitHub (Oct 17, 2024).

Describe the problem

I run a node with multiple advertised routes that were masqueraded using iptabels with an client installed on Rocky 8.
Setting up a routing back into netbird for the 100.24.0.0 adresses works as expected as far as being able to ping Netbird clients from non Netbird clients.

This is not always true for Netbird clients, we can ping through the node with iptables but everything else like ssh or http is not working and stops at the routing node. Using nftables results in not being able to ping all together.
I reproduced this for Debian and a Docker client.

To Reproduce

Steps to reproduce the behavior:

  1. Set a route for a node to advertise a subnet
  2. Disable masquerading (its important to have no exit node on this node as this enables masqerading for all routes on this node, even when disabled)
  3. Testing ping should not work
  4. Enable iptabels with echo 'NB_SKIP_NFTABLES_CHECK=true' | sudo tee -a /etc/sysconfig/netbird and restarting netbird
  5. Ping should now work but nothing else

We can see from iptables that currently no route advertises masquerading

iptables -t nat -S

-P PREROUTING ACCEPT
-P INPUT ACCEPT
-P POSTROUTING ACCEPT
-P OUTPUT ACCEPT
-N NETBIRD-RT-NAT
-A POSTROUTING -j NETBIRD-RT-NAT

And ping is working but no ssh or http

ping 10.1.0.1

Ping wird ausgeführt für 10.1.0.1 mit 32 Bytes Daten:
Antwort von 10.1.0.1: Bytes=32 Zeit=38ms TTL=63

For the ease of configuring masquerading i enable an exit node route which results in following ouput

iptables -t nat -S

-P PREROUTING ACCEPT
-P INPUT ACCEPT
-P POSTROUTING ACCEPT
-P OUTPUT ACCEPT
-N NETBIRD-RT-NAT
-A POSTROUTING -j NETBIRD-RT-NAT
-A NETBIRD-RT-NAT -i wt0 -j MASQUERADE
-A NETBIRD-RT-NAT -o wt0 -j MASQUERADE

And fixing the issues by being able to connect again with the network clients.

Are you using NetBird Cloud?

Self-hosted NetBird

NetBird version

0.30.1

Originally created by @ndziuba on GitHub (Oct 17, 2024). **Describe the problem** I run a node with multiple advertised routes that were masqueraded using iptabels with an client installed on Rocky 8. Setting up a routing back into netbird for the 100.24.0.0 adresses works as expected as far as being able to ping Netbird clients from non Netbird clients. This is not always true for Netbird clients, we can ping through the node with iptables but everything else like ssh or http is not working and stops at the routing node. Using nftables results in not being able to ping all together. I reproduced this for Debian and a Docker client. **To Reproduce** Steps to reproduce the behavior: 1. Set a route for a node to advertise a subnet 2. Disable masquerading (its important to have no exit node on this node as this enables masqerading for all routes on this node, even when disabled) 3. Testing ping should not work 4. Enable iptabels with `echo 'NB_SKIP_NFTABLES_CHECK=true' | sudo tee -a /etc/sysconfig/netbird` and restarting netbird 5. Ping should now work but nothing else We can see from iptables that currently no route advertises masquerading ``` iptables -t nat -S -P PREROUTING ACCEPT -P INPUT ACCEPT -P POSTROUTING ACCEPT -P OUTPUT ACCEPT -N NETBIRD-RT-NAT -A POSTROUTING -j NETBIRD-RT-NAT ``` And ping is working but no ssh or http ``` ping 10.1.0.1 Ping wird ausgeführt für 10.1.0.1 mit 32 Bytes Daten: Antwort von 10.1.0.1: Bytes=32 Zeit=38ms TTL=63 ``` For the ease of configuring masquerading i enable an exit node route which results in following ouput ``` iptables -t nat -S -P PREROUTING ACCEPT -P INPUT ACCEPT -P POSTROUTING ACCEPT -P OUTPUT ACCEPT -N NETBIRD-RT-NAT -A POSTROUTING -j NETBIRD-RT-NAT -A NETBIRD-RT-NAT -i wt0 -j MASQUERADE -A NETBIRD-RT-NAT -o wt0 -j MASQUERADE ``` And fixing the issues by being able to connect again with the network clients. **Are you using NetBird Cloud?** Self-hosted NetBird **NetBird version** `0.30.1`
saavagebueno added the waiting-feedbacktriage-needed labels 2025-11-20 05:28:49 -05:00
saavagebueno commented 2025-11-20 05:28:50 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Nov 5, 2024):

Sorry for the delay @ndziuba, we will investigate the issue and give you a feedback soon.

@mlsmaycon commented on GitHub (Nov 5, 2024): Sorry for the delay @ndziuba, we will investigate the issue and give you a feedback soon.
saavagebueno commented 2025-11-20 05:28:50 -05:00
Author
Owner
Copy Link

@mgarces commented on GitHub (Nov 12, 2024):

can you please validate if 0.31.1 helps with this issue?

@mgarces commented on GitHub (Nov 12, 2024): can you please validate if [0.31.1](https://github.com/netbirdio/netbird/releases/tag/v0.31.1) helps with this issue?
saavagebueno commented 2025-11-20 05:28:50 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Apr 28, 2025):

Hello @ndziuba,

We're currently reviewing our open issues and would like to verify if this problem still exists in the latest NetBird version.

Could you please confirm if the issue is still there?

We may close this issue temporarily if we don't hear back from you within 2 weeks, but feel free to reopen it with updated information.

Thanks for your contribution to improving the project!

@nazarewk commented on GitHub (Apr 28, 2025): Hello @ndziuba, We're currently reviewing our open issues and would like to verify if this problem still exists in the [latest NetBird version](https://github.com/netbirdio/netbird/releases). Could you please confirm if the issue is still there? We may close this issue temporarily if we don't hear back from you within **2 weeks**, but feel free to reopen it with updated information. Thanks for your contribution to improving the project!
saavagebueno commented 2025-11-20 05:28:51 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Jun 1, 2025):

closing issue due to no recent feedback. Feel free to open a new one if the issue persist or reopen if this was a feature request.

@mlsmaycon commented on GitHub (Jun 1, 2025): closing issue due to no recent feedback. Feel free to open a new one if the issue persist or reopen if this was a feature request.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label triage-needed waiting-feedback
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#1349
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?