On Mittwoch, 19. Oktober 2022 01:12:37 CEST Anonforpeace via tor-relays wrote:
> I have set the static NAT and forwarded the port.
On your router?
> Here is what I get.
:-(
Logs and configs are more readable on a pastbin page.
E.g. paste.debian.net or privatebin.deblan.org
> darkhoodie-HP-Compaq-
I have set the static NAT and forwarded the port. Here is what I get. I've
hidden my IP for obvious reasons.
Oct 18 19:04:51 darkhoodie-HP-Compaq-Pro-6300-SFF kernel: [441419.629454] [UFW
BLOCK] IN=eno1 OUT= MAC=24:be:05:0e:ef:2c:78:67:0e:6c:43:68:08:00
SRC=36.155.109.220 DST=192.168.1.171 LEN
Hi,
Bridges are usually not impacted by network-wide DoS as they are not
as public as any other node.
Your node thinks it's unreachable. Have you confirmed the IP it uses
is not hard-coded in your torrc to be your former IP. Have you
configured your router NAT correctly?
Lastly, is it possible tha
Hi there,
Am 16.10.22 um 17:09 schrieb Anonforpeace via tor-relays:
Hello:
My Tor Bridge has been down for awhile as I was moving to a new home. I
have been trying to bring it up again and have been receiving the
messages you see below. I have checked the the tor project status and
see tha
Hello:
My Tor Bridge has been down for awhile as I was moving to a new home. I have
been trying to bring it up again and have been receiving the messages you see
below. I have checked the the tor project status and see that there is a Ddos
attack affecting the network. Is that why I am getting
I got my bridge back online. Turns out I had to set a static NAT address with
port forwarding which I've never had to do before. Thanks all!!
Original Message
On May 10, 2020, 7:56 PM, wrote:
> On [08.05.2020 19](tel:0805202019):39, Anonforpeace wrote:
>
>> I have the port forw
On 08.05.2020 19:39, Anonforpeace wrote:
I have the port forwarded. I've also noticed that the advertised
bandwidth is only 248 KiB/s on the metrics page. This is a first and
I'm not sure how to raise the bandwidth.
I think Advertised Bandwidth on a bridge can be ignored.
My bridge is alone on
Is the ip address of the machine the same as it was before the power
supply issue?
If you do an ifconfig, does the ipv4 (I assume ipv4) address of this
machine match the NAT/forwarding?
That will clear up whether your ip has changed (dynamic IP) and whether
that is the cause of your bridge being in
Hi,
On Friday, May 8, 2020 at 7:39 PM, Anonforpeace
wrote:
I have the port forwarded. I've also noticed that the advertised
bandwidth is only 248 KiB/s on the metrics page. This is a first and
I'm not sure how to raise the bandwidth. Could this be what's causing
it to stay offline??
No. Th
I have the port forwarded. I've also noticed that the advertised bandwidth is
only 248 KiB/s on the metrics page. This is a first and I'm not sure how to
raise the bandwidth. Could this be what's causing it to stay offline??
Original Message
On May 8, 2020, 12:35 PM, Paul Geurt
Apologies for the length but detail is important. My bridge pc's internal
power supply had to be replaced, and was down for a week. After the
replacement, I restarted the daemon and the tor service. Everything seemed
normal except that it's not reachable from outside. No configurations have b
Option: Dynamic internal ip address so the FW rule does point to the right
internal ip address?
Machine has been off for a week so the lease could be expired.
On Fri, May 8, 2020, 18:19 Anonforpeace wrote:
> Apologies for the length but detail is important. My bridge pc's internal
> power suppl
12 matches
Mail list logo
