Virtual Servers (Port Forwarding) RANGE issue on TP-Link Archer VR1210v
Hi Everyone.
I'm writing to report an issue I found regarding the "Virtual Servers" configuration into the "NAT Forwarding" section of the EVDSL Modem TP-Link Archer VR1210v. Below the information of the hardware and software used.
Device: TP-Link Archer VR1210v
Hardware Version: Archer VR1210v v1 00000001
Firmware Version: 2.0.0 0.9 v6041.0 Build 220304 Rel.6349n
The issue I've found is the following:
I am used to attribute sequential ports to the same private IP, so I can unlock all the port for the same device/IP defining only one entry in the modem configuration GUI and using the port range definition instead of defining a single entry per port.
I make an example: for the device with the private IP 192.168.1.177 I've a series of exposed services which runs in the port range 7430-7468. What I usually do is to define a single rule with the port range definition, inserting the port range in the option "External Port", leaving Blank the option "Internal Port".
Below I report a screenshot of the rule on the same Archer VR1210v device I am referring to
To define the port range, I leave the option "Internal Port" as empty. In the past I did for an old router (Archer C2) and this configuration worked as expected.
However on the VR1210v device, when I confirm this configuration pressing the OK button, the entry automatically populates the option "Internal Port", inserting the first port of the "External Port" range defined (example reported below, as the entry appears in list after pressing "OK")
I tried to figure out if the automatic fill-in of the option "Internal Ports" is just a matter of easthetic representation of the entry or it affects the performances/configuration of the "Port Forwording" and, unfortunately, it does. In fact, if from the extranet I direct traffic to one of the ports of the range, traffic is not blocked but it is all redirected to the first port of the range which has been automatically added to the voice "Internal Port".
Referring to the example reported above: If I direct traffic to myip:7445 (where we assume "myip" is my public IP address), traffic is correctly directed to private IP 192.168.1.177 BUT the port which is used is 7430 and not 7445 (the one automatically defined as "Internal Port"). So every call directed to one of the ports of the range will result in a call directed to the port 7430 (first port of the range).
Can somebody suggest me a solution to let "Internal Port" option stay blank? I tried in many ways but I didn't figure it out to how make it work.
I hope somebody might help me.
Thank you