2106 and VPN connection

[jmglass]

Hi,

Test setup for AP 1142 and 5.2.178.0, have a 2106 running 5.2.178.0 with 1142 with two WLANs. Working OK but for VPN connections. See PPTP control messages between wireless client and VPN server up to the (Set-Link-Info), nothing after this from client off the 2106. On 4404s running 4.2.176.0, VPN works OK, see after the (Set-Link-Info) the GRE v1 tunnel being setup correctly.

Trying to verify this is a limitation of the 2106, not version 5.2.178.0? Release notes for 2106 say no support for (VPN termination such as IPsec and L2TP) but this seems to mean the 2106 is the end point, not just passing the connection?

thanks!!

jim

[jmglass]

FYI

~Works: 2106 running 4.2.176.0 with AP-1252, both VPNs work OK on both WLANs

~Works: 2106 running 5.1.163.0 with AP-1252, both VPNs work OK on both WLANs

~Not Working: 2106 running 5.2.157.0 with AP-1252 or AP-1142, neither VPN on either WLAN

~Not Working: 2106 running 5.2.178.0 with AP-1252 or AP-1142, neither VPN on either WLAN

One change between 5.1.163 and 5.2.157 is /Control and Provisioning of Wireless Access Points/ (CAPWAP).

Reading some about this it talks about Layer 3 Mobility "Mobile IP", RFC 3344 which uses GRE encapsulation.

Not sure if this is effecting the VPN tunnel setup.

I upgraded one of our 4404s to 5.2.178.0 and test our VPN connections successfully off AP-1142 and AP-1252s for both WLANs we have configured.

Not sure why I could not get the 2106 to pass our Microsoft VPNs connections but it really does not matter now since I know the 4404s will work.

[f-persson]

We have 2 controllers, 2106 and 2112, both running 5.2.178.0 and have the same problem with PPTP. Is there a solution to this or do we have to downgrade to get it working?

[jmglass]

I never got to the bottom of it. Cisco TAC guys helping me said Cisco VPN client worked fine in their lab testing, they did not have a MicroSoft VPN server to test with so no help for our setup. Must be something with the 21nn line, the 4404 I tested worked OK. The 2106 I had was just a demo unit, our production is 4404s so I left it go after testing OK on a 4404.

jim

[f-persson]

I got this confirmed from Cisco, it's a known bug in 5.2 software, se bug id CSCsx20559

[jmglass]

Thanks, good to know!

jim