[NTLUG:Discuss] @home port blocking?

[Chris Cox]

It was my understanding that in some areas (not mine) that @home
blocked port 80 incoming requests (that is... people trying to
hit a web server on an @home customer's machine).  This was
supposedly just done temporarily to help quash the CR worm
and variants. (not that it would really solve the problem)

However, it seem that each @home is managed differently (in some
cases caused by acquisition).... so it's definitely not something
that one can make a "general" statement about.  So there
may well be some really BAD @home experiences where some
over zealous admin did something really stupid.

Reminds me of a time when a sys admin I worked for decided
to secure the system by taking read permissions off of
/etc/passwd (I left the company shortly thereafter).

The converse is true as well....
there are some @home locations that are still NOT CAPPED!!
(ahh... I remember when....)

Regards,
Chris


MadHat wrote:
> 
> At 05:48 PM 8/20/2001 +0000, you wrote:
> >I know that @home blocks ports for WWW and Netbios inbound and the SMTP
> >port outbound.  Does anyone know of other ports that are blocked?  I
> >just heard a rumor that VPN was blocked as well.  Is there a site to
> >reference or is this just some random observations?
> >
> >Beginning to feel that I'm leaving the real internet and moving into the
> >edges of AOL-space...
> 
> I have not seen any blocked port, in our out, on my @home connection.  I do
> not see how they could block SMTP or IPSec outbound without facing some
> major pushback from subscribers.
> 
> >...Ken
> >_______________________________________________
> >http://www.ntlug.org/mailman/listinfo/discuss
> 
> --
> MadHat at unspecific.com
> 
> _______________________________________________
> http://www.ntlug.org/mailman/listinfo/discuss