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

MikroTik RouterOS container NAT #2234

New Issue
Open
opened 2025-11-20 07:06:19 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 07:06:19 -05:00
Owner
Copy Link

Originally created by @AirP0WeR on GitHub (Aug 29, 2025).

Hello. We're experiencing an issue with NetBird running in a MikroTik RouterOS container (v7.19.4).

We installed containers following official guide (https://docs.netbird.io/how-to/client-on-mikrotik-router).

We have next setup:

Mikrotik router (R1) with 192.168.88.0/24 network
Mikrotik router (R2) with 172.29.200.0/24 network
Issue:

ping inside the netbird container (from R1) to 127.29.200.200 works perfectly
But! Ping from mikrotik (R1) host (ping 172.29.200.200 src-address=192.168.88.1) fails:
packets are visable in netbird dashboard
packets are not reaching the container (tcpdump on container shows nothing)
no ICMP replies received
tcpdump on container interface shows packets arrive when pinging other destinations, routes are configured (dst-address=172.29.200.0/24 gateway=172.17.0.2), ip forwarding is enabled in container, NAT rules configured on RouterOS level.

Now we have a question: why would packets appear in the netbird dashboard but not actually reach the container? Is this related to netbird limitations or is there a specific configuration we're missing for RouterOS container environments?

PS: we're absolutely impressed with NetBird!

We have been evaluating Netbird for the past week as a potential VPN solution for our company. We have over 500 users across multiple branch offices, and Netbird mesh architecture is exactly what we need for our infrastructure.
We're ready to commit to your Enterprise plan with the maximum tier (12$/mounth), but this MikroTik container routing issue is a critical for us.

Originally created by @AirP0WeR on GitHub (Aug 29, 2025). Hello. We're experiencing an issue with NetBird running in a MikroTik RouterOS container (v7.19.4). We installed containers following official guide (https://docs.netbird.io/how-to/client-on-mikrotik-router). We have next setup: Mikrotik router (R1) with 192.168.88.0/24 network Mikrotik router (R2) with 172.29.200.0/24 network Issue: ping inside the netbird container (from R1) to 127.29.200.200 works perfectly But! Ping from mikrotik (R1) host (ping 172.29.200.200 src-address=192.168.88.1) fails: packets are visable in netbird dashboard packets are not reaching the container (tcpdump on container shows nothing) no ICMP replies received tcpdump on container interface shows packets arrive when pinging other destinations, routes are configured (dst-address=172.29.200.0/24 gateway=172.17.0.2), ip forwarding is enabled in container, NAT rules configured on RouterOS level. Now we have a question: why would packets appear in the netbird dashboard but not actually reach the container? Is this related to netbird limitations or is there a specific configuration we're missing for RouterOS container environments? PS: we're absolutely impressed with NetBird! We have been evaluating Netbird for the past week as a potential VPN solution for our company. We have over 500 users across multiple branch offices, and Netbird mesh architecture is exactly what we need for our infrastructure. We're ready to commit to your Enterprise plan with the maximum tier (12$/mounth), but this MikroTik container routing issue is a critical for us.
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
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#2234
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?