OpenConnect Package - AnyConnect Error

SteveM · January 29, 2026, 5:09pm

Hi Team. I’m trying out the OpenConnect package on a RUTX08 and this against a Cisco headend, so using AnyConnect as the profile. The connection fails and looks like it’s resolved in a later OpenConnect package - Got inappropriate HTTP CONNECT response: HTTP/1.1 401 Unauthorized - Cisco AnyConnect external authentication (SAML) when connecting to /CSCOSSLC/tunnel (#659) · Issues · OpenConnect VPN projects / OpenConnect · GitLab

”David Lähnemann
@dlaehnemann
20 Jan 2025
Thanks for resolving this. And for anybody waiting for a new release, here’s how to get the fix now:

While this is obviously different from a stable release, you could grab a build of the latest git master branch / latest git HEAD via the links provided here: OpenConnect VPN client.

This has just worked for me.”

Is there any way to update the OpenConnect package on the router to this later/patched version at all ?. Seems the installed version is 9.12-8 and there might be a 9.12-12 variant with this fix (or any latest version I guess).

Any pointers appreciated.

Matas · January 30, 2026, 9:10am

Hello,

You can install the newer package by utilizing Custom Feeds.

Access the device via SSH → Command Line Interfaces - Teltonika Networks Wiki
Edit the Custom Feeds file to contain the repository of the package by entering vi /etc/opkg/customfeeds.conf → Press “i” to start editing → Once done editing press ESC and write :wq
Lastly, use opkg update and opkg install <packagename> to install the updated package

Regards,
M.

SteveM · January 30, 2026, 12:56pm

Thanks @Matas - really appreciate the reply and will give it a try !. Take care.

SteveM · January 30, 2026, 3:05pm

OK, tried doing updates/different repos, etc and all in dependency hell .

’incompatible architecture’, etc for dependencies such as libxml2-16, etc.

Any idea if the OpenConnect package for RUTOS (and specifically RUTX08) will be updated at any point ?. This to allow connectivity to Cisco ASA/FTD headends as an AnyConnect client ? - seems fix is in later versions of OpenConnect in OpenWRT builds, etc.

Thanks in advance.

Matas · February 2, 2026, 7:33am

Hello,

Thanks for trying either way. I’ll inquire with our R&D whether there’s any possibility to update this package and will get back to you once I have more information.

Regards,
M.

Matas · February 2, 2026, 9:28am

Hi,

I’d like to request a few more details on your configuration & the errors:

Could you provide screenshots of your configuration from the end of Teltonika? Blur out any IP addresses or any other sensitive data.
Could you tell us whether any error messages appear, or simply the connection doesn’t even start?

Regards,
M.

SteveM · February 2, 2026, 1:08pm

Hi @Matas - basically error message is as described in the discussion link in the original post where the ‘fix’ was an updated OpenConnect package. The ‘Cookie was rejected by server’ error pointing to how OpenConnect presents itself as an AnyConnect client……the OpenConnect update providing an update to this mechanism.

Config is just a plain username/password combo and reference to the FQDN to the Cisco ASA headend.

No worries if there are no plans to update OpenConnect - I was just curious to see if I could use a RUTX08 as an AnyConnect hardware client, no expectations really.

Take care.

Matas · February 2, 2026, 1:21pm

Hi, Steve,

Thanks for getting back so quick, I’ve passed this information to our R&D - I’ll let you know if any updates occur.

Regards,
M.

Matas · February 9, 2026, 10:35am

Hi, Steve,

I’ve sent you a form to fill out so I can forward you a testing firmware & package for you to install and test out to see whether the issue has been resolved. In the Ticket ID field, fill it out with 17531

Regards,
M.

SteveM · February 10, 2026, 4:39pm

I’ve filled in the form @Matas - many thanks !

Matas · February 11, 2026, 6:44am

Yep, already sent you everything, will wait for a reply over there.

Regards,
M.

Matas · February 13, 2026, 9:08am

Hi, @SteveM ,

I can see you created a new form again, did you not receive my e-mail? I’ve sent you one on 10 Feb 2026 at 08:28 GMT+2 - it contains the test firmware & package. Could you perhaps check your spam folders & ensure that your company isn’t blocking emails from the outside?

Regards,
M.