Hi,
Gunnar Wolf:
> I guess my nest step will be to talk to their end-user
> service. It's... Well, it's very very very much not fun to sit by the
> phone for ~30 minutes to have them repeat to me to use only a
> reasonably new Windows version and make sure I don't have a virus :-P
> But I will
Yes, I would agree that running an obfuscated bridge would be a good idea, as
the network could use some more of those.
I could only find the instructions for running a vanilla (non obfuscated)
bridge on the tor website, but did some research, and found a guide to running
an obfuscated bridge
> On 12 Jun 2018, at 04:29, Gunnar Wolf wrote:
>
> So, it seems my ISP does not want us to run relays ☹ Can you think of
> any way my connection (oversized for my regular uses) can be put to
> use for Tor? I guess it would not work as a bridge either, would it?
Your relay will work as a bridge
Neel Chauhan dijo [Mon, Jun 11, 2018 at 05:38:31PM -0400]:
> Do you have an alternative choice of ISP? In many countries, you often do
> (e.g. Europe, East Asia). In others, you usually don't (e.g. USA, small
> island nations). If you don't, another option is a VPN with a public IP
> address (that
r1610091651 dijo [Mon, Jun 11, 2018 at 09:34:55PM +0200]:
> Traceroute requires support by all hops on the way, and that's not a given.
> Try pinging the DA's instead or connecting to their tor ports.
>
> Only Dizum doesn't respond to ping requests, but it has a "welcome" page on
> 80.
>
>
Do you have an alternative choice of ISP? In many countries, you often
do (e.g. Europe, East Asia). In others, you usually don't (e.g. USA,
small island nations). If you don't, another option is a VPN with a
public IP address (that is, if you are willing to pay for one).
Once Verizon FiOS (US
On Mon, 11 Jun 2018 at 20:30 Gunnar Wolf wrote:
> Graeme Neilson dijo [Sat, Jun 09, 2018 at 11:53:20AM +1200]:
> > See if you can route to all the authorities.
> > Tor requires that all relays are able to contact all directory
> authorities.
> >
> > In my case tcptraceroute would not get to all
Graeme Neilson dijo [Sat, Jun 09, 2018 at 11:53:20AM +1200]:
> See if you can route to all the authorities.
> Tor requires that all relays are able to contact all directory authorities.
>
> In my case tcptraceroute would not get to all the authorities. For some
> authorities my ISP was not
One thought. Try making sure you are running the newest version of the tor
software. I say this because I know directory authorities recently started
rejecting relays running older versions of tor. Another thing I might check if
possible is if your router has a limit for how many simultaneous
See if you can route to all the authorities.
Tor requires that all relays are able to contact all directory authorities.
In my case tcptraceroute would not get to all the authorities. For some
authorities my ISP was not routing to them.
On 8 June 2018 at 17:35, Gunnar Wolf wrote:
> Roger
Roger Dingledine dijo [Fri, Jun 08, 2018 at 01:20:19AM -0400]:
> First, did your relay find itself reachable (both ORPort and DirPort)
> at startup? Look for lines like
>
> Jun 05 12:47:50.013 [notice] Self-testing indicates your ORPort is reachable
> from the outside. Excellent.
>
> and
>
>
On Thu, Jun 07, 2018 at 11:37:26PM -0500, Gunnar Wolf wrote:
> The following happens every couple of hours:
All of these log entries are fine and normal except this one:
> Jun 07 09:36:19.000 [notice] Heartbeat: It seems like we are not in the
> cached consensus.
> Jun 07 15:36:19.000
Hello,
I have set up a VM at my home server (via fiber DSL) to work as a Tor
relay. I have set up port forwarding for ORport and DirPort (defaults,
9001 and 9030). The logs don't give me any useful information — or,
possibly, I fail to grok anything useful ;-)
The following happens every couple
13 matches
Mail list logo
