Before I get too much flack ... Ya I know 2621? But that is what I have to work with.
I can bring up the far end which is a sonic wall fw. I am almost postive that it is a nat issue and the device does not know to push the interesting traffic through the tunnel ...
I have tried the following nat:
ip nat inside source list 125 interface Ethernet0/0 overload (e0/0 being the outside interface)
Entry 125:
access-list 125 permit ip 172.10.1.0 0.0.0.255(Inside) 172.20.1.0 0.0.0.255(remote inside)
AND:
access-list 130 deny ip 172.10.1.0 0.0.0.255 208.91.230.0 0.0.0.255
access-list 130 permit ip 172.10.1.0 0.0.0.255 any
!
route-map nonat permit 10
match ip address 130
Thanks!!!!
When I perform a traceroute I get the next hop into my isp
Phase 2 stats:
All send errors