Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Has anyone asked Comcast to stop blocking inbound ports?



 On Fri, 21 Dec 2007, Kristian Erik Hermansen wrote: 

> On Dec 21, 2007 4:48 PM, Gregory Boyce <[hidden email]> wrote: 
>> No you don't. 
>> 
>> 22/tcp  open     ssh 
>> 23/tcp  closed   telnet 
>> 139/tcp filtered netbios-ssn 
>> 
>> Open is obvious. 
>> Closed means no filtering but nothing listening. 
>> Filtered means filtered. 
>> 
>> Now you do need to make sure that YOUR system isn't filtering the port. 
> 
> Right, that's what I really meant to say.  Now let me clarify what 
> this all means... 
> 
> OPEN == TCP syn/ack response 
> CLOSED == TCP rst response 
> FILTERED == TCP drop, no response 


BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org