Fixed IP Address NOT working
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I'm starting to get annoyed with the inability of this TP-Link equipment to maintain a designated FIXED IP address on a device.
I need to assign static IP addresses to my IOT devices (sadly, the devices in question I'm having problems with are TP-LINK devices as well !!) to ensure smooth operation with my home automation solution.
I have gone ahead and used a Fixed IP Address:
NOTE .. The IP address does not match the fixed ip address.
Forcing the client to reconnect will temporarily solve the issue but the device will eventually fall back to a DHCP assigned address.
As a workaround and to try to resolve the issue I assigned all my IOT devices an address between 192.168.50.10 and 192.168.50.49.
I then continually force reconnected all the devices until they had their properly assigned fixed IP address.
Lastly,I went into my DHCP settings and set the starting range to be 192.168.50.50:
NOTE: The Omada SDN will NOT allow you to manually input an IP address that falls outside of the defined DHCP range. To get around this, you have to change them BEFORE modifying your range.
Not sure what else I can do but surely I'm not the only one experiencing this issue.
Is this known to TP-Link ? Is it slotted to be resolved anytime soon ?? Is there a work around that actually works ???
As an FYI : Here is a screenshot of my devices and their versions (running the latest version on everything):
I am running the latest version of the Omada Software controller :
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
A few weeks ago, I noticed the issue being back again as well.
I honestly got tired of repeating the same thing over and over again and am glad others are speaking up and voicing their concerns.
There are many different ways you can try to get the correct ip address assigned but their doesn't seem to be one workaround method that works consistently.
- Copy Link
- Report Inappropriate Content
Dear @Omikomi, @Koboldo, @MaziarR, @TandS, and other community members,
Sorry for any trouble caused. After further troubleshooting and investigation with @PapyPom (Thank @PapyPom so much for your great cooperation!), the R&D team has finally addressed the issue.
As a temporary solution, the following solution post has provided the Beta firmware to fix the issue, other beta firmware will be provided gradually, and the subsequent official firmware will add the fix soon.
Solution ER605 ER7206 - “Use Fixed IP Address” (DHCP Reservation) Doesn't Take Effect
Thank you all for your huge support and patience!
- Copy Link
- Report Inappropriate Content
Manager to found a fix for the problem. Basically the lease time for the devices needs to be changed temporarily (i guess its a bug or something). So, go to Settings/Wired Networks/LAN then click on the network you want to modify and in the Lease time set a different value that you are currently having, hit Save then try again to set a Fixed IP to the device. After the IP is set you can revert the Lease time interval (if you want to)
- Copy Link
- Report Inappropriate Content
@TandS I just haven't had to change my IP address before. But recently, I came across routeriplogin.com and decided to do it. But they advised me not just to change private IP addresses but to use dynamic Now I have my doubts. How will dynamic IP addresses respond if DHCP can't handle fixed IP addresses?IP addresses. I started this because I swapped my TL-R600VPN router, which was really slowing down, for a TP-LINK ER605 router. Now, after reading the discussions on your forum, I doubt whether to change the address or let it be.
- Copy Link
- Report Inappropriate Content
@LaurenWelchat In my case, the dynamic IP addresses just uses the fixed IP addresses as well, meaning that now the IP is will be given to another device that doesn't have fix IP configuration.
- Copy Link
- Report Inappropriate Content
@Fae I also have the same issue.
I am using a TL-R605 v1 Gateway on firmware 1.2.1, Omada SDN controller v5.7.4
thanks,
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Fae
I've been using the latest beta for ER605 v1 all week and it STILL doesn't work. After initially setting a fixed IP address for a device (camera) it took several disconnects, but after 10 minutes it appeared to be working and kept the reserved IP address all week. Then I rebooted my ER605 and it lost the fixed IP address. All settings are still the same in the Router/Controller, but it is not following the setting. The client is still getting a random IP address in the pool.
- Copy Link
- Report Inappropriate Content
Ive been in the network game for over 15 years... setting a fixed address outside of the DHCP is not a common practice. Fix Addreses OR a DHCP reserve should be for IPs within the DHCP Pool.
I have 7206 on 1.2.3 firmware and the fixed addresses within the pool is working for me.
Why not manually set the address on devices that is outside the pool?
- Copy Link
- Report Inappropriate Content
If it didn't work at all, then I would tend to agree with you. And I may switch it if it works more reliably.
However (I don't have a link handy), I believe they announced support for this.
Either way, by selecting an address outside the normal pool, it did work (eventually). I'm not able to set an address manually with this device so I have to rely on DHCP. It properly set the address after a couple tries and stayed there all week. But after a router reboot, it lost the address. I finally rebooted my client and it got the right address again.
So I still think this is an ER605 problem. But I may take your suggestion and choose an address within the pool to see if it sticks better.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 14391
Replies: 42
Voters 0
No one has voted for it yet.