OpenWrt: Incompatibility with certain packages, such as mwan3 #1833

Open
opened 2025-11-20 06:07:39 -05:00 by saavagebueno · 2 comments
Owner

Originally created by @wehagy on GitHub (Apr 24, 2025).

Describe the problem

netbird has compatibility issues with certain packages in the OpenWrt, such as mwan3, however, I don't know if the bug is due to netbird, mwan3, or both.

To Reproduce

Steps to reproduce the behavior:

Expected behavior

The two, or more?, apps work together.

Are you using NetBird Cloud?

NetBird Cloud.

NetBird version

N/A

Is any other VPN software installed?

No.

Debug output

Check the links above.

Screenshots

N/A

Additional context

The issue at https://github.com/netbirdio/netbird/issues/3363 is, maybe?, related but covers a different topic.

Have you tried these troubleshooting steps?

  • Checked for newer NetBird versions
  • Searched for similar issues on GitHub (including closed ones)
  • Restarted the NetBird client
  • Disabled other VPN software
  • Checked firewall settings
Originally created by @wehagy on GitHub (Apr 24, 2025). **Describe the problem** `netbird` has compatibility issues with certain packages in the `OpenWrt`, such as `mwan3`, however, I don't know if the bug is due to `netbird`, `mwan3`, or both. **To Reproduce** Steps to reproduce the behavior: - See for context: - https://github.com/netbirdio/netbird/issues/3363#issuecomment-2675491800 - Some of the reports: - https://github.com/openwrt/packages/pull/26002#issuecomment-2669549316 - https://github.com/openwrt/packages/issues/26356#issue-3007271562 - https://forum.openwrt.org/t/anyone-having-issues-with-netbird-0-39-2/230534 **Expected behavior** The two, or more?, apps work together. **Are you using NetBird Cloud?** NetBird Cloud. **NetBird version** N/A **Is any other VPN software installed?** No. **Debug output** Check the links above. **Screenshots** N/A **Additional context** The issue at https://github.com/netbirdio/netbird/issues/3363 is, maybe?, related but covers a different topic. **Have you tried these troubleshooting steps?** - [x] Checked for newer NetBird versions - [x] Searched for similar issues on GitHub (including closed ones) - [x] Restarted the NetBird client - [x] Disabled other VPN software - [x] Checked firewall settings
saavagebueno added the triage-needed label 2025-11-20 06:07:39 -05:00
Author
Owner

@lixmal commented on GitHub (Apr 26, 2025):

I've taken a quick look at mwan3 and it seems to mark every packet with a fwmark. This probably conflicts with NetBird, that also makes use of fwmarks to prevent routing loops.
Setting the env var NB_USE_LEGACY_ROUTING=true should circumvent that. It does the same as NB_SKIP_SOCKET_MARK=true which you seem to have found out already

@lixmal commented on GitHub (Apr 26, 2025): I've taken a quick look at `mwan3` and it seems to mark every packet with a fwmark. This probably conflicts with NetBird, that also makes use of fwmarks to prevent routing loops. Setting the env var `NB_USE_LEGACY_ROUTING=true` should circumvent that. It does the same as `NB_SKIP_SOCKET_MARK=true` which you seem to have found out already
Author
Owner

@wbinek commented on GitHub (May 12, 2025):

Just to let everyone know - I have had compatibility issues with Netbird and Policy Based Routing package in OpenWRT. The PBR also seems to use fwmarks. The PBR was configured to route some IP range through VPN connection (other than netbird) and to my surprise the netbird connection was routed as well even though it had nothing to do with that routed IPs. This was evidenced by showing public IP of routed location in peers tab of netbird GUI.

After setting the NB_USE_LEGACY_ROUTING=true it seems to be fixed and correct (not routed) public IP is shown in peers tab.

@wbinek commented on GitHub (May 12, 2025): Just to let everyone know - I have had compatibility issues with Netbird and `Policy Based Routing` package in OpenWRT. The PBR also seems to use fwmarks. The PBR was configured to route some IP range through VPN connection (other than netbird) and to my surprise the netbird connection was routed as well even though it had nothing to do with that routed IPs. This was evidenced by showing public IP of routed location in peers tab of netbird GUI. After setting the `NB_USE_LEGACY_ROUTING=true` it seems to be fixed and correct (not routed) public IP is shown in peers tab.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#1833