[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-relays] [SOLVED] published descriptor missing from consensus

To: tor-relays@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [tor-relays] [SOLVED] published descriptor missing from consensus
From: Roger Dingledine <arma@xxxxxxx>
Date: Fri, 9 Jun 2017 12:13:33 -0400
Delivered-to: archiver@xxxxxxxx
Delivery-date: Fri, 09 Jun 2017 12:13:54 -0400
In-reply-to: <201706090605.v5965hSv007161@sdf.org>
List-archive: <http://lists.torproject.org/pipermail/tor-relays/>
List-help: <mailto:tor-relays-request@lists.torproject.org?subject=help>
List-id: "support and questions about running Tor relays \(exit, non-exit, bridge\)" <tor-relays.lists.torproject.org>
List-post: <mailto:tor-relays@lists.torproject.org>
List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays>, <mailto:tor-relays-request@lists.torproject.org?subject=subscribe>
List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-relays>, <mailto:tor-relays-request@lists.torproject.org?subject=unsubscribe>
References: <20170604223742.GA8242@moria.seul.org> <201706050014.v550E6Bx006231@sdf.org> <20170605031313.GB8242@moria.seul.org> <201706080844.v588itwE029244@sdf.org> <B910D0AA-7DFE-4160-942B-197A9AD72648@gmail.com> <201706081443.v58Eh0eb019409@sdf.org> <20170608200135.4b040a60@natsu> <201706082230.v58MUbDb021852@sdf.org> <0C622E32-E77A-4965-9CBE-1EF1D83F350D@gmail.com> <201706090605.v5965hSv007161@sdf.org>
Reply-to: tor-relays@xxxxxxxxxxxxxxxxxxxx
Sender: "tor-relays" <tor-relays-bounces@xxxxxxxxxxxxxxxxxxxx>
User-agent: Mutt/1.8.2 (2017-04-18)

On Fri, Jun 09, 2017 at 01:05:43AM -0500, Scott Bennett wrote:
> > I think you will find this is not an uncommon configuration among
> > high-bandwidth relays.
> 
>      I will check further into the procedure for which Roger posted a URL
> to see whether it will indeed give me a list of such addresses that I can
> use.  If so, I will certainly begin running it, scraping the addresses,
> and merging them with the addresses already going into table creation.

It will not do what you want. It is only for exit addresses.

--Roger

_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Follow-Ups:
- Re: [tor-relays] [SOLVED] published descriptor missing from consensus
  - From: Scott Bennett

References:
- Re: [tor-relays] published descriptor missing from consensus
  - From: Roger Dingledine
- Re: [tor-relays] published descriptor missing from consensus
  - From: Scott Bennett
- Re: [tor-relays] published descriptor missing from consensus
  - From: Roger Dingledine
- Re: [tor-relays] [SOLVED] published descriptor missing from consensus
  - From: Scott Bennett
- Re: [tor-relays] [SOLVED] published descriptor missing from consensus
  - From: teor
- Re: [tor-relays] [SOLVED] published descriptor missing from consensus
  - From: Scott Bennett
- Re: [tor-relays] [SOLVED] published descriptor missing from consensus
  - From: Roman Mamedov
- Re: [tor-relays] [SOLVED] published descriptor missing from consensus
  - From: Scott Bennett
- Re: [tor-relays] [SOLVED] published descriptor missing from consensus
  - From: teor
- Re: [tor-relays] [SOLVED] published descriptor missing from consensus
  - From: Scott Bennett

Prev by Author: Re: [tor-relays] keypair does not match its older value
Next by Author: Re: [tor-relays] [SOLVED] published descriptor missing from consensus
Previous by thread: Re: [tor-relays] [SOLVED] published descriptor missing from consensus
Next by thread: Re: [tor-relays] [SOLVED] published descriptor missing from consensus
Index(es):
- Author
- Thread