Thanks to you both Jon and Rick. There are other traffic / protocol specific access lists applied. What I am afraid of this is that am I not opening my router up to a ping flood? The router has a private address but I still need to control this right?
There are various opinions about the value of permitting ping and about the danger of permitting ping. I tend to believe that the potential value of ping as a troubleshooting tool makes it worthwhile to permit inbound ping. I know others who react to the potential use of ping in denial of service attacks and deny it.
Probably the answer will depend on where in your network the router is located and how willing you are to give up a useful tool to be (marginally) safer. If the router were the border router at the edge of your network, I might deny inbound ping on its Internet facing interface. I would be inclined to permit ping on the interior facing interfaces.
If you are concerned about the security implications of permitting ping, then perhaps a middle position would be to permit ping whose source address was internal to your network and to deny ping whose source address was external to your network.
I'm working on a project that includes basic router configurations. I configurated everything including: line console 0, line vty 0 15 and secret passwords. There are 3 routers in the network and every LAN is going t...
Desire to create Terminal Server ("TS" in this document) out of 2811 Cisco Router with HWIC-16A card (with Octal cables)
Desire to use SSH over Telnet
TS is ip'ed, SSH access configured (to the TS)
Python based Script to BULK Import/Delete devices using Cisco Prime API
Check my Repo on GitHub for all the details ( see below link )