feat: rebranded from vpn-router to linux-manager.
This commit is contained in:
1 parent
8efe21bfa6
commit
85a1ffa21f
238 files changed
+5010
-3761
No files matched your search
+12
-8
@@ -1,15 +1,19 @@
|
||||
# Remote Access
|
||||
|
||||
A tab each for IKEv2, OpenVPN and WireGuard access: the settings, whether the router
|
||||
A tab each for IKEv2, OpenVPN and WireGuard access: the settings, whether the server
|
||||
runs the system, why an enabled one does not run yet, and the connected clients.
|
||||
|
||||
The page is there while the VPN component is on (`vpn.enabled`). While the router component is
|
||||
off, the clients reach the networks of `local.cidrs` through NAT from the server's address, on
|
||||
its one interface; while it is on, they are routed with their own addresses.
|
||||
|
||||
## Edit
|
||||
|
||||
Enables or disables the system and sets its address pool (for WireGuard the address of `wg0`) and
|
||||
its port, with OpenVPN's protocol. The router applies a change in the background.
|
||||
its port, with OpenVPN's protocol. The server applies a change in the background.
|
||||
|
||||
IKEv2 and OpenVPN also need the router's `wan.local_fqdn` and its VPN server certificate. A cloud
|
||||
firewall in front of the router, such as an Azure network security group, must allow the OpenVPN
|
||||
IKEv2 and OpenVPN also need the server's `wan.local_fqdn` and its VPN server certificate. A cloud
|
||||
firewall in front of the server, such as an Azure network security group, must allow the OpenVPN
|
||||
and WireGuard ports itself.
|
||||
|
||||
## IKEv2
|
||||
@@ -17,7 +21,7 @@ and WireGuard ports itself.
|
||||
The IPsec security associations, child SAs, connections and connection children of IKEv2 access.
|
||||
|
||||
**DNS domains** (Edit, one per line): the domains, with their subdomains, the clients resolve with
|
||||
the router's DNS, such as `internal.cloudapp.net`; other names stay with the clients' own DNS. The
|
||||
the server's DNS, such as `internal.cloudapp.net`; other names stay with the clients' own DNS. The
|
||||
router pushes them over IKEv2, and the Apple VPN profile names them, so a Mac, iPhone or iPad needs
|
||||
a newly downloaded profile after a change.
|
||||
|
||||
@@ -31,11 +35,11 @@ their password and, when enrolled, the code.
|
||||
- **Connections:** each peer with its user, IPs, endpoint, handshake and traffic.
|
||||
- **Peers:** the devices of the VPN users, each with its user, public key and IPs.
|
||||
- **Add peer:** the user, the device's public key and the IPs, which start as the next free
|
||||
address of the `wg0` network. The router checks that keys are unique and IPs do not overlap.
|
||||
address of the `wg0` network. The server checks that keys are unique and IPs do not overlap.
|
||||
- The eye opens the device's configuration; the download gives `<user>-<n>.conf`, with a
|
||||
placeholder for the device's private key, which the router never has.
|
||||
placeholder for the device's private key, which the server never has.
|
||||
- The remove button removes a peer after a confirmation.
|
||||
- **Server:** the router's public key with a copy icon, the endpoint and the allowed IPs a device
|
||||
- **Server:** the server's public key with a copy icon, the endpoint and the allowed IPs a device
|
||||
needs; **Show config** opens a device configuration with placeholders.
|
||||
- In the configuration dialogs a switch leaves out the `[Interface]` and `PrivateKey` lines, which
|
||||
WireGuard for Windows fills in for a new empty tunnel.
|
||||
Reference in new issue
Block a user