GUI vs Command-line Connect Tunnel Client Capabilities
Description
GUI vs Command-line Connect Tunnel Client Capabilities
Resolution
Topic:
This KB item will describe the capabilities of the Connect Tunnel client when run in either graphical mode (GUI), or via the command line (CLI).
Â
| Â | End Point Control | Certificate authentication (PKI) | Advanced Authentication through Logon Service | Post-connection scripting | Network precedence | Customizable client-side configuration file | Automatic sotware updating |
| Linux - CLI (startct) | No | No | No | No | Yes (see note b) | No | No |
| Linux - GUI (startctui) | Yes (see note a) | Yes (see note a) | Yes (see note a) | Yes (see note a) | Yes (see note b) | No | Yes (see note a) |
| Mac - CLI (startct.sh) | No | No | No | No | Yes (see note b) | No | No |
| Mac - GUI (Aventail Connect.app) | Yes (see note a) | Yes (see note a) | Yes (see note a) | Yes (see note a) | Yes (see note b) | No | Yes (see note a) |
| Windows - CLI (ngdial) | Yes | No (see note d) | Yes | Yes | Yes (see note b) | Yes | Yes (see note c) |
| Windows - GUI | Yes | Yes | Yes | Yes | Yes (see note b) | Yes | Yes |
Notes:
a) This feature only supported on version 10.0.0 and later.
b) This feature was added in version 9.0.0.
c) Windows software updating will work when client displays GUI to end user.
d) You can invoke Connect Tunnel with ngdial when using PKI, but you cannot specify the user's certificate from the command line. You still have to select the user certificate via the GUI.
Related Articles
Categories
not finding your answers?