Falsche Peer-PublicKeys in m16/m13 WireGuard-Configs korrigiert
- m16.conf/m13.conf: Peer-PublicKey war der eigene statt der des Servers, dadurch wurde kein Peer geladen und DNS/VPN funktionierte nicht - setup-base.sh: AllowedIPs Komma→Semikolon fuer NM-Format
This commit is contained in:
parent
384f44441b
commit
75de3c203b
3 changed files with 3 additions and 3 deletions
|
|
@ -183,7 +183,7 @@ if [[ -n "$REPO_DIR" && -f "$WG_CONF" ]]; then
|
|||
WG_ADDR=$(grep -oP 'Address\s*=\s*\K.*' "$WG_CONF")
|
||||
WG_PUBKEY=$(grep -oP 'PublicKey\s*=\s*\K.*' "$WG_CONF")
|
||||
WG_PSK=$(grep -oP 'PresharedKey\s*=\s*\K.*' "$WG_CONF")
|
||||
WG_ALLOWED=$(grep -oP 'AllowedIPs\s*=\s*\K.*' "$WG_CONF" | tr -d ' ')
|
||||
WG_ALLOWED=$(grep -oP 'AllowedIPs\s*=\s*\K.*' "$WG_CONF" | tr -d ' ' | tr ',' ';')
|
||||
WG_ENDPOINT=$(grep -oP 'Endpoint\s*=\s*\K.*' "$WG_CONF")
|
||||
WG_KEEPALIVE=$(grep -oP 'PersistentKeepalive\s*=\s*\K.*' "$WG_CONF")
|
||||
# NM-Verbindungsdatei direkt schreiben (laeuft als root, Keys persistent)
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue