102 remark <[ Company-2 Network Now let's revisit our pseudocode and update it with router configuration information: IF {the source network is 10.109.0.0/24 (int Fo/o) AND the destination is 10.201.0.0/24 (ACL 102) } THEN send the packet out interface So/0.109 IF {the source network is 10.209.0.0/24 (int F0/1) AND the destination is 10.101.0.0/24 (ACL 101)} THEN send the packet out interface SO/0.209 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 Chapter 14: Route Maps 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 link: route-map Company-1 permit 10 match ip address 102 set interface Serial0/0.109 The second forced traffic destined for Company 2's HQ network over Company 2's link: route-map Company- permit 10 match ip address 101 set interface Serial0/0.209 In this example, the source-network part of our pseudocode is matched by applying our route map to the interface attached to the network in question. We do this with the ip policy interface command. We used some fall-through logic here. We knew that Company 1's users' packets headed to Company 1's headquarters would route properly without alteration, as would Company 2's users' packets headed to Company 2's headquarters. The only time we needed to interfere was when either company's users accessed a server at the other company's headquarters-then, and only then, we needed to force the packets to take the other link. To accomplish this, we applied the Company 2 route map to the Company 1 Ethernet interface, and vice versa. We did this on the Branch #9 router: interface FastEtherneto/o description Company-1 Users ]> ip address 10.109.0.1 255.255.255.0 ip policy route-map Company-1 half-duplex interface FastEtherneto/1 description <[ Company-2 Users ]> ip address 10.209.0.1 255.255.255.0 ip policy route-map Company-2 half-duplex Polic