How do I change the IP to other IP than 192.168.12.x?

  • 15 January 2022
  • 3 replies


I have an existing TPLINK AX11000 router that is setup with the 192.168.10.x network with a bunch of IOT devices in that subnet (static and dynamic addresses).  I am able to plug the Tmobile 5G gateway into the WAN port of my existing router and everything works as is.  (with Tmobile as the WAN network at 192.168.12.x)

However, all wifi and hardwired connections behind  my AX11000 router are at least 50% slower than devices that are connected directly to the Tmobile 5G gateway. Not sure if it is a double NAT latency that caused this.

Is there a way to change the IP on the Tmobile 5G gateway to use 192.168.10.x so I can modify my router to be switch/access point so they are on the same internal network.  it will be too cumbersome to change my internal devices to be on the 192.168.12.x and change my internal router to match.  


3 replies

I’m in the same boat and can’t find any info on how to change the served DHCP subnet on the device. Pretty disappointing from an otherwise decent services.


I just spoke with a Tmobile support team member.  Unfortunately there is no way to change the default IP address range on the Tmobile 5G home internet.  I will have to change all of my devices to be on the 192.168.12.x range if I want to flatten my network to be all on the same subnet.  

Not sure if the future firmware update will allow this change to happen. 


Thanks for the response!

I got the same answer from a support rep today. The level 1 rep I spoke with didn’t really understand the issue (he kept going back to / thinking it’s a wifi connectivity issue...) until I explained it 3 different ways. Finally he said it’s not possible. I asked him to submit a change request, which he said he would; and he said that all support calls are recorded (and inferred all were listened to - highly doubtful) and my query and suggestion would be heard.

We’ll see. I’ve never seen a router that didn’t allow the user to change its IP address and/or its DHCP range. While I like the service, this is a HUGE issue that needs to be addressed. It can be a show-stopper for some, and a real pain for most. Let’s hope a firmware update will do it and that they actually do address the issue.