Re: [tor-talk] obfsproxy failure: obfs3

[lee colleton <lee@xxxxxxxxxxxx>]

Yes, I've opened the ports in the Google Compute Engine (see below). I'll
follow up on their forum to make sure I've altered the firewall properly.

--lee

lee@li388-156:~$ gcutil --service_version="v1beta15"
--project="colleton.net:tor-cloud" listfirewalls
+------------------------+---------------------------------------+---------+------------+-------------+-------------+
|          name          |              description              |
network | source-ips | source-tags | target-tags |
+------------------------+---------------------------------------+---------+------------+-------------+-------------+
| default-allow-internal | Internal traffic from default allowed |
default | 10.0.0.0/8 |             |             |
| default-ssh            | SSH allowed from anywhere             |
default | 0.0.0.0/0  |             |             |
| tor-obfsproxy          |                                       |
default | 0.0.0.0/0  |             | obfsproxy   |
+------------------------+---------------------------------------+---------+------------+-------------+-------------+
lee@li388-156:~$ gcutil --service_version="v1beta15"
--project="colleton.net:tor-cloud" getfirewall tor-obfsproxy
+---------------+-------------------------------+
|   property    |             value             |
+---------------+-------------------------------+
| name          | tor-obfsproxy                 |
| description   |                               |
| creation-time | 2013-08-07T18:37:35.986-07:00 |
| network       | default                       |
| source-ips    | 0.0.0.0/0                     |
| source-tags   |                               |
| target-tags   | obfsproxy                     |
| allowed       | tcp: 443, 9001, 40872, 52176  |
+---------------+-------------------------------+
lee@li388-156:~$



On Wed, Aug 14, 2013 at 9:19 PM, Roger Dingledine <arma@xxxxxxx> wrote:

> On Wed, Aug 14, 2013 at 09:08:03AM -0700, lee colleton wrote:
> > There's a more serious issue in that my server doesn't appear to be
> > reachable. I've opened tcp:443,9001 along with the two specifiedobfsproxy
> > ports
> >
> > Aug 14 15:26:58.000 [notice] Bootstrapped 100%: Done.
> > Aug 14 15:26:58.000 [notice] Now checking whether ORPort
> > 173.255.119.202:443 is reachable... (this may take up to 20 minutes --
> > look for log messages indicating success)
> > Aug 14 15:28:00.000 [notice] New control connection opened.
> > Aug 14 15:46:56.000 [warn] Your server (173.255.119.202:443) has not
> > managed to confirm that its ORPort is reachable. Please check your
> > firewalls, ports, address, /etc/hosts file, etc.
>
> Well, that's because it's unreachable. (I just tried.)
>
> Can you try following the suggestion in the log message?
>
> --Roger
>
> --
> tor-talk mailing list - tor-talk@xxxxxxxxxxxxxxxxxxxx
> To unsusbscribe or change other settings go to
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
>
-- 
tor-talk mailing list - tor-talk@xxxxxxxxxxxxxxxxxxxx
To unsusbscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk