How to change the LAN port IP of a Tenda router? Both versions have conflicts with 192.168.0.1, and after I changed them, I found the IP changes on its own

cousin moved, he called me to install the network. His main router is a Mercury D191G, and his study is far away. I brought my retired Tenda AC10 over to serve as an AP for the backup signal. With all the cables connected, here's the problem: both routers default to 192.168.0.1. I type 0.1 in my browser, and sometimes it goes to Mercury backend, sometimes Tenda backend—it all depends on who answers first. The equipment also fluctuates between good and bad; the robot vacuum disconnects every ten minutes. This is a LAN IP collision, and one of them needs to be replaced. The Mercury unit that runs the main router won't be touched; I'll fix it myself.

both are 192.168.0.1, how did they collide

first clarify this matter. The LAN port IP is the router's house number in its own local area network. The router uses this address to provide backend pages and DHCP services. Mercury and Tengda come with default 192.168.0.1. Using either device alone works fine, but the problem is that both have to be connected to the same network.

my cousin's method is LAN-to-LAN: Mercury LAN port has a cable plugged into Tenda's LAN port, leaving Tenda's WAN port empty, downgrading it to switch plus AP. This connection method is correct. I've previously written about the full process of old router switching to AP, and the problem is that two identical house numbers appear in one network. DHCP services on both machines are sending addresses simultaneously, so the devices obey whoever gets the gateway, causing network chaos. That's why changing the AP requires two things: change the LAN port IP to a different one, and turn off DHCP. can only have one per site, I only remembered this after I fell into a trap.

there's another way to mention it: in optical modem router mode, some custom models have LAN side 192.168.0.1, which clashes with Tenda. How do you determine who should yield to whom in this situation? I wrote about the method in my article about IP conflicts between optical modem and router, and the approach is universal. As for the company VPN running the 192.168.0.0/24 substation, which causes disconnections when connecting to the VPN while working from home, the entire segment needs to be replaced. I have written a detailed account of the entire switching process for the Mercury version, the article about changing from 192.168.0.1 to 2.1 just follow the instructions; Tenda only has a different menu path.

Before

start, make sure to understand: the new and old interfaces have different menu names

the most annoying thing about Tenda is that the new and old firmware menus don't match at all. If you search online for tutorials and click for a long time without finding the menu, 90% of the time it's because the tutorial is different from the interface of your machine. I wrote about interface recognition methods in the article about 0.1 not opening, so here I'll give a direct conclusion.

my AC10 is an older model, the backend path is tendawifi.com, and after logging in, go to the left menu for network parameters, open LAN port settings, and fill in 192.168.0.1 in the IP address field. By the way tendawifi.com this domain is locally resolved by the router's own DNS, and it always points to the router's current IP. So after changing the subnet, you can still access the domain without memorizing the numbers. I'll use this fun fact later.

use as an AP: change the LAN port IP to the same network segment 0.2

to open and reform. Connect your computer to Tenda's WiFi (not connected yet, so single-player operation is most stable). Enter the tendawifi.com browser, find LAN port settings, change the IP address from 192.168.0.1 to 192.168.0.2, keep the subnet mask 255.255.255.0 unchanged, and save. The router will restart itself. Once you start up, 0.1 is no longer the same device. Enter 192.168.0.2 in your browser to verify. If it works, it means the change was successful.

here's a clear selection idea: when using an AP, the IP should be the same subnet as the main router, staggering only the last bit. Mercury is 0.1, Tenda changes it to 0.2, so you can directly press 0.2 on any device to manage Tenda. If you switch to 192.168.3.1 for cross-network segments, you might not find it in AP mode. The last digit ranges from 2 to 254. Do not use 0 or 255, and do not use the main router ranges frequently allocated in the DHCP pool, to avoid collisions with dynamic addresses. I changed it to 0.2 because Mercury's DHCP pool starts at 100, and the front addresses are reserved for fixed devices, which is safe.

after changing the IP, one step left to wrap up: shut down Tenda's DHCP servers. For older models, uncheck and enable in the DHCP server settings; New machines don't need to fuss over this; just switch to work mode. the universal relay article mentioned the client plus AP mode, IP is assigned by the main router. Two generations of machines, two paths, but the same destination: only Mercury remains on the entire internet, the only one who spawns.

use the main router: replace the entire segment, following the same approach as Mercury's modification

if your Tenda is the main router and you want to avoid the zero segment of the VPN or optical modem, then it's not just about missing one segment—you need to replace the entire subsidiary. Same menu: this time enter IP 192.168.3.1 (avoid segments 0, 1, 2, which are often occupied by optical modems and printers, and don't use 31, Xiaomi router is used by default), save and restart.

there are three differences between the method of modifying it as an AP. First, DHCP can't turn off , and you also need to check if the address pool is following the new network segment. Older firmware sometimes has to manually change the pool from 192.168.0.100 to 192.168.3.100. If you don't change it, the address the device receives doesn't match the gateway, so you can't access the network. Second, after the change tendawifi.com the domain can still be accessed. As mentioned earlier, it points to the router's current IP, which is more user-friendly than digital addresses. Third, the WAN port internet settings are completely unaffected, dial-up information remains the same and doesn't need to be refilled.

chain reaction after revision, three things must be investigated

changing an IP isn't just about saving and restarting; it dragged on three more times, and the first time I changed, I missed the second one.

first case, all devices that have been linked to static IPs have lost contact. I bound the static address 192.168.0.106 to the TV box on the AC10, changed it to 0.2, and the DHCP pool stayed the same, but the box was fine; but if you switch the entire segment to 3.1, all devices manually filling in static IPs have to change their addresses and gateways to three segments one by one. Devices like printers and NAS that don't speak on their own are especially prone to missing information, and only remembered when the surveillance was offline in the middle of the night. I wrote how to bind static IPs, and when switching segments, I followed the reverse operation again.

the second item, the old model is voided according to the rules set by IP segments. AC10 that generation, speed limits were based on IP ranges. Previously, I set speed limits for TV boxes, and the rules were 192.168.0.105 to 110. is the old interface in the speed limit section. After switching to 3.1, these rules can't match any device, which means silence is invalid, no errors or reminders, and you have to manually refill the rules. The new model has device speed limits, so you don't have this problem.

third item: do you still recognize it on your mobile app? Tenda WiFi is bound to a router, so changing the IP doesn't affect the binding relationship. However, I've tested that after changing the segment, the app has to reconnect for a while before the device list refreshes. This is normal, so don't rush to uninstall and reinstall. Troubleshooting App binding issues a different matter, so don't confuse them.

I didn't change it, but the IP changed on its own, what's going on

this pitfall deserves a separate section, because among those searching for LAN port IPs, some are forced to do so because of this phenomenon: I haven't changed the settings, so why can't I tendawifi.com in, or maybe I switched to a different device in 0.1?

two sources. The first scenario is that the router is switched to WISP or universal repeater mode. In this mode, Tenda will automatically change the LAN port IP to 192.168.1.1 to prevent conflicts with upper-level devices. This is a proactive firmware action, not a fault. If you press 0.1, of course you won't get in, but try pressing 192.168.1.1—90% of the time you'll get in. Later, my cousin was reckless and tried to fix the bridge, and this phenomenon confused him. He asked me over the phone if the router was broken. the second , someone at home has tampered with the router, or it has been reset and restored to the default 0.1. When you can't tell the difference, connect your phone to its WiFi and tap wherever the gateway address is pointed. Whoever the gateway is, you enter their backend. If you really can't find it, reset and redo it in just ten minutes. the reset button shares the same hole as WPS, so pay attention to the duration when pressing it.

the final order: follow it to avoid pitfalls: first think about whether this Tengda will be the AP or the main router. When AP, it should be the same network segment with a single digit and turn off DHCP; when the main router is switched to the entire segment and checked the DHCP pool; Before modifying, take screenshots of the bound static devices and the old speed limit rules for backup; After changing the address, you can access the backend using a new address or tendawifi.com verification; If you find the IP has changed on its own, first check if it switched to the bridge mode, then check if someone has reset it. After my cousin's unit was upgraded to 0.2, both routers operated independently, and the robot vacuum never disconnected again. The 300Mbps broadband speed test returned to a normal level of over 290Mbps.