WAN IP Alias / Port forwarding / WAN IP Alias / "source port already exists"
WAN IP Alias / Port forwarding / WAN IP Alias / "source port already exists"
Hi,
I have a WAN connection with several public IPs (28 subnet). I have configured the WAN2 like:
IP: 82.216.XXX.242
SM: 255.255.255.240
GW: 82.216.XXX.141
I then added all IPs (like 82.216.XXX.243, 82.216.XXX.244, 82.216.XXX.245, etc.) as WAN IP alias adresses.
Then, under "Transmission" "NAT" I added some port forwardings. I have port 10000 to be forwarded on the main IP (82.216.XXX.242). Hence, I left the "WAN IP" selection empty.
When trying to add another port forwarding for the same port, but selecting another WAN IP (82.216.XXX.243) I get the error "The source port already exists for the chosen interface(s). Please change the source port.".
I even tried to set another WAN IP for my first port forwarding. Simply, so that a WAN IP is selected and that this field is not empty. Same result.
Is this a bug? Anything I did wrong?
BR
C
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Does anyone have information if this is already solved? THere was a major update for the Omada Controller Software but I do not know, if this problem has been solved with this new version. C
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Honkman Is there anyone from TP-Link followinfg this thread? Any idea when this basic function will be implemented and availabel?
BR
C
- Copy Link
- Report Inappropriate Content
@Honkman I am facing the issue with the ER605. Since we are not able to do port forwarding, is it possible to "manually" add the rules in ACL?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1164
Replies: 14
Voters 0
No one has voted for it yet.