Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
What do you mean by "it didn't make any difference"? SYNcookies can't stop a SYN flood attack, but it ensures the attack doesn't use any resources (memory) on the server being attacked. Bandwidth will still be consumed, of course.
If you're publishing a web server on the public internet, you should expect HTTP requests from random IP addresses. There are lots of script kiddies out there scanning for web servers. If you don't want people to access your server, you shouldn't make it available to them.
That doesn't make sense to me as at first glance as it appears to stop outbound, but...
I gave it a go and It has cleaned it up!
Still seeing the SYN packets coming in,
But of course, I guess there is no way of physically stopping the SYN packets from being delivered by the ISP router!
So they will always appear on the tcpdump?
Make sense?
(excuse me I am using this as a learning exercise!)
I guess sending anything back to the attacker is ignored anyway. In this sort of attack anyway.
Last edited by bigearsbilly; 02-07-2014 at 11:24 AM.
That doesn't make sense to me as at first glance as it appears to stop outbound, but...
I gave it a go and It has cleaned it up!
Still seeing the SYN packets coming in
Of course they're still sent by the attacker. But now they are ignored by your OS.
Quote:
Originally Posted by bigearsbilly
But of course, I guess there is no way of physically stopping the SYN packets from being delivered by the ISP router!
So they will always appear on the tcpdump?
Make sense?
(excuse me I am using this as a learning exercise!)
Yes you'll still see it on a tcpdump but only what is coming from the attacker. You should see no reply from your server.
Do the test, fire a tcpdump with and without the "blackholing" (type "ip ro del bl <ip>" to remove it from the routing)
Quote:
Originally Posted by bigearsbilly
I guess sending anything back to the attacker is ignored anyway. In this sort of attack anyway.
Indeed, the goal of this attack is a denial of service.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.