[178268] in North American Network Operators' Group
Re: Wisdom of using 100.64/10 (RFC6598) space in an Amazon VPC
daemon@ATHENA.MIT.EDU (Eric Germann)
Mon Feb 23 23:28:10 2015
X-Original-To: nanog@nanog.org
From: Eric Germann <ekgermann@cctec.com>
In-Reply-To: <CAA5Ek4fdZO1_3LzX26Ra8_+vvEKrCcVFo_Uu27HFcHaWEtkGgA@mail.gmail.com>
Date: Mon, 23 Feb 2015 23:28:04 -0500
To: Blair Trosper <blair.trosper@gmail.com>
X-Assp-Envelope-From: ekgermann@cctec.com
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Mulling over the implications of this.
[root@ip-100-64-0-55 ~]# traceroute s3.amazonaws.com
traceroute to s3.amazonaws.com (54.231.0.64), 30 hops max, 60 byte =
packets
1 ec2-79-125-0-202.eu-west-1.compute.amazonaws.com (79.125.0.202) =
1.068 ms 0.824 ms 0.787 ms
2 178.236.1.18 (178.236.1.18) 1.193 ms 1.164 ms 0.869 ms
3 * * *
4 54.239.41.133 (54.239.41.133) 76.046 ms 76.029 ms 75.986 ms
5 54.239.41.166 (54.239.41.166) 76.314 ms 76.281 ms 76.244 ms
6 72.21.220.77 (72.21.220.77) 76.143 ms 76.054 ms 76.095 ms
7 205.251.245.224 (205.251.245.224) 76.346 ms 72.21.222.149 =
(72.21.222.149) 76.261 ms 205.251.245.230 (205.251.245.230) 76.360 ms
8 * * *
...
30 * * *
but,=20
[root@ip-100-64-0-55 ~]# wget https://s3.amazonaws.com
--2015-02-24 04:20:18-- https://s3.amazonaws.com/
Resolving s3.amazonaws.com... 54.231.12.48
Connecting to s3.amazonaws.com|54.231.12.48|:443... connected.
HTTP request sent, awaiting response... 307 Temporary Redirect
Location: http://aws.amazon.com/s3/ [following]
--2015-02-24 04:20:18-- http://aws.amazon.com/s3/
Resolving aws.amazon.com... 54.240.250.195
Connecting to aws.amazon.com|54.240.250.195|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: =E2=80=9Cindex.html.1=E2=80=9D
[ <=3D> =
] 179,606 158K/s in 1.1s
2015-02-24 04:20:20 (158 KB/s) - =E2=80=9Cindex.html.1=E2=80=9D saved =
[179606]
ICMP would break from the intermediates, but ICMP from the API endpoint =
should still work. Will have to chew on this a bit overnight.
EKG
> On Feb 23, 2015, at 9:03 PM, Blair Trosper <blair.trosper@gmail.com> =
wrote:
>=20
> Might be ill-advised since AWS uses it themselves for their internal =
networking. Just traceroute to any API endpoint from an EC2/VPC =
resource or instance. :)
>=20
> On Mon, Feb 23, 2015 at 2:43 PM, M=C3=A5ns Nilsson =
<mansaxel@besserwisser.org <mailto:mansaxel@besserwisser.org>> wrote:
> Subject: Wisdom of using 100.64/10 (RFC6598) space in an Amazon VPC =
deployment Date: Mon, Feb 23, 2015 at 10:02:44AM -0500 Quoting Eric =
Germann (ekgermann@cctec.com <mailto:ekgermann@cctec.com>):
> > Currently engaged on a project where they=E2=80=99re building out a =
VPC infrastructure for hosted applications.
>=20
> <snip>
>=20
> > Thoughts and thanks in advance.
>=20
> using the wasted /10 for this is pretty much equal to using RFC1918 =
space.
>=20
> IPv6 was invented to do this right.
>=20
> --
> M=C3=A5ns Nilsson primary/secondary/besserwisser/machina
> MN-1334-RIPE +46 705 989668 =
<tel:%2B46%20705%20989668>
> It's NO USE ... I've gone to "CLUB MED"!!
>=20
