OpenDNS CGNAT Issues
cb.list6 at gmail.com
Tue Sep 11 13:28:42 UTC 2018
On Tue, Sep 11, 2018 at 6:04 AM Matt Hoppes <
mattlists at rivervalleyinternet.net> wrote:
> That isn’t a solution. He still will need to dual stack and CGNat that.
But the flows that can support ipv6, will go ipv6 and not be subject to
these abuse triggers.
Look, this list has monthly reports from some small network operator
hurting their customers with CGN NAT. Meanwhile, the big guys like Comcast
/ Charter / ATT / Cox have moved onto ipv6.
Where does that leave the little guy with CGN?
Right here. Screaming into the avoid begging for help. Some special
And, me, saying you had 10+ years of not deploying ipv6. Here’s to the
next 10 years of you email this list about your own failure to keep up with
We will have this discussion again and again. Not sure your customers will
stick around, all they know is your CGN space got black listed from yet
> On Sep 11, 2018, at 08:54, Ca By <cb.list6 at gmail.com> wrote:
> On Mon, Sep 10, 2018 at 9:12 PM Darin Steffl <darin.steffl at mnwifi.com>
>> I have a ticket open with OpenDNS about filtering happening on some of
>> our CGNAT IP space where a customer has "claimed" the IP as theirs so other
>> customers using that same IP and OpenDNS are being filtered and not able to
>> access sites that fall under their chosen filter.
>> I have a ticket open from 6 days ago but it's not going anywhere fast.
>> Can someone from OpenDNS contact me or point me to a contact there to
>> help get this resolved? I believe we need to claim our CGNAT IP space so
>> residential users can't claim IP's of their own.
>> Thank you!
> You should provide your users ipv6, opendns supports ipv6 and likely will
> not have this issue you see
> I am sure it may cost you time / money / effort. But this old thing we
> call ipv4 is in a death spiral, and it will just get worse and worse for
> you without ipv6.
>> Darin Steffl
>> Minnesota WiFi
>> <http://www.facebook.com/minnesotawifi> Like us on Facebook
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NANOG