#
l2tp
Here are 33 public repositories matching this topic...
Docker image to run an IPsec VPN server, with IPsec/L2TP and Cisco IPsec
-
Updated
Mar 4, 2020 - Shell
Setup your own private, secure, free* VPN on the Amazon AWS Cloud in 10 minutes. CloudFormation
aws
security
cloudformation
encryption
ipsec
vpn
vpn-server
vpn-client
l2tp
ssh-tunnel
ipsec-vpn
vpn-service
aws-cloud
lono
-
Updated
Feb 18, 2020
L2TP and L2TP/IPsec support for NetworkManager
-
Updated
Mar 4, 2020 - C
slavikme
commented
Jul 8, 2019
First of all, good job!
Some minor note:
I noticed here that you are forwarding ports docker container creation. But you are also using option --net=host on the same line. This behavior is pointless, as the port forwarding concept doesn't exists when using host's network.
You can feel free to remove all -p opti
Desktop application for creating a personal VPN server. L2TP, PPTP, OpenVPN, WireGuard. | Providers: DigitalOcean, Linode, CryptoServers, Hetzner Cloud
openvpn
digitalocean
linode
vpn
anonymous
vpn-server
vpn-client
l2tp
pptp
security-tools
cryptoservers
-
Updated
Feb 24, 2020 - JavaScript
Builds VPN server on AWS EC2 with QR code support. Works on Ubuntu, OSX and Debian variants including Raspbian.
-
Updated
Mar 4, 2020 - Shell
SoftEther VPN Server Installer for CentOS, Ubuntu, RedHat, etc, Supports: SoftEther, OpenVPN, IPSEC / L2TP, SSTP, User Management, User Statistics, etc
openvpn
ipsec
vpn
openvpn-configuration
openvpn-server
vpn-server
vpn-client
l2tp
openvpn-admin
ipsec-vpn
openvpn-monitor
openvpn-installer
softether
sstp
softethervpn
openvpn-auth
-
Updated
Feb 26, 2020 - Shell
This program will connect desktop clients to Meraki firewalls
-
Updated
Aug 19, 2019 - Python
Setup a L2TP VPN Server with static DNS mapping fixed. Firmware version: 2.0.8
-
Updated
Feb 20, 2020
Improve this page
Add a description, image, and links to the l2tp topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the l2tp topic, visit your repo's landing page and select "manage topics."
Right now in different places in the SE codebase there are references to /opt and then as well to /usr.
All SE code should reference one place only. Could someone please create a PR that fixes this.
This PR should also take PR #454 into consideration (no conflicts)