Different IP main vs. repeater

[lindros2]

I swear that up until recently, my devices had the SAME address when connecting to the main router (let's call it, 192.168.10.1) and a repeater (192.168.10.150 or whatever).

I have three ASUS routers, and the IP issue appears on both of the extenders:

- Main: AC68U
- Repeater 1: AC5300
- Repeater 2: AC68U

A smartphone received x.x.x.40 on repeater 1, but x.x.x.200 on repeater 2.

 

[OzarkEdge]

I swear that up until recently, my devices had the SAME address when connecting to the main router (let's call it, 192.168.10.1) and a repeater (192.168.10.150 or whatever).

I have three ASUS routers, and the IP issue appears on both of the extenders:

- Main: AC68U
- Repeater 1: AC5300
- Repeater 2: AC68U

A smartphone received x.x.x.40 on repeater 1, but x.x.x.200 on repeater 2.

I don't understand the problem. You are concerned that devices get different IP addresses from the router DHCP server?

OE

 

[Ronald Schwerer]

I swear that up until recently, my devices had the SAME address when connecting to the main router (let's call it, 192.168.10.1) and a repeater (192.168.10.150 or whatever).

I have three ASUS routers, and the IP issue appears on both of the extenders:

- Main: AC68U
- Repeater 1: AC5300
- Repeater 2: AC68U

A smartphone received x.x.x.40 on repeater 1, but x.x.x.200 on repeater 2.

On my TP-Link repeaters, the first 3 bytes of the MAC changes for all the devices that connect to them. IDK if ASUS repeaters do this. That could explain different IPs, especially if they are manually configured in DHCP.
I had fixed IPs on my IoT stuff before adding repeaters (guest SSID). So I was at first annoyed at having to allocate two IPs (one for original device MAC and another for the repeater version. But it turns out I like it better since it is easy to tell where the client connected by examining the client list. I can also exclude the original client MAC on the router to force connection to the repeaters.