Gaming Consoles and IPv4

Matt Hoppes mattlists at rivervalleyinternet.net
Sun Sep 27 18:51:08 UTC 2020


Call of Duty seems to be especially problematic. 

> On Sep 27, 2020, at 2:45 PM, info--- via NANOG <nanog at nanog.org> wrote:
> 
> 
> Not every game are made the same or use the same network engine.
>  
> Which games on PS4 are more problematic in your opinion?
>  
> Jean
>  
> From: NANOG <nanog-bounces+jean=ddostest.me at nanog.org> On Behalf Of Matt Hoppes
> Sent: Sunday, September 27, 2020 2:23 PM
> To: Darin Steffl <darin.steffl at mnwifi.com>
> Cc: North American Network Operators' Group <nanog at nanog.org>
> Subject: Re: Gaming Consoles and IPv4
>  
> I understand that. But there’s a host of reasons why that night not work - two devices trying to use UPNP behind the same PAT device, an apartment complex or hotel WiFi system, etc. 
> 
> 
> On Sep 27, 2020, at 2:17 PM, Darin Steffl <darin.steffl at mnwifi.com> wrote:
> 
> 
> This isn't rocket science.
>  
> Give each customer their own ipv4 IP address and turn on upnp, then they will have open NAT to play their game and host. 
>  
> On Sun, Sep 27, 2020, 12:50 PM Matt Hoppes <mattlists at rivervalleyinternet.net> wrote:
> I know the solution is always “IPv6”, but I’m curious if anyone here knows why gaming consoles are so stupid when it comes to IPv4?  
> 
> We have VoIP and video systems that work fine through multiple layers of PAT and NAT. Why do we still have gaming consoles, in 2020, that can’t find their way through a PAT system with STUN or other methods?
> 
> It seems like this should be a simple solution, why are we still opening ports or having systems that don’t work?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20200927/e0822c9e/attachment.html>


More information about the NANOG mailing list