cisco ccna 200-301 volume 1

cisco ccna 200-301 volume 1.Note that there is an additional problem when using standard ACLs: all traffic from 192.168.5.1 leaving interface E0 is discarded. As a result, that user cannot access not only the server, but also other devices in that segment. Another problem with using standard ACLs is that they are not very network friendly since they are usually placed as close as possible to the target device: by the time the packet is almost ready to reach the targettarget device before dropping them. This wastes network bandwidth, especially when the source device sends a lot of traffic to the target device.192.168.5.0Figure 21.1 Location of ACLs21.4.2 Extending ACLsFor the previous example, it is much better to place the ACL as close to the source device as possible to avoid traffic crossing almost the entire network before it is dropped. However, with a standard ACL, this would prevent users from accessing most of the resources in the network.However, extended ACLs have no such limitations, as they are able to filter based on the source and destination addresses in the IP packet headers. With this in mind, it is recommended that extended ACLs be placed as close to the source device as possible to prohibit unwanted traffic from traveling through the network. Extended ACLs can filter based on both source and destination IP addresses, so use them to both prohibit the source device from accessing a specific destination device and to allow it to access other devices.For the previous example, the configuration is similar to the following when using extended ACLs.Router(config)# access-list 100 deny ip host 192.168.5.1host 192.168.1.1