Differences

This shows you the differences between two versions of the page.

Link to this comparison view

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 vgaeteradocs: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.  (GlobalProtect mode is new in OpenConnect 8.0 and is not yet fully integrated into OpenWrt).  A companion VPN server ''ocserv'' which implements the AnyConnect protocol is also available for OpenWrt.  The rest of this page describes the ocserv server.  To set up an OpenConnect client, see [[docs:guide-user:services:vpn:openconnect:client]]+{{section>meta:infobox:howto_links#basic_skills&noheader&nofooter&noeditbutton}}
  
-This is a beginner's guide to setting up OpenConnect as a SERVICE (ocserv) on OpenWRT for use with a client running either the OpenConnect client or Cisco's Anyconnect.+===== Introduction ===== 
 +  * This how-to describes the method for setting up [[wp>OpenConnect|OpenConnect]] server on OpenWrt. 
 +  * Follow [[docs:guide-user:services:vpn:openconnect:client|OpenConnect client]] for client setup and [[docs:guide-user:services:vpn:openconnect:extras|OpenConnect extras]] for additional tuning.
  
-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://github.com/openwrt/packages/tree/master/net/ocserv|here]] did NOT WORK for me, and it seemed like there is an easier, more elegant solution as described in the [[http://www.infradead.org/ocserv/recipes-ocserv-pseudo-bridge.html|OpenConnect documentation on Pseudo-Bridging]].+===== Goals ===== 
 +{{section>docs:guide-user:services:vpn:wireguard:server#goals&noheader&nofooter&noeditbutton}}
  
-For an overview of all VPN-related articles (including other VPN technologies), see [[docs:guide-user:services:vpn:overview]].+===== Command-line instructions ===== 
 +==== 1. Preparation ==== 
 +Install the required packages. 
 +Specify configuration parameters for VPN server.
  
-===== Use Case (the beginner's configuration) ===== +<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, or access their private network.+# 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="4443" 
 +VPN_POOL="192.168.7.0 255.255.255.0" 
 +VPN_DNS="${VPN_POOL%.* *}.1" 
 +VPN_USER="USERNAME" 
 +VPN_PASS="PASSWORD" 
 +</code>
  
-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 insecureYou cannot, for example, secure your traffic from a public hotspot using a split tunnel since your banking traffic will go through the PUBLIC hotspot and not through your VPN tunnel.+==== 2Key management ==== 
 +Generate password hash for VPN client.
  
-===== Why use OpenConnect ===== +<code bash> 
-  * Your network provider is BLOCKING IPSEC trafficThis is apparently POLICY for mobile carriers, though they deny it. OpenConnect is SSL. +# Generate password hash 
-  Your client only supports AnyConnect or the OpenConnect Client. (Blackberry, for example, does not support OpenVPN). +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 "/^${VPN_USER}:.*:/s///p" /etc/ocserv/ocpasswd)" 
 +</code>
  
-[[http://www.infradead.org/openconnect/|OpenConnect official site]]+==== 3Firewall ==== 
 +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:pkgdata:ocserv]] + [[packages:pkgdata:luci-app-ocserv]]+# Configure firewall 
 +uci rename firewall.@zone[0]="lan" 
 +uci rename firewall.@zone[1]="wan" 
 +uci del_list firewall.lan.device="vpns+" 
 +uci add_list firewall.lan.device="vpns+" 
 +uci -q delete firewall.oc 
 +uci set firewall.oc="rule" 
 +uci set firewall.oc.name="Allow-OpenConnect" 
 +uci set firewall.oc.src="wan" 
 +uci set firewall.oc.dest_port="4443" 
 +uci set firewall.oc.proto="tcp udp" 
 +uci set firewall.oc.target="ACCEPT" 
 +uci commit firewall 
 +/etc/init.d/firewall restart 
 +</code>
  
-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://www.infradead.org/ocserv/recipes-ocserv-pseudo-bridge.html|recipe: ocserv pseudo bridge]].+==== 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="${VPN_PORT}" 
 +uci set ocserv.config.ipaddr="${VPN_POOL% *}" 
 +uci set ocserv.config.netmask="${VPN_POOL#* }" 
 +uci -q delete ocserv.@routes[0] 
 +uci -q delete ocserv.@dns[0] 
 +uci set ocserv.dns="dns" 
 +uci set ocserv.dns.ip="${VPN_DNS}" 
 +uci -q delete ocserv.@ocservusers[0] 
 +uci set ocserv.client="ocservusers" 
 +uci set ocserv.client.name="${VPN_USER}" 
 +uci set ocserv.client.password="${VPN_HASH}" 
 +uci commit ocserv 
 +/etc/init.d/ocserv restart 
 +</code>
  
-1) Edit /etc/config/ocserv as follows, or use LUCI: +===== Testing ===== 
-      config ocserv 'config' +{{section>docs:guide-user:services:vpn:wireguard:server#testing&noheader&nofooter&noeditbutton}}
-           option enable '1'                                          +
-           option port '443'                                          +
-           option netmask '255.255.255.253'                           +
-           option ipaddr '192.168.1.100'                             +
-           option zone 'lan'           +
-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. +
-   NOTEthe 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+
  
-       config dns                                                         +===== Troubleshooting ===== 
-           option ip '192.168.1.1'      +Collect and analyze the following information.
-      +
-3) Edit /etc/config/firewall or use LUCI and add the following rules: +
-    config rule                       +
-        option name 'Allow SSL vpn in (tcp)' +
-        option src 'wan'                     +
-        option proto 'tcp'                   +
-        option dest_port '443'               +
-        option target 'ACCEPT'               +
-                                             +
-    config rule                                  +
-        option name 'Allow SSL vpn in (udp)' +
-        option src 'wan'                     +
-        option proto 'udp'                   +
-        option dest_port '443'               +
-        option target 'ACCEPT'     +
-         +
-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; /etc/init.d/ocserv restart; sleep 10
  
-    iptables -A input_rule -i vpns+ -j ACCEPT +# Log and status 
-    iptables -A forwarding_rule -i vpns+ -j ACCEPT +logread -e ocserv; netstat ---p | grep -e ocserv
-    iptables -A forwarding_rule -o vpns+ -j ACCEPT +
-    iptables -A output_rule -o vpns+ -j ACCEPT+
  
-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 configuration 
-5) Edit /etc/sysctl.conf and add the following line: +uci show network; uci show firewall; uci show ocserv 
-     net.ipv4.conf.all.proxy_arp=1 +</code>
- +
-Then type sysctl -p to reload the configuration file. The purpose is described in the recipe above. +
- +
-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 service and fire up the openconnect server to test it out. +
-That's all there is to it!+
  
  • Last modified: 2024/10/17 17:27
  • by andrewz