What are the pro/cons to using Easyvpn in network-extention mode with split-tunneling as opposed to using a regular site-to-site vpn connection. We have about 70 remote offices with Pix 501s already setup with site-to-site and will be replaceing the 501's with 887 routers. Now the question should we go to easyvpn on these new routers back to our hub ASA or stay site-to-site? Any info or experiences with this type of conversion would be appreciated.
EZVPNs allow easier provisioning on the client side, as the policy can be 'controlled' from the server head-end. Also the EZVPN client has a auto-connect option, making it more seamless (with regards to connectivity).
When the EZVPN client will connect, it will propose various security policies to the server, so the EZVPN server can choose the Phase1/2 policies. IN a L2L VPN (Direct Encapsulation) both sides need to define the same policy (Manually). The downside is that EZVPN is a Cisco Proprietary technology! If you ever want to phase out the Cisco hardware, you need to re-do the whole thing.
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...