Edit 20240322 noonish
ISP technician repaired my modem.
My 2 former Wireguard clients now have blue clouds.
So, no issue with Wireguard/AREDNI set up.
Thanks to all for the offered assistance.
73, Chuck
2 regular-node to regular-node tunnel clients.
I get the 'blue cloud' then later the tunnels fail.
Is anyone else experiencing this?
73, Chuck
ISP technician repaired my modem.
My 2 former Wireguard clients now have blue clouds.
So, no issue with Wireguard/AREDNI set up.
Thanks to all for the offered assistance.
73, Chuck
2 regular-node to regular-node tunnel clients.
I get the 'blue cloud' then later the tunnels fail.
Is anyone else experiencing this?
73, Chuck
Orv W6BI
NAT and Firewall Traversal Persistence
FYI, This is from the wireguard forum. I've had such issues in the past with Sonicwall firewalls & VPN tunnels dropping when they get too quiet. I haven't yet tested the nightly builds as I'm looking to get a couple more nodes for the lab.
[By default, WireGuard tries to be as silent as possible when not being used; it is not a chatty protocol. For the most part, it only transmits data when a peer wishes to send packets. When it's not being asked to send packets, it stops sending packets until it is asked again. In the majority of configurations, this works well. However, when a peer is behind NAT or a firewall, it might wish to be able to receive incoming packets even when it is not sending any packets. Because NAT and stateful firewalls keep track of "connections", if a peer behind NAT or a firewall wishes to receive incoming packets, he must keep the NAT/firewall mapping valid, by periodically sending keepalive packets. This is called persistent keepalives. When this option is enabled, a keepalive packet is sent to the server endpoint once every interval seconds. A sensible interval that works with a wide variety of firewalls is 25 seconds. Setting it to 0 turns the feature off, which is the default, since most users will not need this, and it makes WireGuard slightly more chatty. This feature may be specified by adding the PersistentKeepalive = field to a peer in the configuration file, or setting persistent-keepalive at the command line. If you don't need this feature, don't enable it. But if you're behind NAT or a firewall and you want to receive incoming connections long after network traffic has gone silent, this option will keep the "connection" open in the eyes of NAT.]
Orv W6BI
Sorry.
Thanks folks for this place to ask for assistance.
3s, Chuck