How to maintain assigned static IPs with Range Extender

[demery]

I'm using a TL-WR1043N/ND router with Gargoyle 1.7.2. The WR1043 is set up as a "Gateway" rather than a repeater. I have a dozen or so static IPs assigned to devices using their MAC addresses to permit high data limits. All other unlisted devices get a random IP address with limited data usage each day. Using only the WR1043, all assigned IPs and data limits work fine.

I have now installed a TP Link RE590T range extender using the same SSID and password as the WR1043 router. It seems that devices that connect to the network through the RE590T extender receive different IP addresses than the IP addresses assigned by the WR1043 - thereby defeating the functionality of the assigned static IPs and limits assigned on the Gargoyle router. Static IPs assigned with Gargoyle on the WR1043 are not recognized when connected through the extender and receive random IP addresses (thereby ignoring the higher data limits permitted for these devices).

I expect there is a way to carry the Gargoyle assigned IPs "through" the extender - thereby preserving the data limit settings assigned in Gargoyle. Is this possible? Would the proper method to be to set up a second WR1043 running Gargoyle as a "repeater" rather than to use a Range Extender?

Any suggestions would be most helpful.

Thank you
-Dave

[Lantis]

Page 22 and 23 of http://www.tp-link.com/res/down/doc/_1_ ... 0.0_UG.pdf

My first guess is that the extender is operating a DHCP server. Disabling it should fix.

[demery]

Thanks for your suggestion. I did find the DHCP Server option on the extender, turned it from Auto to Off, and rebooted both the router and extender. Unfortunately devices for which I've assigned a static IP on the Gargoyle router still come up with an assigned, random IP address on the Gargoyle router when connected through the range extender.

Any other ideas?

Thank you

[Lantis]

Please report back in 12-24 hours. The DHCP leases may need to expire first

[demery]

Good suggestion. The leases expire in 12 hours according to Gargoyle/Status/Connected Hosts. I've temporarily reset the lease expiration to 1 hour (from 12 hours) so I won't have to wait so long with other changes, but this apparently doesn't affect current leases.

I did call TP-Link's tech support and they assured me the RE590T range extender DOES NOT assign IP numbers - it ONLY passes data back and forth. So it seems the issue may be in my settings with Gargoyle.

I'll repost after the leases expire in 12 hours to let you know the outcome.

Thank you

[demery]

Unfortunately turning off the DHCP on the range extender, and waiting a day for the leases to terminate (set at 12 hours) did not solve the issue. Any other suggestions? I expect I don't have something set properly on Gargoyle, but am not certain what it might be.

To recap the problem: Devices with assigned IPs on Gargoyle appear with the proper IP when connected via wifi on the Gargoyle wifi. But when the same devices connect through the range extender, they come up with different IPs (last set of numbers change) on the list of connected devices on Gargoyle - thereby defeating the assigned IPs.

[Lantis]

What kind of devices do you have connected to it?
If you have any PCs, I'm wondering if we can try to be a bit more extreme about refreshing the DHCP leases. (I still think this is the issue)

On a PC at the command prompt window if you:
ipconfig /release
ipconfig /renew

Hopefully the PC will now get its intended address.
If that works then we can work on other devices.

if it doesn't fix it then I'm unsure where to go next.