Home Network Admin
Administer Tim's home network: devices connected over Tailscale, with a Synology NAS and Macs accessible via SSH.
Read references/network-inventory.md for the full device list, IPs, SSH config, and network topology before performing any task.
SSH Access
SSH configs are defined in ~/.ssh/config. Use the short aliases:
ssh synology - Synology NAS (custom port, user tdhopper)ssh dobro - Mac (default port, user thopper)
SSH keys are managed via 1Password agent. If SSH fails with auth errors, verify 1Password is unlocked and the SSH agent is running.
Synology NAS Administration
The Synology runs DSM. Common admin tasks via SSH:
- Packages:
synopkg list (installed), synopkg status <pkg>, synopkg start/stop <pkg>
- Docker/Container Manager:
sudo docker ps, sudo docker logs <container>, sudo docker compose (compose files often in /volume1/docker/)
- Disk/volume health:
df -h, cat /proc/mdstat, synodisk --enum
- Shared folders: typically under
/volume1/
- DSM web UI:
https://synology:5001 or https://100.86.145.18:5001
- Logs:
/var/log/ and DSM log center
For destructive operations (deleting files, stopping services, modifying configs), confirm with the user first.
Tailscale
Tailscale connects all devices over a WireGuard mesh. Run tailscale status to discover the tailnet name and device list.
- On macOS, the
tailscale CLI may not be on PATH. Use: /Applications/Tailscale.app/Contents/MacOS/Tailscale
- Check status:
tailscale status (or the full path above)
- Verify connectivity:
tailscale ping <hostname>
- All devices are reachable via MagicDNS (e.g.,
synology.<tailnet>.ts.net)
Caddy Reverse Proxy (on dobro)
Caddy runs on dobro, providing HTTPS reverse proxy for *.hopperhosted.com. The Caddyfile is at ~/Caddyfile (tracked in yadm). TLS uses Cloudflare DNS-01 challenge.
See references/network-inventory.md for the full list of proxied subdomains and backends.
- Manage Caddy on dobro:
ssh dobro then brew services restart caddy, caddy reload --config ~/Caddyfile
- Logs:
journalctl -u caddy or brew services info caddy depending on how it's managed
- Edit Caddyfile locally: it's tracked in yadm dotfiles at
~/Caddyfile
File Transfer
- Between local and remote hosts:
scp or rsync using the SSH aliases
- Example:
rsync -avz ~/files/ synology:/volume1/backup/files/
- For large transfers, prefer
rsync with --progress
Troubleshooting
- Can't SSH: Check 1Password is unlocked, verify Tailscale is connected (
tailscale status), ping the Tailscale IP
- DNS issues: Check if MagicDNS resolves (
dig @100.100.100.100 synology.<tailnet>.ts.net), fall back to Tailscale IPs directly
- NAS unresponsive: Try ping, check DSM web UI, SSH may still work even if DSM is sluggish
- Slow network: Check if traffic is going through Tailscale relay (
tailscale status shows DERP relay vs direct connection)
1---2name: home-network-admin3description: Manage and troubleshoot Tim's home network, SSH into devices, administer the Synology NAS, and work with Tailscale. Use when the user wants to (1) SSH into or run commands on remote machines (synology, dobro), (2) manage the Synology NAS (files, packages, Docker, backups, Surveillance Station), (3) troubleshoot network connectivity or DNS, (4) check Tailscale status or manage the tailnet, (5) transfer files between machines, (6) check device health or disk usage, (7) manage the Caddy reverse proxy on dobro (*.hopperhosted.com), (8) any home server or home network administration task.4---56# Home Network Admin78Administer Tim's home network: devices connected over Tailscale, with a Synology NAS and Macs accessible via SSH.910Read [references/network-inventory.md](references/network-inventory.md) for the full device list, IPs, SSH config, and network topology before performing any task.1112## SSH Access1314SSH configs are defined in `~/.ssh/config`. Use the short aliases:1516- `ssh synology` - Synology NAS (custom port, user tdhopper)17- `ssh dobro` - Mac (default port, user thopper)1819SSH keys are managed via 1Password agent. If SSH fails with auth errors, verify 1Password is unlocked and the SSH agent is running.2021## Synology NAS Administration2223The Synology runs DSM. Common admin tasks via SSH:2425- **Packages**: `synopkg list` (installed), `synopkg status <pkg>`, `synopkg start/stop <pkg>`26- **Docker/Container Manager**: `sudo docker ps`, `sudo docker logs <container>`, `sudo docker compose` (compose files often in `/volume1/docker/`)27- **Disk/volume health**: `df -h`, `cat /proc/mdstat`, `synodisk --enum`28- **Shared folders**: typically under `/volume1/`29- **DSM web UI**: `https://synology:5001` or `https://100.86.145.18:5001`30- **Logs**: `/var/log/` and DSM log center3132For destructive operations (deleting files, stopping services, modifying configs), confirm with the user first.3334## Tailscale3536Tailscale connects all devices over a WireGuard mesh. Run `tailscale status` to discover the tailnet name and device list.3738- On macOS, the `tailscale` CLI may not be on PATH. Use: `/Applications/Tailscale.app/Contents/MacOS/Tailscale`39- Check status: `tailscale status` (or the full path above)40- Verify connectivity: `tailscale ping <hostname>`41- All devices are reachable via MagicDNS (e.g., `synology.<tailnet>.ts.net`)4243## Caddy Reverse Proxy (on dobro)4445Caddy runs on dobro, providing HTTPS reverse proxy for `*.hopperhosted.com`. The Caddyfile is at `~/Caddyfile` (tracked in yadm). TLS uses Cloudflare DNS-01 challenge.4647See [references/network-inventory.md](references/network-inventory.md) for the full list of proxied subdomains and backends.4849- **Manage Caddy on dobro**: `ssh dobro` then `brew services restart caddy`, `caddy reload --config ~/Caddyfile`50- **Logs**: `journalctl -u caddy` or `brew services info caddy` depending on how it's managed51- **Edit Caddyfile locally**: it's tracked in yadm dotfiles at `~/Caddyfile`5253## File Transfer5455- Between local and remote hosts: `scp` or `rsync` using the SSH aliases56- Example: `rsync -avz ~/files/ synology:/volume1/backup/files/`57- For large transfers, prefer `rsync` with `--progress`5859## Troubleshooting60611. **Can't SSH**: Check 1Password is unlocked, verify Tailscale is connected (`tailscale status`), ping the Tailscale IP622. **DNS issues**: Check if MagicDNS resolves (`dig @100.100.100.100 synology.<tailnet>.ts.net`), fall back to Tailscale IPs directly633. **NAS unresponsive**: Try ping, check DSM web UI, SSH may still work even if DSM is sluggish644. **Slow network**: Check if traffic is going through Tailscale relay (`tailscale status` shows DERP relay vs direct connection)
diegosouzapw