   Cleansing an IP's "bad rep"
  Suppose a static IP was previously used for illegal purposes (such as file-sharing) and that IP is now chached in every dirty server on the net, each goon looking for illegal content is directed to that IP and it''s not possible to actually request a new static IP. Is there a way to clean up this "bad reputation" - get it out of the p2p filesharing caches and perhaps decrease the traffic directed at it at least tenfold?   "Finishing in second place, simply means you are the first loser." - PouyaCat
  Shame on you, Crispy. Naughty.- CD   Brought to you by Code_Dark;  Speaking of bad reps for static IPs, at a place where I worked, a print ripper was compromised and used to host pornography (lots and lots of pornography). They fixed that, but now that they have a firewall in place, they STILL get lots of HTTP requests for that computer. Mind you, this was years before I showed up.Crispy == screwed. ;  Spend a while setting up your router and firewall very very carefully.  Eventually i''d like to think that most of these sites will notice your IP is no longer working and will drop you from their lists.   - It''s a life''s work:Image Hosting @ $5/3 Months :30Gig/month bandwidth Reseller Plan @ $40/3 MonthGeneric WebHost: The Cheapest Hosting Around!-ryan@lecherousjester.com ;  Forward all requests to 127.0.0.1 ;  Any decent connection can take plenty of SYN packets thrown at it without hiccuping, as long as it never ACKs them. Put a very restrictive port firewall into place; no common services, or common services on alternative ports. Filter all ICMP.   "Sneftel is correct, if rather vulgar." --Flarelocke ;quote:Original post by aftermath  Forward all requests to 127.0.0.1   I concur!- CD   Brought to you by Code_Dark;quote:Original post by Code_Dark  Shame on you, Crispy. Naughty.I''m not the naughty one here - I only inherited the system after the previous guy left.>> Forward all requests to 127.0.0.1 What good does that make? 90% of the requests are from people who are only trying to get the illegal files that seem to have existed at this IP. However, I need to allow equal legitimate access to all sources as well. I don''t think this can be achieved through filtering...Today I suggested to my boss that they should demand the ISP for a new IP. Besides, the current connection is 8Mbit/800kbit for 150 students and costs the equivalent of 20 of my home connections (1Mbit/256kbit just for me). That''s gotta suck.FYI: I''ve never run and never intend to run things such as a Gnutella server. Besides, this is at my work place so basically all I''m worried about is HTTP statistics and the "bad rep" which could potentially get the company I work for into quite a bit of trouble. "Finishing in second place, simply means you are the first loser." - PouyaCat;  Slashdot had an artile a week ago or so if I remember correctly on port knocking, which to the outside world makes all ports seem stealted, no response.  However, the server keeps track of what ports have been requested.  If certian ports are requested in the correct order in a set time (like 10 seconds), you can have it open access to a port.  Its basically like setting up a password you need to enter to get to any of the services. 