On Wed, 11 Jun 2025 16:05:36 +0200
Martin Pauly <pa...@hrz.uni-marburg.de> wrote:
> The reason I would like CLI on Windows may sound a bit strange:
> This time, I would like to replace the whole Pre-Login
> VPN connection with an openconnect one.
I have only a thought, based on my experience, to offer.
It will be a easier to work entirely from the command line
than try to go through a gui. (Unless you're just using
the gui to come up with the initial openconnect command
to try, and then you'll add more options to reveal
more debugging information.
(I too recall a documentation page for cisco, but haven't
tried to find it. I last used just -u and --authgroup,
and also --script to vpnc-script-sshd because I want
the vpn in a separate network namespace. There
may be no way to do the latter on MS Windows.)
A second thought would be to debug on Linux, and use
what you learn to make MS Windows work. Life is fraught....
Regards,
Karl <k...@karlpinc.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
_______________________________________________
openconnect-devel mailing list
openconnect-devel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/openconnect-devel
