[plug] Blocking of Port 80

[Matthew]

Basicly most ISP's have blocked code red at the router level, 
currently we are filtering code red for quite a number of
ISP's in Perth, since the majority of ISP's in Perth do not
have the network grunt in order to check then block
every incoming packet without major network degregation.

Currently we are filtering code red at the core level
of the network, and we have had no complaints from clients
being unable to hit any web pages since the implementation,
which was over 3 weeks ago now.

Have FUN!

- Matthew Murray

Worldcom / UUNET Network Engineer

-----Original Message-----
From: Craig Foster [mailto:fostware at iinet.net.au]
Sent: Tuesday, 14 August 2001 10:16 PM
To: Plug Mailing List
Subject: [plug] Blocking of Port 80


What do people make of the following e-mail I recieved from iiNet support
after access to port 80 inbound refused to work? (HTTPS works sweet, HTTP
connection timeout)
I run a small dyndns.org machine so I can try out things like webmail, php,
cgi, etc.
I also know of a few people not with iiNet and some overseas who are having
similar problems.

ipchains input ACCEPT, output ACCEPT, forward MASQ (hey this e-mail had to
get out somehow :-)

Is this a little too helpful for an ISP, or are they just protecting the
great unwashed?

Regards,

Craig Foster



Sent Tue 14/08/2001 1:43 AM


>Good Morning

>At the moment I believe we are only filtering any http
>requests that have the same characteristics as what the
>code red was looking for. As far as I am aware, all other
>http requests should work fine. Please let us know if
>you are still having problems.

>Kind Regards
><*name removed to protect the blameless*>
>iiNet Support