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. In the majority of configurations, this works well. When it's not being asked to send packets, it stops sending packets until it is asked again. For the most part, it only transmits data when a peer wishes to send packets.
$ wg genkey tee privatekey wg pubkey >publickey NAT and Firewall Traversal Persistence By default, WireGuard tries to be as silent as possible when not being used it is not a chatty protocol.
