255.255.255.0 or /24 gives us max of 256 IPs, if we want to have range of 512 IP like in my case I need to set it 255.255.254.0 or /23. This is definitely a bug because if we want ip range from 192.168.0.1- 192.168.1.254 we need to set subnet to /23 http://jodies.de/ipcalc?host=192.168.0.1&mask1=23&mask2= and if i set port forwarding for IP 192.168.1.251 its gets set to 192.168.0.251 instead. i have switched deco to AP mode for now, but would prefer to use it in router mode

@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 !

@TP-Link 

 

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.

@TP-Link_Deco 

 

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.

I guess I am right, silence on this issue, means TPlink have moved on without fixing it. What happened to the beta firmware fix from November ??

@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.

@Vraj.Patel 

 

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.