[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

AWS issues with 172.0.0.0/12

Subject: AWS issues with 172.0.0.0/12
From: mpalmer at hezmatt.org (Matt Palmer)
Date: Wed, 2 Oct 2019 07:39:03 +1000
In-reply-to: <[email protected]>
References: <CA+LTh5VjFN6ADDy8g2jrd_Lqf3GmJgwgzn4Pg7XyNBppfaHFyg@mail.gmail.com> <[email protected]> <CA+LTh5U3SKASAnQ7_hO1qpuhB-MHs3uRdVqqJiascr6+Ygc2eQ@mail.gmail.com> <[email protected]> <CAL9jLaZGCBNYH7r-Lqchz+OyCKhMV7wajzZAwqVUX10ZJYd-wA@mail.gmail.com> <[email protected]>

On Tue, Oct 01, 2019 at 04:50:33AM -0400, Jim Popovitch via NANOG wrote:
> On 10/1/2019 4:09 AM, Christopher Morrow wrote:
> > possible that this is various AWS customers making iptables/firewall mistakes?
> >    "block that pesky rfc1918 172/12 space!!"
> 
> AWS also uses some 172/12 space on their internal network (e.g. the network
> that sits between EC2 instances and the AWS external firewalls)

Does AWS use 172.0.0.0/12 internally, or 172.16.0.0/12?  They're different
things, after all.

- Matt

Follow-Ups:
- AWS issues with 172.0.0.0/12
  - From: jimpop at domainmail.org (Jim Popovitch)

References:
- AWS issues with 172.0.0.0/12
  - From: mehmet at akcin.net (Mehmet Akcin)
- AWS issues with 172.0.0.0/12
  - From: diosbejgli at gmail.com (Andras Toth)
- AWS issues with 172.0.0.0/12
  - From: mehmet at akcin.net (Mehmet Akcin)
- AWS issues with 172.0.0.0/12
  - From: bortzmeyer at nic.fr (Stephane Bortzmeyer)
- AWS issues with 172.0.0.0/12
  - From: morrowc.lists at gmail.com (Christopher Morrow)
- AWS issues with 172.0.0.0/12
  - From: jimpop at domainmail.org (Jim Popovitch)

Prev by Date: This DNS over HTTP thing
Next by Date: AWS issues with 172.0.0.0/12
Previous by thread: AWS issues with 172.0.0.0/12
Next by thread: AWS issues with 172.0.0.0/12
Index(es):
- Date
- Thread