TCP throughput capped at ~95 Mbps through NetBird tunnel for incoming traffic only #6822
-
Before posting
TopicCLI Deployment typeNetBird Cloud Operating system or environmentLinux, macOS NetBird version0.74.7 QuestionI am seeing a TCP throughput limit through Netbird. Setup:
Results: TCP Pi → VPS: ~95 mbps The tunnel itself appears capable of high throughput, but TCP traffic in one direction of the Pi is very limited. Same results when going from Macbook to Pi, it's slow. But Macbook to VPS is fast. Pi can easily do ~950 Mbps to other internet facing public iPerf3 servers, not using the tunnel. Things tested:
Zero improvement. Example CPU is not saturated during the slow tests (~95% idle). Is there any known NetBird/WireGuard forwarding limitation or processing path that could explain asymmetric TCP throughput while UDP and reverse TCP reach ~900 Mbps? I couldn't test Tailscale at the moment but I swear that easily did upwards of 400-500 mbit/s when using the Pi as an exit node before. Desired outcomeNo response What have you tried?No response Relevant environment detailsNo response Logs or outputNo response Additional contextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
I am - yet again - an idiot. Spent an hour looking at this, trying things, turns out the underlying ISP connection on the Pi side changed to a DOCSIS modem. Ergo... capped at 1000/100 Mbps :-) |
Beta Was this translation helpful? Give feedback.
I am - yet again - an idiot. Spent an hour looking at this, trying things, turns out the underlying ISP connection on the Pi side changed to a DOCSIS modem. Ergo... capped at 1000/100 Mbps :-)