[tor-relays] Unreachable ORPort - Potential ISP block?

CJ Barlow iamthechong at gmail.com
Sun Apr 5 23:03:03 UTC 2015


Hi Kurt,

My ISP is Vivint Wireless. I don't really have modem, my router connects
directly to the receiver on my roof. It's not satellite Internet (my ping
times to a local SpeedTest server are 3 ms).

On Sun, Apr 5, 2015 at 4:21 PM, Kurt Besig <kbesig at socal.rr.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 4/5/2015 12:31 PM, CJ Barlow wrote:
> > I'm attempting to run a Relay but I haven't been able to get it
> > the ORPort to be confirm as reachable. I've tried lots of things
> > but I'm hoping there is something I haven't thought of yet that can
> > make this work! I've got a 50Mbps symmetrical connection (without
> > data caps) that I would love to have the Tor network utilize.
> >
> > Hardware info: - Asus RT-N66U running DD-WRT - Raspberry Pi 2
> > running Raspbian - SanDisk MicroSDHC UHS-I 16GB
> >
> > Here are all the steps I've taken: - Formatted the MicroSDHC with
> > Win32DiskImager. - Followed the Instructables Raspberry Pi Tor
> > Relay configuration guide. - Port forwarded via NAT/QoS then Port
> > Forwarding. Protocol is set to TCP, double-checked IP is what is
> > assigned to Raspberry Pi 2 and enable box is checked. - ORPort set
> > to 9001. Also changed ORPort to 443, did "sudo service tor reload"
> > and changed the port in the forwarding section of my router. -
> > Tried router DMZ for Raspberry Pi LAN IP.
> >
> > I would really like to get this to work, if possible. I can't run
> > an Exit node on my connection but since my connection sits unused
> > for most of the day it should be put to good relay use.
> >
> >
> > _______________________________________________ tor-relays mailing
> > list tor-relays at lists.torproject.org
> > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> >
> Out of curiosity, if this is a cable connection what kind of cable
> modem are you using?
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.22 (MingW32)
>
> iQEcBAEBAgAGBQJVIbV/AAoJEJQqkaGlFNDPS/QH/Rb/ogBAmbF6vEETkspGJqW+
> D+vOxPB9Vd5k4JJRWsdk+ZcgEq3u9Q104YSUIte15P8OIC2UfrRSm560TwQprd+4
> DKkCWSBgQjj1uIJuylsepOqAunFUYaLZDKImeRg9H+2Bz7Ap2rPcB/UE/uYhf1rC
> T+j8CGS8fYA2Rx2VfPDXOPJbvRM/eSrZMjuhnZt7Y5CedUz1WTYLTbnDBKSKGbFk
> 4p6Mgbm/F7pFlJn2ON1EfXj9fsbtWcNleeMR0sSf93dRk4VTNF28ZEETslvUkMil
> 9E1HPVDHAQUM7lxknTFs7NMDnAJkHsWp+ut5zHphAcNLuxY5pN+cBp20Ke7D+ho=
> =o4cL
> -----END PGP SIGNATURE-----
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> http://www.avast.com
>
> _______________________________________________
> tor-relays mailing list
> tor-relays at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20150405/0346606c/attachment.html>


More information about the tor-relays mailing list