Unable to change LAN IP Type for wireless device

Solved
WellyHartanto
Getting noticed

Unable to change LAN IP Type for wireless device

Hello,

I just noticed that I was unable to change the LAN IP Type for wireless device.
The dropdown just did not show anything other than the current value (either it's DHCP or Static).
I had to revert to old version to be able to change this value.

I checked with my colleagues, and they were experiencing the same issue.

 

Is this a known bug? Or is it well...just me?

1 Accepted Solution
cmr
Kind of a big deal
Kind of a big deal

It can be changed, the box appears behind the current item in the GUI so you cannot see it.  Click on the pencil next to the Ip to open the box that shows DHCP in the first row and the VLAN in the second row (if the current IP is DHCP).  This will change the twistie from pointing down to pointing up.  Then press the down arrow on the keyboard twice, followed by the return key.  You will now see that the top box says static and the fields you need all appear.

cmr_0-1768341611233.png

cmr_1-1768341648946.png

cmr_2-1768341703978.png

 

 

If my answer solves your problem please click Accept as Solution so others can benefit from it.

View solution in original post

10 Replies 10
JamesT91
Head in the Cloud
Head in the Cloud

Known issue yet to be fixed, this is feedback from our ticket raised last month:

 

As discussed, this is a known issue that is already being tracked. In the AP Summary sidebar, the LAN IP Type cannot currently be changed between Static and DHCP. I have attached your case as a child to the main open investigation, which is actively being reviewed by our UI Engineering team.

RouterEdge
Conversationalist

Thanks for sharing @JamesT91, I'm having same issue on our end since December.

cmr
Kind of a big deal
Kind of a big deal

It can be changed, the box appears behind the current item in the GUI so you cannot see it.  Click on the pencil next to the Ip to open the box that shows DHCP in the first row and the VLAN in the second row (if the current IP is DHCP).  This will change the twistie from pointing down to pointing up.  Then press the down arrow on the keyboard twice, followed by the return key.  You will now see that the top box says static and the fields you need all appear.

cmr_0-1768341611233.png

cmr_1-1768341648946.png

cmr_2-1768341703978.png

 

 

If my answer solves your problem please click Accept as Solution so others can benefit from it.
WellyHartanto
Getting noticed

Hello @cmr 
Thanks for the tips.
I just checked today, it seems to work just fine now without having to do extra steps.

RouterEdge
Conversationalist

@cmr thanks for the help, your solution has worked for me.

cmr
Kind of a big deal
Kind of a big deal

@RWelch this is the discussion I was about to link your question to...

If my answer solves your problem please click Accept as Solution so others can benefit from it.
RWelch
Kind of a big deal
Kind of a big deal

Thanks @cmr - not exactly the same issue per se.  I am aware of how to change from one to the other but the issue is that "when doing so" there is partial information from the previous setting that remains such as IP address in the VLAN field when going back to DHCP.  It appears to definitely be a GUI BUG IMO.

Why does the IP address info linger?  In order to SAVE this - one has to manually DELETE this info (data) before being able to SAVE it.  Causes additional steps which is problematic when doing this to a network with say 15 or more meraki devices (APs).  

Just give me back the OLD view and I'll zip it and be happy 😃


Screenshot 2026-02-04 at 13.58.28.png

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
cmr
Kind of a big deal
Kind of a big deal

Ah yes, that is part 2 of the new UI feature set...  It's infuriating isn't it!

If my answer solves your problem please click Accept as Solution so others can benefit from it.
RWelch
Kind of a big deal
Kind of a big deal

Indeed - perhaps a year or so from now we will see it fixed (fingers crossed).

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
RWelch
Kind of a big deal
Kind of a big deal

Again - it's not a change that is ready for production (introduction) yet here we are taking 3 steps backwards (takes longer to do a simple task and is more complex than previously was).  SMH.

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
Get notified when there are additional replies to this discussion.