Tag Info

New answers tagged


Plan A: Try using another ip range than the real DHCP server. A DHCP server is not supposed to NACK a request for an ip outside it's IP range. Plan B: it is a race condition, so flood the client with DHCPOFFER messages. Plan C: use arpspoofing, it's much easier.


I don't think client certificates will solve the problem of computational DoS. Consider the sequence of messages in SSL / TLS: The client certificate is sent to the server after the ServerKeyExchange message. In the case of [EC]DHE_RSA the ServerKeyExchange message involves the server signing the DH parameters with it's long term public key. So the server ...


Since you mentioned home network, I'm going to bring up a couple of points that may be unique to them. First, there's the use of dumb switches. Quite often, home customer premises equipment will use dumb unmanaged switches with no support for spanning tree. Internally, this might be a separate switch chip or it might be integrated onto main ...


A little background first. As you know, when communicating over a network, programs split raw data into "packets", which as well as this raw data also contain some extra information: Where does this particular packet fit inside the entire block of data being transmitted? Who does the packet come from? To whom does it need to be delivered? Routers are the ...


Generally, if you are doing DoS from computer to another, you are hitting anything (like routers, ...) between them with the same load.


If you start to send lots of packets it would probably create a bottleneck on the network. But you can try to send only a few packets just for testing purposes.


It will surely impact the complete network, as sending too many packets would lead to bandwidth starvation in the local network. Also the router through which you are connected could start dropping packets if it isn't capable of handling them all !! I would rather suggest for you to test the DDoS on a virtual environment.


I would look at Akamai which also has a CDN based DDoS prevention system. However they also have a web application firewall (WAF) which can do some pretty sophisticated filtering based on request headers or any other data in the HTTP/HTTPS sessions. Even if you don't use Akamai per se, I think a WAF should be considered.

Top 50 recent answers are included