Hi,
I've been running a Snowflake (the stand-alone Go-proxy kind build from source)
as a Debian service.
I was working fine before, showing a handful of anonymous connections per day.
Recently it shows a new log message: "NAT type: restricted" after "starting"
and I have not seen any new connec
My bridge was running fine, then started throwing the same error over and over.
See my last two days of logs here: https://pastebin.com/7FNXC6PZ. Function
doesn't seem to be affected as the heartbeats still show users.
Can or should I do anything about this?__
How do you define abusive traffic?
Do analyze dumps of your network traffic?
Is your ISP sending more abuse letters than usual?
If the latter, then it might just be a fluke - when I ran exits, the
same thing happened - one month 17 abuse reports, the other month
193.. nothing you can do about it
I am as well constantly getting emails about it from my ISP. As well as a few
companies... not sure why there ramping up. For now I setup a mail rule to
forward them to a different mailbox inside my email.
Thanks,
John Csuti
> On Jul 18, 2020, at 8:43 PM, John Ricketts wrote:
>
> All,
>
> I
On 7/18/20 10:45 AM, dmz21 wrote:
> Recently it shows a new log message:
Did you upgrde the sources before?
--
Toralf
signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torpr
# SERVER #1
# niftycastoroide
MyFamily $9EEDBAD7EE351996DFC91578E882BEF4FE5EDBFA
# niftyentry100
MyFamily $7ED3D8AFAC750F8CC0BDF8C87FE3BCBA2BBE2209
# niftyentry103
MyFamily $7226BE09B7A81000BBF7D959E360B2FE41CCC639
# niftyentry106
MyFamily $E6288334BC0F95345817811880DDEA184E63AE69
# niftyentry107
Low three-figures right now
HIgh would be in the low four-figures
Shit got real is middle four-figures
per day
nifty
> On 19. Jul 2020, at 02:36, John Ricketts wrote:
>
> All,
>
> I'm getting about 4x the abuse traffic that I normally get from running
> exits. Anyone else noticing this tre
Nos oignons' relays:
F47B 13BF CE4E F48C DEF6 C4D7 C7A9 9208 EBB9 72B5
8E6E DA78 D8E3 ABA8 8D87 7C3E 37D6 D4F0 938C 7B9F
90FD 830C 357A 5109 AB3C 5052 8771 3F1A C811 174C
578E 007E 5E45 35FB FEF7 758D 8587 B07B 4C8C 5D06
9BA8 4E8C 9008 3676 F86C 7427 C8D1 0592 5F13 716C
C656 B41A EFB4 0A14 1967
On Sunday, July 19, 2020 7:25 PM, Toralf Förster wrote:
> On 7/18/20 10:45 AM, dmz21 wrote:
>
> > Recently it shows a new log message:
>
> Did you upgrde the sources before?
I rebuild it from (an updated) default git branch before starting it every
time, which is sort of daily.
Not sure when th
Which you can answer with a template document, stating that you are
not responsible for the traffic and that you, as the ISP / network
provider are protected by law, and can not be held responsible for
data passing through your routers.
2020-07-19 4:41 GMT, John Ricketts :
> I have received more s
Hi all,
So my middel guard relay at
https://metrics.torproject.org/rs.html#details/79E3B585803DE805CCBC00C1EF36B1E74372861D
As well as my bridge at
https://metrics.torproject.org/rs.html#details/EF36AE38C162E96E0645E1DF25EF19522ADBAF90
Are not updating, though I had configured them to be updat
It is worth noting, tor conscious does not immediately update. It can take
40 minutes up to about 3 hours for an operating status update to appear in
the conscious based on my experience from the bridge and middle relay I run.
>> Your relay has a very large number of connections to other relays. I
12 matches
Mail list logo
