[tor-relays] VPS/Tor Final Thoughts

[Kurt Besig]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I thought it might be helpful to any other volunteer that may have
been silently following this thread to quickly post the issues with my
VPS Tor server that were resolved.

1. Setting up iptables allowed connections to my server.

2. Adding my server's [ip address] to the /etc/torrc resolved the
problem of tor attempting to connect to the "node" my server is on
rather than the actual ip my server is on.

3. Checking the user groups and permissions necessary to allow access
to tor files.

Other thoughts: As mentioned numerous times arm is a comfy frontend,
but certainly not necessary after investigating system tools such as
lsof and utilizing nload or munin. Also having ntp installed and
running is helpful I think.

Again thanks for all the help and have a very happy holiday season!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWaDXxAAoJEJQqkaGlFNDPGh4H/0uDGiSIq9dYjDBNSIrVRoBQ
sBGjLdFhvdFSJ4dsTRPspAKC+6zg4FnGSj1isBFBmJOLIN71oIo6qXkrXoQgyS+Q
crnNYucyC6Vo8vQdK72QabuAJZGE2+VXfwTw/82NhldIQnKJzyfnjNKZYamR486y
KQJGzPHls2abZPu0zyx/ay7pZRUZWzGvfc1yShQ6yTsiVqCJk456aPRd0/rbkLMQ
dG/TOHHSOAJzMsZXk92rzk0JNBBYhwkOTiNyPQDd+S68IWyLXp5wC0hE4KTdRmf/
Osa8NIB3FQyYeg6XAjxZ1PhYSc8Lp91+K220znS/2lXStxjrdUFY4TU7119iYpA=
=a7HY
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] Crash and obfs error

[Geoff Down]

Hello all,
 a couple of quick questions.
Tor exited with this error:
Dec 09 06:35:34.000 [err] descriptor at 0x62ee080 begins with unexpected
string "".  Is another process running in our data directory?  Exiting.
 I've a vague feeling it's happened once before - anything to worry
 about?
Also, on restarting Tor with Obfsproxy already running, I got
Dec 09 14:14:43.000 [warn] Server managed proxy encountered a method
error. (obfs3 Could not set up listener (0.0.0.0:xx) for 'obfs3'
(Address already in use).)
Dec 09 14:14:43.000 [warn] Managed proxy at '/usr/bin/obfsproxy' failed
the configuration protocol and will be destroyed.
 does this mean that Tor is running without obfsproxy now, and I need to
 stop both and restart?
It's quite annoying that Tor doesn't remember its auto-picked port, and
I have to change the port-forwarding rule every time.
Thanks,
GD

-- 
http://www.fastmail.com - IMAP accessible web-mail

___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] Bridge Accounting Period Resets Stats

[akashic]

I'm running some bridges on VPS where I set 10GB monthly limit.  I never
come close to the quota, but the bridges reset with a new port and new
stats every accounting period.  This is undesirable because it means
people who wrote down my bridge and port will no longer be able to
connect.  And Atlas take 6 more days to mark the bridge as fast again.

I like port diversity, but monthly switch seems excessive if 25% of every
month is spent resetting stats.

Can I set a longer accounting period, like 6 months?  Failing that, what's
the risk if I just get rid of the quota?  Throttle rate of 200KB/s could
add to 4TB/mo in worst case, which will get a VPS account killed.  What's
a more realistic worst case if I keep 200KB throttle with no monthly
accounting?


___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Crash and obfs error

[Yawning Angel]

On Thu, 10 Dec 2015 01:26:41 +
Geoff Down  wrote:

[snip[
> Also, on restarting Tor with Obfsproxy already running, I got
> Dec 09 14:14:43.000 [warn] Server managed proxy encountered a method
> error. (obfs3 Could not set up listener (0.0.0.0:xx) for 'obfs3'
> (Address already in use).)
> Dec 09 14:14:43.000 [warn] Managed proxy at '/usr/bin/obfsproxy'
> failed the configuration protocol and will be destroyed.
>  does this mean that Tor is running without obfsproxy now, and I need
> to stop both and restart?

Yes.  For what it's worth, newer versions of tor (0.2.7.x) has code to
prevent this from happening on Linux systems by using prctl to force
the kernel into cleaning up children with SIGTERM.

obfs4proxy also has the same prctl() trickery and additional code for
non-Linux systems so it can self-terminate on parent exit.

> It's quite annoying that Tor doesn't remember its auto-picked port,
> and I have to change the port-forwarding rule every time.

This should get persisted in the state file.

Regards,

-- 
Yawning Angel


pgp29dnnHV2KV.pgp
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays