secureh...@gmail.com wrote on 8/4/23 01:46:
I tried reporting a similar issue a few months ago (post wasn’t approved by
moderator). I was running a relay from my home ISP. After a short while
certain websites became inaccessible from other computers in my home network
that shared the same public
toritdown via tor-relays wrote on 8/22/22 23:49:
I am suddenly finding numerous entries in my /var/log/tor/notices log that look
like this:
Aug 22 01:21:46.000 [warn] Unable to store router descriptor
Aug 22 01:21:46.000 [warn] Error writing to
"/var/lib/tor/cached-descriptors.new": No space
Roger Dingledine wrote on 5/24/22 02:44:
On Mon, May 23, 2022 at 12:18:41PM +0200, Marco Predicatori wrote:
the graph shows a marked difference between written bytes per second and
read bytes per second om 2022-05-19 and 2022-05-20. In any other day the
bytes are roughly the same. What might my
Hi,
the graph shows a marked difference between written bytes per second and read
bytes per second om 2022-05-19 and 2022-05-20. In any other day the bytes are
roughly the same. What might my node have "written" on those two days?
Eddie wrote on 8/1/21 7:31 PM:
> On 7/29/2021 7:57 AM, Marco Predicatori wrote:
>> ...Many packets coming from other Tor nodes where dropped. The Tor log
>> doesn't
>> mention
>> any problem. What may be wrong?
>>
>> --
>
> Not that it helps any, but
Hi, my Tor node is inside a local network protected by a firewall. Only port
9001
is NATted towards the Tor server.
Moreover, I have iptables active on the Tor server itself. The outer firewall
blocks any incoming packet except for packets on port 9001 and returning packets
from established
Marco Predicatori wrote on 6/10/21 10:12 AM:
> Hi,
>
> whenever my IP changes, my node stops relaying traffic, and after a few hours
> I
> see in the logs
> [notice] Heartbeat: It seems like we are not in the cached consensus.
>
> In past versions I remember seeing in
Hi,
whenever my IP changes, my node stops relaying traffic, and after a few hours I
see in the logs
[notice] Heartbeat: It seems like we are not in the cached consensus.
In past versions I remember seeing in the logs something like "...your ip seems
to have changed...", followed by a new
David Goulet wrote on 3/24/21 1:18 PM:
> Oops.. this fell off my radar, mis-placed in my Inbox :(
Thanks David, no problem.
9 days now of flawless Tor running.
Bye, Marco
signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing
s7r wrote on 3/11/21 6:16 PM:
> I only find this log message unclear:
>
> [notice] Unable to find IPv6 address for ORPort 9001. You might want to
> specify
> IPv6Only to it or set an explicit address or set Address.
>
> I think it means "... You might want to specify *IPv4Only* to it or set it
William Kane wrote on 3/11/21 6:36 PM:
> @s7r:
>
> You are right, I did not read his torrc.
>
> Relays on randomly rotated (most ISP's have adopted a 24 hour lease
> model) IP addresses are disruptive to long term connections anyway
> (this is partially mitigated by not assigning them the stable
potlatch wrote on 3/11/21 12:42 AM:
> They specifically state the ban was for:
> Providing *file sharing services or access to newsgroups;*...
This is beyond ludicrous! Any ISP on the planet offers access to file sharing
and newsgroups. I stopped using Paypal many years a go, but in the age of
s7r wrote on 3/9/21 3:12 PM:
> Please paste your entire torrc (without any sensitive data of course).
> We have some slight misbehavior for the IPv6 auto discovery.
Here:
https://pastebin.com/9VEZD9Zw
> Along with the torrc please state if you have IPv6 of any kind to that box and
> if yes which
Hi,
I've recently upgraded to Tor 0.4.5.6. Everything seems to work fine, but in the
notices_log file I have a lot of these lines:
[notice] Unable to find IPv6 address for ORPort 9001. You might want to specify
IPv6Only to it or set an explicit address or set Address.
I don't have IPv6, and any
Андрей Гвоздев wrote on 9/21/20 11:19 AM:
> Hello
> I'm running a TOR relay, every time I SSH to my server I see a message
> that there were thousands of failed login attempts
> Do you see this message too?
Plenty, don't worry. Any IP with the ssh port open is targeted. Make sure you
keep your
Keifer Bly wrote on 30/06/2018 02:22:
> Hello,
>
> I am aware that email addresses used in the “ContactInfo: “ in a
> relay operator’s torrc file is publicly listed on the tor relay.
> However, what I am wondering, is there a way to obfuscate the
> email address on
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Toralf Förster wrote on 03/11/2016 11:39:
>> https://atlas.torproject.org/#details/A1D5528320F51B910C996CE9988FAFAF4780044F
>>
> Advertised Bandwidth
> 76.8 KB/s
>
> Not too much fun with such a lame relay I fear
Very little fun indeed, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Peter Palfrader wrote on 03/11/2016 09:59:
> Don't do short keyids. Long keyids are strictly better.
> Ideally, provide the full fingerprint.
Good advice. Done, thanks.
Marco
- --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
ane...@tutanota.de wrote on 03/11/2016 09:15:
> When I insert my PGP key just like a block of text below the
> contactinfo line my Tor relay stops working. What is the correct
> way to insert the PGP key into the torrc file?
ContactInfo has to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Juuso Lapinlampi wrote on 31/10/2016 14:25:
> Putting the word out: I was interrogated by the Finnish police...
All my support to you, for what it's worth. If you are running a Tor
node, don't give up. We, who live in relatively decent countries,
Too bad when a Tor node operator is intimidated out of his activity.
I understand your position, thank you for your efforts.
Marco
stig atle steffensen wrote on 01/08/2016 08:15:
> I decided today to turn the node into a non-exit node this morning.
> The stress of not knowing if something will
Green Dream wrote on 08/04/2016 01:54:
> As I already said, this particular case is not so clear cut. However
> letting the police poke around...
I didn't realize that Tor was against the police, or vice-versa, at
least in decent countries like yours or mine, so far. I don't think
it's a good
krishna e bera wrote on 07/04/2016 04:28:
> On 04/06/2016 04:29 AM, Marco Predicatori wrote:
>> krishna e bera wrote on 05/04/2016 23:27:
>>> On 04/05/2016 02:38 PM, grarpamp wrote:
>>>> http://www.npr.org/sections/alltechconsidered/2016/04/04/472992023/when-a-
Pavel Zhovner, on 06/28/2013 09:37 AM, wrote:
Yes, I was experienced the same issues with Skype.
Skype blocks connect's from tor network.
Same situation here.
--
http://www.predicatori.it/marco/
___
tor-relays mailing list
24 matches
Mail list logo
