packages

History

Matthew Sykes f2fb6217ab openconnect: Restore support for vpnc-script hooks * Restore hooks support from vpnc-script * Use consistent style for tests and blocks in openconnect.sh * Cleanup code that writes banner to syslog Signed-off-by: Matthew Sykes <matthew.sykes@gmail.com>		2014-12-20 11:09:33 -05:00
..
files	openconnect: Restore support for vpnc-script hooks	2014-12-20 11:09:33 -05:00
patches	openconnect: added upstream patch for dynamic IPs	2014-12-05 20:01:32 +01:00
Config.in	openconnect: add an option to support stoken	2014-12-07 21:18:52 -08:00
Makefile	openconnect: add an option to support stoken	2014-12-07 21:18:52 -08:00
README	openconnect: add an option to support stoken	2014-12-07 21:18:52 -08:00

README

The openconnect client expects to be configured using the uci interface.

To setup a VPN connection, add the following to /etc/config/network:

config interface 'MYVPN'
        option _orig_ifname 'vpnc'
        option _orig_bridge 'false'
        option proto 'openconnect'
        option server 'vpn.example.com'
        option port '4443'
        option username 'test'
        option password 'secret'
        option serverhash 'AE7FF6A0426F0A0CD0A02EB9EC3C5066FAEB0B25'
        option token_mode 'rsa' # when built with stoken support
        option token_secret 'secret' # when built with stoken support

The additional files are also used:
/etc/openconnect/user-cert-vpn-MYVPN.pem: The user certificate
/etc/openconnect/user-key-vpn-MYVPN.pem: The user private key
/etc/openconnect/ca-vpn-MYVPN.pem: The CA certificate (instead of serverhash)

After these are setup you can initiate the VPN using "ifup MYVPN", and
deinitialize it using ifdown. You may also use the luci web interface
(Network -> Interfaces -> MYVPN Connect).

Note that you need to configure the firewall to allow communication between
the MYVPN interface and lan.


There is a luci plugin to allow configuring an openconnect interface from
the web environment; see the luci-protocol-openconnect package.