Closed Lusitaniae closed 1 month ago
This is probably caused by innernet
trying the local addresses reported by other peers. You can disable it on either side:
--no-nat-candidates
on the remote peer side--no-nat-traversal
on the local peer side(or both to be really sure)
I'll go ahead and close this, but feel free to follow-up.
We're running servers in Hetzner and every time we install innernet it triggers a netscan alert on hetzner which requires manual intervention
We'd like to have a flag to disable such behavior because anyway a lot of providers don't offer separate internal routing between nodes
as a work around we'll implement a firewall rule preventing outgoing connections to 51820 on udp
hetzner emails looks like: