* wg unable to communicate after laptop suspend
@ 2018-08-09 7:29 Paul Hedderly
0 siblings, 0 replies; only message in thread
From: Paul Hedderly @ 2018-08-09 7:29 UTC (permalink / raw)
To: WireGuard mailing list
Morning all - I'm not sure if I'm doing something wrong, or this is
something the kernel module could help with.
When wg interface is started, it punches a hole through my firewall
(upnp?) and all is well. After a suspend wg cannot receive replies from
Would it be easy to get wg to notice keepalives failing and try the
upnp again? I know I can just restart the wg interface... but I'd love
to not have to.
Or am I barking up the wrong tree?
Thanks again for an amazing tool!
^ permalink raw reply [flat|nested] only message in thread
only message in thread, back to index
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-08-09 7:29 wg unable to communicate after laptop suspend Paul Hedderly
WireGuard Archive on lore.kernel.org
Archives are clonable:
git clone --mirror https://lore.kernel.org/wireguard/0 wireguard/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 wireguard wireguard/ https://lore.kernel.org/wireguard \
Newsgroup available over NNTP:
AGPL code for this site: git clone https://public-inbox.org/ public-inbox