Actions
Bug #8341
closedNAT Port forwarding issues (port collision from internal host)
Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
02/20/2018
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.2_1
Affected Architecture:
Description
I think this should be omitted by design:
Found following constellation who troubled me for many hours:
PortNAT: Internet incoming -> DstPort 55555 -> Internal host "UNO" DstPort 55555
LAN host "DUE" connects with (random) SrcPort 55555 to DstPort MQTT internet
In this case MQTT is a longterm active connection and omits new connections for the incoming PortNAT for many hours.
As workaround i made a rule who blocks LAN outgoing src port 55555
But i think this is something that should be solved internally?
Files
Actions
Also available in: Atom