]> www.infradead.org Git - users/dwmw2/openconnect.git/commit
For Pulse, send ESP only of the same IP protocol as we're connected over
authorDavid Woodhouse <dwmw2@infradead.org>
Tue, 16 Jul 2019 10:37:59 +0000 (11:37 +0100)
committerDavid Woodhouse <dwmw2@infradead.org>
Tue, 16 Jul 2019 10:37:59 +0000 (11:37 +0100)
commitb4f50f8bd5da7e6ac926ddd5095501edbc204cd0
tree9769995b8dd81f6415dd70bed71a18171123babc
parent59d1622992aaec2955a6775235e275967724261b
For Pulse, send ESP only of the same IP protocol as we're connected over

It really seems that when we're connected over Legacy IP, it only accepts
Legacy IP packets in ESP. And when we're connected over IPv6, it only
accepts IPv6 packets in ESP.

This matches the behaviour of the Windows client too.

If you connect to a NC server over IPv6 it doesn't even offer the ESP
config (since NC doesn't support IPv6 within the tunnel).

Someone really ought to report this bug to Pulse. For IPv6 VPN traffic
to be forced into TCP-over-TCP mode when you happen to be connected to
the VPN over Legacy IP is very bad.

Signed-off-by: David Woodhouse <dwmw2@infradead.org>
esp.c
mainloop.c
oncp.c