2 <VAR match="VAR_ORIGIN" replace="" />
3 <VAR match="VAR_CVSID" replace=""/>
5 <INCLUDE file="inc/header.tmpl" />
7 <VAR match="VAR_SEL_INDEX" replace="selected" />
8 <VAR match="VAR_SEL_PLATFORMS" replace="selected" />
9 <PARSE file="menu1.xml" />
10 <PARSE file="menu2.xml" />
12 <INCLUDE file="inc/content.tmpl" />
14 <h1>Supported Platforms</h1>
16 <p>OpenConnect is known to work, with both IPv6 and Legacy IP, on Linux
17 (including Android), OpenBSD, FreeBSD (including Debian GNU/kFreeBSD), NetBSD, DragonFly BSD,
18 OpenIndiana/OpenSolaris, Solaris 10/11 and Mac OS X platforms, and should be trivially
19 portable to any other platform supporting
20 <a href="http://en.wikipedia.org/wiki/TUN/TAP">TUN/TAP</a>devices and
21 on which <a href="http://www.openssl.org/">OpenSSL</a> runs.</p>
23 <p>For Solaris support, and for IPv6 on any platform, the
24 <tt>vpnc-script</tt> shipped with vpnc itself (as of v0.5.3)
25 is not sufficient. It is necessary to use the script from my <a
26 href="http://git.infradead.org/users/dwmw2/vpnc-scripts.git">vpnc-scripts</a>
27 repository instead.</p>
30 It is known to work on at least i386, x86_64, PowerPC and MIPS
31 processors, and should not have issues with portability to other CPUs.</p>
32 <p>Note that 'Cisco Secure Desktop' support may require the ability to run Linux/i386 binaries; see the <a href="csd.html">CSD page</a>.</p>
36 Platform support for new UNIX systems is relatively simple to add
37 — most of the difference is in the TUN/TAP device handling, and
38 the major variants of that are already supported.</p>
40 A port to Windows should be fairly simple, since a TUN/TAP driver
41 exists for Windows and Cygwin should make the basic port work OK.</p>
43 A port to Symbian, to provide VPN connectivity on phone handsets,
44 would be very useful. Any volunteers?</p>
47 <INCLUDE file="inc/footer.tmpl" />