nsaspy/dotfiles
1
1
Fork 0
Code Issues 45 Pull requests 8 Projects Releases 1 Packages Wiki Activity Actions 5

ssh: repoint vpn alias to PiVPN CT and add tunnel-stable pivpn alias #215

Open
nsaspy wants to merge 1 commit from fix/pivpn-ssh-alias into master
pull from: fix/pivpn-ssh-alias
merge into: nsaspy:master
Conversation 0 Commits 1 Files changed 1 +157
nsaspy commented 2026-09-19 17:54:57 +00:00
Owner
Copy link

Problem

Connected over the PiVPN (CT 115 pivpn.lost.system on proxmox), SSH to flake worked but ssh vpn timed out.

Root cause

  • The CT's eth0 is statically configured 10.50.50.43 (pct config 115); the vpn alias still pointed at 10.50.50.30, which has no ARP entry (dead).
  • The CT's IP has drifted before (logins seen from .69 earlier in the week), so a second tunnel-stable alias is warranted.

Changes

  • vpn Hostname → 10.50.50.43 (verified: ssh vpn lands on the CT, port 22 open, root key auth OK).
  • New pivpn alias → 10.6.0.1 (the CT's wg0 address) — reachable over the VPN regardless of LAN IP drift.
  • .ssh/config now tracked here; deployed on flake via the existing symlink convention (~/.ssh/config -> ../.dotfiles/.ssh/config). Keys remain untracked.

Verification

  • ssh -G vpn|pivpn resolve to the expected hostnames.
  • TCP/22 to 10.50.50.43 open; interactive ssh vpn returns pivpn / 10.50.50.43 10.70.70.2 10.6.0.1.
  • prolog-verification gate passed (5 machine-recorded observations at HEAD 0b6e119).

Fixes the VPN SSH timeout reported from the road.

## Problem Connected over the PiVPN (CT 115 `pivpn.lost.system` on proxmox), SSH to `flake` worked but `ssh vpn` timed out. ## Root cause - The CT's eth0 is statically configured `10.50.50.43` (`pct config 115`); the `vpn` alias still pointed at `10.50.50.30`, which has no ARP entry (dead). - The CT's IP has drifted before (logins seen from `.69` earlier in the week), so a second tunnel-stable alias is warranted. ## Changes - `vpn` Hostname → `10.50.50.43` (verified: `ssh vpn` lands on the CT, port 22 open, root key auth OK). - New `pivpn` alias → `10.6.0.1` (the CT's wg0 address) — reachable over the VPN regardless of LAN IP drift. - `.ssh/config` now tracked here; deployed on flake via the existing symlink convention (`~/.ssh/config -> ../.dotfiles/.ssh/config`). Keys remain untracked. ## Verification - `ssh -G vpn|pivpn` resolve to the expected hostnames. - TCP/22 to 10.50.50.43 open; interactive `ssh vpn` returns `pivpn` / `10.50.50.43 10.70.70.2 10.6.0.1`. - prolog-verification gate passed (5 machine-recorded observations at HEAD 0b6e119). Fixes the VPN SSH timeout reported from the road.
ssh: repoint vpn alias to PiVPN CT and add tunnel-stable pivpn alias
Some checks failed
Nix / workflows (pull_request) Failing after 3s
Details
Nix / image-progress-tests (pull_request) Has been skipped
Details
Nix / logos (pull_request) Has been skipped
Details
Nix / workflows (push) Failing after 25s
Details
Nix / image-progress-tests (push) Has been skipped
Details
Nix / logos (push) Has been skipped
Details
0b6e119180 
The pivpn.lost.system CT (115 on proxmox) now lives at 10.50.50.43;
the old vpn alias pointed at stale 10.50.50.30 and timed out. Also add
a pivpn alias for 10.6.0.1 (the CT's wg0 address) which is reachable
over the VPN regardless of LAN IP drift, and start tracking .ssh/config
here. Desktop deploy follows the existing symlink convention.
Some checks failed
Nix / workflows (pull_request) Failing after 3s
Details
Nix / image-progress-tests (pull_request) Has been skipped
Details
Nix / logos (pull_request) Has been skipped
Details
Nix / workflows (push) Failing after 25s
Details
Nix / image-progress-tests (push) Has been skipped
Details
Nix / logos (push) Has been skipped
Details
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin fix/pivpn-ssh-alias:fix/pivpn-ssh-alias
git switch fix/pivpn-ssh-alias

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch master
git merge --no-ff fix/pivpn-ssh-alias
git switch fix/pivpn-ssh-alias
git rebase master
git switch master
git merge --ff-only fix/pivpn-ssh-alias
git switch fix/pivpn-ssh-alias
git rebase master
git switch master
git merge --no-ff fix/pivpn-ssh-alias
git switch master
git merge --squash fix/pivpn-ssh-alias
git switch master
git merge --ff-only fix/pivpn-ssh-alias
git switch master
git merge fix/pivpn-ssh-alias
git push origin master
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug
Something isn't working

  
documentation
Improvements or additions to documentation

  
duplicate
This issue or pull request already exists

  
enhancement
New feature or request

  
good first issue
Good for newcomers

  
help wanted
Extra attention is needed

  
invalid
This doesn't seem right

  
question
Further information is requested

  
wontfix
This will not be worked on

No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nsaspy/dotfiles!215
No description provided.