On Wednesday, March 23, 2022 6:08:10 PM CET Toralf Förster wrote:
> On 3/21/22 18:45, meskio wrote:
>
> > Thank you for running bridges,
> > let me know if you need any help upgrading it.
>
>
> I'm not really familar with Debian and do wonder, what line I have to
> add to
On 3/21/22 18:45, meskio wrote:
Thank you for running bridges,
let me know if you need any help upgrading it.
I'm not really familar with Debian and do wonder, what line I have to
add to /etc/apt/apt.conf.d/50unattended-upgrades to get that
automatically installed ? Maybe I need to add the
Looks like my ISP has shut me down. The ports I were using are now blocked.
I checked them with an online port checker.
I tried.
___
tor-relays mailing list
tor-relays@lists.torproject.org
Hi meskio,
Thanks for the detailed response.
My bridge has been assigned to telegram so that explains why it's not active
yet.
Watching per country stats makes sense for determining where the bridge has
been blocked.
Also good to know the bridge state should be fully disposed when recycling
Quoting Just a Pleb (2022-03-23 02:43:54)
> 1) How long is typical (or what factors are involved ) before the bridge
> address is given out to users.
It should take less than 3 hours to start being taken into account by
rdsys/bridgedb. But unless you configure a specific distributor you will be
Hi All,
I have three lifecycle questions:
1) How long is typical (or what factors are involved ) before the bridge
address is given out to users.
2) How do I know when the bridge is burned (identified and blocked)
3) When it is burned and I build a new one on an other address should I copy
Hey Cristian,
you could run both, but some people think it's not the best idea because
if one service gets blocked the other one is also affected.
With dynamic IP addresses, also if they're only changing every other few
days, its probably better to run a snowflake proxy as obtaining new
