Re: [tor-relays] Unbelieveable

2015-12-05 Thread Sean Greenslade 
> > Check your firewall, and gateway port forwards if the server is
> > behind a NAT. If you're not sure where to start, post the output of
> > "sudo iptables -L"
> > 
> > --Sean
> > 
> I've made several iptables and saved them, I thought, however every
> time I reboot the VPS all my rules are gone.
> ~$ sudo iptables -L
> > Chain INPUT (policy ACCEPT) target prot opt source
> > destination
> > 
> > Chain FORWARD (policy ACCEPT) target prot opt source
> > destination
> > 
> > Chain OUTPUT (policy ACCEPT) target prot opt source
> > destination
> 
> 
> but:
>  cat /etc/iptables.rules
> # Generated by iptables-save v1.4.21 on Fri Dec  4 04:30:56 2015
> *raw
> :PREROUTING ACCEPT [2424:210831]
> :OUTPUT ACCEPT [1856:540218]
> COMMIT
> # Completed on Fri Dec  4 04:30:56 2015
> # Generated by iptables-save v1.4.21 on Fri Dec  4 04:30:56 2015
> *nat
> :PREROUTING ACCEPT [229:8057]
> :POSTROUTING ACCEPT [86:5885]
> :OUTPUT ACCEPT [86:5885]
> COMMIT
> # Completed on Fri Dec  4 04:30:56 2015
> # Generated by iptables-save v1.4.21 on Fri Dec  4 04:30:56 2015
> *mangle
> :PREROUTING ACCEPT [2424:210831]
> :INPUT ACCEPT [2424:210831]
> :FORWARD ACCEPT [0:0]
> :OUTPUT ACCEPT [1856:540218]
> :POSTROUTING ACCEPT [1856:540218]
> COMMIT
> # Completed on Fri Dec  4 04:30:56 2015
> # Generated by iptables-save v1.4.21 on Fri Dec  4 04:30:56 2015
> *filter
> :INPUT ACCEPT [0:0]
> :FORWARD ACCEPT [0:0]
> :OUTPUT ACCEPT [581:184073]
> - -A INPUT -i lo -j ACCEPT
> - -A INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
> - -A INPUT -p tcp -m tcp --dport 80 -j ACCEPT
> - -A INPUT -p tcp -m tcp --dport 443 -j ACCEPT
> - -A INPUT -p tcp -m tcp --dport 9052 -j ACCEPT
> - -A INPUT -p tcp -m tcp --dport 9051 -j ACCEPT
> - -A INPUT -p tcp -m tcp --dport 9001 -j ACCEPT
> - -A INPUT -p tcp -m tcp --dport 9030 -j ACCEPT
> - -A INPUT -p tcp -m tcp --dport 22 -j ACCEPT
> - -A INPUT -j DROP
> COMMIT
> # Completed on Fri Dec  4 04:30:56 2015
> 
> 
> > 3:/etc/network$ cat interfaces # This configuration file is
> > auto-generated. # # WARNING: Do not edit this file, your changes
> > will be lost. # Please create/edit /etc/network/interfaces.head
> > and # /etc/network/interfaces.tail instead, their contents will be 
> > # inserted at the beginning and at the end of this file,
> > respectively. # # NOTE: it is NOT guaranteed that the contents of
> > /etc/network/interfaces.tail # will be at the very end of this
> > file. #
> > 
> > # Auto generated lo interface auto lo iface lo inet loopback
> > 
> > # Auto generated venet0 interface auto venet0 iface venet0 inet
> > manual up ifconfig venet0 up up ifconfig venet0 127.0.0.2 up route
> > add default dev venet0 down route del default dev venet0 down
> > ifconfig venet0 down
> > 
> > 
> > iface venet0 inet6 manual up route -A inet6 add default dev venet0 
> > down route -A inet6 del default dev venet0
> > 
> > auto venet0:0 iface venet0:0 inet static address 167.114.35.28 
> > netmask 255.255.255.255
> 
> > cat sysctl.conf
> 
> > # Uncomment the next line to enable packet forwarding for IPv4 
> > net.ipv4.ip_forward=1
> > 
> > # Uncomment the next line to enable packet forwarding for IPv6 #
> > Enabling this option disables Stateless Address Autoconfiguration #
> > based on Router Advertisements for this host 
> > net.ipv6.conf.all.forwarding=1

iptables doesn't automatically load anything on boot; it starts with a
clean slate. Most distros have a preferred way of loading that save file
on boot, typically a service of some sort. Check your distro's docs for
the specifics.

But before you go enabling the firewall, verify that the tor process is
binding to the ports correctly. Restart the VPS, make sure tor is
running, then run the following:

"sudo lsof | grep LISTEN"

It should output something like this:

> sshd398   root3u IPv4  104876616   0t0 TCP 
> *:ssh (LISTEN)
> sshd398   root4u IPv6  104876623   0t0 TCP 
> *:ssh (LISTEN)
> tor1129   _tor6u IPv4  105943714   0t0 TCP 
> *:https (LISTEN)
> tor1129   _tor7u IPv4  105943715   0t0 TCP 
> *:http (LISTEN)
> tor1129  1130 _tor6u IPv4  105943714   0t0 TCP 
> *:https (LISTEN)
> tor1129  1130 _tor7u IPv4  105943715   0t0 TCP 
> *:http (LISTEN)

Note that I'm using the HTTP(S) ports for my relay, you should see the
ports you have selected for ORPort and DIRPort. Also note the asterisk
indicating that it is listening on all network interfaces. If it only
lists one specific interface, ensure that it is the correct
(internet-facing) interface.

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

Re: [tor-relays] Unbelieveable

2015-12-05 Thread john saylor 
On 12/04/15 00:07, I wrote:
> I thought I was joining a loose but passionate, clever and idealistic 
> community.
> I thought I would learn just being a listener and building my knowledge of 
> security and servers.


disappointments result from expectations.

i have learned some things by reading this list. i have learned other
things as well.


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

Re: [tor-relays] Unbelieveable

2015-12-05 Thread Kenneth Freeman 


On 12/03/2015 10:09 PM, Michael McConville wrote:
> Kurt Besig wrote:
>> Well. even a doctor would make a few suggestions based on some sort of
>> experience based reasoning. Perhaps some connection problems
>> associated with running tor-arm on a VPS vs. a home server...things of
>> that nature. Also I was just wondering as I don't see many of the
>> relay operators that used to post to this list around anymore, has
>> something changed to make them move on??
>> Lots of people whining about their consensus weight numbers, but
>> little of substance being posted.
> 
> The people who know what they're doing can quickly, reliably
> set-and-forget relays. That's the ideal scenario - tweaking knobs is
> mostly a liability and performance issues are a development concern.

This is very much the case.


0xDD79757F.asc
Description: application/pgp-keys


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

Re: [tor-relays] Unbelieveable

2015-12-05 Thread Kurt Besig 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/4/2015 8:25 PM, Damian Johnson wrote:
> For what it's worth process permissions aren't at play here. Arm
> is failing to talk with the control port - permissions could cause
> us to be unable to read the authentication cookie, but that would
> be a different message.
> 
> Cheers! -Damian
> 
> 
> On Fri, Dec 4, 2015 at 5:36 PM, Manager Bahia del Sol LLC 
>  wrote:
>> 
>> No worries,
>> 
>> Are you sure the user or group is debian_tor? The default is
>> debian-tor in Ubuntu.
>> 
>> If that isn't the problem,
>> 
>> First I would be sure tor is actually running. top or top -u
>> debian-tor The second will show if tor is actually running as the
>> user you think it is.
>> 
>> If it is, then see if it is listening on the control port sudo
>> netstat -ntlp | grep LISTEN
>> 
>> If it is I would suspect that either a firewall is blocking that
>> port. If you have one running try shutting it down for a few
>> minutes while you try to start arm.
>> 
>> Or maybe it is a permissions issue where arm is not running as
>> the same user as tor. You could try starting arm as root to see
>> if it would start. But, do not run arm as root full time. Only
>> try to start it as a test.
>> 
>> 
>> 
>> -- Manager of Bahia del Sol LLC
>> 
>> 
>> ___ tor-relays
>> mailing list tor-relays@lists.torproject.org 
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>> 
> ___ tor-relays mailing
> list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
> Dec 05 21:17:46.000 [notice] Your IP address seems to have changed
> to 167.114.35.28 (METHOD=INTERFACE). Updating. Dec 05 21:17:46.000
> [notice] Our IP Address has changed from 142.4.217.95 to
> 167.114.35.28; rebuilding descriptor (source: METHOD=INTERFACE). 
> Dec 05 21:18:42.000 [notice] Your IP address seems to have changed
> to 142.4.217.95 (METHOD=GETHOSTNAME HOSTNAME=ca3.pulseservers.com).
> Updating. Dec 05 21:18:42.000 [notice] Our IP Address has changed
> from 167.114.35.28 to 142.4.217.95; rebuilding descriptor (source:
> METHOD=GETHOSTNAME HOSTNAME=ca3.pulseservers.com). Dec 05
> 21:18:43.000 [notice] Self-testing indicates your ORPort is
> reachable from the outside. Excellent. Publishing server
> descriptor. Dec 05 21:38:37.000 [warn] Your server
> (142.4.217.95:9030) has not managed to confirm that its DirPort is
> reachable. Please check your firewalls, ports, address, /etc/hosts
> file, etc. Dec 05 21:58:37.000 [warn] Your server
> (142.4.217.95:9030) has not managed to confirm that its DirPort is
> reachable. Please check your firewalls, ports, address, /etc/hosts
> file, etc.
I've gotten this far, not being much good at networking I can't tell
where the problem lies.. do I need to forward something?

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWYzh6AAoJEJQqkaGlFNDPCeYIAJln5C5Z+7n69zcoW1/RdUxi
iduyKB/lnXc1Be190dSsHikjXVWv2hYvbnwvn3RuGOAft29WHd/OJi+GK9qBAB57
qdL+sl4PvlJVlWYH8hDK65FHqmZ85UYRX0nP5KsvRLbzKlNiX1rGSJPfpVSeOlK8
2bvSG/b4+Y4ZqmlxmLyJW5eJnMMzOHJdTf/OgUefnqic5KB1BLXygFi566lYYNMC
d8R8RObw8Rez/9H4+cKXcbNfnN2Yh0RMwpHF8nqpU8D292kO+Koz/xhfsu9VXRfe
DBKhCSfKdDJBNiP0zI13Y1OB5tq4SG0sKhhGCCavW+3oelT2ujyTBgB4xAyszkY=
=U+4y
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Unbelieveable

2015-12-05 Thread Kurt Besig 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/5/2015 3:20 PM, Sean Greenslade wrote:
>>> Dec 05 21:17:46.000 [notice] Your IP address seems to have
>>> changed to 167.114.35.28 (METHOD=INTERFACE). Updating. Dec 05
>>> 21:17:46.000 [notice] Our IP Address has changed from
>>> 142.4.217.95 to 167.114.35.28; rebuilding descriptor (source:
>>> METHOD=INTERFACE). Dec 05 21:18:42.000 [notice] Your IP address
>>> seems to have changed to 142.4.217.95 (METHOD=GETHOSTNAME
>>> HOSTNAME=ca3.pulseservers.com). Updating. Dec 05 21:18:42.000
>>> [notice] Our IP Address has changed from 167.114.35.28 to
>>> 142.4.217.95; rebuilding descriptor (source: METHOD=GETHOSTNAME
>>> HOSTNAME=ca3.pulseservers.com). Dec 05 21:18:43.000 [notice]
>>> Self-testing indicates your ORPort is reachable from the
>>> outside. Excellent. Publishing server descriptor. Dec 05
>>> 21:38:37.000 [warn] Your server (142.4.217.95:9030) has not
>>> managed to confirm that its DirPort is reachable. Please check
>>> your firewalls, ports, address, /etc/hosts file, etc. Dec 05
>>> 21:58:37.000 [warn] Your server (142.4.217.95:9030) has not
>>> managed to confirm that its DirPort is reachable. Please check
>>> your firewalls, ports, address, /etc/hosts file, etc.
>> I've gotten this far, not being much good at networking I can't
>> tell where the problem lies.. do I need to forward something?
> Check your firewall, and gateway port forwards if the server is
> behind a NAT. If you're not sure where to start, post the output of
> "sudo iptables -L"
> 
> --Sean ___ tor-relays
> mailing list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
I've made several iptables and saved them, I thought, however every
time I reboot the VPS all my rules are gone.
~$ sudo iptables -L
> Chain INPUT (policy ACCEPT) target prot opt source
> destination
> 
> Chain FORWARD (policy ACCEPT) target prot opt source
> destination
> 
> Chain OUTPUT (policy ACCEPT) target prot opt source
> destination


but:
 cat /etc/iptables.rules
# Generated by iptables-save v1.4.21 on Fri Dec  4 04:30:56 2015
*raw
:PREROUTING ACCEPT [2424:210831]
:OUTPUT ACCEPT [1856:540218]
COMMIT
# Completed on Fri Dec  4 04:30:56 2015
# Generated by iptables-save v1.4.21 on Fri Dec  4 04:30:56 2015
*nat
:PREROUTING ACCEPT [229:8057]
:POSTROUTING ACCEPT [86:5885]
:OUTPUT ACCEPT [86:5885]
COMMIT
# Completed on Fri Dec  4 04:30:56 2015
# Generated by iptables-save v1.4.21 on Fri Dec  4 04:30:56 2015
*mangle
:PREROUTING ACCEPT [2424:210831]
:INPUT ACCEPT [2424:210831]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [1856:540218]
:POSTROUTING ACCEPT [1856:540218]
COMMIT
# Completed on Fri Dec  4 04:30:56 2015
# Generated by iptables-save v1.4.21 on Fri Dec  4 04:30:56 2015
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [581:184073]
- -A INPUT -i lo -j ACCEPT
- -A INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
- -A INPUT -p tcp -m tcp --dport 80 -j ACCEPT
- -A INPUT -p tcp -m tcp --dport 443 -j ACCEPT
- -A INPUT -p tcp -m tcp --dport 9052 -j ACCEPT
- -A INPUT -p tcp -m tcp --dport 9051 -j ACCEPT
- -A INPUT -p tcp -m tcp --dport 9001 -j ACCEPT
- -A INPUT -p tcp -m tcp --dport 9030 -j ACCEPT
- -A INPUT -p tcp -m tcp --dport 22 -j ACCEPT
- -A INPUT -j DROP
COMMIT
# Completed on Fri Dec  4 04:30:56 2015


> 3:/etc/network$ cat interfaces # This configuration file is
> auto-generated. # # WARNING: Do not edit this file, your changes
> will be lost. # Please create/edit /etc/network/interfaces.head
> and # /etc/network/interfaces.tail instead, their contents will be 
> # inserted at the beginning and at the end of this file,
> respectively. # # NOTE: it is NOT guaranteed that the contents of
> /etc/network/interfaces.tail # will be at the very end of this
> file. #
> 
> # Auto generated lo interface auto lo iface lo inet loopback
> 
> # Auto generated venet0 interface auto venet0 iface venet0 inet
> manual up ifconfig venet0 up up ifconfig venet0 127.0.0.2 up route
> add default dev venet0 down route del default dev venet0 down
> ifconfig venet0 down
> 
> 
> iface venet0 inet6 manual up route -A inet6 add default dev venet0 
> down route -A inet6 del default dev venet0
> 
> auto venet0:0 iface venet0:0 inet static address 167.114.35.28 
> netmask 255.255.255.255

> cat sysctl.conf

> # Uncomment the next line to enable packet forwarding for IPv4 
> net.ipv4.ip_forward=1
> 
> # Uncomment the next line to enable packet forwarding for IPv6 #
> Enabling this option disables Stateless Address Autoconfiguration #
> based on Router Advertisements for this host 
> net.ipv6.conf.all.forwarding=1

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWY4QyAAoJEJQqkaGlFNDPpiEH/jpcbG8GurVjOsSDneOQvKU3
o9cY536TmP2J8+t+JgTfG5KVm/lL1jzBT6/NE62xkWMPrrrdRGx4mLLJJ+AKjTdJ
t+89gBgBdtBfaWtGu29XcgXh/wbWB9EDMZgkKi2iSh9CEVMC5uTZKPXtzslUl6Rk

Re: [tor-relays] Unbelieveable

2015-12-05 Thread ZEROF 
Just build new torrc, that fixed my issue.

cd /etc/tor/
cp torrc torrc.bak
touch torrc

Use this for torrc (nano torrc), replace some info to match your relay

http://0bin.net/paste/tdUuzTHwZI-BRWQy#JPmufzd+g0W0cx0WyB4g0iU12jU0WFpZRWtKVg6iDbS

When you are done:

sevice tor restart

Then,

sudo -u debian-tor arm

I use screen session for this.

On 5 December 2015 at 20:18, Kurt Besig  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 12/4/2015 8:25 PM, Damian Johnson wrote:
> > For what it's worth process permissions aren't at play here. Arm
> > is failing to talk with the control port - permissions could cause
> > us to be unable to read the authentication cookie, but that would
> > be a different message.
> >
> > Cheers! -Damian
> >
> >
> > On Fri, Dec 4, 2015 at 5:36 PM, Manager Bahia del Sol LLC
> >  wrote:
> >>
> >> No worries,
> >>
> >> Are you sure the user or group is debian_tor? The default is
> >> debian-tor in Ubuntu.
> >>
> >> If that isn't the problem,
> >>
> >> First I would be sure tor is actually running. top or top -u
> >> debian-tor The second will show if tor is actually running as the
> >> user you think it is.
> >>
> >> If it is, then see if it is listening on the control port sudo
> >> netstat -ntlp | grep LISTEN
> >>
> >> If it is I would suspect that either a firewall is blocking that
> >> port. If you have one running try shutting it down for a few
> >> minutes while you try to start arm.
> >>
> >> Or maybe it is a permissions issue where arm is not running as
> >> the same user as tor. You could try starting arm as root to see
> >> if it would start. But, do not run arm as root full time. Only
> >> try to start it as a test.
> >>
> >>
> >>
> >> -- Manager of Bahia del Sol LLC
> >>
> >>
> >> ___ tor-relays
> >> mailing list tor-relays@lists.torproject.org
> >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> >>
> > ___ tor-relays mailing
> > list tor-relays@lists.torproject.org
> > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> >
> > Dec 05 21:17:46.000 [notice] Your IP address seems to have changed
> > to 167.114.35.28 (METHOD=INTERFACE). Updating. Dec 05 21:17:46.000
> > [notice] Our IP Address has changed from 142.4.217.95 to
> > 167.114.35.28; rebuilding descriptor (source: METHOD=INTERFACE).
> > Dec 05 21:18:42.000 [notice] Your IP address seems to have changed
> > to 142.4.217.95 (METHOD=GETHOSTNAME HOSTNAME=ca3.pulseservers.com).
> > Updating. Dec 05 21:18:42.000 [notice] Our IP Address has changed
> > from 167.114.35.28 to 142.4.217.95; rebuilding descriptor (source:
> > METHOD=GETHOSTNAME HOSTNAME=ca3.pulseservers.com). Dec 05
> > 21:18:43.000 [notice] Self-testing indicates your ORPort is
> > reachable from the outside. Excellent. Publishing server
> > descriptor. Dec 05 21:38:37.000 [warn] Your server
> > (142.4.217.95:9030) has not managed to confirm that its DirPort is
> > reachable. Please check your firewalls, ports, address, /etc/hosts
> > file, etc. Dec 05 21:58:37.000 [warn] Your server
> > (142.4.217.95:9030) has not managed to confirm that its DirPort is
> > reachable. Please check your firewalls, ports, address, /etc/hosts
> > file, etc.
> I've gotten this far, not being much good at networking I can't tell
> where the problem lies.. do I need to forward something?
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.22 (MingW32)
>
> iQEcBAEBAgAGBQJWYzh6AAoJEJQqkaGlFNDPCeYIAJln5C5Z+7n69zcoW1/RdUxi
> iduyKB/lnXc1Be190dSsHikjXVWv2hYvbnwvn3RuGOAft29WHd/OJi+GK9qBAB57
> qdL+sl4PvlJVlWYH8hDK65FHqmZ85UYRX0nP5KsvRLbzKlNiX1rGSJPfpVSeOlK8
> 2bvSG/b4+Y4ZqmlxmLyJW5eJnMMzOHJdTf/OgUefnqic5KB1BLXygFi566lYYNMC
> d8R8RObw8Rez/9H4+cKXcbNfnN2Yh0RMwpHF8nqpU8D292kO+Koz/xhfsu9VXRfe
> DBKhCSfKdDJBNiP0zI13Y1OB5tq4SG0sKhhGCCavW+3oelT2ujyTBgB4xAyszkY=
> =U+4y
> -END PGP SIGNATURE-
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>



-- 
http://www.backbox.org
http://www.pentester.iz.rs
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Unbelieveable

2015-12-04 Thread AMuse 
 

Looks like you got more than you paid for. 

On 2015-12-03 18:46, Kurt Besig wrote: 

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> That I got two responses after posting to tor-relays regarding a
> fairly simple, I thought, CntrolPort question on a new VPS relay..
> That's pathetic. Thanks for all your input.
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.22 (MingW32)
> 
> iQEcBAEBAgAGBQJWYP6FAAoJEJQqkaGlFNDPTCUIAKGRC9/XUKeBLrhIlXUrZd03
> oTiWdNJebmCRJ55gXbXv+2VxwM18YipkkwEIRmxrSdUsvzn2zRZ11FOnv1Yi8tFY
> oiD8HgqLVe6pcDepslPPe/SJyMz6tIqBnosYG6yADOpYCXRR22ehRlPQHkdg2kZ+
> ePBWJwDVop8WXUDwgAxRFd/jp/WWjLRt90bgHpcupEzbGi7GMTvNbftHEBeJvhwc
> g1xp5gZlvBgCT8Kb03dXQCUaYQ8hpjc9zbo4sQwnJNOZpyU6ftLdsoODa8NRW73s
> bslUj6EjQ5P2+tC2d9Q7s669XpLoxipJm1QiYVqFPIfLo48F4GjW1r64SKBxHVw=
> =mddV
> -END PGP SIGNATURE-
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays [1]

 

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

Re: [tor-relays] Unbelieveable

2015-12-04 Thread mick 
On Fri, 04 Dec 2015 09:29:58 -0800
AMuse  allegedly wrote:

>  
> 
> Looks like you got more than you paid for. 
> 
> On 2015-12-03 18:46, Kurt Besig wrote: 
> 
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> > 
> > That I got two responses after posting to tor-relays regarding a
> > fairly simple, I thought, CntrolPort question on a new VPS relay..
> > That's pathetic. Thanks for all your input.
>

+1 to that.

People on this list are all volunteers - both as relay operators and as
list participants. If any of those volunteers choose to help fellow
list members, then good for them. However, if list posters whine and
castigate others then they should not be surprised if no-one helps in
future.

Mick  
 

-

 Mick Morgan
 gpg fingerprint: FC23 3338 F664 5E66 876B  72C0 0A1F E60B 5BAD D312
 http://baldric.net

-



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

Re: [tor-relays] Unbelieveable

2015-12-04 Thread tor-server-creator 

 
Am Freitag, 4. Dezember 2015 08:57 schrieb Josef 'veloc1ty' Stautner 
:

 

Have you restarted
Tor after you made changes?
 
Yes. After ive done changes i always restart the Server hard. Tor is 
Running As Daemon so hours after restart i just do a check at 
atlas.torproject.org if its up ~ usually it is, so just fine


dont hesitate to ask but dont expect a answer here. join irc or your 
local kind community.

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

Re: [tor-relays] Unbelieveable

2015-12-04 Thread AMuse 
 

Are you aware that you just wrote "write that sort of retort privately"
by not, yourself, writing your retort privately? 

As to why I published my original reply to the list, it's because I felt
that other lurkers who are perhaps newbies to how open source support
listservs work might also benefit from the lesson. 

On 2015-12-04 13:22, I wrote: 

> write that sort of retort privately

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

Re: [tor-relays] Unbelieveable

2015-12-04 Thread I 




write that sort of retort privately
 -Original Message-From: tor-am...@foofus.comSent: Fri, 04 Dec 2015 10:33:03 -0800To: tor-relays@lists.torproject.orgSubject: Re: [tor-relays] Unbelieveable
Believe it or not, Kurt, if you'd asked in your follow-up in anything resembling a nice or appreciative tone, I'd have helped you.  I'm on too many email lists and things get buried sometimes, so I didn't see any of your original requests.  I had a few minutes today where I could have chatted with you on IRC and worked things out, maybe.
Instead I gave you a pithy short reply, because that's all your attitude deserves.
Take it as a life lesson (or not, I don't really care that much) but you'll get a lot more support from people if you don't act like an entitled jerk who deserves other peoples' time and expertise for free.
 
On 2015-12-04 10:21, Kurt Besig wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/4/2015 9:29 AM, AMuse wrote:
Looks like you got more than you paid for. On 2015-12-03 18:46, Kurt Besig wrote: That I got two responses after posting to tor-relays regarding a fairly simple, I thought, CntrolPort question on a new VPS relay.. That's pathetic. Thanks for all your input.
Yeah, that's the kind of useful answer that has made this list so
popular...thanks for the response. >>
___

tor-relays mailing list tor-relays@lists.torproject.org <mailto:tor-relays@lists.torproject.org> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWYdmyAAoJEJQqkaGlFNDP8D0IAL8sX+r3T6QUKIMP/+fKKgF3
CVARI2JMo6LN2/WTdPvZxe7Bky1d5zfWqkicLzjVTbY8E9O1EsCd1ZIvNAYIDp82
UfFo4hgBxT0aFTd6ViXIbBTBMifszN4/XRlhg8U4wuNKUlSE9tIPODCSC4Pm645A
+vLBMO9nmsiZiAhSUrqF2lqViobL/aj1FR6nShi8GTN/JMc/udHYevi5GT4BRW/0
VTIta2Qz9JU+OUb1dTYvr/K43yotPleQXttt4uyWnBzFVFfRQ8JQ1uG/TL4mm3Eg
AeRoLSHryN/X5UhEtyLuN78uQ53FCDLaun9n5ZzXPeWA62Dyjzb1SNZixRiBn20=
=W5X6
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


 
 





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

Re: [tor-relays] Unbelieveable

2015-12-04 Thread Michael McConville 
David Schulz wrote:
> Am 04.12.2015 20:12, schrieb Michael McConville:
> >I suspect you're also getting few replies because relatively few
> >experienced relay operators use arm. That's only a guess, but I found
> >arm a needless, breakable complication after the rush of running my
> >first relay wore off.
> >
> >It is fun to use and useful to beginners, though.  :-)  No disrespect to
> >the developers.
> 
> Do you got an alternative for arm? i use munin too, for connections etc.

Just the logs, these days.
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Unbelieveable

2015-12-04 Thread Michael McConville 
Michael McConville wrote:
> David Schulz wrote:
> > Am 04.12.2015 20:12, schrieb Michael McConville:
> > >I suspect you're also getting few replies because relatively few
> > >experienced relay operators use arm. That's only a guess, but I
> > >found arm a needless, breakable complication after the rush of
> > >running my first relay wore off.
> > >
> > >It is fun to use and useful to beginners, though.  :-)  No
> > >disrespect to the developers.
> > 
> > Do you got an alternative for arm? i use munin too, for connections
> > etc.
> 
> Just the logs, these days.

As someone else mentioned, I use general system tools (for OpenBSD:
systat, ifstat, pftop, lsof, etc.) for more complicated diagnoses.
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Unbelieveable

2015-12-04 Thread Manager Bahia del Sol LLC 
 No worries,Are you sure the user or group is debian_tor?The default is debian-tor in Ubuntu.If that isn't the problem,First I would be sure tor is actually running.toportop -u debian-torThe second will show if tor is actually running as the user you think it is.If it is, then see if it is listening on the control portsudo netstat -ntlp | grep LISTENIf it is I would suspect that either a firewall is blocking that port. If you have one runningtry shutting it down for a few minutes while you try to start arm.Or maybe it is a permissions issue where arm is not running as the same user as tor. You could try starting arm as rootto see if it would start. But, do not run arm as root full time. Only try to start it as a test.   --  Manager of Bahia del Sol LLC ___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Unbelieveable

2015-12-04 Thread Damian Johnson 
For what it's worth process permissions aren't at play here. Arm is
failing to talk with the control port - permissions could cause us to
be unable to read the authentication cookie, but that would be a
different message.

Cheers! -Damian


On Fri, Dec 4, 2015 at 5:36 PM, Manager Bahia del Sol LLC
 wrote:
>
> No worries,
>
> Are you sure the user or group is debian_tor?
> The default is debian-tor in Ubuntu.
>
> If that isn't the problem,
>
> First I would be sure tor is actually running.
> top
> or
> top -u debian-tor
> The second will show if tor is actually running as the user you think it is.
>
> If it is, then see if it is listening on the control port
> sudo netstat -ntlp | grep LISTEN
>
> If it is I would suspect that either a firewall is blocking that port. If
> you have one running
> try shutting it down for a few minutes while you try to start arm.
>
> Or maybe it is a permissions issue where arm is not running as the same user
> as tor. You could try starting arm as root
> to see if it would start. But, do not run arm as root full time. Only try to
> start it as a test.
>
>
>
> --
>  Manager of Bahia del Sol LLC
>
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Unbelieveable

2015-12-04 Thread AMuse 
 

Believe it or not, Kurt, if you'd asked in your follow-up in anything
resembling a nice or appreciative tone, I'd have helped you. I'm on too
many email lists and things get buried sometimes, so I didn't see any of
your original requests. I had a few minutes today where I could have
chatted with you on IRC and worked things out, maybe. 

Instead I gave you a pithy short reply, because that's all your attitude
deserves. 

Take it as a life lesson (or not, I don't really care that much) but
you'll get a lot more support from people if you don't act like an
entitled jerk who deserves other peoples' time and expertise for free. 

On 2015-12-04 10:21, Kurt Besig wrote: 

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> On 12/4/2015 9:29 AM, AMuse wrote:
> 
>> Looks like you got more than you paid for. On 2015-12-03 18:46, Kurt Besig 
>> wrote: That I got two responses after posting to tor-relays regarding a 
>> fairly simple, I thought, CntrolPort question on a new VPS relay.. That's 
>> pathetic. Thanks for all your input.
> 
> Yeah, that's the kind of useful answer that has made this list so
> popular...thanks for the response. >>
> ___
> tor-relays mailing list tor-relays@lists.torproject.org 
>  
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays [1] 
> ___ tor-relays mailing list 
> tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays [1]

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWYdmyAAoJEJQqkaGlFNDP8D0IAL8sX+r3T6QUKIMP/+fKKgF3
CVARI2JMo6LN2/WTdPvZxe7Bky1d5zfWqkicLzjVTbY8E9O1EsCd1ZIvNAYIDp82
UfFo4hgBxT0aFTd6ViXIbBTBMifszN4/XRlhg8U4wuNKUlSE9tIPODCSC4Pm645A
+vLBMO9nmsiZiAhSUrqF2lqViobL/aj1FR6nShi8GTN/JMc/udHYevi5GT4BRW/0
VTIta2Qz9JU+OUb1dTYvr/K43yotPleQXttt4uyWnBzFVFfRQ8JQ1uG/TL4mm3Eg
AeRoLSHryN/X5UhEtyLuN78uQ53FCDLaun9n5ZzXPeWA62Dyjzb1SNZixRiBn20=
=W5X6
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays [1]

 

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

Re: [tor-relays] Unbelieveable

2015-12-04 Thread Kurt Besig 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/4/2015 9:29 AM, AMuse wrote:
> Looks like you got more than you paid for.
> 
> 
> 
> On 2015-12-03 18:46, Kurt Besig wrote:
> 
> That I got two responses after posting to tor-relays regarding a 
> fairly simple, I thought, CntrolPort question on a new VPS relay.. 
> That's pathetic. Thanks for all your input.
Yeah, that's the kind of useful answer that has made this list so
popular...thanks for the response. >>
___
>> tor-relays mailing list tor-relays@lists.torproject.org
>>  
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
> 
> 
> 
> 
> 
> ___ tor-relays mailing
> list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWYdmyAAoJEJQqkaGlFNDP8D0IAL8sX+r3T6QUKIMP/+fKKgF3
CVARI2JMo6LN2/WTdPvZxe7Bky1d5zfWqkicLzjVTbY8E9O1EsCd1ZIvNAYIDp82
UfFo4hgBxT0aFTd6ViXIbBTBMifszN4/XRlhg8U4wuNKUlSE9tIPODCSC4Pm645A
+vLBMO9nmsiZiAhSUrqF2lqViobL/aj1FR6nShi8GTN/JMc/udHYevi5GT4BRW/0
VTIta2Qz9JU+OUb1dTYvr/K43yotPleQXttt4uyWnBzFVFfRQ8JQ1uG/TL4mm3Eg
AeRoLSHryN/X5UhEtyLuN78uQ53FCDLaun9n5ZzXPeWA62Dyjzb1SNZixRiBn20=
=W5X6
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Unbelieveable

2015-12-04 Thread Kurt Besig 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/4/2015 10:33 AM, AMuse wrote:
> Believe it or not, Kurt, if you'd asked in your follow-up in
> anything resembling a nice or appreciative tone, I'd have helped
> you.  I'm on too many email lists and things get buried sometimes,
> so I didn't see any of your original requests.  I had a few minutes
> today where I could have chatted with you on IRC and worked things
> out, maybe.
> 
> Instead I gave you a pithy short reply, because that's all your
> attitude deserves.
> 
> Take it as a life lesson (or not, I don't really care that much)
> but you'll get a lot more support from people if you don't act like
> an entitled jerk who deserves other peoples' time and expertise for
> free.
> 
> 
> 
> On 2015-12-04 10:21, Kurt Besig wrote:
> 
> On 12/4/2015 9:29 AM, AMuse wrote:
 Looks like you got more than you paid for. On 2015-12-03
 18:46, Kurt Besig wrote: That I got two responses after
 posting to tor-relays regarding a fairly simple, I thought,
 CntrolPort question on a new VPS relay.. That's pathetic.
 Thanks for all your input.
> Yeah, that's the kind of useful answer that has made this list so 
> popular...thanks for the response. >> 
> ___
> tor-relays mailing list tor-relays@lists.torproject.org 
>  
>  > 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

> 
___ tor-relays mailing
 list tor-relays@lists.torproject.org 
  
 https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>>
 
___
>> tor-relays mailing list tor-relays@lists.torproject.org
>>  
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
> 
> 
> 
> You're right, I have been too hasty in my negative responses
to this list's subscribers. For that I do apologize to everyone. I too
am nothing more than a volunteer relay operator like most here and as
such have no special privileges or power to "force" anyone's response.
In  hindsight I realize that. Unfortunately living in this fast paced
society of entitlement it's easy to occasionally get caught up in it,
again, for that I am sorry.
> 
> ___ tor-relays mailing
> list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWYd14AAoJEJQqkaGlFNDPSZIIAMPMhePI3zEdxEbeAH7g7SWB
tAsMyesHOfSu4T8m1pHK/ia/fYfIbEBsMhrRPSvjJGJi6qtVRflcMtScvsxRJ49g
4lv5KAcZfUx+coT3XAzK2Cv69LADNsME0sJLME8STH3ZHszo48T4Uv3ZV3hZQuSv
K5cUQ8OHyradfTVHjLQYXSJmjlVRvpqUfN2ingUX8f4Z52K9onT/rVvLjlHoj7iS
/2euRiIGAoNgn7qriaG9hOIMgCg/CChw1CD1lQ4zj/hPKd8cqisD5SGpmPvVMP7j
iRcWh1hFR+7aklJXBr3+3qWUM5WGpDzqc885rLSecSZIt6PJBJVgdagBW+UOXeU=
=zaHm
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Unbelieveable

2015-12-04 Thread Josef Stautner 
He is right.
Do you want help now or what?

Am 04.12.2015 um 19:21 schrieb Kurt Besig:
> On 12/4/2015 9:29 AM, AMuse wrote:
> > Looks like you got more than you paid for.
>
>
>
> > On 2015-12-03 18:46, Kurt Besig wrote:
>
> > That I got two responses after posting to tor-relays regarding a
> > fairly simple, I thought, CntrolPort question on a new VPS relay..
> > That's pathetic. Thanks for all your input.
> Yeah, that's the kind of useful answer that has made this list so
> popular...thanks for the response. >>
> ___
> >> tor-relays mailing list tor-relays@lists.torproject.org
> >> 
> >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
>
>
>
>
>
> > ___ tor-relays mailing
> > list tor-relays@lists.torproject.org
> > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
>
> ___ > tor-relays mailing list > 
> tor-relays@lists.torproject.org >
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


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

Re: [tor-relays] Unbelieveable

2015-12-04 Thread Michael McConville 
I suspect you're also getting few replies because relatively few
experienced relay operators use arm. That's only a guess, but I found
arm a needless, breakable complication after the rush of running my
first relay wore off.

It is fun to use and useful to beginners, though.  :-)  No disrespect to
the developers.
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Unbelieveable

2015-12-04 Thread David Schulz 

Do you got an alternative for arm? i use munin too, for connections etc.

Am 04.12.2015 20:12, schrieb Michael McConville:

I suspect you're also getting few replies because relatively few
experienced relay operators use arm. That's only a guess, but I found
arm a needless, breakable complication after the rush of running my
first relay wore off.

It is fun to use and useful to beginners, though.  :-)  No disrespect 
to

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


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

Re: [tor-relays] Unbelieveable

2015-12-04 Thread Roman Mamedov 
On Fri, 04 Dec 2015 20:15:18 +0100
David Schulz  wrote:

> Do you got an alternative for arm? i use munin too, for connections etc.

"For connections"? Why do you ever need to view the actual connections from/to
your relay.

As alternatives to arm, when looking after a relay that's spinning up, I use
'nload' and 'top', and for the longer term monitoring I have a small script
which periodically mails me outputs of 'vnstat' hourly/daily/monthly reports
running from crontab.

-- 
With respect,
Roman


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

Re: [tor-relays] Unbelieveable

2015-12-03 Thread k0nsl 
Hi,
It's difficult to nail down without any actual information to go on.
It's sort of like saying "my back hurts" and asking people what may have
caused it to hurt. You'll get a few random answers, at best.
-k0nsl

Den 12/4/2015 kl. 3:46 AM, skrev Kurt Besig:
> That I got two responses after posting to tor-relays regarding a
> fairly simple, I thought, CntrolPort question on a new VPS relay..
> That's pathetic. Thanks for all your input.
> ___ > tor-relays mailing list > 
> tor-relays@lists.torproject.org >
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >

-- 
This e-mail message may contain confidential or legally privileged
information and is intended only for the use of the intended
recipient(s). Any unauthorized disclosure, dissemination, distribution,
copying or the taking of any action in reliance on the information
herein is prohibited.



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

Re: [tor-relays] Unbelieveable

2015-12-03 Thread Kurt Besig 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/3/2015 7:11 PM, k0nsl wrote:
> Hi, It's difficult to nail down without any actual information to 
> go on. It's sort of like saying "my back hurts" and asking people 
> what may have caused it to hurt. You'll get a few random answers, 
> at best. -k0nsl
> 
> Den 12/4/2015 kl. 3:46 AM, skrev Kurt Besig:
>> That I got two responses after posting to tor-relays regarding a
>>  fairly simple, I thought, CntrolPort question on a new VPS 
>> relay.. That's pathetic. Thanks for all your input. 
>> ___ > tor-relays 
>> mailing list > tor-relays@lists.torproject.org >
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >
> 
> -- This e-mail message may contain confidential or legally 
> privileged information and is intended only for the use of the 
> intended recipient(s). Any unauthorized disclosure, dissemination, 
> distribution, copying or the taking of any action in reliance on 
> the information herein is prohibited.
> 
> 
> 
> ___ tor-relays mailing 
> list tor-relays@lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
Well. even a doctor would make a few suggestions based on some sort of
experience based reasoning. Perhaps some connection problems
associated with running tor-arm on a VPS vs. a home server...things of
that nature. Also I was just wondering as I don't see many of the
relay operators that used to post to this list around anymore, has
something changed to make them move on??
Lots of people whining about their consensus weight numbers, but
little of substance being posted.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWYQv1AAoJEJQqkaGlFNDP4d4H/iSOTYsEa3Q+Kj5BIREOY+Ka
KsoplgYbVPbUxg9x37BD88p7+02YMKlwhEW5sMemd/+ySC9IsXhsdfxXrRaE+SZk
tm6+Wd2FoZBDoYem5e87PNo1fBuOE4aBgS3XNBuA2H6FZRpNpY8asOB4YlJdxy66
83aTDB43gRqkHpONgyBcYnhOuOt6L9CiZyXkJqtLpgYAtvmwv82MRYMU72PHsLjE
Dzh+tj4o+FnsDVgC5nnk4yPXyeStMMQLdx51IuamTvji7n/JJD+HQmc94wTq1ocI
AW3GCoeAId7XNtpkVgtfT1lVIS8D177edQHbGAjSIEEE3E+QVhizvSWtBU1i13w=
=/kbu
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Unbelieveable

2015-12-03 Thread Josef 'veloc1ty' Stautner 
Yeah I see the probleme: Your didn't provide any Config extract nor logs
nor other stuff like that.
Provide your config to see if you made an unix socket or a network
socket or if you set any password. If you set up a network listener
please provide netstat output. Maybe a dumb question: Have you restarted
Tor after you made changes?

Provide information that the community can analyze. Just whining won't help.

~Josef

Am 04.12.2015 um 06:07 schrieb I:
>> Also I was just wondering as I don't see many of the
>> relay operators that used to post to this list around anymore, has
>> something changed to make them move on??
>> Lots of people whining about their consensus weight numbers, but
>> little of substance being posted.
> Well, for me it is obvious. This list is a massive disappointment so I don't 
> wonder why it's quiet.
>
> I thought I was joining a loose but passionate, clever and idealistic 
> community.
> I thought I would learn just being a listener and building my knowledge of 
> security and servers.
>
> In nearly four years I've learned little except not to post unless I'm able 
> to cope with a smack from out of the blue for not knowing.
>
>
>
>
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays




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

Re: [tor-relays] Unbelieveable

2015-12-03 Thread Michael McConville 
Kurt Besig wrote:
> Well. even a doctor would make a few suggestions based on some sort of
> experience based reasoning. Perhaps some connection problems
> associated with running tor-arm on a VPS vs. a home server...things of
> that nature. Also I was just wondering as I don't see many of the
> relay operators that used to post to this list around anymore, has
> something changed to make them move on??
> Lots of people whining about their consensus weight numbers, but
> little of substance being posted.

The people who know what they're doing can quickly, reliably
set-and-forget relays. That's the ideal scenario - tweaking knobs is
mostly a liability and performance issues are a development concern.
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] Unbelieveable

2015-12-03 Thread Kurt Besig 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

That I got two responses after posting to tor-relays regarding a
fairly simple, I thought, CntrolPort question on a new VPS relay..
That's pathetic. Thanks for all your input.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJWYP6FAAoJEJQqkaGlFNDPTCUIAKGRC9/XUKeBLrhIlXUrZd03
oTiWdNJebmCRJ55gXbXv+2VxwM18YipkkwEIRmxrSdUsvzn2zRZ11FOnv1Yi8tFY
oiD8HgqLVe6pcDepslPPe/SJyMz6tIqBnosYG6yADOpYCXRR22ehRlPQHkdg2kZ+
ePBWJwDVop8WXUDwgAxRFd/jp/WWjLRt90bgHpcupEzbGi7GMTvNbftHEBeJvhwc
g1xp5gZlvBgCT8Kb03dXQCUaYQ8hpjc9zbo4sQwnJNOZpyU6ftLdsoODa8NRW73s
bslUj6EjQ5P2+tC2d9Q7s669XpLoxipJm1QiYVqFPIfLo48F4GjW1r64SKBxHVw=
=mddV
-END PGP SIGNATURE-
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays