A user of openconnect-gp reported an unexpected response to the
Juniper "hostname packet"
(https://github.com/dlenski/openconnect/issues/113).
$ openconnect --juniper juniper.server.com --cookie="DSID=..."
...
> 0000: 19 00 00 04 00 00 00 0c 00 65 34 30 37 65 37 32
> 0010: 62 65 36 66 34 bb 01 00 00 00 00
Read 3 bytes of SSL record
< 0000: 00 00 01
Unexpected response of size 3 after hostname packet
The expected 3-byte response here is something like d2 01 00, where
the first two bytes indicate the length of the subsequent routing
configuration packet (0x01d2) and the third byte indicates status (0
means success).
The response here indicates some kind of error (length 0, status 1),
and I've never seen it on a real Juniper server before.
Has anyone encountered this? Is there some version of the Juniper
NC/Pulse server which is known to be intolerant of the "hostname
packet" as sent by openconnect? Any workarounds?
Thanks,
Dan
ps- This issue is *not* the same as the one wherein some versions of
Juniper concatenate the 3-byte response and the following
configuration packet, which I already submitted a patch for and which
is David merged in:
http://git.infradead.org/users/dwmw2/openconnect.git/commitdiff/342a85bf8b49165dddeb679a1d4abd55afca89e3
_______________________________________________
openconnect-devel mailing list
openconnect-devel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/openconnect-devel
