SG2218 DHCP not working after firmware v1.20.4 applied
My equipment:
Gateway/Controller/Router: ER7212PC v1.0
Switch: SG2218 v1.20
Since I applied firmware v1.20.4 to the switch, new devices connected to switch ports can no longer obtain an IP address (new client devices are listed with MAC addresses, but IP addresses are shown as dashes). All existing switch-connected client devices appear to continue to function normally; this only seems to affect client devices added since the firmware update.
If I connect the new devices to an available router port, IP addresses are assigned. Before firmware v1.20.4, new devices connected to the switch were getting IP addresses just fine.
New wireless devices are getting IP addresses correctly.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @e-sarge
Thanks for posting in our business forum.
The client page does not reflect the actual status of the device. It is delayed because the sync is periodic.
Have you verified on the devices where their MAC addresses are displayed there?
This is basically a statement without concrete verification. Simply based on what device page displayed.
- Copy Link
- Report Inappropriate Content
I am seeing a weird variation of this
In my stack, i have a SG3452 and a SG2218P, both running the 27th december firmware
I also have a dumb 16 port POE switch for cameras etc, stuff that doesnt need management through omada. My OC 200 is actually connected to this switch
If i connect a device using DHCP to either my 3452 or 2218P, they get an IP address on the default vlan and all is normal.
If i connect the same device to my dumb switch (which is uplinked to my 3452 with an "All" port profile), devices do NOT get served an IP address on the default vlan.
Any device which is not using DHCP and is using a static works on any port on any switch.
Its really strange that DHCP doesnt seem to pass through the uplink port on my dumb poe switch. If i disconnect the cable and plug a DHCP device into the exact same port that i was using as its uplink on the 3452, it gets DHCP.
If i connect the dumb switch to spare router port - DHCP working again through the dumb switch.
Its really strange.
- Copy Link
- Report Inappropriate Content
Yes over multiple days and Omada login sessions, the Omada Clients page does not "update". This is not a web interface "timing" issue.
Also on the devices, their network setup showed no IP address assigned.
As soon as I connected the devices to the router instead of this switch, the Omada web interface showed their IP address at the next 2-minute refresh (no dashes) and the devices' network setup pages showed the correct IP address as expected (on the correct VLAN, and in one case using the correct reserved IP address).
I had set up similar devices before the v1.20.4 update, and the devices were assigned IP addresses via the switch (correct VLAN, correct reserved IP address).
- Copy Link
- Report Inappropriate Content
Hi @e-sarge
Thanks for posting in our business forum.
e-sarge wrote
Yes over multiple days and Omada login sessions, the Omada Clients page does not "update". This is not a web interface "timing" issue.
Also on the devices, their network setup showed no IP address assigned.
As soon as I connected the devices to the router instead of this switch, the Omada web interface showed their IP address at the next 2-minute refresh (no dashes) and the devices' network setup pages showed the correct IP address as expected (on the correct VLAN, and in one case using the correct reserved IP address).
I had set up similar devices before the v1.20.4 update, and the devices were assigned IP addresses via the switch (correct VLAN, correct reserved IP address).
I think my question is not answered. I am aware of the situation you've described, but the question remains.
Have you verified on the devices where their MAC addresses are displayed there?
- Copy Link
- Report Inappropriate Content
You highlighted this question "Have you verified on the devices where their MAC addresses are displayed there?"
In my original post, I said the clients showed up in the client list. I didn't specifically say the MAC addresses were displayed on the relevant lines in the Omada client list, but without the MAC address how would I know that I was dealing with the new devices? I thought that was assumed. I did say that on those Omada client lines the IP addresses were missing (represented with dashed lines).
As far as your "verified on the devices" phrase, what specifically did you want me to verify? I did describe how the devices didn't have an assigned IP address, and by inference, when I said the client devices were connected to the router, they got IP addresses and functioned as expected, so the client devices are not the cause.
One of the devices was a firestick with an ethernet adapter (I had another of the same configuration already connected to the same switch for many weeks without issue). The other was a TV Tuner (which functions as a headless server). I have other server devices already connected on that same switch as well, also working before the firmware upgrade.
I don't know how much more clear this can be. I had two new client devices (quite different from each other, but very similar to other older client devices on the same switch) that did not receive IP addresses after the firmware update, but the similar client devices on the same switch had no DHCP issues at all prior to the firmware update. And furthermore, the two new client devices worked fine when connected directly to the router ports, so the client devices themselves are not faulty.
- Copy Link
- Report Inappropriate Content
Hi @e-sarge
Thanks for posting in our business forum.
e-sarge wrote
You highlighted this question "Have you verified on the devices where their MAC addresses are displayed there?"
In my original post, I said the clients showed up in the client list. I didn't specifically say the MAC addresses were displayed on the relevant lines in the Omada client list, but without the MAC address how would I know that I was dealing with the new devices? I thought that was assumed. I did say that on those Omada client lines the IP addresses were missing (represented with dashed lines).
As far as your "verified on the devices" phrase, what specifically did you want me to verify? I did describe how the devices didn't have an assigned IP address, and by inference, when I said the client devices were connected to the router, they got IP addresses and functioned as expected, so the client devices are not the cause.
One of the devices was a firestick with an ethernet adapter (I had another of the same configuration already connected to the same switch for many weeks without issue). The other was a TV Tuner (which functions as a headless server). I have other server devices already connected on that same switch as well, also working before the firmware upgrade.
I don't know how much more clear this can be. I had two new client devices (quite different from each other, but very similar to other older client devices on the same switch) that did not receive IP addresses after the firmware update, but the similar client devices on the same switch had no DHCP issues at all prior to the firmware update. And furthermore, the two new client devices worked fine when connected directly to the router ports, so the client devices themselves are not faulty.
Then I think this is hard to reproduce. There isn't much I can share with the test and dev team.
Will you be able to provide your environment with us through a remote desktop to debug and analyze this?
That seems to be the only way to verify what you have described.
All I want to learn is that the device is actually not getting the IP address you described after the firmware upgrade. Verify means you actually log in to this specific device, check its cable and everything shows as "connected" but it does not get an IP address from the DHCP server on your router while it bypasses the switch.
So we gotta confirm it and decide what direction we should go if there is a code error in the firmware or if something else goes haywire.
If you don't understand what I mean, I mean everything in this: Howto - A Guide to Use Forum Effectively. Read Before You Post.
- Copy Link
- Report Inappropriate Content
Of course I confirmed on the devices. You think I would just look at the Omada admin page and then write a report???
And before you ask, I rebooted the device and re-tested before trying anything else. That didn't help either.
I can send any logs you need (just let me know what you need and how to get it).
Here is the relevant portion of the logs from my TV Tuner:
19700101-00:00:01 System: reset reason = power on 19700101-00:00:02 System: network link 100f 19700101-00:00:22 System: ip address obtained: [fe80::218:ddff:fe0a:af7c]/64 19700101-00:00:22 System: ip address obtained: 169.254.89.245/16 19700101-00:00:37 System: myhdhomerun_sync: webclient error (dns failed) 19700101-00:10:55 System: myhdhomerun_sync: webclient error (dns failed) 19700101-00:20:14 System: network link down 19700101-00:20:14 System: ip address released: 169.254.89.245 19700101-00:20:29 System: ip address released: [fe80::218:ddff:fe0a:af7c] 19700101-00:20:29 System: myhdhomerun_sync: webclient error (dns failed) 19700101-00:20:50 System: network link 100f 19700101-00:20:51 System: ip address obtained: 192.168.20.7/24 19700101-00:20:51 System: ip address obtained: [fe80::218:ddff:fe0a:af7c]/64
You can see the timestamp 19700101-00:00:22 is where the DHCP failed (it self-assigned an un-addressable IP address)
Timestamp 19700101-00:20:51 is where I connected it to the router and it got an IP address from DHCP.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 120
Replies: 7
Voters 0
No one has voted for it yet.