From: FingerlessGloves <me@FingerlessGloves.me>
To: Daniel <email@example.com>
Subject: Re: Wish - Add PostUp/PostDown per peer section
Date: Mon, 20 Feb 2023 11:29:21 +0000 [thread overview]
Message-ID: <538cc161fec50f06cffcc0d0e08b0a10@FingerlessGloves.me> (raw)
This would be very handy.
Currently we have a python script that reads in the peers and
add/removes ARP entries from the physical interface, which runs as a
service and checks WireGuard every 10 seconds 😅.
On 2023-02-20 09:33 AM, Daniel wrote:
> Hello. Would it be possible to add the PostUp and PostDown commands in
> peer section ?
> Ex. of use case: dynamically add route when a peer connect
> Have a nice day
prev parent reply other threads:[~2023-02-20 11:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 9:33 Daniel
2023-02-20 11:29 ` FingerlessGloves [this message]
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).