Tag Info

New answers tagged

2

You should read A Question of DNS Protocols by Geoff Huston, which is an actual investigation into this idea, with statistics and everything: If the DNS represents such a significant vulnerability for the Internet through these UDP-based reflection attacks, then does TCP represent a potential mitigation? Could we realistically contemplate moving ...


2

I have found that these automated, undirected scans are usually scanning IPs randomly and do not include a Host: header or include a bogus Host: header. Filtering out requests with bad Host headers can reduce the nuisance logging a bit and possibly reduce the impact on your server, depending on the server's architecture. This doesn't make your server much ...


2

While all of them lead to a 404 Not Found, CPU cycles are wasted in processing these requests ... Somewhere CPU cycles "must be wasted" to filter out these requests. But it depends on the kind of requests and of your server and application setup how much cycles this will be and where exactly they will be needed. If there is a clear source of these ...


1

As was stated a secondary IP via the same gateway will not help. This text-based diagram shows why: {INTERNET} <---> [Hitron, the Gateway, 2xIP] <--IP Passthrough---(a) (a)---> [dd/wrt NightHawk, 2xIP] <---> Devices on the network IP Passthrough only works because the Hitron device sees all the traffic first, then it goes to the ...


1

Your Hitron device is still acting as a gateway. This means that any traffic targeted to your second device must be handled by the Hitron. When the Hitron device is running out of resources, every host which is using the Hitron as a gateway is affected. First of all, it's not very effective to work around this issue without a external gateway like VPN. ...



Top 50 recent answers are included