I am running a bridge, realseven, fingerprint
10B5293C71793DC1E56A5B17434C0539F70FBB38. It's been up for 71 days and has yet
to get the stable flag or more than 3 or 4 connected clients. Is there
something misconfigured?
~~~
No me preguntas nada, no te diré una m
Fixed it by installing from deb file.
-Original Message-
From: Dr Gerard Bulger
Sent: 21 February 2021 19:09
To: 'tor-relays@lists.torproject.org'
Subject: Nyx
Sorry if wrong forum
Nyx install out of the box, never had this error on starting before Ubuntu
18.04 Traceback (most recen
On 2/21/2021 7:16 PM, enrollado wrote:
I am running a bridge, realseven, fingerprint
10B5293C71793DC1E56A5B17434C0539F70FBB38. It's been up for 71 days and
has yet to get the stable flag or more than 3 or 4 connected clients.
Is there something misconfigured?
Bridges don't get the stable fla
Sorry if wrong forum
Nyx install out of the box, never had this error on starting before
Ubuntu 18.04
Traceback (most recent call last):
File "/usr/bin/nyx", line 11, in
load_entry_point('nyx==2.0.4', 'console_scripts', 'nyx')()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.
On 21.02.2021 12:12, Toralf Förster wrote:
Would an iptables ruel with "recent" and "limit" be a solution here ?
If yes, how do you use that (do you have a code snippet)?
Example SSH:
*filter
:INPUT DROP [0:0]
:FORWARD DROP [0:0]
:OUTPUT ACCEPT [0:0]
## Drop incoming connections which make m
niftybunny wrote:
> Glad to hear its nothing personal. Putin still loves me ??
>
> Thats Perl? I have no clue what it does.
>
> We already changed the timers on the TCP connections and we have scripts
> running which are blocking IPs who will send us x connections. Right now
> they changed
On 2/21/21 12:37 PM, niftybunny wrote:
If I get say 2 connections from a single IP it would be blocked with
iptables.
Even much less looks unusal
With this command
watch -d -x bash -c 'ss --all --numeric --processes state syn-recv |
sort -k 5 -n'
I do see a handful of addresses -
On 20 Feb (11:52:33), Manager wrote:
>Hello,
>
>im trying to enable prometheus metrics, and... something goes wrong:
>
>torrc:
>MetricsPort 9166
>MetricsPortPolicy accept *
>
>after tor restart in logs:
>Tor[15368]: Opening Metrics listener on 127.0.0.1:9166
>Tor[
Not at home but its just a cronjob running every x minutes and checking via
netstat how many connections I get from every single IP. If I get say 2
connections from a single IP it would be blocked with iptables.
Nothing fancy at all but it works as long as there are very few IPs ddosing me.
On 2/20/21 12:29 PM, niftybunny wrote:
We already changed the timers on the TCP connections and we have scripts
running which are blocking IPs who will send us x connections. Right now
they changed tactics and for me it looks like SYNC flood from datacenter IP
ranges and a few 100 IPs whic
10 matches
Mail list logo