[tor-relays] SWIPing IPs (Was Re: Final Warning Notice)

[Marina Brown]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/10/2013 01:38 AM, Tom Ritter wrote:
> On 7/9/2013 9:03 PM, hack at riseup.net wrote:
>> A brief "whois" on the IP 216.243.58.198 reveals that the abuse
>> address is listed as CondoInternet.
>> 
>> Does anybody have experience getting an IP allocation so that the
>> abuse address is listed differently?
>> 
>> I have little experience, but perhaps this is a way out of this
>> problem if condo's problem is the number of abuse complaints and
>> the time it takes them.
> 
> It's my understanding that very few (and by very few I don't know
> or have ever heard of any) who will SWIP (change the abuse contact)
> an IP for anything under a /28 allocation. If one would SWIP a
> single IP, it'd probably require a very expensive bandwidth
> package.
> 
> I've thought quite a bit about pooling resources and getting a /28
> from a provider, and then assigning those IPs as secondary IPs on
> cheap VPS providers, and then routing the traffic via encrypted
> IPSEC/GRE tunnels.  But the /28 would have to be advertised in a
> single location, because people won't do BGP routes for single IPs
> (or maybe even /28s).
> 
> So if the /28 was registered in a datacenter in Chicago, all exit
> traffic would go to that datacenter (bad) then be shipped to the
> real Tor node in say Europe (slow), and then do the 3-hop Tor path.
> So I eventually gave up on that idea.
> 
> But my networking kung-fu is not as strong as others, so maybe via
> multicast or anycasts tricks this could work?
> 

A /28 SWIP only works for the name of the ip addresses, not the
nameservers. The parent ip space would still be listed and the rDNS
would have to be delegated from the provider nameserver.

Persistant complainants will always CC the upstream of the ip space
anyway.

A /24 would be better as you could shield the upstream a tiny bit more.

Multi/anycast, at least using BGP, require the assistance of the ISP.

- -- Marina Brown


> -tom _______________________________________________ tor-relays
> mailing list tor-relays at lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJR3MVbAAoJEEy/Yrjnmw6cmgYP/0L9V60W3CVWw66eJaWsE3nG
wj7h58sUpVH0pUgTQlx7bI9dancKt2bDY1QNErIvBzxCxvxe0kt09iGFZyUo5gVL
1oLAUfJOLzyd1rTatU+NQOaTf6vXdphK3ki+QmvDR6oAjEHMqdoWDy1JmC0TgEeW
P44s5uf/10RAT61G13c32SMS2gjscLzTwo7UBW8PXdlUj8XRdeEPl+uRHua/CB+y
H0XpmDDTwiQJEg4prTZU8bggiOpMynb5pDZJxW+5jje0OZ04UsHWlVm7GGwkzAns
08SuLgP7kmq/l+j81LdqP+9ag7sackiqjZXT0QWz9nHdorWwgaNo3rcTDIB8I2/a
U/7Vw8htXkKXlyxYRR2XGgzQyGMql9fZtOitAwixJrI806gpnWH6/c0KGMI3SKDm
IsM9FSJGe3MG+PUsNKQDCSHU7wrCKvW9BmN/I0/BlamX0f+ag51zqKl05WPGpjLP
Ar21ifopuuL1Xwsg8AhRkK9sQMGYo16hjT6/lbaDxMlSd0AS84x8OWBDiCwXVyKf
kap/8xaOfr6gUk37YcmOJHlBiMbI7VeE67YMawxZ2FANxY1c/92swgAmBZPVS0sV
a1c9L9eUk+cUcyzU3i5T10wyJj1RbuKokC6dbdnBdgnHBTDWffCn0b7tuM/1ZmsA
JqW/T4nMS3epuinyt184
=NIDZ
-----END PGP SIGNATURE-----