Open c0repwn3r opened 7 months ago
The STUN packets you are seeing are the relayed VPN traffic. This is expected because your peer seems to connect to all other peers via the relay. You should investigate if that machines sits behind a very restrictive NAT that requires to use the relay instead of peer to peer connections
This machine is behind a NAT, but it shouldn’t prevent establishing a direct connection… standard traversal techniques should be succeeding - relaying shouldn’t be nessecary. I’ll look on other machines and see what they’re emitting… the common factor is that a running NetBird client has a habit of crippling networks. I’ll investigate further.
Describe the problem
Any running NetBird client is spewing out hundreds of STUN packets per second, crippling several networks we have dev machines at.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Once a tunnel has been successfully established or if a tunnel has failed to connect for a long enough period of time, calm down the STUN packet flow, perhaps to 1 packet per 2 seconds per host.
Are you using NetBird Cloud?
Selfhosted
NetBird version
0.26.2
NetBird status -d output:
Screenshots
n/a
Additional context
Occurs on all devices on all networks.