two directions will succeed in stopping users from actually connecting to the servers. For the
first set of criteria, an access list stopping packets from entering the serial interface of R1, thus
stopping packets destined to PC11 and PC12, will suffice. For the second criteria to disallow
traffic between Site 2 and Site 3, the access lists are also placed in R1. The access lists will stop
the packets earlier in their life if they are placed in R2 and R3, but the traffic will be minimal
because no true application traffic will ever successfully be generated between IP hosts at Sites
2 and 3.
subinterfaces on R1's S0 interface. Other options are valid as well.
filter is added on R2 to filter Server 3 from the SAP table. The filter could filter incoming SAPs
on R2's E0 or filter outgoing SAP updates out R2's S0 port. In this case, anticipating the day
that a second Ethernet port is used on R2, and anticipating the fact that the objective probably
meant that local clients should have access to Server 3, the plan in this case is to filter outbound
SAPs on R2's S0 interface.
calculate the broadcast address, you should write down the subnet number in binary. Then copy
down the network and subnet portions of the subnet number directly below it, leaving the host
bit positions empty. Then write all binary 1s in the host bit positions. Finally, convert the
number back to decimal, 8 bits at a time. The result is the subnet broadcast address and is the
high end of the range of assignable addresses in that subnet.
broadcast addresses, and the range of valid assignable IP addresses.
(Last 2 Bytes)