ccna collaboration 210-060 book

ccna collaboration 210-060 book.R3 (config-router)#no auto-summary R3(config-router)#network 172.16.0.0 R3(config-router)#passive-interface GigabitEthernetO/O R3(config- router)#exitChapter 9 ACLs .119 .R3(config)#access-Ust 2 remark ONLY HOST PCI CAN TELNET R3(config)#access-list 2 permit host 172.16.1.100 R3(config)#access-list 1 remark DENY NETWORK 172.16.2.0 FROM R1 R3(config)#access-list 1 deny 172.16.2.0 0.0.0.255 log R3(config)#access-list 1 permit any According to the principle that standard IPv4 ACLs should be close to the destination, define an IPv4 ACL on R3 R3(config)#interface gigabitEthernet0/0 R3(config-if)#ip access-group 1 out Apply IPv4 ACL under the interface, if no IPv4 ACL is defined, it will not have any filtering effect R3(config-if R3(config-line)#line vty 0 4 R3(config-line)#access-class 2 in R3(config-line)#password cisco R3(config-line)#privilege level 15 R3(config-line)#login(1) Telnet TestExcept for the PCI host, which can successfully Telnet the router's interface addresses, Telnet the router with other addresses as the source.The following message is displayed: .. % Connection refused by remote host(2) ping testIn router R1±ping host 172.16.3.100, the result is as follows: Type escape sequence to abort. Sending 5,100-byte ICMP Echos to 172.16.3.100, timeout is 2 seconds: !!!!! Success rateis 100 percent (5/5), round-trip min/avg/max = 28/29/32 msThe above output shows that using the standard ping command, it can ping through because the standard ping command is initiated with the address of the router S0/0/0 interface and is not denied by the IPv4ACL on R3. Rl#ping source *Type escape sequence to abort. sending 5,100-byte ICMP Echos to 172.16.3.100,timeout is 2 seconds: Packet sent with a source address of172.16.2.1