Deco X60 port Forwarding issue
I just bought Deco X60 pack of 3 a week ago. While setting up port forwarding I found this issue.
https://youtu.be/TuA-k4__L1Y
So far the only workaround I was able to find set ip of the device I need to forward in range of 192.168.0.1/24.
My network settings are
Range: 192.168.0.1/22
Subnet: 255.255.252.0
Gateway: 192.168.0.1
Deco is setup in router mode and as DHCP server.
I was only able to test this issue on android app as I don't own any iOS devices.
Please suggest changes if I have made any configuration errors.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi, thank you all for reminding, this issue is not forgotten, it will be fixed in the next version firmware, please kindly wait for the new firmware.
- Copy Link
- Report Inappropriate Content
@TP-Link_Deco Any estimate about when this new firmware can be available ?
Until then, my domotica is unreachable from outside my LAN, as it is on a subnet 192.168.70.x while the default gateway is on 192.168.68.x.
So the port forwarding keeps defaulting back to the 192.168.68.x subnet....
Changing the IP address of the domotica is not an option as a lot of things rely on the static ip addresses assigned within our LAN.
The issue started with updating the X60 to the latest firmware. So a quick fix would be much appreciated !
- Copy Link
- Report Inappropriate Content
Thank you very much for your continuous concern about this case.
The beta firmware would be released in the next few weeks.
Once there is any updated news, I could come back here as once.
Thanks a lot for your time and patience.
- Copy Link
- Report Inappropriate Content
Exactly the same issue here. Desperately need a fix. I need to port forward to my VPN server which has a static local address. This has been working fine for my old TPLINK C7 router. When I switch over to the Dec x60 and do the same port forwarding I get the 192.168.1.18 address changing to 192.168.0.18 issue and external access to the vpn server doesn't work. I have to delay implementation until this is fix appropriately. Not willing to entertain changes to the ip address range or other stop gap fixes. This is a standard feature every router has had for many years, I never anticipated these sort of issues.
- Copy Link
- Report Inappropriate Content
Still waiting for a fix for this issue. Has there been a firmware update to resolve it, or has it been forgotten and Tplink has moved on to the next product and left existing users with DECO's that aren't working properly.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi, this issue has not been forgotten and it would be fixed in the later firmware upgrade.
But I haven't got the updated news about the exact time of the firmware release date;
Currently, there is a workaround:
Please try to change the subnet mask under the LAN IP address to be 255.255.255.0;
Thank you very much for your understanding and support.
- Copy Link
- Report Inappropriate Content
@TP-Link Sorry but that is not an acceptable answer...
On my last post of 2020-11-30, the feedback from you was a firmware update was coming 'in the next few weeks'.
We're almost 3 months later. Still no firmware upgrade.
The 'workaround' is not a workaround, as I need the extra subnets - I'm not happy to re-do the whole network thing because of a delayed firmware upgrade ?
So please, please launch a hotfix for this bad firmware upgrade. That s right, the issue was caused by a new firmware upgrade that broke what was working well.
- Copy Link
- Report Inappropriate Content
This is still broken and it's been months. Every other router does this just fine. Changing the subnet mask to 255.255.255.0 is not working.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 6172
Replies: 25