Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| docs:guide-user:services:vpn:openconnect:server [2020/10/16 19:46] – [Why use OpenConnect] update vgaetera | docs:guide-user:services:vpn:openconnect:server [2023/03/25 10:46] – [2. Key management] vgaetera | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== OpenConnect server ====== | + | ====== OpenConnect server ====== |
| - | OpenConnect is an SSL-based VPN client which is inter-operable with the commercial products Cisco AnyConnect, Juniper Pulse Connect Secure, and Palo Alto Networks GlobalProtect. | + | {{section> |
| - | This is a beginner' | + | ===== Introduction ===== |
| + | * This how-to describes the method for setting up [[wp>OpenConnect|OpenConnect]] server | ||
| + | * Follow [[docs: | ||
| - | The primary goal of this HOWTO is to get a working OpenConnect tunnel with the least amount of compatability issues. Note that the instructions provided [[https:// | + | ===== Goals ===== |
| + | {{section> | ||
| - | For an overview of all VPN-related articles (including other VPN technologies), | + | ===== Command-line instructions ===== |
| + | ==== 1. Preparation ==== | ||
| + | Install the required packages. | ||
| + | Specify configuration parameters for VPN server. | ||
| - | ===== Use Case (the beginner' | + | <code bash> |
| - | The user wants a client to access their OpenWrt router and the network it supports on the back securely with a minimum of compatibility issues and minimum configuration fuss. The client can be a mobile user roaming on a mobile network OR at a public wifi hotspot, and wants to EITHER secure their traffic from eavesdropping, | + | # Install packages |
| + | opkg update | ||
| + | opkg install ocserv | ||
| - | The end result will be an encrypted connection directly between the client (on the WAN side) and LAN side of the OpenWRT, such that the client effectively has access to the LAN side as if they were local, PLUS the benefits of their OpenWRT firewall for browsing the Internet. | + | # Configuration parameters |
| + | VPN_PORT=" | ||
| + | VPN_POOL=" | ||
| + | VPN_DNS=" | ||
| + | VPN_USER=" | ||
| + | VPN_PASS=" | ||
| + | </ | ||
| - | Note that this is a FULL tunnel, meaning all traffic is routed through the VPN once connected. This is, in my opinion, the only type of tunnel to use, as a split tunnel is inherently insecure. You cannot, | + | ==== 2. Key management ==== |
| + | Generate password hash for VPN client. | ||
| - | ===== Why use OpenConnect ===== | + | <code bash> |
| - | * Your network provider is BLOCKING IPSEC traffic. This is apparently POLICY for mobile carriers, though they deny it. OpenConnect is SSL. | + | # Generate password hash |
| - | | + | ocpasswd ${VPN_USER} << EOI |
| - | * You just want a secure SSL-based VPN to your LAN. | + | ${VPN_PASS} |
| + | ${VPN_PASS} | ||
| + | EOI | ||
| + | VPN_HASH="$(sed -n -e "/ | ||
| + | </ | ||
| - | [[http:// | + | ==== 3. Firewall ==== |
| + | Consider VPN network as private. | ||
| + | Assign VPN interface to LAN zone to minimize firewall setup. | ||
| + | Allow access to VPN server from WAN zone. | ||
| - | ===== Server | + | <code bash> |
| - | You will want the following packages: [[packages: | + | # Configure firewall |
| + | uci rename firewall.@zone[0]=" | ||
| + | uci rename firewall.@zone[1]=" | ||
| + | uci del_list firewall.lan.device=" | ||
| + | uci add_list firewall.lan.device=" | ||
| + | uci -q delete firewall.oc | ||
| + | uci set firewall.oc=" | ||
| + | uci set firewall.oc.name=" | ||
| + | uci set firewall.oc.src=" | ||
| + | uci set firewall.oc.dest_port=" | ||
| + | uci set firewall.oc.proto="tcp udp" | ||
| + | uci set firewall.oc.target=" | ||
| + | uci commit firewall | ||
| + | / | ||
| + | </ | ||
| - | One of the easiest setups is to configure the VPN as a pseudo-bridge with Proxy ARP. What this means is that you will connect and be on the LAN side of your router with no additional routing needed, as if you were there. The configuration is described in this recipe[[http:// | + | ==== 4. VPN service ==== |
| + | Configure VPN service. | ||
| - | Router is configured at 192.168.1.1 | + | <code bash> |
| - | DHCP hosts are configured to use the range 192.168.1.2-192.168.1.50 | + | # Configure VPN service |
| - | You want your VPN hosts to use the range 192.168.1.100 and have only 1-2 hosts connecting at any given time | + | uci -q delete ocserv.config.enable |
| + | uci -q delete ocserv.config.zone | ||
| + | uci set ocserv.config.port=" | ||
| + | uci set ocserv.config.ipaddr=" | ||
| + | uci set ocserv.config.netmask=" | ||
| + | uci -q delete ocserv.@routes[0] | ||
| + | uci -q delete ocserv.@dns[0] | ||
| + | uci set ocserv.dns=" | ||
| + | uci set ocserv.dns.ip=" | ||
| + | uci -q delete ocserv.@ocservusers[0] | ||
| + | uci set ocserv.client=" | ||
| + | uci set ocserv.client.name=" | ||
| + | uci set ocserv.client.password=" | ||
| + | uci commit ocserv | ||
| + | / | ||
| + | </ | ||
| - | 1) Edit / | + | ===== Testing ===== |
| - | | + | {{section> |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | This will put your VPN clients at 192.168.1.100+. Note that the netmask limits the # of clients you can have to TWO. Change as necessary. | + | |
| - | NOTE: the above suggests port 443 as the preferred port. This is to support MOBILE clients. | + | |
| - | Many mobile network operators are blocking other ports (despite the FCC open internet order), | + | |
| - | but they cannot block port 443, therefore 443 is more likely to work for the majority of mobil users. | + | |
| - | + | ||
| - | 2) Add your DNS server | + | |
| - | | + | ===== Troubleshooting ===== |
| - | option ip ' | + | Collect |
| - | + | ||
| - | 3) Edit / | + | |
| - | config rule | + | |
| - | option name 'Allow SSL vpn in (tcp)' | + | |
| - | option src ' | + | |
| - | option proto ' | + | |
| - | option dest_port ' | + | |
| - | option target ' | + | |
| - | + | ||
| - | config rule | + | |
| - | option name 'Allow SSL vpn in (udp)' | + | |
| - | option src ' | + | |
| - | option proto ' | + | |
| - | option dest_port ' | + | |
| - | option target ' | + | |
| - | + | ||
| - | What this does is accept traffic for SSL on the WAN side. | + | |
| - | 4) Add the following to /etc/firewall.user (or use LUCI): | + | <code bash> |
| + | # Restart services | ||
| + | /etc/init.d/log restart; / | ||
| - | iptables -A input_rule -i vpns+ -j ACCEPT | + | # Log and status |
| - | | + | logread |
| - | iptables -A forwarding_rule -o vpns+ -j ACCEPT | + | |
| - | iptables | + | |
| - | What these do is allow traffic from the VPN interface(s). | + | # Runtime configuration |
| + | pgrep -f -a ocserv | ||
| + | ip address show; ip route show table all | ||
| + | ip rule show; ip -6 rule show; nft list ruleset | ||
| - | Lastly: | + | # Persistent |
| - | 5) Edit / | + | uci show network; uci show firewall; uci show ocserv |
| - | | + | </ |
| - | + | ||
| - | Then type sysctl -p to reload the configuration | + | |
| - | + | ||
| - | 5) Add users(and passwords) to your OpenConnect service. I find LUCI to be pretty easy to use for all of these steps. | + | |
| - | + | ||
| - | FINALLY: Restart your firewall | + | |
| - | That's all there is to it! | + | |