Re: Testing bridge capabilities

2007-12-30 Thread Drake Wilson
Quoth Andrew Del Vecchio <[EMAIL PROTECTED]>, on 2007-12-30 21:18:29 -0800: > GRC says port is closed but not stealthed. Firestarter shows that I have > a remote connection via tor on port 433, and TCP433 is allowed. What > could still be going wrong here? Okay, you know what? _443_ or _433_? Wh

Re: Testing bridge capabilities

2007-12-30 Thread Andrew Del Vecchio
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 GRC says port is closed but not stealthed. Firestarter shows that I have a remote connection via tor on port 433, and TCP433 is allowed. What could still be going wrong here? Any help would be appreciated. Thanks, Andrew - -- People just like you lo

Re: Testing bridge capabilities

2007-12-29 Thread F. Fox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Andrew Del Vecchio wrote: > How do I go about > testing my functionality? Also, if I can't use 443, are there other > typically not blocked ports that it would be worth using? AFAIK, Cox doesn't block port 443 - at least not here. I have "kitsune" l

Re: Testing bridge capabilities

2007-12-27 Thread Michael Holstein
I've got my OR set up to be a bridge, and everything seems to be going ok. However, I suspect that my ISP (Cox Communications) may be blocking HTTP port 433, as I can't get a confirmation on it. Well geez .. that's easy .. just tell us your IP address and we'll see if we can telnet to port 4

Testing bridge capabilities

2007-12-26 Thread Andrew Del Vecchio
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey all, I've got my OR set up to be a bridge, and everything seems to be going ok. However, I suspect that my ISP (Cox Communications) may be blocking HTTP port 433, as I can't get a confirmation on it. I know for sure that they block port 80 as of 2