Tizian 「ティツィアーン」
3f6581d6e2
Ubuntu 26.04 confines wg-quick in an AppArmor profile whose nft sub-profile may read nothing in /etc/wireguard, so the tunnel failed to come up at home. The unit's drop-in (wg-quick-halkyon.conf, before-docker.conf before) loads the rules before the interface exists and deletes them after it is gone, so the tunnel never runs without them. ramiel, on 24.04, keeps PostUp. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Tizian 「ティツィアーン」 <raisondetredev@pm.me>
18 lines
781 B
Text
18 lines
781 B
Text
# Home's end of the tunnel through which ramiel publishes halkyon.li (ADR 0039, D8), as
|
|
# /etc/wireguard/wg-halkyon.conf on the instance's host at home (root, 0600), brought
|
|
# up by wg-quick@wg-halkyon before Docker, its rules loaded around it (both
|
|
# wg-quick-halkyon.conf). Its private key is a file of its own beside it, never here.
|
|
# Setting it up: host/README.md.
|
|
|
|
[Interface]
|
|
Address = 10.61.97.2/30
|
|
PostUp = wg set %i private-key /etc/wireguard/wg-halkyon.key
|
|
|
|
# ramiel, dialled by its address: home opens nothing on the FRITZ!Box, and a new home
|
|
# address needs no change anywhere. The keepalive keeps the way back open through the
|
|
# router's NAT.
|
|
[Peer]
|
|
PublicKey = <ramiel's public key>
|
|
Endpoint = 45.129.181.128:51820
|
|
AllowedIPs = 10.61.97.1/32
|
|
PersistentKeepalive = 25
|