Files

Test / test (push) Has been cancelled

Details

refactor(rego-tunnel): Replace QEMU VM with native Docker Cisco VPN

- Switch from linux-vm QEMU image to cisco-vpn native Docker image
- Change port from 8006 to 6080 (noVNC)
- Remove VM-specific config (RAM, CPU, bridges, taps, QEMU)
- Add VPN credential fields (email, password, TOTP, VPN host)
- Add auto-connect and VNC password options
- Update description.md with new documentation
- Simplify Docker requirements (no /dev/kvm needed)

Benefits:
- No QEMU/VM overhead - runs natively in Docker
- Full Cisco Secure Client 5.1.14.145 with GUI
- Auto-login with TOTP support
- Auto-reconnect on disconnect

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2026-01-16 19:47:11 +00:00

2.0 KiB

Executable File

Raw Blame History

Rego Tunnel - Cisco Secure Client VPN

Run Cisco Secure Client (AnyConnect) with full GUI support in Docker using noVNC.

Features

Full Cisco Secure Client 5.1.14.145 with GUI
VPN, DART, and Posture modules pre-installed
Web-based VNC access via noVNC
Systemd support for proper service management
No QEMU or VM overhead - runs natively in Docker
Auto-login with TOTP support - fully automated connection
Auto-reconnect on disconnect

Quick Start

Install the app through Runtipi
Configure credentials (optional) through app settings for auto-connect
Access the VPN GUI at http://<your-server>:6080/vnc.html
Default VNC password: cisco123

Auto-Connect

For fully automated VPN connection:

Fill in your VPN Email, Password, and TOTP Secret in app settings
Enable "Auto-Connect on Start"
The container will automatically connect to VPN on startup

Manual Connect

If you prefer manual login:

Access the noVNC interface at port 6080
Use the Cisco Secure Client GUI to connect
Enter your credentials manually

VPN CLI (inside container)

# Connect to VPN
docker exec -it rego-tunnel /opt/cisco/secureclient/bin/vpn connect <server>

# Check status
docker exec -it rego-tunnel /opt/cisco/secureclient/bin/vpn state

# Disconnect
docker exec -it rego-tunnel /opt/cisco/secureclient/bin/vpn disconnect

Troubleshooting

VPN connects but immediately disconnects

Check if the DNS files are writable. Restart the container if needed.

"Unable to start VA" error

This usually means the DNS files are read-only. Restart the container.

noVNC not accessible

Check if the VNC service is running:

docker exec rego-tunnel systemctl status vnc.service

Technical Details

The container uses:

--privileged mode for systemd and DNS mount manipulation
NET_ADMIN capability for VPN tunnel creation
/dev/net/tun device for the VPN tunnel
Ports: 6080 (noVNC web UI), 5901 (VNC)

2.0 KiB Executable File Raw Blame History