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
Support for fixed IPs outside of the normal DHCP pool was added in v5.0 of the controller software.
https://community.tp-link.com/en/business/forum/topic/256396
I still may put this client back in the normal pool if it's causing issues, but it's supposed to work this way (and did until I rebooted the ER605; then the client got a random address).
- Copy Link
- Report Inappropriate Content
Dear @supermarkert,
If I didn't get it wrong, only one device (the camera) in your network would get a random IP address from DHCP instead of use the reserved IP address, and your ER605 v1 is running with 1.2.2_Build 20230118 (Beta), right? May I know the brand and model number of your camera?
- Copy Link
- Report Inappropriate Content
yes, I believe you had it right. The camera is the only one I reference because it's the only one I noticed with the wrong address (if others had the issue, they resolved themselves).
It's a Reolink Wifi Doorbell camera. I just set it up early last week on Monday, which is why I was paying attention to it. My normal DHCP pool is 192.168.10.30 - .255, but for this client I selected a Fixed Address at 192.168.10.13.
After several Reconnects and refreshes during initial setup, eventually the client took this address and it was working fine for ~week (well past any reservation times). Then my ER605 rebooted on a schedule in the middle of the night, and the camera became stuck on a 192.168.10.105 address. This is when I noticed the issue the next day.
Several Reconnects didn't resolve the issue, so I eventually rebooted the camera and it finally got the 192.168.10.13 address again.
- Copy Link
- Report Inappropriate Content
@Fae
FYI, it just happened again. I rebooted the camera (troubleshooting reasons) and the client came back with a 192.168.10.55 address. This is a new address, and only could have come from the ER605.
So I'm giving up trying to give it a fixed IP outside of the DHCP pool, and will now just try from within the pool and see if I have any issues over the next few days.
- Copy Link
- Report Inappropriate Content
Dear @supermarkert,
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineers to provide further assistance. The ticket ID is TKID230216622, please check your email box and ensure the support email is well received. Thanks!
- Copy Link
- Report Inappropriate Content
Dear @supermarkert,
I'd like to add the updated solution here. The new beta firmware ER605(UN)_v1_1.2.2_Build 20230208 (Beta) has been provided, you may follow this updated solution post for upgrading. Cheers!
- Copy Link
- Report Inappropriate Content
Hi there, I'm experiencing same problems as people above.
Everything's up to date:
Yet most of the devices set to fixed ip are using differents addresses:
^Should be "4", is "13" as seen above - even after rebooting both access point and switch.
Is there a new beta update for my config?
- Copy Link
- Report Inappropriate Content
@pnprv I'm experiencing this exact same issue right now. Commenting to stay in the loop
- Copy Link
- Report Inappropriate Content
@TandS same problem here, i have several (10) ezviz cameras, all of them has fixed IP from the camera itself. but OMADA give some random IP so the camera wont work, sometimes doesnt give IP at all. its only this 2, tried everything ( resetting camera, rebooting everything, only a few reconnects solve the problem for a while, but not forever. i have ER605, all in the latest verison.
- Copy Link
- Report Inappropriate Content
Same here, fixed IP is not working. Please fix already.
While you're at it, might as well fix 'Lock to AP' as it also doesn't work.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 14393
Replies: 42
Voters 0
No one has voted for it yet.