policy routing using route maps

aueddonline

I'm trying to get telnet traffic from 10.1.3.1 which is on a directly connected subnet of R4 s0/0 going to 5.5.5.5 to be policy routed to next hop address 10.0.0.3 using a route map, config below. My guess is my ACL might be screwed,

this is appiled to s0/0 using ' ip policy route-map cloud'

R4_2691#show route-map
route-map cloud, permit, sequence 10
Match clauses:
ip address (access-lists): cloud
Set clauses:
ip next-hop 10.0.0.3
Policy routing matches: 0 packets, 0 bytes

R4_2691#show access-list
Extended IP access list cloud
10 permit tcp host 10.1.3.1 eq telnet host 5.5.5.5 gt 1023

mikej412

If you're telneting from 10.1.3.1 to 5.5.5.5 -- it's 5.5.5.5 that will be listening on port 23 for a telnet connection.

Your source port will start off on a random high port number, but the request has to go to port 23. After the connection, 5.5.5.5 if it accepts it, will respond with it's own random high port number that 10.1.3.1 should use for the connection.

aueddonline

cool so just need to switch the ports round on the ACL

aueddonline

route-map cloud, permit, sequence 10
Match clauses:
ip address (access-lists): cloud
Set clauses:
ip next-hop 10.0.0.3
Policy routing matches: 55 packets, 2509 bytes


hey i'm match packets thanks mike

aueddonline

*Mar 1 03:20:02.363: IP: s=11.0.2.1 (Serial0/0), d=2.2.2.2, len 100, FIB policy rejected - normal forwarding
*Mar 1 03:20:03.059: IP: s=11.0.2.1 (Serial0/0), d=2.2.2.2, len 100, FIB policy match
*Mar 1 03:20:03.059: IP: s=11.0.2.1 (Serial0/0), d=2.2.2.2, len 100, FIB policy rejected - normal forwarding
*Mar 1 03:20:03.067: IP: s=11.0.2.1 (Serial0/0), d=2.2.2.2, len 100, FIB policy match
*Mar 1 03:20:03.067: IP: s=11.0.2.1 (Serial0/0), d=2.2.2.2, len 100, FIB policy rejected - normal forwarding
*Mar 1 03:20:03.071: IP: s=11.0.2.1 (Serial0/0), d=2.2.2.2, len 100, FIB policy match
*Mar 1 03:20:03.071: IP: s=11.0.2.1 (Serial0/0), d=2.2.2.2, len 100, FIB policy rejected - normal forwarding
*Mar 1 03:20:03.079: IP: s=11.0.2.1 (Serial0/0), d=2.2.2.2, len 100, FIB policy match
*Mar 1 03:20:03.079: IP: s=11.0.2.1 (Serial0/0), d=2.2.2.2, len 100, FIB policy rejected - normal forwarding


this is a different policy, but does the debug suggest that only half of the packets are having the policy applied?