inate from; the routing protocol simply provides the best path to the destination networks. With route maps and policy routing, we were able to change that. Chapter 14: Route Maps The configuration for the Ethernet links on Branch-9 is simple (I've removed the access lists that prevent inter-Ethernet communication to avoid any confusion, as these ACLs are not germane to this discussion): interface FastEtherneto/o ip address 10.109.0.1 255.255.255.0 interface FastEtherneto/1 ip address 10.209.0.1 255.255.255.0 What we had to do was add a policy map on each Ethernet interface that told the router to alter the next hop of each packet sent to the HQ offices, based on the source address contained in the packet. First, we had to define our route maps. The logic for the route maps is shown in this snippet of pseudocode: If the source network is 10.109.0.0/24 and the destination is 10.101.0.0/24 Then send the packet out interface So/0.109 If the source network is 10.209.0.0/24 and the destination is 10.201.0.0/24 Then send the packet out interface So/0.209 In route map terms, we needed to match the destination address of the packet and then set the next hop. These route maps would then be applied to the input inter- faces to accomplish our goal. To match IP addresses in route maps, you need to specify and include access lists. We made two access lists to match the destination networks. Access list 101 matched the 10.101.0.0/24 network (Company 1), and access list 102 matched the 10.201.0.0/24 network (Company 2): access-list 101 permit ip any 10.101.0.0 0.0.0.255 access-list 101 remark <[ Company-1 Network ]> access-list 102 permit ip any 10.201.0.00.0.0.255 access-list 102 remark <[ Company-2 Network With the destination networks defined, we were able to create route map clauses to match against them. After matching the destination network, we needed to change the interface to which the packet would switch within the router. The first route map forced packets destined for Company 1's HQ network to go across Company 1's 