gateguard
asked on
route-map nonat permit 10 ?
What is this command doing?
route-map nonat permit 10
route-map nonat permit 10
gateguard,
! * Use a route map to define which traffic from the private
! * network should be included in the NAT process:
route-map nonat permit 10
match ip address 150
http://www.siliconvalleyccie.com/cisco-hn/vpn-cisco.htm
PL
! * Use a route map to define which traffic from the private
! * network should be included in the NAT process:
route-map nonat permit 10
match ip address 150
http://www.siliconvalleyccie.com/cisco-hn/vpn-cisco.htm
PL
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
That looks like a line in a VPN router config. If so, there should be a corresponding line that says something like '
ip nat inside source route-map nonat interface Ethernet0 overload '
Basically, it differentiates VPN 'interesting traffic' from traffic bound for the Internet. As Pete shows, it should be followed by a match ip address line that you can line up with an access list line (such as 'access-list 150 permit ip 10.10.130.0 0.0.0.255 10.10.0.0 0.0.255.255'). Whatever is in the access list is enacted on the traffic heading to the Internet.
So, if you had this in your config:
ip nat inside source route-map nonat interface Ethernet0 overload
route-map nonat permit 10
match ip address 150
access-list 150 deny ip 10.10.130.0 0.0.0.255 10.10.0.0 0.0.255.255
access-list 150 permit ip 10.10.130.0 0.0.0.255 any
All traffic from 10.10.130.0 destined for 10.10.0.0 would be denied access to the Internet.
All traffic from 10.10.130.0 destined for anywhere else would be allowed out to the Internet. (And NATted.)
I *believe* that the 10 reference speaks to the number you used for your crypto isakmp policy, but I'm not sure.
ip nat inside source route-map nonat interface Ethernet0 overload '
Basically, it differentiates VPN 'interesting traffic' from traffic bound for the Internet. As Pete shows, it should be followed by a match ip address line that you can line up with an access list line (such as 'access-list 150 permit ip 10.10.130.0 0.0.0.255 10.10.0.0 0.0.255.255'). Whatever is in the access list is enacted on the traffic heading to the Internet.
So, if you had this in your config:
ip nat inside source route-map nonat interface Ethernet0 overload
route-map nonat permit 10
match ip address 150
access-list 150 deny ip 10.10.130.0 0.0.0.255 10.10.0.0 0.0.255.255
access-list 150 permit ip 10.10.130.0 0.0.0.255 any
All traffic from 10.10.130.0 destined for 10.10.0.0 would be denied access to the Internet.
All traffic from 10.10.130.0 destined for anywhere else would be allowed out to the Internet. (And NATted.)
I *believe* that the 10 reference speaks to the number you used for your crypto isakmp policy, but I'm not sure.
See Irmoores comments here http://oldlook.experts-exchange.com/questions/20705266/VPN-setup-between-3620-and-2621-many-questions.html
PeteL