Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
If the Internet companies were able to ping internet users before they sent packets to a connection. If they didn't get a hit they would just drop the call. Wouldn't it greatly improve security? I know in Russia they block all udp.
Usually there is no need to do such a thing. Most connections use TCP/IP "sockets" which are bi-directional and persistent. Once the socket has been established, there's no further verification required before sending traffic through it.
"Russia" certainly does not "block all UDP," and even "the Great Firewall of China™" has holes in it.
None of this has anything to do with security. The only way to provide security for a TCP/IP or UDP connection is to encrypt the traffic.
"Ping" (ICMP ECHO ...) is simply a very lightweight way to see if an IP-address is occupied ... i-f the computer in question is programmed to respond to it.
Last edited by sundialsvcs; 04-19-2017 at 05:22 PM.
As we all know a ip4 header diagram contains both source and destination address. Ping only works on a valid ip address. If it is fake it doesn't go through. Ping may be trivial but it does work. A local switch could be programmed to ping all packets on arrival and drop any invalid? If this doesn't work how could it work?
Interesting 'study'. I'm guessing NAT is a key piece, where 'many' IP are 192.168.1.2
I was trying to come up with 'good' web-research keywords, but I hit this tangent via:
use ping to verify valid nat source IP bogus|spoof
Can anyone advise on a better web-research ...? Thanks!
p.s. packet filtering ? http://wpollock.com/AUnixSec/IptablesOverview.htm
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.