WARFRAME CONNECTION CHECKLIST

Record your own values; the guide's LAN addresses are examples.

Platform / game version:
Date and time:
Router model / firmware:
Connection: home / hotspot / campus / VPN
VPN provider, location and NAT mode (if used):
Exact Warframe network-analysis message:
Game UDP pair:
Gaming device LAN IPv4:
DHCP reservation:
Router WAN IPv4 (compare privately with home public IPv4 outside VPN):
ISP confirms public IPv4 with incoming UDP access: yes / no / unknown
Second router upstream: yes / no / unknown

ONE CHANGE AT A TIME
[ ] Allow Warframe through the active firewall profile.
[ ] Check router UPnP; on PC, check the game UPnP/NAT-PMP setting too.
[ ] If automatic mapping works, keep it and test invites.
[ ] Give a second PC a different in-game pair before creating its rules.
[ ] If using manual rules, match protocol UDP + both game ports + LAN IP.
[ ] Follow the game's manual setup guidance for disabling automatic mapping.
[ ] Check other devices before changing router-wide UPnP.
[ ] Check CGNAT / double NAT if the warning remains.

Device 1: LAN IP ______ ; UDP pair ______ / ______
Device 2: LAN IP ______ ; UDP pair ______ / ______

VERIFICATION
Network-analysis message after change:
I can join a friend: yes / no
Friend can join me: yes / no
Mission loads with both players: yes / no
Voice chat works (if used): yes / no
Second peer tested:
Both home devices tested at once:
Result after restarting / reconnecting VPN:

NEXT ACTION
[ ] Warning cleared and invites work: save settings and stop.
[ ] Strict NAT remains: check the home upstream connection or VPN route.
[ ] Warning cleared but invites fail: compare with another friend.
[ ] Relevant route already checked: send results to the provider or Warframe Support.

FOR SUPPORT
Attach the exact warning, platform, router model, selected UDP ports and
results. On PC, use the launcher's gear menu > Get Logs when requested.
Send logs privately to Warframe Support; do not post them publicly.