Project

General

Profile

Actions

Feature #7727

open

uPnP fails to properly give out subsequent reservations when multiple gaming systems are playing the same game/using the same port.

Added by Anonymous about 4 years ago. Updated about 2 months ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
UPnP/NAT-PMP
Target version:
Start date:
07/26/2017
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default

Description

It's a bug with pfsense, at least in my eyes (nearly 15 years experience in IT and am a senior security engineer with a fortune 500 company). You currently cannot have 2 systems, whether console or gaming PC playing the same game at the same time using pfsense. The second client will always fail to connect. I have done everything you are supposed to do:Static outbound ports, uPnP ACL, firewall rules, NAT reflection. I even hired a freelancer with pfsense experience going back to when it was monowall. He took 10 minutes to look at my config and told me that it looked exactly how it was supposed to look. He then did his own troubleshooting and came to the exact conclusion that I did. uPnP is broken in pfsense 2.4.

Just to prove a point I plugged in my netgear r8500, booted it up, updated its firmware and restored defaults. Upon the subsequent reboot, the 2 clients picked up uPnP reservations immediately (unlike pfsense where it takes 30+ seconds to get the one that does eventually pickup) and both reported back with open nat. I was able to join the same lobbys with both clients and play together for extended periods.


Files

miniupnpd-2.1.20190210,1.txz (64.3 KB) miniupnpd-2.1.20190210,1.txz Jim Pingle, 06/01/2020 03:37 PM
Actions

Also available in: Atom PDF