Thanks for your replies...
In the last week or so I've been testing further...
Using the following items to slow/alleviate the otherwise randomness of ip's
and port's been generated via my cgnat boundary nodes...
APP - Address pooling paired
EIM - Endpoint independent mapping
EIF - Endpoint ind
That would be Sony...
On Sun, Jul 22, 2018, 10:24 AM Ca By wrote:
> On Sun, Jul 22, 2018 at 6:23 AM Radu-Adrian Feurdean <
> na...@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 o
On Sun, Jul 22, 2018 at 6:23 AM Radu-Adrian Feurdean <
na...@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 or
> what.
>
> Not specific to Juniper, but it's NOT fixed.
> You'll either sta
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 or what.
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 ex
One of the biggest deal-breakers about the Miltiservices DPC and MPC is
that it does not support NAT Transversal (UDP hole punching), which is
probably the reason you're having trouble with the PS4 online gaming. It
also messes with VoIP too.
As for the IPsec issue, im not sure if that would be re
(please forgive cross-posting between jnsp and nanog.looking for anyone who
could help shed light)
I moved customers behind MS-MPC-128G (MX960) CGNat boundary a few nights
ago. for the most part it went well. with these couple issues. please let me
know what you know about this and how to fix.
6 matches
Mail list logo