Age | Commit message (Collapse) | Author |
|
|
|
|
|
$ generate ipsec mac-ios-profile <connection> remote <ip>
|
|
The migrator from 20-to-21 is required as 19-to-20 on VyOS 1.3 - thus simply
rename/reorder the two migrators to not break things the hard way when
upgrading from 1.3 -> 1.4.
|
|
|
|
|
|
set vpn ipsec remote-access connection rw authentication client-mode 'eap-radius'
set vpn ipsec remote-access connection rw authentication id '192.0.2.1'
set vpn ipsec remote-access connection rw authentication server-mode 'x509'
set vpn ipsec remote-access connection rw authentication x509 ca-certificate 'CAcert_Class_3_Root'
set vpn ipsec remote-access connection rw authentication x509 certificate 'vyos'
set vpn ipsec remote-access connection rw esp-group 'ESP-RW'
set vpn ipsec remote-access connection rw ike-group 'IKE-RW'
set vpn ipsec remote-access connection rw local-address '192.0.2.1'
set vpn ipsec remote-access connection rw pool 'ra-rw-ipv4'
set vpn ipsec remote-access connection rw unique 'never'
set vpn ipsec remote-access pool ra-rw-ipv4 name-server '192.0.2.2'
set vpn ipsec remote-access pool ra-rw-ipv4 prefix '192.168.22.0/24'
set vpn ipsec remote-access radius nas-identifier 'fooo'
set vpn ipsec remote-access radius server 172.16.100.10 key 'secret'
|
|
|
|
As this is only related to remote-access, keeping it under "options" simply
feels wrong.
|
|
pki: T3642: Add ability to write generated certificates/keys to files
|
|
|
|
(cherry picked from commit 7292631373ea50f9908796ef2eda32e672d1df2e)
|
|
filenames
|
|
|
|
As the keys are now stored inside the CLI configuration and no longer in a file
on the filesystem, this command is no longer required.
Also there are dedicated CLI commands available to display the additional
Wireguard information.
- show interfaces wireguard wg10
- show interfaces wireguard wg10 summary
|
|
As the keys are now stored inside the CLI configuration and no longer in a file
on the filesystem, this command is no longer required.
|
|
As the keys are now stored inside the CLI configuration and no longer in
a file on the filesystem, this command is no longer required.
|
|
bridge: op-mode: T3698: Support bridge monitoring
|
|
Per interface public-key can now be retrieved via:
vyos@vyos:~$ show interfaces wireguard wg10 public-key
+XZr0oUjYRQuB/kcO1f+puOjKkiOWBG8eZX1Jpyq2n0=
|
|
|
|
|
|
Update/refresh of DNS records is now handled internally by Strongswan.
|
|
|
|
bridge: op-mode: T3667: Fix displaying members of a specific bridge interface
|
|
pki: https: T3642: Migrate HTTPS to use PKI configuration
|
|
|
|
|
|
pki: openvpn: T3642: Migrate OpenVPN to PKI and refactor
|
|
|
|
|
|
generate ipsec mac-ios-profile <connection> remote <ip|fqdn>
will generate a matching IPSec profile which can be loaded on an iOS device.
|
|
pki: eapol: T3642: Migrate EAPoL to use PKI configuration
|
|
|
|
|
|
pki: openconnect: sstp: T3642: Migrate OpenConnect and SSTP to PKI configuration
|
|
|
|
|
|
This extends commit 22791e26 ("VRF: T3655: proper connection tracking for VRFs")
so that when the netfilter table is removed, we first check if it exists at all,
and if it does not exist we do not remove it.
This fixes the smoketest error:
PermissionError: [Errno 1] failed to run command: nft delete table inet vrf_zones
|
|
pki: wireguard: T3642: Migrate Wireguard private key directly into CLI
|
|
|
|
Also renames peer pubkey to public-key for consistency
|
|
Connection uniqueness policy to enforce. To avoid multiple connections from the
same user, a uniqueness policy can be enforced.
* never: never enforce such a policy, even if a peer included INITIAL_CONTACT
notification
* keep: reject new connection attempts if the same user already has an active
connection
* replace: delete any existing connection if a new one for the same user gets
established
To compare connections for uniqueness, the remote IKE identity is used. If EAP
or XAuth authentication is involved, the EAP-Identity or XAuth username is used
to enforce the uniqueness policy instead.
|
|
Remote access IP pools can now be defined at a global level and referenced
in IPSec remote-access connections. To defined a pool use:
set vpn ipsec remote-access pool global-ipv4 name-server '172.16.1.1'
set vpn ipsec remote-access pool global-ipv4 prefix '192.168.0.0/24'
set vpn ipsec remote-access pool global-ipv6 name-server '2001:db8::1'
set vpn ipsec remote-access pool global-ipv6 prefix '2001:db8:1000::/64'
A connection can then reference the pool:
set vpn ipsec remote-access connection foo pool 'global-ipv4'
set vpn ipsec remote-access connection foo pool 'global-ipv6'
|
|
... this enables a dual-stack IKEv2 VPN deployment.
|
|
|
|
|
|
This reverts commit 70f7f06e778efa4bd3c2ad127d66c080e1db80c5.
|
|
|
|
|
|
|