Deco with two IP addresses with different third quartets
I added the Deco devices using the standard TP-Link Deco app, following the sequence suggested by the app itself.
My two Decos have two IP addresses whose third octet is different:
192.168.71.250 (the master, installed first, connected via Ethernet to the router)
192.168.68.101 (the second, the slave, connected via backhaul to the first WiFi network).
I can't figure out why the third octet is different despite proper installation.
That is, I'm wondering why the slave acquired an IP address with a different third octet than the first, "192.168.68.25x" instead of "192.168.71.2xx".
What kind of IP should I expect in the third pairing of the third, new device I will install?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Thanks for reaching out to TP-Link support! I understand you're puzzled about why your two Deco units have IP addresses with different third octets (192.168.71.250 and 192.168.68.101), and you'd like to know what IP range to expect for a third unit.
The good news is that everything is working correctly — both devices are actually on the same network.
The key is the subnet mask. The default LAN configuration on Deco uses 192.168.68.1 with a /22 subnet mask. A /22 subnet doesn't just cover the 192.168.68.x range — it spans a block of four consecutive class-C ranges:
• 192.168.68.0 – 192.168.68.255
• 192.168.69.0 – 192.168.69.255
• 192.168.70.0 – 192.168.70.255
• 192.168.71.0 – 192.168.71.255
So both 192.168.68.101 and 192.168.71.250 fall within this single /22 network. They are not on separate networks — the third octet difference is perfectly normal and expected behavior with a /22 subnet.
The Deco's DHCP server assigns addresses from anywhere within this entire pool, so devices (including Deco units themselves) can receive IPs with third octets of 68, 69, 70, or 71 — all valid and all on the same LAN.
When you add your third Deco unit, it will also receive an IP address somewhere within this 192.168.68.x–192.168.71.x range. The exact address will simply be the next available one assigned by the DHCP server, and regardless of the third octet, it will be part of the same mesh network.
Thanks
- Copy Link
- Report Inappropriate Content
Would making them sequential help?
- No performance, stability, or mesh benefit.
- The mesh already works correctly across the full /22 range.
- Resetting a unit just to force it onto a 192.168.68.x address is unnecessary and risks temporary downtime for no gain.
The only possible minor “cosmetic” reasons someone might want sequential addresses are personal preference or easier mental tracking when looking at a device list. Those are not technical benefits.Bottom line: Leave the IPs as they are. Everything is functioning as designed.
Thanks
- Copy Link
- Report Inappropriate Content
Thanks for reaching out to TP-Link support! I understand you're puzzled about why your two Deco units have IP addresses with different third octets (192.168.71.250 and 192.168.68.101), and you'd like to know what IP range to expect for a third unit.
The good news is that everything is working correctly — both devices are actually on the same network.
The key is the subnet mask. The default LAN configuration on Deco uses 192.168.68.1 with a /22 subnet mask. A /22 subnet doesn't just cover the 192.168.68.x range — it spans a block of four consecutive class-C ranges:
• 192.168.68.0 – 192.168.68.255
• 192.168.69.0 – 192.168.69.255
• 192.168.70.0 – 192.168.70.255
• 192.168.71.0 – 192.168.71.255
So both 192.168.68.101 and 192.168.71.250 fall within this single /22 network. They are not on separate networks — the third octet difference is perfectly normal and expected behavior with a /22 subnet.
The Deco's DHCP server assigns addresses from anywhere within this entire pool, so devices (including Deco units themselves) can receive IPs with third octets of 68, 69, 70, or 71 — all valid and all on the same LAN.
When you add your third Deco unit, it will also receive an IP address somewhere within this 192.168.68.x–192.168.71.x range. The exact address will simply be the next available one assigned by the DHCP server, and regardless of the third octet, it will be part of the same mesh network.
Thanks
- Copy Link
- Report Inappropriate Content
Thanks for your reply.
I had a slight confusion that didn't affect the question or answer:
The main Deco received the IP address 192.168.68.xx during the initialization process. The second Deco, initialized immediately after the first—connected to WiFi—received the IP address 192.168.71.xx.
You confirmed that this is perfectly normal and expected. Furthermore, the subnet mask (a feature I need to investigate further) /22 includes addresses "68" and "71," which therefore aren't in a second subnet; they always belong to the same network.
I was intrigued that the third Deco purchased and initialized the following week also received "68."
So I wondered if it might be a good idea to reset Deco "71" in an attempt to get it to receive "68."
Given your explanation and the fact that everything is working fine, it's not a good idea.
Right?
- Copy Link
- Report Inappropriate Content
Would making them sequential help?
- No performance, stability, or mesh benefit.
- The mesh already works correctly across the full /22 range.
- Resetting a unit just to force it onto a 192.168.68.x address is unnecessary and risks temporary downtime for no gain.
The only possible minor “cosmetic” reasons someone might want sequential addresses are personal preference or easier mental tracking when looking at a device list. Those are not technical benefits.Bottom line: Leave the IPs as they are. Everything is functioning as designed.
Thanks
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 192
Replies: 4
Voters 0
No one has voted for it yet.