[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-relays] automation needs of big relay ops (implemented as ansible role)
- To: Nusenu <nusenu@xxxxxxxxxxxxxxx>, David Stainton <dstainton415@xxxxxxxxx>, arzhel@xxxxxxxxxxx
- Subject: Re: [tor-relays] automation needs of big relay ops (implemented as ansible role)
- From: Moritz Bartl <moritz@xxxxxxxxxxxxxx>
- Date: Wed, 18 Feb 2015 00:00:02 +0100
- Authentication-results: mail.headstrong.de (amavisd-new); dkim=pass (1024-bit key) reason="pass (just generated, assumed good)" header.d=headstrong.de
- Cc: tor-relays@xxxxxxxxxxxxxxxxxxxx, team@xxxxxxxxxxxxxx
- Delivered-to: archiver@xxxxxxxx
- Delivery-date: Tue, 17 Feb 2015 18:00:19 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=headstrong.de; h=content-transfer-encoding:content-type:content-type :in-reply-to:references:subject:subject:mime-version:from:from :date:date:message-id:received; s=mail; t=1424214004; x= 1426028405; bh=kNbTl6sSSkzHNevVM0aPCEVioriAHVu+au0/3N2EtEA=; b=g DfRwarxzoDkSkP9pTWOguxXtR6xeMF+8Sqo2xzW9o4/7yTkYMO+0+nTHvV+pfpRn CCfNh4hMj4zTcZWbomUg7PXLRAxAIIBoWZJXcLvHN892bxK1S9W2Bs0BDcq6q3u+ eK0qRUBaK1YopV1lQuSs8A369EwWY20p3QA+5GWfwc=
- In-reply-to: <54E3C534.5020404@xxxxxxxxxxxxxxx>
- 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: <54E22F82.4070904@xxxxxxxxxxxxxxx> <CAFN1edqqgSw-Qym2tK1FCoEw+jnXtExPESWg6DrgCdezfjzsJA@xxxxxxxxxxxxxx> <54E261A8.5050100@xxxxxxxxxxxxxxx> <CAFN1edoROpNok6ZCkAaxTjMQrqG_wD_+d=w_W4-RoCWOLYkqUg@xxxxxxxxxxxxxx> <54E37A81.9060904@xxxxxxxxxxxxxxx> <54E3B9E2.8080808@xxxxxxxxxxxxxx> <54E3BFD5.40608@xxxxxxxxxxxxxxx> <54E3C127.90308@xxxxxxxxxxxxxx> <54E3C534.5020404@xxxxxxxxxxxxxxx>
- Reply-to: tor-relays@xxxxxxxxxxxxxxxxxxxx
- Sender: "tor-relays" <tor-relays-bounces@xxxxxxxxxxxxxxxxxxxx>
On 02/17/2015 11:48 PM, Nusenu wrote:
> I'm wondering why a relay (not bridge) op would order that many IP
> addresses on a host were he can not make use of it, but adding a
> simple check like "stop creating new instances once RAM/instancecount
> below X" is possible (or "ok lets use the remaining IPs for bridges" ;).
For exit relays, you want WHOIS reassignment. Many providers only offer
that for larger IP ranges, and then by default assign all of them to the
machine. I would expect many relay admins to take the default install
and simply run ansible on top of that, so they don't even actively set
up all the IPs by themselves (or have an interest in using them all),
they simply 'inherit' them from the ISP.
--
Moritz Bartl
https://www.torservers.net/
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays