The "punchy" documentation states:
"punchy.punch
Default: False
When enabled, Nebula will periodically send "empty" packets to the underlay IP addresses of hosts it has established tunnels to in order to maintain the "hole" punched in the NAT's firewall."
It would be nice to add, that this interval is 5 second (when idle) and packets are sent from both sides, containing 1 byte.
Also, this does not only apply to NAT punched sessions. Also directly connected sessions send 1 udp byte every 5 seconds, from both sides.
For people working with NATs, even internal inter-address-space NATs this is a very important information
The "punchy" documentation states:
"punchy.punch
Default: False
When enabled, Nebula will periodically send "empty" packets to the underlay IP addresses of hosts it has established tunnels to in order to maintain the "hole" punched in the NAT's firewall."
It would be nice to add, that this interval is 5 second (when idle) and packets are sent from both sides, containing 1 byte.
Also, this does not only apply to NAT punched sessions. Also directly connected sessions send 1 udp byte every 5 seconds, from both sides.
For people working with NATs, even internal inter-address-space NATs this is a very important information