On 2024-10-23 05:27, George Hartley via tor-relays wrote:
Any advice on this?
How many concurrent exit connections do you have? And how often do you
see bad actors running scanners? It shouldn't be too onerous to rate
limit on --dport 22 globally. This is no worse than blocking 22
outright
In modern Debian, there is no more "iptabbles-nft" package. The package
"iptables" IS iptables-nft. When you $ sudo apt-get install iptables,
you will only get iptables-nft. The optables command is a soft-link to
it.
This is a translation layer that takes iptables rules and inserts them
as
On 2024-10-31 23:15, Neel Chauhan wrote:
It would be hard to explain to Verizon I run Tor relays since they
technically don't allow servers. I hope I'm not forced onto AT&T
Internet Air as my particular co-op rental unit won't let met get
Spectrum even when other units can, not that I wanted S
On 2024-10-31 11:44, marie wrote:
Marie (running all relays with a *.ketamin.trade hostname)
Hi Marie. I just wanted to write and point out looking at your relays
that none of them have the MyFamily configuration set up. The ownership
association between them should be declared.
On 2024-10-29 06:04, Toralf Förster via tor-relays wrote:
On 10/29/24 04:33, Pierre Bourdon wrote:
Some tcpdumps showing random RSTs coming back to my machines running
relays (with no traffic being initiated by said machines beforehand):
You used somethign like this? :
tcpdump -i enp8s0 'tcp[
On 2024-11-08 08:47, tor-relays+tor-rel...@queer.cat wrote:
This rule will also count SYN-ACKs sent from your own server to bots
trying to connect to your SSH on port 22.
The rule is on the source port = 22, not the destination port = 22.
Incoming bot connections will not have a sport = 22.
On 2024-11-05 16:32, George Hartley via tor-relays wrote:
Also, please consider using a provider that is not overcrowded with
Tor nodes already like OVH.
I can recommend Wedos.cz ... https://wedos.cz/en/
They block access to their web site to Tor users. This doesn't bode well
for how Tor frien
I just reset my SYN-ACK detection nft counter and it's still showing
activity:
tcp sport 22 tcp flags == 0x12 counter packets 9 bytes 504
That was in five minutes.
On 2024-11-08 03:03, Red Oaive wrote:
Thank-you for you efforts, and for the efforts of the anonymous
contributors! And let me
Thank-you for you efforts, and for the efforts of the anonymous
contributors! And let me second the motion requesting (much) more
information about the perps.
Do we know the full impact though? The vast majority of relay operators
seem not to be on the mailing list. What are the actual numb
Bug 40994 (reported at
https://gitlab.torproject.org/tpo/core/tor/-/issues/40994) has become a
fairly serious impediment to running relays. I generally obtain two
ipv4 addresses on my machines and the ports I want to use for tor are
not available on both addresses. So listening on 0.0.0.0 is
Thank-you for the private and forum replies with various suggestions.
Suggesions were in two flavours:
1) Add OutboundBindAddress - no efect. I did not expect this to have an
effect as it only addresses the outbound bind address.
2) Problem is with nyx pointing to
https://github.com/torproject/
Thank-you for all assistance. It still does not appear to be a bug in
nyx, but it does appear to be a bug only in tor's reporting through its
control port. As such it is, I'm sure, a low priority to fix in light
of efforts to replace the c relay. I've updated the bug report.
On 2024-12-16 06:39, George Hartley via tor-relays wrote:
Hi,
it seems that your address is not reachable for me:
You were pinging his link local fe80 address, which isn't routable. He
is having troubles listening on the real IPv6 address, which he
obfuscated.
On 2024-12-15 19:37, Eddie
13 matches
Mail list logo
