Also as usual, the criteria for the access list is subject to interpretation. One solution is to
filter packets sent from hosts on the Ethernet off R3, filtering them as they enter R1, on
either of R1's serial interfaces. By filtering packets in only one direction, applications that
require a two-way flow will not successfully communicate. By filtering on both of R1's
serial interfaces for inbound traffic, any valid route for the incoming packets will be
checked.
adding the SAP for Server 2 to its SAP table, R2 will never advertise that server in a GNS
request, nor will Server 3 learn about Server 2's SAPs from R2's SAP updates. So, the
plan is to place incoming SAP filters on both serial interfaces on R2, to filter Server 2 from
being added to R2's SAP table.
solutions for Part A of Scenario 9-1 to direct you in identifying IP and IPX addresses and
determining the logic behind the access lists. For Scenario 9-1, Part B, perform the following
tasks:
design.
encapsulation elsewhere.