Unexpected Pulse config packet (server version 9.1R16)
A Pulse appliance to which I was connecting regularly, suddenly stopped working. A bit of poking revealed they have upgraded the appliance just yesterday, presumably to the latest version as it now features the Ivanti logo.
Symptoms:
- connecting using
--protocol=nc
looks to work, the connection is established and I get routes pushed and nameservers set, but no traffic is flowing through the tunnel (I wasn't actively using the nc protocol before, I just tried it now as a fallback, may have been broken before the upgrade) - connecting using
--protocol=pulse
yields "Unexpected Pulse config packet" with a dump of the packet (full, somewhat anonimised, error attached as error.txt, I'm happy to provide unmangled output out of band)
I'm running openconnect 9.01 from Arch, but a fresh build from the master
branch does the same.
Pointers welcome!
Edited by Daniel Lenski