[lug] TP-Link Router Q.

Stephen Queen svqueen at gmail.com
Mon May 6 18:22:33 MDT 2019


Years ago I was running into similar problems on a number of routers
(openwrt). I can't remember the exact details, but it had to do with the
file buried in /var that kept track of assigned ip address. When the lease
on the address expired, then the address could be re-assigned.  I could
also go into the file with an editor, and delete the entry, and if memory
surves me correctly, I had to restart the dhcp server.

On Mon, May 6, 2019, 2:57 PM D. Stimits <stimits at comcast.net> wrote:

> Just to add to the mystery, after a few reboots of the router the reserved
> address showed up again from where I originally deleted it. I deleted the
> address binding to the old MAC yet again...and this time it stuck and I was
> able to assign the new MAC to the old address. I'm not sure, but I had
> saved configuration as a starting point before wiping the router...and it
> may be this config save caused the "ghost" old MAC binding to show up again.
>
> On May 6, 2019 at 2:13 PM "D. Stimits" <stimits at comcast.net> wrote:
>
> Hi,
>
>
> My internet searches have been fruitless on this topic (the router docs
> only say how it should work, but don't take into account that it is
> broken), but I know a lot of people here have worked with the TP-Link
> routers, so maybe someone here has run into this issue.
>
>
> I just had to replace a network card going to a *TP-Link TL-WR940N*. The
> old NIC was bound by MAC address and the IP was reserved to that MAC
> address. So I wanted to bind the new MAC address to that old reserved IP
> address.
>
>
> I deleted the original entry, including both MAC binding and reserved IP.
> I rebooted. Now I'm trying to add the new MAC to the old IP (which I see is
> no longer reserved or bound). The only trouble is that it refuses the old
> IP because it says the IP is in conflict with an already reserved IP. I
> have found no method to change this and I did in fact delete the old IP
> reservation. The IP it claims is still in existence is not (so far as I can
> tell).
>
>
> It claims (the European spelling "conflictes" is actually spelled that way
> in the error message):
>
> Error code: 20010
>
> The entry conflictes with the existing reserved addresses.
>
>
> I have about 10 MACs and a number of rules already set up and I really
> don't want to wipe the entire router and start over from scratch. Does
> anyone here know if there is a way to force the reserved address to be
> given up so I can bind it again without resetting the entire router? Is
> wiping the entire setup the only way to assign a new MAC to an old reserved
> IP?
>
>
> Thanks!
>
>
>
>
> _______________________________________________
> Web Page: http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: irc.hackingsociety.org port=6667 channel=#hackingsociety
>
>
>
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: irc.hackingsociety.org port=6667 channel=#hackingsociety
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20190506/fe71b5aa/attachment.html>


More information about the LUG mailing list