The expectation with EZVPN client to server is that the client is using a default route pointing out the interface to the internet. Thus by default that default route will send the traffic out and the affected traffic will be matched. If you are not using a default route on the client for traffic then you need to add something to send the traffic out the interface.
Regards, Tyson Scott - CCIE #13513 R&S, Security, and SP Managing Partner / Sr. Instructor - IPexpert, Inc. Mailto: [email protected] Telephone: +1.810.326.1444, ext. 208 Live Assistance, Please visit: www.ipexpert.com/chat eFax: +1.810.454.0130 IPexpert is a premier provider of Self-Study Workbooks, Video on Demand, Audio Tools, Online Hardware Rental and Classroom Training for the Cisco CCIE (R&S, Voice, Security & Service Provider) certification(s) with training locations throughout the United States, Europe, South Asia and Australia. Be sure to visit our online communities at www.ipexpert.com/communities and our public website at www.ipexpert.com <http://www.ipexpert.com/> From: [email protected] [mailto:[email protected]] On Behalf Of Vybhav Ramachandran Sent: Monday, July 26, 2010 10:34 AM To: Kingsley Charles; OSL Security Subject: Re: [OSL | CCIE_Security] Legacy EzVPN routing traffic Yep.. after adding the static route on the client , i did a #ping <server's subnet> source loopback10000 and i could see the counters increasing.
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
