Re: [tor-relays] Relay C19B33758B3A5144894233EC4C95D7985B9FD101

2019-04-08 Thread ylms
On 4/5/19 10:58 AM, ylms wrote: > "[WARN] Error binding network socket: Address already in use [991 > duplicates hidden]" > > I did use a search engine, but am not sure what too look for further. > Also let me know if I should not worry at all. > > 991 warnings are probably since tor is

Re: [tor-relays] Relay C19B33758B3A5144894233EC4C95D7985B9FD101

2019-04-08 Thread ylms
On 4/5/19 6:16 PM, li...@for-privacy.net wrote: > Hint for ylms: Socks 0 + reject in the torrc config. > > SocksPort 0 > SocksPolicy reject * I think the latter is not needed because I did set "SocksPort 0" now, then reloaded the config and got this: 09:06:52 [NOTICE] Closing

Re: [tor-relays] Relay C19B33758B3A5144894233EC4C95D7985B9FD101

2019-04-08 Thread ylms
On 4/5/19 5:31 PM, li...@for-privacy.net wrote: > Am 05.04.2019 10:58, schrieb ylms: > >> can someone point me at some information about this warning? >> >> "[WARN] Error binding network socket: Address already in use  [991 >> duplicates hidden]" > > Log message is clear: > You have assigned a

Re: [tor-relays] Relay C19B33758B3A5144894233EC4C95D7985B9FD101

2019-04-08 Thread ylms
On 4/5/19 12:36 PM, torg...@linux-hus.dk wrote: > hi, the adress is in use check what is running on your system and check > also the ports sudo lsof -i -P -n | grep LISTEN does not show any ports used twice for the same address. yl ___ tor-relays

Re: [tor-relays] Relay C19B33758B3A5144894233EC4C95D7985B9FD101

2019-04-05 Thread lists
Am 05.04.2019 17:59, schrieb Neel Chauhan: One thing that could happen (but may not apply to you) is your SOCKSPort. Set it to 0 to not listen, or to a random number if you have to listen for SOCKS connections. Hint for ylms: Socks 0 + reject in the torrc config. SocksPort 0 SocksPolicy

Re: [tor-relays] Relay C19B33758B3A5144894233EC4C95D7985B9FD101

2019-04-05 Thread Neel Chauhan
On 2019-04-05 11:31, li...@for-privacy.net wrote: Am 05.04.2019 10:58, schrieb ylms: can someone point me at some information about this warning? "[WARN] Error binding network socket: Address already in use [991 duplicates hidden]" Log message is clear: You have assigned a port number

Re: [tor-relays] Relay C19B33758B3A5144894233EC4C95D7985B9FD101

2019-04-05 Thread lists
Am 05.04.2019 10:58, schrieb ylms: can someone point me at some information about this warning? "[WARN] Error binding network socket: Address already in use [991 duplicates hidden]" Log message is clear: You have assigned a port number twice. Either two Tor-instances run on the same (TCP)

Re: [tor-relays] Relay C19B33758B3A5144894233EC4C95D7985B9FD101

2019-04-05 Thread ylms
Hello again, can someone point me at some information about this warning? "[WARN] Error binding network socket: Address already in use [991 duplicates hidden]" I did use a search engine, but am not sure what too look for further. Also let me know if I should not worry at all. 991 warnings are

Re: [tor-relays] Relay C19B33758B3A5144894233EC4C95D7985B9FD101

2019-03-12 Thread ylms
On 3/11/19 11:54 PM, teor wrote: > We would like to make tor more helpful, and make it guess IPv6. > But we're not there yet. > > Until then, people have to learn the details of tor's config For relays on dynamic ADSL lines it would be helpful to provide the static host part of an /56 or /64

Re: [tor-relays] Relay C19B33758B3A5144894233EC4C95D7985B9FD101

2019-03-12 Thread Volker Mink
There are a lot. Keyweb for example, exone in poland   Yeah, as said it is not a new relay, just lost the old one. But I would like to add a new one, just finding a useful Germany hoster is not easy to find.   ___ tor-relays mailing list

Re: [tor-relays] Relay C19B33758B3A5144894233EC4C95D7985B9FD101

2019-03-11 Thread teor
Hi, > On 12 Mar 2019, at 05:34, ylms wrote: > >> On 3/9/19 5:07 AM, teor wrote: >> ORPort [IPv6]:Port >> >> For example: >> >> ORPort [2001:db8::1]:9001 >> >> Tor doesn't guess IPv6 addresses yet. > > That was very helpful to find my stupid mistake. We would like to make tor more helpful,

Re: [tor-relays] Relay C19B33758B3A5144894233EC4C95D7985B9FD101

2019-03-11 Thread ylms
Hello teor, On 3/9/19 5:07 AM, teor wrote: > ORPort [IPv6]:Port > > For example: > > ORPort [2001:db8::1]:9001 > > Tor doesn't guess IPv6 addresses yet. That was very helpful to find my stupid mistake. thanks. yl ___ tor-relays mailing list

Re: [tor-relays] Relay C19B33758B3A5144894233EC4C95D7985B9FD101

2019-03-11 Thread ylms
Hello Roger, thanks for you reply. On 3/9/19 4:08 AM, Roger Dingledine wrote: > On Fri, Mar 08, 2019 at 03:52:48PM +0100, ylms wrote: >> Hello, >> I just setup a new exit, I know it takes time to "train", but I would be >> interested in tips on how to tweak it. >> I just replaces a old exit that

Re: [tor-relays] Relay C19B33758B3A5144894233EC4C95D7985B9FD101

2019-03-08 Thread teor
Hi, > On 9 Mar 2019, at 13:08, Roger Dingledine wrote: > >> I also have some questions. >> >> Atlas does not show any IPv6 address, is this normal? > > I see that you have an ipv6 exit policy set, but I don't see any > ipv6 address in your relay descriptor. > > (You can see your relay

Re: [tor-relays] Relay C19B33758B3A5144894233EC4C95D7985B9FD101

2019-03-08 Thread Roger Dingledine
On Fri, Mar 08, 2019 at 03:52:48PM +0100, ylms wrote: > Hello, > I just setup a new exit, I know it takes time to "train", but I would be > interested in tips on how to tweak it. > I just replaces a old exit that used the same IP, but unfortunately we > lost that config/key. > > So any tips are

[tor-relays] Relay C19B33758B3A5144894233EC4C95D7985B9FD101

2019-03-08 Thread ylms
Hello, I just setup a new exit, I know it takes time to "train", but I would be interested in tips on how to tweak it. I just replaces a old exit that used the same IP, but unfortunately we lost that config/key. So any tips are welcome in general. I also have some questions. Atlas does not show