[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
OpenDNS CGNAT Issues
Guys, I'm not asking about IPv6. I'm simply asking for a contact at OpenDNS.
And we are purchasing enough IPv4 space to provide an IP to every customer
but it's not ready yet.
Thank you
On Tue, Sep 11, 2018 at 8:39 AM, Ca By <cb.list6 at gmail.com> wrote:
>
>
> On Tue, Sep 11, 2018 at 6:31 AM Matt Hoppes <[email protected]
> rivervalleyinternet.net> wrote:
>
>> So don't CGNat? Buy IPv4 addresses at auction?
>>
>
> As long as you donâ??t deploy ipv6, you should be good.
>
> Seriously. Not sure why this is so hard. IPv4 does not scale. Your
> customers, like my customers, probably mostly go to Youtube, google, fb,
> netflix, .... all which have ipv6. Giving your existing customers ipv6
> moves this traffic off your cgn. And gives them a path to dns services.
>
> But you do you. if you ask NANOG, how to solve this problem, and missed
> the 3 NANOG meeting presos at every meeting about how ipv6 is good .... not
> sure what you expect here. Definately not a shoulder to cry on, but i wm
> sure some v4 brokers and cgn box pushers see your customers blood in the
> water.
>
> CB
>
>>
>> On 9/11/18 9:28 AM, Ca By wrote:
>> >
>> >
>> > On Tue, Sep 11, 2018 at 6:04 AM Matt Hoppes
>> > <mattlists at rivervalleyinternet.net
>> > <mailto: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
>> > exception.
>> >
>> > 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 the times.
>> >
>> > 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 another service
>> >
>> > #realtalk
>> >
>> >
>> > On Sep 11, 2018, at 08:54, Ca By <cb.list6 at gmail.com
>> > <mailto:cb.list6 at gmail.com>> wrote:
>> >
>> >>
>> >>
>> >> On Mon, Sep 10, 2018 at 9:12 PM Darin Steffl
>> >> <darin.steffl at mnwifi.com <mailto:darin.steffl at mnwifi.com>> wrote:
>> >>
>> >> Hello,
>> >>
>> >> 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
>> >>
>> >> https://www.opendns.com/about/innovations/ipv6/
>> >>
>> >> 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
>> >> www.mnwifi.com <http://www.mnwifi.com/>
>> >> 507-634-WiFi
>> >> <http://www.facebook.com/minnesotawifi> Like us on Facebook
>> >> <http://www.facebook.com/minnesotawifi>
>> >>
>>
>
--
Darin Steffl
Minnesota WiFi
www.mnwifi.com
507-634-WiFi
<http://www.facebook.com/minnesotawifi> Like us on Facebook
<http://www.facebook.com/minnesotawifi>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20180911/81cf6d77/attachment.html>