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.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.