| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2020-10-30 | smoketest: openvpn: extend server verify() test with TLS auth keys | Christian Poessinger | |
| 2020-10-30 | smoketest: openvpn: test server mode verify() steps | Christian Poessinger | |
| 2020-10-30 | smoketest: openvpn: test site2site mode verify() steps | Christian Poessinger | |
| 2020-10-30 | smoketest: openvpn: test client mode verify() steps | Christian Poessinger | |
| 2020-10-19 | smoketest: openvpn: test VRF assignment | Christian Poessinger | |
| 2020-10-19 | smoketest: openvpn: ensure interfaces do not persist after deletion | Christian Poessinger | |
| 2020-10-18 | smoketest: openvpn: add server (P-t-MP) and site2site testcases | Christian Poessinger | |
| 2020-10-18 | openvpn: T2969: force creation of tunnel interfaces | Christian Poessinger | |
| A lot of VyOS code requires the Kernel interface to be present in order to properly work and adjust the interface to the users CLI intends (alias, ipv6, vrf - just to name a few). OpenVPN - when run in client mode - only creates the interface (e.g. vtun1) when the connection to the OpenVPN server was successful. This can't be always the case due to e.g. software-updates or routing issues to the remote side. This will in the end result in a zombie OpenVPN client interface where some config items might not have been set when the interface finally comes up - imagine a wrong assigned VRF instance. By always creating the OpenVPN interface manuall we ensure that all the CLI settings are properly configured in the OS kernel. | |||
| 2020-10-18 | smoketest: openvpn: add initial client test | Christian Poessinger | |
