I have a few questions,
I have two obfs4 bridges updated with sw, one old since a few years and the
other very new.
The older one I now notice all of a sudden have gotten distribution mechanisms
'none'. It had 'moat' earlier, what would make it change like this? It usually
has between 50-100
Hi
I wrote about incorrect date stamps for relays/bridges on atlas/metrics site in
December 2021.
This has reappeared since some time (dont know for how long).
First seen fullt incorrect by years and all times unlogic, first seen later
than last restarted etc.
Is this a common problem or
Hi,
I am thinking of starting another bridge. In regards to the current situation,
is there a real benefit in deploying one within Russia or does that really not
matter?
A tor op___
tor-relays mailing list
tor-relays@lists.torproject.org
of that page before the latest upgrade so it appears the
change should have something to to with that somehow.
This is on Debian.
A tor op
‐‐‐ Original Message ‐‐‐
On Monday, December 27th, 2021 at 11:59 PM, nusenu
wrote:
> Hi,
>
> could you paste the Relay Search page l
I notice that the "first seen" info on my obfs4 bridge status page on tor atlas
/ metrics all of a sudden is incorrect, by years. Not sure if it's something
that introduced itself with latest update or what.
The various graphs on traffic and users are still correct through.
A tor
or
what?
I guess, should I want to continue providing service, that it's useful or
possibly preferred to move over the keys/config (?) to indicate same admin (and
for users if there's no noticeable interruption the move won't even be noticed
I suppose).
TIA,
a tor op
Well, can be hard to say just looking at that number. Linux is not Windows.. it
doesn't have to reboot every time it's patched.
A tor op
Originalmeddelande
På 4 okt. 2019 14:35, Steve Snyder < swsny...@snydernet.net> skrev:
On 10/4/19 7:39 AM, li...@for-privacy.net
http://lmgtfy.com/?q=CVE-2017-0380
> Original Message
> Subject: Re: [tor-relays] More recent rpm somewhere?
> Local Time: September 17, 2017 12:53 PM
> UTC Time: September 17, 2017 12:53 PM
> From: bnag...@gmail.com
> To: tor-relays@lists.torproject.org
>
> On Sun, Sep 17, 2017
Hi
I'm running an obfs4 bridge and upgraded to latest version.
Use Debian Jessie (8.9).
One thing that puzzles me is the log
/var/log/tor/log
I used to always see some useful info there, like number of connecting clients
during the last 6 hours etc.
I have an entry:
[notice] Clean shutdown
Nope that need not be it.
I had my bridge relay running for many moths with a few Mbps BW and it steadily
had the guard flag set.
When doing the latest TOR upgrade I upped the BW-limit 100% but since that tor
service restart it has now been running some 40 days without getting the guard
flag
:56, a tor op <ato...@protonmail.ch> wrote:
>
> Mine is still missing the guard flag after 17 days since reboot.
Your bridge, or your relay?
I'm happy to help with relays, and fingerprints can be made public.
Bridges are a bit more complicated, and fingerprints should be
k
Mine is still missing the guard flag after 17 days since reboot.
Original Message
Subject: Re: [tor-relays] Normal to lose stable/guard flags on relay reboot?
Local Time: February 6, 2017 12:04 AM
UTC Time: February 6, 2017 12:04 AM
From: dl1...@gmx.de
To:
Hi
When a tor admin updates a tor node, what is the reasoning for punishing the
status by removing flags like the guard flag?
The node may have been up for months on end without issues and goes down for a
few minutes during install and restart and comes up with a newer version, hence
it is
Hi
I am a TOR bridge operator running a bridge with 8 Mbps advertised BW and
having obfs4 installed. Been up a year or so on this install.
I'll put a few misc thoughts out here, only been lurking on list earlier.
I have been thinking a little about how useful this system is (MY bridge that
14 matches
Mail list logo
