nanog mailing list archives
Re: issues through CGNat (juniper ms-mpc-128g in mx960)
From: Ross Tajvar <ross () tajvar io>
Date: Sun, 22 Jul 2018 10:24:27 -0400
That would be Sony... On Sun, Jul 22, 2018, 10:24 AM Ca By <cb.list6 () gmail com> wrote:
On Sun, Jul 22, 2018 at 6:23 AM Radu-Adrian Feurdean < nanog () radu-adrian feurdean net> wrote:On Thu, Jul 19, 2018, at 16:34, Aaron Gould wrote:I don't know if it's fixed on the endpoints, or in the cgnat config orwhat. Not specific to Juniper, but it's NOT fixed. You'll either start spending time on work-arounds or you start selling a new service with dedicated public IPv4 - more expensive than the CGNATed one. Or you can afford to still delay deploying CGN.Or, do us all a favor, and leave PS4 broken and refer your customers to Nintendo for them to support ipv6. If you dont, then we all remain hostage to nintendo and their dedicated ipv4 bs
Current thread:
- issues through CGNat (juniper ms-mpc-128g in mx960) Aaron Gould (Jul 19)
- Re: issues through CGNat (juniper ms-mpc-128g in mx960) Matt Erculiani (Jul 19)
- Re: issues through CGNat (juniper ms-mpc-128g in mx960) Radu-Adrian Feurdean (Jul 22)
- Re: issues through CGNat (juniper ms-mpc-128g in mx960) Ca By (Jul 22)
- Re: issues through CGNat (juniper ms-mpc-128g in mx960) Ross Tajvar (Jul 23)
- Re: issues through CGNat (juniper ms-mpc-128g in mx960) Ca By (Jul 22)
- RE: issues through CGNat (juniper ms-mpc-128g in mx960) Aaron Gould (Jul 31)