OpenDNS, or anyone for that matter, should never see 100.64/10 ip's. If they do, something is wrong at the source, and OpenDNS wouldn't be able to reply anyway (or at least have the reply route back to the user). -----Original message----- From:Aled Morris via NANOG <[email protected]> Sent:Tue 09-11-2018 11:57 am Subject:Re: OpenDNS CGNAT Issues To:[email protected]; CC:NANOG <[email protected]>; Incidentally, I hope OpenDNS considers 100.64.0.0/10 <http://100.64.0.0/10> as space that can't be registered to any end-user. Aled
- Re: OpenDNS CGNAT Issues Ca By
- Re: OpenDNS CGNAT Issues Matt Hoppes
- Re: OpenDNS CGNAT Issues Ca By
- Re: OpenDNS CGNAT Issues Darin Steffl
- Re: OpenDNS CGNAT Issues Jared Mauch
- Re: OpenDNS CGNAT Issues Lee Howard
- Re: OpenDNS CGNAT Issues Denys Fedoryshchenko
- Re: OpenDNS CGNAT Issues Michael Crapse
- Re: OpenDNS CGNAT Issues Aled Morris via NANOG
- Re: OpenDNS CGNAT Issues Mark Andrews
- RE: OpenDNS CGNAT Issues Jerry Cloe
- Re: OpenDNS CGNAT Issues Christopher Morrow
- Re: OpenDNS CGNAT Issues Owen DeLong
- Re: OpenDNS CGNAT Issues Christopher Morrow
- RE: OpenDNS CGNAT Issues Kenny Taylor
- Re: OpenDNS CGNAT Issues Owen DeLong
- Re: OpenDNS CGNAT Issues valdis . kletnieks
- Re: OpenDNS CGNAT Issues Owen DeLong
- Re: OpenDNS CGNAT Issues valdis . kletnieks

