Error messages / traceroute

[David Woodhouse]

On Mon, 2010-02-22 at 12:11 +0100, Johannes Becker wrote:
> if you use the option --script, openconnect doesn't complain if
>    the script file doesn't exist
> or if
>   the script file is not executable

I think those are fixed in v2.21 by this commit:
http://git.infradead.org/users/dwmw2/openconnect.git/commitdiff/392494b4

> or if 
>   you misspell  --script as -script.

Hm, the '-s' option is an alias for the --script option. So '-script' is
equivalent to '-s cript' or '--script=cript'. Perhaps a warning message
if !strcmp(vpninfo->vpnc_script, "cript") might be helpful? :)

> traceroute doesn't work while the tunnel is set up. (Not
> really important for me.)

It should; that sounds like perhaps something on your end has broken
firewalling rules set up -- are outbound UDP or incoming ICMP packets
getting stopped?

> I didn't find an explanation how to use openconnect with
> network-manager. I guess network-manager-openconnect
> doesn't support user/passord authentication at the moment.

It supports everything that we support from the command line. After
installing the openconnect and NetworkManager-openconnect packages, just
use the NM configuration tool to add a VPN of the appropriate type, and
it should all be fairly simple.

-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse at intel.com                              Intel Corporation