Thanks for replying yurisk.
The route tables show nothing on the Local Lan side (left), and 192.168.0.0 255.255.255.0 on the right, which is my internal network.
I thought my: access-list inside_nat0_outbound extended permit ip 192.168.0.0 255.255.255.0 192.168.2.0 255.255.255.0 took care of that.
I will make the access-list AAATunnelACL an extended one. Do I have to use the word "extended" when using the CLI - I noticed your example says "standard" but you mentioned making it "extended"
I have used the sysopt command in previous attempts, but it didn't solve anything. I will add it to my current config though.
Main Topics
Browse All Topics





by: yuriskPosted on 2008-10-24 at 05:55:23ID: 22795680
When connected what do you see in Routes Tab of the VPn client Statistics ?
ROutes that client gets once connected are defined by
access-list AAATunnel_splitTunnelAcl standard permit 192.168.0.0 255.255.255.0
Can you make this ACL an extended one, listing both source and destination ?
access-list AAATunnel_splitTunnelAcl standard permit 192.168.0.0 255.255.255.0 192.168.2.0 255.255.255.0
The second part of the question regarding the ACL that may block the IPsec traffic, 1st ACL applied is
only for traffic coming inbound from outside, and as long as you can connect successfully shouldn't
be a problem. To make sure you can always try (config) sysopt permit ipsec To circumvent any ACL
for IPsec raffic only. But seems more like route issue.