Fixed IP Address not working (ER7206 FW 1.2.1)
I have a VLAN for my IOT devices. This morning i had a blackout and several things went wrong when trying to restore everything:
- Like above, this device didn't use its Fixed IP settings (I am on 1.2.1)
- Initially when it started, and I have had this issue before, the DHCP for the IOT VLAN was not working at all. All the IP addresses were assigned the 169.*.*.* type addresses and it wasn't until I went into the Network Settings in Omada and changed the DHCP range from 172.16.1.1 - 172.16.1.254 to 172.16.1.2 - 172.16.1.254, that it all started to work again. Note, that it doesn't matter what I change the DHCP to, it just matters that it changes, I'm assuming this triggers it to reconfigure the gateway.
I am using Omada Controller 5.3.1
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Dear @rg.kszi, @RBL, @PavelV, and other community members,
rg.kszi wrote
I have the same issue. DHCP reservation not working. I (think) had no issue with this until I updated my route firmware to 1.2.1 about a week ago. (or my clients not reported it to me earlier).
Sorry for any trouble caused. After further troubleshooting and investigation, the R&D team has finally addressed the issue.
The following solution post has provided the Beta firmware to fix the issue (other beta firmware will be provided gradually).
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
- Copy Link
- Report Inappropriate Content
Also this happens when I try to set a fixed IP address. The IOT Network is in the 172.16.1.* range, not 192.168.1.*
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Dear @Utmstgsn,
Utmstgsn wrote
I have a VLAN for my IOT devices. This morning i had a blackout and several things went wrong when trying to restore everything:
- Like above, this device didn't use its Fixed IP settings (I am on 1.2.1)
- Initially when it started, and I have had this issue before, the DHCP for the IOT VLAN was not working at all. All the IP addresses were assigned the 169.*.*.* type addresses and it wasn't until I went into the Network Settings in Omada and changed the DHCP range from 172.16.1.1 - 172.16.1.254 to 172.16.1.2 - 172.16.1.254, that it all started to work again. Note, that it doesn't matter what I change the DHCP to, it just matters that it changes, I'm assuming this triggers it to reconfigure the gateway.
I am using Omada Controller 5.3.1
Do you mean that all of your IOT devices now can get the Fixed IP addresses after you change the DHCP range?
The router 1.2.1 firmware should have fixed the Fixed IP address not working issue, please confirm it.
- Copy Link
- Report Inappropriate Content
@Fae I mean, that none of devices will get an IP via DHCP, regardless of whether I have configured an Fixed IP or not, until I change the range.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I have the same issue. DHCP reservation not working. I (think) had no issue with this until I updated my route firmware to 1.2.1 about a week ago. (or my clients not reported it to me earlier).
Omada Controller Version: 5.1.7
Router ER605 1.0, firmware: 1.2.1
Sorry to say this, but it is very annoying bug again. I like omada, but nowadays every new firmware update contains a new bug, like this... I use DCHP reservation on my clients notebooks in order to use our network printer/scanner. All of the sudden they can't scan documents because of this...
- Copy Link
- Report Inappropriate Content
rg.kszi wrote
I have the same issue. DHCP reservation not working. I (think) had no issue with this until I updated my route firmware to 1.2.1 about a week ago. (or my clients not reported it to me earlier).
Omada Controller Version: 5.1.7
Router ER605 1.0, firmware: 1.2.1
Sorry to say this, but it is very annoying bug again. I like omada, but nowadays every new firmware update contains a new bug, like this... I use DCHP reservation on my clients notebooks in order to use our network printer/scanner. All of the sudden they can't scan documents because of this...
As mentioned in another thread I have the same issue, when upgraded the TL-R605 v1.0 to 1.2.1, devices with fixed ip-addresses got different ip's. Reverting back to 1.2.0 solved the issue.
My current setup:
1x OC200 (5.1.7 Build:1.15.2 Build 20220323 Rel.60717)
1x TL-R605 v1.0 (1.2.0)
1x TL-SG2218 v1.0 (1.1.3)
3x TL-SG2210P v3.20 (3.20.2)
2x EAP245(EU) v3.0 (5.0.6)
2x EAP225-Outdoor(EU) v1.0 (5.0.9)
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 3159
Replies: 26
Voters 0
No one has voted for it yet.