On Thu, Jan 30, 2014 at 10:18 AM, Thomas Glanzmann <thomas at glanzmann.de> wrote: > Hello Nikos, > I just wanted to let you know that AnyConnect now works with IPv6 like a > charm. Thank you for the fix. I'm currently using it. > Jan 30 10:13:16 infra ocserv[10334]: 85.154.119.84:50691 assigned IPv4 to 'sithglan': 10.12.12.155 > Jan 30 10:13:16 infra ocserv[10334]: 85.154.119.84:50691 assigned IPv6 to 'sithglan': 2a01:4f8:bb:5fd:0:a:c0c:9a01 > The problem with the MTU was really that I had set my mtu a long time ago on > Windows to 1400 and never changed it back. The reason for that was that a > customer side had MTU Discovery problems and I needed circumvent the bug. > I ran the following command to correct the MTU: > Start => cmd => Right click execute as administrator > netsh interface ipv4 set subinterface "Local Area Connection" mtu=1500 store=persistent It seems we arrived at the same conclusion independently :) I've also changed the way the MTU suggested by the client is taken into account, so that may improve things further. However, I am curious on how IPv6 is handled on the cisco equipment. Does it assign a single IP to the VPN client or does it send a subnet? regards, Nikos
