Project

General

Profile

Actions

Bug #14065

closed

UPnP not working when WAN IP is private IP range.

Added by Greger Blennerud over 1 year ago. Updated over 1 year ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
UPnP/NAT-PMP
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
All
Affected Architecture:
All

Description

The changes and updates to miniupnp that have been made in the last year have been much appreciated by everyone having gamers in their households. However, there is still an issue for those who are stuck behind a modem or router providing a private IP to pfsense WAN. One where bridge mode is not available, such as most consumer 4G/5G routers.

The issue is not related to double NAT. Rather it simply seems to throw an error if WAN IP is detected to be private IP.
All games tested (mostly various CoD games) get Open NAT despite the double NAT situation provided the IP on the WAN side is * not * of "private IP tyoe". A further prerequisite is that pfsense is placed in DMZ (all ports open) on the upstream router. Testing verified on LTE-router which allows setting any IP range on LAN side.

Providing a simple override mechanism to manually force UPnP not to check for Private IP, would solve this "bug" in a simple way...

Actions

Also available in: Atom PDF