<div dir="auto">IPv6 all the things.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Oct 10, 2019, 12:11 PM Neil Hanlon <<a href="mailto:neil@shrug.pw">neil@shrug.pw</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="zoom:0%"><div dir="auto">RCN here in the greater Boston area does CGNAT inside <a href="http://10.0.0.0/8" target="_blank" rel="noreferrer">10.0.0.0/8</a>. This doesn't surprise me. </div>
<div class="gmail_quote">On Oct 10, 2019, at 11:27, Javier J <<a href="mailto:javier@advancedmachines.us" target="_blank" rel="noreferrer">javier@advancedmachines.us</a>> wrote:<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="auto">
<div>
Very strange ATT would put end users on an RFC 1918 block unless they were doing NAT to the end user.
</div>
<div dir="auto">
If they were doing NAT, I would expect CGNAT in the 100.something or other range.
</div>
<div dir="auto">
<br>
<br>
<div class="gmail_quote" dir="auto">
<div dir="ltr" class="gmail_attr">
On Thu, Oct 10, 2019, 11:07 AM Mehmet Akcin <
<a href="mailto:mehmet@akcin.net" target="_blank" rel="noreferrer">mehmet@akcin.net</a>> wrote:
<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div dir="auto">
Yes
</div>
</div>
<div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">
On Wed, Oct 9, 2019 at 20:46 Javier J <
<a href="mailto:javier@advancedmachines.us" rel="noreferrer noreferrer" target="_blank">javier@advancedmachines.us</a>> wrote:
<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">
<div dir="ltr">
I'm just curious, was the ip in the RFC 1918
<a href="http://172.16.0.0/16" rel="noreferrer noreferrer" target="_blank">172.16.0.0/16</a> range?
<div>
<br>
</div>
<div>
<a href="https://tools.ietf.org/html/rfc1918" rel="noreferrer noreferrer" target="_blank">https://tools.ietf.org/html/rfc1918</a>
<br>
</div>
<div>
<br>
</div>
<div>
<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">
On Mon, Oct 7, 2019 at 6:01 PM Mehmet Akcin <
<a href="mailto:mehmet@akcin.net" rel="noreferrer noreferrer" target="_blank">mehmet@akcin.net</a>> wrote:
<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">
<div dir="ltr">
To close the loop here (in case if someone has this type of issue in the future), I have spoken to AT&T instead of trying to work it out with AWS Hosted Vendor, Reolink.
<div>
<br>
</div>
<div>
AT&T Changed my public IP, and now I am no longer in that 172.x.x.x block, everything is working fine.
</div>
<div>
<br>
</div>
<div>
mehmet
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">
On Thu, Oct 3, 2019 at 2:54 PM Javier J <
<a href="mailto:javier@advancedmachines.us" rel="noreferrer noreferrer" target="_blank">javier@advancedmachines.us</a>> wrote:
<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">
<div dir="auto">
Auto generated VPC in AWS use RFC1819 addresses. This should not interfere with pub up space.
<div dir="auto">
<br>
</div>
<div dir="auto">
What is the exact issue? If you can't ping something in AWS chances are it's a security group blocking you.
</div>
<div dir="auto">
<br>
</div>
<div dir="auto">
<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">
On Tue, Oct 1, 2019, 7:00 PM Jim Popovitch via NANOG <
<a href="mailto:nanog@nanog.org" rel="noreferrer noreferrer" target="_blank">nanog@nanog.org</a>> wrote:
<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">
On October 1, 2019 9:39:03 PM UTC, Matt Palmer <
<a href="mailto:mpalmer@hezmatt.org" rel="noreferrer noreferrer noreferrer" target="_blank">mpalmer@hezmatt.org</a>> wrote:
<br> >On Tue, Oct 01, 2019 at 04:50:33AM -0400, Jim Popovitch via NANOG
<br> >wrote:
<br> >> On 10/1/2019 4:09 AM, Christopher Morrow wrote:
<br> >> > possible that this is various AWS customers making
<br> >iptables/firewall mistakes?
<br> >> > "block that pesky rfc1918 172/12 space!!"
<br> >>
<br> >> AWS also uses some 172/12 space on their internal network (e.g. the
<br> >network
<br> >> that sits between EC2 instances and the AWS external firewalls)
<br> >
<br> >Does AWS use
<a href="http://172.0.0.0/12" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">172.0.0.0/12</a> internally, or
<a href="http://172.16.0.0/12" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">172.16.0.0/12</a>? They're
<br> >different
<br> >things, after all.
<br> >
<br>
<br> I don't know their entire operations, but they do use some
<a href="http://172.16.0.0/12" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">172.16.0.0/12</a>
<br> addresses internally. And yes, that is very different than 172/12, sorry
<br> for the confusion.
<br>
<br> -Jim P.
<br>
<br>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>--
<br>
<div dir="ltr" data-smartmail="gmail_signature">
Mehmet
<br>+1-424-298-1903
</div>
</blockquote>
</div>
</div>
</div></blockquote></div></div></blockquote></div>