pMTU discovery

[berni at birkenwald.de (Bernhard Schmidt)]

On 08.06.2012 14:02, David Woodhouse wrote:

Hello David,

>> we're currently testing OpenConnect 3.20 against our new shiny ASA Beta
>> which finally does IPv6 transport. However, when we do use that, we have
>> MTU problems on the link. The official AnyConnect client works fine.
>
> It'd be very interesting to know where the Cisco client gets its numbers
> from. How does this compare?

Since that patch doesn't apply to 3.20 I tried HEAD, but it fails to 
compile.

make[2]: Leaving directory `/tmp/buildd/openconnect-3.20+git20120608.1/po'
make[2]: Entering directory `/tmp/buildd/openconnect-3.20+git20120608.1'
   CC     libopenconnect_la-version.lo
   CC     libopenconnect_la-ssl.lo
   CC     libopenconnect_la-http.lo
   CC     libopenconnect_la-auth.lo
   CC     libopenconnect_la-library.lo
   CC     libopenconnect_la-compat.lo
   CC     libopenconnect_la-openssl.lo
   CCLD   libopenconnect.la
   CC     openconnect-xml.o
   CC     openconnect-main.o
main.c: In function 'main':
main.c:400:123: error: 'openconnect_binary_version' undeclared (first 
use in this function)
main.c:400:123: note: each undeclared identifier is reported only once 
for each function it appears in
main.c:400:266: warning: left-hand operand of comma expression has no 
effect [-Wunused-value]
main.c:400:1985: warning: left-hand operand of comma expression has no 
effect [-Wunused-value]
make[2]: *** [openconnect-main.o] Error 1
make[2]: Leaving directory `/tmp/buildd/openconnect-3.20+git20120608.1'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/buildd/openconnect-3.20+git20120608.1'
dh_auto_build: make -j1 returned exit code 2


Bernhard