From: crodges <crodges@csphy.pw>
To: help-guix@gnu.org
Subject: Wireguard configuration - PostUp and PostDown
Date: Sat, 28 Aug 2021 15:55:45 -0700 [thread overview]
Message-ID: <4144851.J7mxVJ4J92@sceadufaex> (raw)
Hello everyone,
I managed to configure wireguard on a vps running guix and created clients for
my desktop and cellphone. What I want to do (and did already in a Debian vps)
is to make wireguard's lan accessible to anyone connected and also browse the
internet using this vpn.
As I remember, I need to allow ip forwarding using
sysctl net.ipv4.ip_forward=1
and I also need to put these rules into wireguard (the server) under
[interface],
PostUp = iptables -A FORWARD -i wg0 -j ACCEPT; iptables -t nat -A POSTROUTING
-o eth0 -j MASQUERADE; ip6tables -A FORWARD -i wg0 -j ACCEPT; ip6tables -t nat
-A POSTROUTING -o eth0 -j MASQUERADE
PostDown = iptables -D FORWARD -i wg0 -j ACCEPT; iptables -t nat -D
POSTROUTING -o eth0 -j MASQUERADE; ip6tables -D FORWARD -i wg0 -j ACCEPT;
ip6tables -t nat -D POSTROUTING -o eth0 -j MASQUERADE
Problem is, looking at the latest guix manual, PostUp and PostDown doesn't
seem to exist yet. Do they exist but are still undocumented?
If they don't exist, where should be a reasonable place to add this
configurations? I'm trying to do everything the guix way, when I finish this
machine configuration, I'd like it to be fully replicable.
next reply other threads:[~2021-08-29 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-28 22:55 crodges [this message]
2021-08-30 12:25 ` Wireguard configuration - PostUp and PostDown Pierre Langlois
2021-08-31 16:16 ` crodges
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4144851.J7mxVJ4J92@sceadufaex \
--to=crodges@csphy.pw \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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 read-only IMAP folder(s) and NNTP newsgroup(s).