Network Specifications

Esports Infrastructure Guide

Overview Setup Guide

Game Requirements

Valorant Rocket League Smash Ultimate

NBA 2K26 Brawlhalla Fortnite Marvel Rivals

Show Cisco IOS Commands

Toggle technical firewall configuration examples

Network Configuration Overview

Security Objectives

To ensure esports games can compete without network restrictions while maintaining security, use a structured approach with VLAN segmentation, robust NAT, and dedicated public IP addresses per device. This method ensures esports traffic is isolated and secure while allowing necessary connections.

Key Goals:

Ensure esports traffic does not interfere with critical school systems
Maintain network control while allowing necessary connections
Prevent unauthorized access or misuse of network resources
Comply with CIPA and other relevant regulations

Why Network Segmentation Matters

Schools typically implement network restrictions to protect student safety and preserve bandwidth for educational purposes. However, esports require more open network access than standard school operations. Network segmentation using VLANs allows schools to:

Isolate gaming traffic from academic and administrative systems
Apply different security policies to different network zones
Optimize bandwidth allocation with Quality of Service (QoS)
Monitor and control esports-specific network activity
Maintain CIPA compliance while enabling competitive gaming

Common Networking Challenges

Esports programs face unique connectivity requirements that differ from typical school network usage:

NAT Type Issues

Many competitive games require "Open" or "Moderate" NAT types for peer-to-peer connections. Strict NAT can prevent matchmaking and cause disconnections. Solution: Dedicated public IPs with 1:1 NAT mapping.

Port Forwarding

Games communicate on specific ports that may be blocked by default. Rather than opening all ports (security risk), use allowlist approach for required ports only.

Latency & Packet Loss

Competitive gaming is extremely sensitive to network latency. Implement QoS policies to prioritize gaming traffic and ensure wired ethernet connections (wireless not recommended).

Recommended Network Architecture

Most successful scholastic esports programs implement a three-tier approach:

Internet Gateway

Firewall/Router

├─ VLAN 10: Administrative

School Staff, Servers

├─ VLAN 20: Student Network

Standard Educational Use

├─ VLAN 30: Guest/Wireless

Visitor Access

└─ VLAN 50: Esports Gaming Lab

Dedicated with specific rules

Each VLAN operates on its own subnet (e.g., 10.50.0.0/24 for esports) with dedicated DHCP scope and firewall rules controlling inter-VLAN traffic.

Step-by-Step Configuration Guide

1Plan Your Network Topology

Before making changes, document your current network and plan the esports VLAN structure:

Inventory devices: Count all gaming PCs, consoles, and peripherals
Choose VLAN ID: Select an unused VLAN number (e.g., VLAN 50)
Define IP subnet: Choose private IP range (e.g., 10.50.0.0/24 = 254 hosts)
Identify switch ports: Document which physical ports will be esports lab
Plan public IPs: Determine how many dedicated IPs needed from ISP

Example IP Scheme

VLAN 50 (Esports): 10.50.0.0/24
Gateway: 10.50.0.1
DHCP Pool: 10.50.0.100 - 10.50.0.200
Static Reservations: 10.50.0.10 - 10.50.0.50 (for consoles/servers)

2Create the Esports VLAN

On your managed switch, create a new VLAN for esports traffic. Most schools use Cisco, HP, or Ubiquiti equipment:

Cisco Switch Configuration

The following commands will create VLAN 50, assign ports 1-24 to it, and configure a trunk port to your router/firewall:

Cisco IOS Commands:

configure terminal
vlan 50
  name ESPORTS_LAB
  exit

interface range GigabitEthernet1/0/1-24
  switchport mode access
  switchport access vlan 50
  spanning-tree portfast
  exit

interface GigabitEthernet1/0/48
  switchport mode trunk
  switchport trunk allowed vlan 10,20,30,50
  exit

write memory

This configuration:

Creates VLAN 50 named "ESPORTS_LAB"
Assigns ports 1-24 as access ports for gaming devices
Configures port 48 as trunk to carry multiple VLANs to router
Enables portfast for immediate connection (no spanning-tree delay)

3Configure Router/Firewall Interface

On your router or Layer 3 switch, create the VLAN interface and assign the gateway IP. This example shows configuration for Cisco routers:

Cisco IOS Commands:

interface Vlan50
  description ESPORTS_LAB_GATEWAY
  ip address 10.50.0.1 255.255.255.0
  no shutdown
  exit

ip dhcp pool ESPORTS_VLAN50
  network 10.50.0.0 255.255.255.0
  default-router 10.50.0.1
  dns-server 8.8.8.8 8.8.4.4
  lease 7
  exit

ip dhcp excluded-address 10.50.0.1 10.50.0.50

Alternative for standalone router: If using a separate firewall appliance (pfSense, FortiGate, etc.), create a VLAN interface on the router that connects to the firewall, then configure the VLAN on the firewall side.

4Configure Firewall Rules (Allowlist Approach)

Create firewall rules that allow ONLY required gaming traffic. Start with deny-all, then add specific permits:

! Create access list for esports traffic
ip access-list extended ESPORTS_OUTBOUND
  
  ! Allow DNS
  permit udp 10.50.0.0 0.0.0.255 any eq 53
  
  ! Allow HTTP/HTTPS (game downloads, auth)
  permit tcp 10.50.0.0 0.0.0.255 any eq 80
  permit tcp 10.50.0.0 0.0.0.255 any eq 443
  
  ! Allow Steam (example)
  permit tcp 10.50.0.0 0.0.0.255 any range 27015 27030
  permit udp 10.50.0.0 0.0.0.255 any range 27000 27030
  
  ! Allow Valorant (example)
  permit tcp 10.50.0.0 0.0.0.255 any range 8393 8400
  permit udp 10.50.0.0 0.0.0.255 any range 7000 8000
  
  ! Deny all other outbound traffic
  deny ip 10.50.0.0 0.0.0.255 any log
  exit

! Apply to VLAN interface
interface Vlan50
  ip access-group ESPORTS_OUTBOUND out
  exit

Important

Add all required ports for each game your program plays. See game-specific sections in this guide. Test thoroughly—missing ports will prevent matchmaking.

5Request and Configure Dedicated Public IPs

Contact your ISP to obtain a block of static public IP addresses. Most esports programs need at least 8-16 IPs:

IP Block Sizing

/29 subnet = 8 IPs (6 usable after network/broadcast/gateway)
/28 subnet = 16 IPs (14 usable)
/27 subnet = 32 IPs (30 usable)

Example: If you have 12 gaming PCs, request a /28 block

Once you have the IP block, configure 1:1 NAT (Static NAT) on your firewall:

! Example: Map private IPs to public IPs
! Assumes public IP block: 203.0.113.0/28

ip nat inside source static 10.50.0.10 203.0.113.1
ip nat inside source static 10.50.0.11 203.0.113.2
ip nat inside source static 10.50.0.12 203.0.113.3
! ... continue for each device

! Mark inside interface
interface Vlan50
  ip nat inside
  exit

! Mark outside interface
interface GigabitEthernet0/0
  ip nat outside
  exit

For gaming consoles: Use DHCP reservations based on MAC address to ensure each console always gets the same private IP, which is then mapped to its dedicated public IP.

6Configure MAC-Based Reservations (Consoles)

Gaming consoles (Xbox, PlayStation, Nintendo Switch) benefit from consistent IP assignments:

! First, find the MAC address of each console
! (Usually in System Settings → Network)

! Create DHCP reservations
ip dhcp pool XBOX_STATION_1
  host 10.50.0.10 255.255.255.0
  client-identifier 01aa.bbcc.ddee.ff
  default-router 10.50.0.1
  dns-server 8.8.8.8
  exit

ip dhcp pool PS5_STATION_1
  host 10.50.0.11 255.255.255.0
  client-identifier 0111.2233.4455.66
  default-router 10.50.0.1
  dns-server 8.8.8.8
  exit

! Then map these to public IPs (see step 5)

7Implement Quality of Service (QoS)

Prioritize gaming traffic to minimize latency and packet loss:

! Create class map for gaming traffic
class-map match-any ESPORTS_TRAFFIC
  match access-group name ESPORTS_OUTBOUND
  exit

! Create policy map
policy-map ESPORTS_QOS
  class ESPORTS_TRAFFIC
    priority percent 60
    set dscp ef
  class class-default
    fair-queue
  exit

! Apply to WAN interface
interface GigabitEthernet0/0
  service-policy output ESPORTS_QOS
  exit

QoS Benefits

• Reserves 60% of bandwidth for gaming during matches
• Marks packets with DSCP EF (Expedited Forwarding) for upstream QoS
• Prevents bufferbloat and maintains low latency
• Ensures consistent performance even when network is busy

8Configure Wireless SSID (Optional)

If wireless gaming is required (not recommended for competitive play), create a dedicated SSID:

! On wireless controller or AP
wlan ESPORTS_WIRELESS 50
  ssid ESPORTS_5G
  authentication open
  authentication key-management wpa2 psk
  wpa-psk ascii YourSecurePassword123!
  vlan 50
  no shutdown
  exit

Wireless Not Recommended

Wireless connections introduce latency variance and packet loss. Use wired ethernet whenever possible for competitive gaming. If wireless is necessary, use 5GHz band and enable WPA2-Enterprise for better security.

9Monitor and Log Network Activity

Enable logging for security and troubleshooting:

! Enable logging
logging buffered 51200
logging console warnings
logging monitor informational

! Log ACL denies
ip access-list extended ESPORTS_OUTBOUND
  ! ... existing rules ...
  deny ip any any log
  exit

! Configure SNMP for monitoring (optional)
snmp-server community public RO
snmp-server location "Esports Lab"
snmp-server contact "it@school.edu"

Consider deploying a SIEM (Security Information and Event Management) system or using your firewall's built-in analytics to track:

Bandwidth usage per device
Connection attempts to blocked sites
Unusual traffic patterns
NAT translation errors

10Test and Validate

Before going live, conduct thorough testing:

Testing Checklist

✓ Verify each device receives correct IP via DHCP
✓ Test internet connectivity from each station
✓ Launch each game and verify matchmaking works
✓ Check NAT type in game settings (should be Open/Moderate)
✓ Run speed test to verify bandwidth allocation
✓ Test voice chat functionality
✓ Attempt to access blocked websites (should fail)
✓ Monitor latency during test matches (should be <30ms)
✓ Verify logging is capturing traffic

Pilot Program

Start with 2-4 stations before full deployment. Run for 1-2 weeks monitoring performance, security, and student behavior. Adjust firewall rules as needed before expanding to full lab.

Additional Resources

For equipment-specific configuration guides:

Cisco: VLAN Configuration Guide
pfSense: VLAN Documentation
Ubiquiti: UniFi VLAN Setup
FortiGate: FortiGate VLAN Guide

Common Troubleshooting

Issue: "Strict NAT" or "Cannot Connect to Match"

Cause: NAT translation or port forwarding not configured correctly
Solution: Verify 1:1 NAT mappings, check that required ports are open in firewall, ensure no other NAT device between firewall and gaming device

Issue: High Latency During Matches

Cause: QoS not configured, bandwidth congestion, wireless connection
Solution: Implement QoS policies, upgrade internet connection, switch to wired ethernet

Issue: Game Won't Download/Update

Cause: Firewall blocking CDN or launcher ports
Solution: Verify HTTP/HTTPS (80/443) allowed, check game launcher specific ports (Steam, Epic, etc.)

VALORANT Network Requirements

System Requirements

PC - Riot Client

Component	Minimum	Recommended
Operating System	Windows 10 64-bit	Windows 11 64-bit
Processor	Intel Core i3-4150 / AMD FX-6300	Intel Core i5-9400F / AMD Ryzen 5 2600X
Graphics	NVIDIA GeForce GT 730 / AMD Radeon R7 240	NVIDIA GeForce GTX 1050 Ti / AMD Radeon R7 370
Memory	4 GB RAM	8 GB RAM
Storage	8 GB available space (SSD recommended)	16 GB available space on SSD

Port Configuration

Service Name	Protocol	Port Range
VALORANT Game Client	UDP	5000-5500, 8088
Voice Chat	TCP	Choose 50 ports from 1024-65000
Installer and Master	TCP	8393-8400
PVP.net	TCP	2099, 5222-5223
HTTP Connections	TCP	80, 443
Spectator Mode	TCP/UDP	8088

Regional Voice Ports

NA Voice Port Ranges

UDP 27016-27024

Voice Chat Configuration

Important Note

You do not need to open the entire 1024-65000 range for voice chat. Choose any 50 consecutive ports within this range (for example: 61000-61050). This provides adequate capacity while maintaining security.

Firewall Configuration Example

VALORANT Game Client Ports:

Cisco IOS ACL Configuration:

permit udp 10.50.0.0 0.0.0.255 any range 5000 5500
permit udp 10.50.0.0 0.0.0.255 any eq 8088
permit tcp 10.50.0.0 0.0.0.255 any range 8393 8400
permit tcp 10.50.0.0 0.0.0.255 any eq 2099
permit tcp 10.50.0.0 0.0.0.255 any range 5222 5223
permit tcp 10.50.0.0 0.0.0.255 any eq 8088

Voice Chat Ports (choose 50 consecutive ports):

Cisco IOS ACL Configuration:

permit tcp 10.50.0.0 0.0.0.255 any range 61000 61050
permit udp 10.50.0.0 0.0.0.255 any range 27016 27024

Rocket League Network Requirements

System Requirements

PC - Steam/Epic

PlayStation 5

Xbox Series X|S

Component	Minimum	Recommended
Operating System	Windows 10 64-bit	Windows 11 64-bit
Processor	2.5 GHz Dual Core	3.0 GHz Quad Core
Graphics	NVIDIA GeForce GTX 760 / AMD Radeon R7 270X	NVIDIA GeForce GTX 1060 / AMD Radeon RX 580
Memory	4 GB RAM	8 GB RAM
Storage	20 GB available space	20 GB available space on SSD
DirectX	Version 11	Version 12

Port Configuration - PC

Service	Protocol	Port Range
Steam Client	TCP	27015, 27036
Steam Client	UDP	27000-27030, 27036
Epic Games Services	TCP	80, 443, 3478-3479, 5222, 5795-5847
Epic Games Services	UDP	3478-3479
Rocket League Game	TCP	80, 443
Rocket League Game	UDP	7000-9000

Firewall Configuration Example

Steam Client Ports:

Cisco IOS ACL Configuration:

permit tcp 10.50.0.0 0.0.0.255 any eq 27015
permit tcp 10.50.0.0 0.0.0.255 any eq 27036
permit udp 10.50.0.0 0.0.0.255 any range 27000 27030
permit udp 10.50.0.0 0.0.0.255 any eq 27036

Epic Games Services:

Cisco IOS ACL Configuration:

permit tcp 10.50.0.0 0.0.0.255 any eq 80
permit tcp 10.50.0.0 0.0.0.255 any eq 443
permit tcp 10.50.0.0 0.0.0.255 any range 3478 3479
permit tcp 10.50.0.0 0.0.0.255 any eq 5222
permit tcp 10.50.0.0 0.0.0.255 any range 5795 5847
permit udp 10.50.0.0 0.0.0.255 any range 3478 3479

Rocket League Game Traffic:

Cisco IOS ACL Configuration:

permit udp 10.50.0.0 0.0.0.255 any range 7000 9000

Connection Requirements

Network Type

Broadband internet connection required. Minimum 3 Mbps down / 1 Mbps up. Wired ethernet strongly recommended for competitive play. Expect 40-60ms latency to game servers in optimal conditions.

Super Smash Bros. Ultimate Network Requirements

System Requirements

Nintendo Switch

Super Smash Bros. Ultimate is exclusive to Nintendo Switch. Requires:

Nintendo Switch console (any model)
Super Smash Bros. Ultimate game (digital or physical)
Nintendo Account linked to console
Internet connection
Note: Nintendo Switch Online subscription NOT required for local/tournament play, but required for online quickplay

Required Nintendo Domains

The following domains must be allowlisted for proper Nintendo Switch connectivity. This list has been compiled from schools experiencing connection issues and may not be exhaustive.

veer.hac.lp1.d4c.nintendo.net

e0d67c509fb203858ebcb2fe3f88c2aa.baas.nintendo.com

dragons.hac.lp1.dragons.nintendo.net

sun.hac.lp1.d4c.nintendo.net

accounts.nintendo.com

cdn.accounts.nintendo.com

receive-lp1.dg.srv.nintendo.net

ctest.cdn.nintendo.net

capi.lp1.op2.nintendo.net

broker.lp1.npns.srv.nintendo.net

atum.hac.lp1.d4c.nintendo.net

dauth-lp1.ndas.srv.nintendo.net

bcat-list-lp1.cdn.nintendo.net

bcat-data-lp1.cdn.nintendo.net

beach.hac.lp1.eshop.nintendo.net

app-a05.lp1.npns.srv.nintendo.net

bcat-topics-lp1.cdn.nintendo.net

lp1.npns.srv.nintendo.net

consumer.lp1.npns.srv.nintendo.net

tagaya.hac.lp1.eshop.nintendo.net

Firewall Configuration Example

Nintendo Switch Network Access:

Cisco IOS ACL Configuration:

permit tcp 10.50.0.0 0.0.0.255 any eq 443

Important Notes

• All Nintendo domains listed above must be allowlisted in your firewall
• Nintendo Switch uses dynamic ports for peer-to-peer connections
• Best practice: Configure 1:1 NAT for each console (see Configuration Guide for MAC-based reservations)

NAT Type Requirement

Critical Requirement

You MUST have an Open NAT Type (NAT Type A) to guarantee connection between Nintendo Switch consoles. This is essential for competitive play. Strict NAT (Type D or F) will prevent peer-to-peer connections. Configure 1:1 NAT with dedicated public IP per console.

How to Check NAT Type on Switch

1. Open System Settings
2. Navigate to Internet → Test Connection
3. View NAT Type result

NAT Type A or B: ✓ Good for online play
NAT Type C: ⚠ May have issues
NAT Type D or F: ✗ Will not work for competitive

For additional assistance with Nintendo Switch network configuration, refer to Nintendo Customer Support.

NBA 2K26 Network Requirements

System Requirements

PlayStation 5

Xbox Series X|S

NBA 2K26 for competitive VESL play is console-only. Supported platforms:

PlayStation 5
Xbox Series X|S

Port Configuration - PlayStation 5

Protocol	Port Range	Purpose
TCP	80, 443	HTTP/HTTPS
TCP	3478-3480	PSN Services
UDP	3074, 3478-3479	Game Traffic
TCP	3658	PlayStation Services
UDP	3658, 6000-6999	Voice Chat / Party

Port Configuration - Xbox Series X|S

Protocol	Port Range	Purpose
TCP	3074	Xbox Live
UDP	88, 500, 3074, 3544, 4500	Xbox Services
TCP	3478-3480	Game Traffic
UDP	3478-3479	Game Traffic

Firewall Configuration Examples

PlayStation 5 Configuration:

Cisco IOS ACL Configuration:

permit tcp 10.50.0.0 0.0.0.255 any eq 80
permit tcp 10.50.0.0 0.0.0.255 any eq 443
permit tcp 10.50.0.0 0.0.0.255 any range 3478 3480
permit tcp 10.50.0.0 0.0.0.255 any eq 3658
permit udp 10.50.0.0 0.0.0.255 any eq 3074
permit udp 10.50.0.0 0.0.0.255 any range 3478 3479
permit udp 10.50.0.0 0.0.0.255 any eq 3658
permit udp 10.50.0.0 0.0.0.255 any range 6000 6999

Configure 1:1 NAT for each PS5 (critical):

Cisco IOS NAT Configuration:

ip nat inside source static 10.50.0.20 203.0.113.20
ip nat inside source static 10.50.0.21 203.0.113.21

Xbox Series X|S Configuration:

Cisco IOS ACL Configuration:

permit tcp 10.50.0.0 0.0.0.255 any eq 3074
permit tcp 10.50.0.0 0.0.0.255 any range 3478 3480
permit udp 10.50.0.0 0.0.0.255 any eq 88
permit udp 10.50.0.0 0.0.0.255 any eq 500
permit udp 10.50.0.0 0.0.0.255 any eq 3074
permit udp 10.50.0.0 0.0.0.255 any eq 3544
permit udp 10.50.0.0 0.0.0.255 any eq 4500
permit udp 10.50.0.0 0.0.0.255 any range 3478 3479

Configure 1:1 NAT for each Xbox (critical):

Cisco IOS NAT Configuration:

ip nat inside source static 10.50.0.30 203.0.113.30
ip nat inside source static 10.50.0.31 203.0.113.31

Console NAT Requirements

Critical for Consoles

PlayStation 5: Requires NAT Type 2 or better. Type 3 will cause connection issues.
Xbox Series X|S: Requires Open NAT. Moderate may work but not recommended. Strict NAT will fail.

Solution: Assign dedicated public IP to each console using 1:1 NAT and MAC-based DHCP reservations (see Configuration Guide for details).

Connection Requirements

Network Type

Broadband internet required. Minimum 5 Mbps down / 2 Mbps up. Wired ethernet strongly recommended. Online gameplay requires stable, low-latency connection (preferably <50ms to 2K servers).

Brawlhalla Network Requirements

System Requirements

PC - Steam

PlayStation 4/5

Xbox One/S/Series X|S

PC Requirements:

Component	Minimum	Recommended
Operating System	Windows 7, 8, 10 (64-bit)	Windows 10/11 (64-bit)
Processor	Dual Core 2.0 GHz	Quad Core 2.5 GHz
Graphics	Intel HD 4000 or better	NVIDIA GeForce GTX 660 / AMD Radeon HD 7870
Memory	2 GB RAM	4 GB RAM
Storage	1 GB available space	2 GB available space
DirectX	Version 10	Version 11

Console Platforms:

PlayStation 4
PlayStation 5
Xbox One
Xbox One S
Xbox Series X
Xbox Series S

Port Configuration - PC/Steam

Service	Protocol	Port Range
Steam Client	TCP	27015, 27036
Steam Client	UDP	27000-27030, 27036
HTTP/HTTPS	TCP	80, 443

Port Configuration - PlayStation 4/5

Protocol	Port Range	Purpose
TCP	80, 443	HTTP/HTTPS
TCP	3478-3480	PSN Services
UDP	3074, 3478-3479	Game Traffic
TCP	3658	PlayStation Services

Port Configuration - Xbox One/S/Series X|S

Protocol	Port Range	Purpose
TCP	3074	Xbox Live
UDP	88, 500, 3074, 3544, 4500	Xbox Services
TCP	3478-3480	Game Traffic
UDP	3478-3479	Game Traffic

Firewall Configuration Examples

PC/Steam Configuration:

Cisco IOS ACL Configuration:

permit tcp 10.50.0.0 0.0.0.255 any eq 27015
permit tcp 10.50.0.0 0.0.0.255 any eq 27036
permit udp 10.50.0.0 0.0.0.255 any range 27000 27030
permit udp 10.50.0.0 0.0.0.255 any eq 27036
permit tcp 10.50.0.0 0.0.0.255 any eq 80
permit tcp 10.50.0.0 0.0.0.255 any eq 443

PlayStation 4/5 Configuration:

Cisco IOS ACL Configuration:

permit tcp 10.50.0.0 0.0.0.255 any eq 80
permit tcp 10.50.0.0 0.0.0.255 any eq 443
permit tcp 10.50.0.0 0.0.0.255 any range 3478 3480
permit tcp 10.50.0.0 0.0.0.255 any eq 3658
permit udp 10.50.0.0 0.0.0.255 any eq 3074
permit udp 10.50.0.0 0.0.0.255 any range 3478 3479

Xbox One/S/Series X|S Configuration:

Cisco IOS ACL Configuration:

permit tcp 10.50.0.0 0.0.0.255 any eq 3074
permit tcp 10.50.0.0 0.0.0.255 any range 3478 3480
permit udp 10.50.0.0 0.0.0.255 any eq 88
permit udp 10.50.0.0 0.0.0.255 any eq 500
permit udp 10.50.0.0 0.0.0.255 any eq 3074
permit udp 10.50.0.0 0.0.0.255 any eq 3544
permit udp 10.50.0.0 0.0.0.255 any eq 4500
permit udp 10.50.0.0 0.0.0.255 any range 3478 3479

Connection Requirements

Connection Type

Broadband internet connection required. Game uses peer-to-peer networking for matches, so low latency and stable connection is critical. Wired ethernet strongly recommended for all platforms.

Fortnite Network Requirements

System Requirements

PC - Epic Games

PlayStation 4/5

Xbox One/S/Series X|S

Mobile (iOS/Android)

PC Requirements:

Component	Minimum	Recommended
Operating System	Windows 10 64-bit	Windows 11 64-bit
Processor	Intel Core i3-3225 / AMD FX-4350	Intel Core i5-7300U / AMD Ryzen 3 3300U
Graphics	Intel HD 4000 / AMD Radeon Vega 8	NVIDIA GeForce GTX 960 / AMD Radeon R9 280
Memory	8 GB RAM	16 GB RAM
Storage	26 GB available space	26 GB available space on SSD
DirectX	Version 11	Version 12

Console Platforms:

PlayStation 4
PlayStation 5
Xbox One
Xbox One S
Xbox Series X
Xbox Series S

Mobile Platforms:

Android: OS 8.0 or higher, 4GB RAM minimum, Adreno 530 GPU or equivalent
iOS: iPhone 6S Plus or newer, iPad Mini 4 or newer, iPad Air 2 or newer, iPad Pro (all models)

Port Configuration - PC

Service	Protocol	Port Range
HTTP/HTTPS	TCP	80, 443
Epic Games Services	TCP	3478-3479, 5222, 5795-5847
Epic Games Services	UDP	3478-3479

Port Configuration - PlayStation 4/5

Protocol	Port Range	Purpose
TCP	80, 443	HTTP/HTTPS
TCP	3478-3480	PSN Services
TCP	5222, 5795-5847	Epic Games Services
UDP	3074, 3478-3479	Game Traffic
TCP	3658	PlayStation Services

Port Configuration - Xbox One/S/Series X|S

Protocol	Port Range	Purpose
TCP	3074	Xbox Live
TCP	3478-3480	Game Traffic
TCP	5222, 5795-5847	Epic Games Services
UDP	88, 500, 3074, 3544, 4500	Xbox Services
UDP	3478-3479	Game Traffic

Port Configuration - Mobile (iOS/Android)

Mobile devices use the same Epic Games Services ports as other platforms:

Protocol	Port Range
TCP	80, 443, 3478-3479, 5222, 5795-5847
UDP	3478-3479

Note: Mobile devices typically connect via school wireless network. Ensure mobile traffic is allowed through your wireless VLAN firewall rules.

Firewall Configuration Examples

PC Configuration:

Cisco IOS ACL Configuration:

permit tcp 10.50.0.0 0.0.0.255 any eq 80
permit tcp 10.50.0.0 0.0.0.255 any eq 443
permit tcp 10.50.0.0 0.0.0.255 any range 3478 3479
permit tcp 10.50.0.0 0.0.0.255 any eq 5222
permit tcp 10.50.0.0 0.0.0.255 any range 5795 5847
permit udp 10.50.0.0 0.0.0.255 any range 3478 3479

PlayStation 4/5 Configuration:

Cisco IOS ACL Configuration:

permit tcp 10.50.0.0 0.0.0.255 any eq 80
permit tcp 10.50.0.0 0.0.0.255 any eq 443
permit tcp 10.50.0.0 0.0.0.255 any range 3478 3480
permit tcp 10.50.0.0 0.0.0.255 any eq 5222
permit tcp 10.50.0.0 0.0.0.255 any range 5795 5847
permit tcp 10.50.0.0 0.0.0.255 any eq 3658
permit udp 10.50.0.0 0.0.0.255 any eq 3074
permit udp 10.50.0.0 0.0.0.255 any range 3478 3479

Xbox One/S/Series X|S Configuration:

Cisco IOS ACL Configuration:

permit tcp 10.50.0.0 0.0.0.255 any eq 3074
permit tcp 10.50.0.0 0.0.0.255 any range 3478 3480
permit tcp 10.50.0.0 0.0.0.255 any eq 5222
permit tcp 10.50.0.0 0.0.0.255 any range 5795 5847
permit udp 10.50.0.0 0.0.0.255 any eq 88
permit udp 10.50.0.0 0.0.0.255 any eq 500
permit udp 10.50.0.0 0.0.0.255 any eq 3074
permit udp 10.50.0.0 0.0.0.255 any eq 3544
permit udp 10.50.0.0 0.0.0.255 any eq 4500
permit udp 10.50.0.0 0.0.0.255 any range 3478 3479

Mobile (iOS/Android) Configuration:

Mobile devices on wireless network (adjust subnet to match your wireless VLAN):

Cisco IOS ACL Configuration:

permit tcp 10.30.0.0 0.0.0.255 any eq 80
permit tcp 10.30.0.0 0.0.0.255 any eq 443
permit tcp 10.30.0.0 0.0.0.255 any range 3478 3479
permit tcp 10.30.0.0 0.0.0.255 any eq 5222
permit tcp 10.30.0.0 0.0.0.255 any range 5795 5847
permit udp 10.30.0.0 0.0.0.255 any range 3478 3479

Connection Requirements

Network Type

Broadband internet connection required. Minimum 3 Mbps download, 1 Mbps upload recommended for optimal performance. Lower latency results in better gameplay experience—target <50ms to Epic servers. Mobile devices require stable WiFi connection (5GHz recommended).

Additional Resources

For detailed Epic Games Launcher firewall configuration: Epic Games Support Article

Marvel Rivals Network Requirements

System Requirements

PC - Steam/Epic

PlayStation 5

Xbox Series X|S

PC Requirements:

Component	Minimum	Recommended
Operating System	Windows 10 64-bit (1909 or newer)	Windows 11 64-bit
Processor	Intel Core i5-6600K / AMD Ryzen 5 1600X	Intel Core i5-10400 / AMD Ryzen 5 5600X
Graphics	NVIDIA GeForce GTX 1060 / AMD RX 580 / Intel Arc A380	NVIDIA GeForce RTX 2060 Super / AMD RX 5700-XT / Intel Arc A750
Memory	16 GB RAM	16 GB RAM
Storage	70 GB available space	70 GB available space on SSD
DirectX	Version 12	Version 12
Resolution	1920 x 1080 minimum	1920 x 1080 or higher

Console Platforms:

PlayStation 5
Xbox Series X
Xbox Series S

Port Configuration - PC

Service	Protocol	Port Range
HTTP/HTTPS	TCP	80, 443
Marvel Rivals Game	TCP	8880-8881, 9000-9002, 10002-10005, 10200-10204
Steam (if applicable)	TCP	27015, 27036
Steam (if applicable)	UDP	27000-27030
Epic Games (if applicable)	TCP	3478-3479, 5222, 5795-5847
Epic Games (if applicable)	UDP	3478-3479

Port Configuration - PlayStation 5

Protocol	Port Range	Purpose
TCP	80, 443	HTTP/HTTPS
TCP	8880-8881, 9000-9002, 10002-10005, 10200-10204	Marvel Rivals Game
TCP	3478-3480	PSN Services
UDP	3074, 3478-3479	Game Traffic
TCP	3658	PlayStation Services

Port Configuration - Xbox Series X|S

Protocol	Port Range	Purpose
TCP	3074	Xbox Live
TCP	8880-8881, 9000-9002, 10002-10005, 10200-10204	Marvel Rivals Game
UDP	88, 500, 3074, 3544, 4500	Xbox Services
TCP	3478-3480	Game Traffic
UDP	3478-3479	Game Traffic

Firewall Configuration Examples

Marvel Rivals Game Ports:

Cisco IOS ACL Configuration:

permit tcp 10.50.0.0 0.0.0.255 any eq 80
permit tcp 10.50.0.0 0.0.0.255 any eq 443
permit tcp 10.50.0.0 0.0.0.255 any range 8880 8881
permit tcp 10.50.0.0 0.0.0.255 any range 9000 9002
permit tcp 10.50.0.0 0.0.0.255 any range 10002 10005
permit tcp 10.50.0.0 0.0.0.255 any range 10200 10204

If using Steam launcher:

Cisco IOS ACL Configuration:

permit tcp 10.50.0.0 0.0.0.255 any eq 27015
permit tcp 10.50.0.0 0.0.0.255 any eq 27036
permit udp 10.50.0.0 0.0.0.255 any range 27000 27030

If using Epic Games launcher:

Cisco IOS ACL Configuration:

permit tcp 10.50.0.0 0.0.0.255 any range 3478 3479
permit tcp 10.50.0.0 0.0.0.255 any eq 5222
permit tcp 10.50.0.0 0.0.0.255 any range 5795 5847
permit udp 10.50.0.0 0.0.0.255 any range 3478 3479

PlayStation 5 Configuration:

Cisco IOS ACL Configuration:

permit tcp 10.50.0.0 0.0.0.255 any eq 80
permit tcp 10.50.0.0 0.0.0.255 any eq 443
permit tcp 10.50.0.0 0.0.0.255 any range 8880 8881
permit tcp 10.50.0.0 0.0.0.255 any range 9000 9002
permit tcp 10.50.0.0 0.0.0.255 any range 10002 10005
permit tcp 10.50.0.0 0.0.0.255 any range 10200 10204
permit tcp 10.50.0.0 0.0.0.255 any range 3478 3480
permit tcp 10.50.0.0 0.0.0.255 any eq 3658
permit udp 10.50.0.0 0.0.0.255 any eq 3074
permit udp 10.50.0.0 0.0.0.255 any range 3478 3479

Xbox Series X|S Configuration:

Cisco IOS ACL Configuration:

permit tcp 10.50.0.0 0.0.0.255 any eq 3074
permit tcp 10.50.0.0 0.0.0.255 any range 8880 8881
permit tcp 10.50.0.0 0.0.0.255 any range 9000 9002
permit tcp 10.50.0.0 0.0.0.255 any range 10002 10005
permit tcp 10.50.0.0 0.0.0.255 any range 10200 10204
permit tcp 10.50.0.0 0.0.0.255 any range 3478 3480
permit udp 10.50.0.0 0.0.0.255 any eq 88
permit udp 10.50.0.0 0.0.0.255 any eq 500
permit udp 10.50.0.0 0.0.0.255 any eq 3074
permit udp 10.50.0.0 0.0.0.255 any eq 3544
permit udp 10.50.0.0 0.0.0.255 any eq 4500
permit udp 10.50.0.0 0.0.0.255 any range 3478 3479

Launcher Requirements

Important

Marvel Rivals can be launched through Steam or Epic Games Store. Ensure all ports for your chosen launcher are open in addition to the game-specific ports listed above.

Network Configuration

Marvel Rivals requires stable, low-latency internet connection for optimal competitive play. The game uses dedicated servers for matchmaking.

Connection Requirements

Broadband internet connection required. Recommended: 25+ Mbps download, 5+ Mbps upload. Low-latency, stable connection essential for competitive play. Wired ethernet strongly recommended over wireless.

Authentication Required

Permission Required

Esports Network and Port Configuration Guide