@CarlosGeadas 

Definitely needing firmware update and features added.

I am wishing I had stayed with my M4 system.

Jason

@CarlosGeadas 

I have several tp-link products and I think they are shipping with less and less features. Soon, all the visible features we'll get is a on/off switch and status led. The first wifi extender I got stated, for example, the % of signal strength - a percentage. The more modern one that I got later, only said "signal strong/weak/etc". This is worst since, with a number, I can get a more accurate best position/placement indication than a mere "good/excelent" statement.

It's not just the P9, it's with all the products. I really don't get it.

Would it be bad to have a 3 output/configuration level system? A "simple" output for the people how really don't care/don't know and just want to plug and play. A second output level for the people how understand and/or want to have control, where they can choose ip ranges/subnet's, values, see detailed values, etc. And a third level for the "rocket scientists" out there how really want to control the last possible bit of configuration. This is not hard to do, I just don't know if the product managers would like to offer "so much" for the price they charge.

So I guess I'll just wait for the firmware updates and hope I can get one or two of the needed features before the updates only update the v2+ of the hardware.

This shoud be understood as a constructive criticism - in the end, I keep buying tp-link's products, which are good (not as good as advertised), but could easilly be great.

@CarlosGeadas This is absurd - a router that isn't able to change a local LAN IP. A health warning label should have been placed at the front of the box. I just purchased the P9 and looks like Ive got to ditch tp link all together.

@JenGardner 

If it had only said, "This is half-baked tech" I certainly would have not bought it.

@CarlosGeadas I am very disappointed that we cannot change the DHCP lease range. I would have purchased a different model if I knew this was the case. Sigh... I hope they fix it soon.

@MgaLawin 

I've checked yesterday for new firmware and nothing. This product continues with the 1.0.0 build, from 19/07/2019. I really expected more and better.

@Kevin_Z That is the dumbest thing I have ever heard. So now all my devices that connect via wifi and dhcp cannot talk to my other devices using a different static ip address range because not only does the P9 assign a completely different DHCP range to my router, even though I have set a static IP on the P9 device, it's DHCP range is not even configurable!! To suggest assigning static ip addresses to every device in the house is stupid. Please fix this problem asap. This has completely broken my hive installation as Amazon Echo devices can no longer connect to the Hive Hub. You've turned my smart home into a dumb home!

EDIT: And it also means that the printers connected to my server are no longer accessible to any of my kids computers  

@CarlosGeadas 

+1 for getting this sorted ASAP.

Such a basic request.

Wish I could return the product!!

@CarlosGeadas 

Any word from tp-link on this?  Seems like it has been quite a while and I agree this feature is sorely needed.  I get they are trying to keep things simple, but there are times when this function is needed.

CarlosGeadas wrote

Hi,

 

Is there any way to change the IP address range to be assigned to clients when in Router mode?

I'm getting a 192.168.68.x DHCP range, but I have some existing equipments with fixed IP at 192.168.1.x range that I want to maintain as they are. So I need P9 to allow me to specify the IP allocation range.

 

How can I do it?

 

Thank you!