Notice that traceroute sends UDP traffic so it will not match with the above access-list. R2Īccess-list 100 permit tcp any host 5.5.5.5 But what will happen to traffic that is not matched with the access-list? Will they be dropped? We will test this by replacing our access-list with an unmatched traffic like TCP. Verify the traffic has been matched with the access list:Īnd that is all of Policy Based Routing on this lab. We should also disable CEF routing so that you can see the detailed match (use “no ip cef” command in global config mode) We can turn on “debug ip policy” on R2 to have a closer look at the policy match. Now we will create a Policy Based Routing on R2 so that all traffic destined for 5.5.5.5 (R5 Loopback0) goes through R3: R2Īccess-list 100 permit ip any host 5.5.5.5 R1įastEthernet link has higher bandwidth (lower cost) than Serial link so traffic from R1 to R5 will surely go through R4 to R5: For R1 we only need a default route to R2. In the initial config we will configure IP addresses on all interfaces and run OSPF on R2, R3, R4, R5. You can download the Initial Config Lab here. + Create Policy Based Routing on R2 so that traffic from R1 to the Loopback interface of R5 (5.5.5.5) must go through R3 (the less optimal path). + Enable OSPF on all interfaces of R2, R3, R4, R5 using only one command on each router.
C3640 jk9s mz.124 16.bin for gns3 download how to#
In this lab we will learn how to use Policy Based Routing to send traffic via the route we want.
0 kommentar(er)
