POLICY BASED NAT HELP!
currently have an 1841 with an adsl interface going to the internet with a public static nat to 10.1.1.1 for the inside. Currently ALL traffic goes OUT of the D0 adsl interface which is becoming congested.
To alleviate the congestion a separate 2mb leased line is being brought online, but this has a different network to the ADSL line. I am going to connect the new leased line router to my existing 1841 by using the spare ethernet port on the 1841 & a crossover cable to the 1721 leased line router.
My issue is this.
I want to use Policy based routing to route both mail & PPTP traffic down the new leased line & all other traffic down the existing ADSL line.
HOW do I configure the NAT part of this, as I only have ONE inside address of 10.1.1.1 which ALREADY has a one to one nat for the ADSL?
I need some kind of policy based NAT for my pptp traffic & my SMTP traffic for the 10.1.1.1 address as well as leaving the existing Static nat which points to the adsl router.
Can this be done, or is it impossible?
I HAVE ALREADY LOOKED AT PBR LINKS ON THE CISCO SITE AND CANNOT FIND AN EXAMPLE!
To alleviate the congestion a separate 2mb leased line is being brought online, but this has a different network to the ADSL line. I am going to connect the new leased line router to my existing 1841 by using the spare ethernet port on the 1841 & a crossover cable to the 1721 leased line router.
My issue is this.
I want to use Policy based routing to route both mail & PPTP traffic down the new leased line & all other traffic down the existing ADSL line.
HOW do I configure the NAT part of this, as I only have ONE inside address of 10.1.1.1 which ALREADY has a one to one nat for the ADSL?
I need some kind of policy based NAT for my pptp traffic & my SMTP traffic for the 10.1.1.1 address as well as leaving the existing Static nat which points to the adsl router.
Can this be done, or is it impossible?
I HAVE ALREADY LOOKED AT PBR LINKS ON THE CISCO SITE AND CANNOT FIND AN EXAMPLE!
Comments
-
rossonieri#1
Member Posts: 799 ■■■□□□□□□□
hello,
never mind the old post,
do try this :
this will create an asymmetric route - receive in d0 and send on e1
assume your internal net is 10.10.10.0/24 on e0
outside : d0 10.10.11.1/24, e1 10.10.12.1/24
in global :
route-map <name> permit <tag>
match ip addr <acl#>
set ip next-hop <outgoing interface IP>
acl # permit SA DA eq <protocol>
! apply to your internal network server incoming interface
int e0
--> ip policy route-map <name>
sh ip pol
sh route-m
cheers
the More I know, that is more and More I dont know.