# Flint 2 on V4.11.0 network disconnect/reconnect **URL:** \ **Category:** Router\ **Created:** [November 3, 2026, 9:13pm UTC](https://forum.gl-inet.com/t/flint-2-on-v4-11-0-network-disconnect-reconnect/72570 "2026-11-03T21:13:22Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![psyenz101](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/p/5fc32e/32.png) [@psyenz101](https://forum.gl-inet.com/u/psyenz101)\ **Post date:** [November 3, 2026, 9:13pm UTC](https://forum.gl-inet.com/t/flint-2-on-v4-11-0-network-disconnect-reconnect/72570/1 "2026-11-03T21:13:22Z")
Since updating to firmware v4.11.0 (stable version, not beta), everytime I make a change to reserved IP's (e.g., adding a new one), the entire network connection drops for a short bit, it does automatcally reconnect but if streaming music as an example, the stream stops until manually restarting it. This scenario never happened prior to the update. And I have also experienced connection issues with sonos speakers (all newer versions like the ERA's) even though they have had static ip's assigned since day 1 and run outside the vpn tunnel. No concrete "evidence" but as stated, this did not happen with earlier firmware versions with same config. Just wondering if anyone had any ideas what is happening? Possibly a bug? ---
**Author:** ![Chimpans](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/c/c5a1d2/32.png) [@Chimpans](https://forum.gl-inet.com/u/Chimpans)\ **Post date:** [November 5, 2026, 6:04am UTC](https://forum.gl-inet.com/t/flint-2-on-v4-11-0-network-disconnect-reconnect/72570/3 "2026-11-05T06:04:37Z")
Interesting. Are you on the old "Stable" or the new "OP25"? Both have the same version number. If it's OP25, maybe post it here where a lot of users are notified of new thread posts instead: > [@OP25 Firmware for Flint 2 & Beryl AX is out](https://forum.gl-inet.com/t/op25-firmware-for-flint-2-beryl-ax-is-out/69771/267): > > Thanks a lot for that. Sounds like you will backport the kernel patch to your routers? If so, I applaud you! That's the right way to protect all of your older releases too. And upstream OpenWrt 25 will officially update in the coming days/weeks with a fix too (they will include the 6.12.113 kernel which is fixed). ---
**Author:** ![psyenz101](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/p/5fc32e/32.png) [@psyenz101](https://forum.gl-inet.com/u/psyenz101)\ **Post date:** [November 5, 2026, 11:34am UTC](https://forum.gl-inet.com/t/flint-2-on-v4-11-0-network-disconnect-reconnect/72570/4 "2026-11-05T11:34:37Z")
I'm on the stable 4.11.0 version. I am considering flashing the 4.11 OpenWrt 25 version though because of the kernel age since, tbh, I wouldn't have a clue on backporting the kernel. I'm just a basic user, a novice here, nothing advanced in what I do so it's a learn as I go scenario. Something I did though that apparently prevented the complete network restart when assigning/reassigning static ip's was to make the ip reservations in the Flint GUI and rather than select "apply", I went to terminal and restarted dnsmasq from there. This seemed to have accomplished the assignment of the reserved IP's without a complete network restart, which seems to be what the "Apply" does in the GUI. And thank you for the reply. I did go to that post you cited and after reading comments there am feeling more comfortable with doing the update to OP25. ---
**Author:** ![will.qiu](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/w/b38774/32.png) [@will.qiu](https://forum.gl-inet.com/u/will.qiu)\ **Post date:** [November 6, 2026, 4:06am UTC](https://forum.gl-inet.com/t/flint-2-on-v4-11-0-network-disconnect-reconnect/72570/5 "2026-11-06T04:06:38Z")
Hi, Thanks for sharing your findings. Adding or editing an IP reservation in the GL.iNet web interface on v4.11 automatically applies the change and restarts `dnsmasq` in the background. You do not need to click **Apply** or restart `dnsmasq` manually. ![image](https://forum-static.gl-inet.com/original/3X/6/0/60f55aa21873f781d245c477ea2a2f36dd23a9a1.png) The **Apply** button reapplies the LAN network settings and restarts the corresponding LAN interface, briefly interrupting connections. It is needed when changing settings such as the router’s LAN IP address. We’ll discuss with our product and development teams whether the **Apply** button can be disabled when there are no pending LAN settings changes. ---
**Author:** ![psyenz101](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/p/5fc32e/32.png) [@psyenz101](https://forum.gl-inet.com/u/psyenz101)\ **Post date:** [November 6, 2026, 12:26pm UTC](https://forum.gl-inet.com/t/flint-2-on-v4-11-0-network-disconnect-reconnect/72570/7 "2026-11-06T12:26:33Z")
Hey Will, Thank you for the explanation, now it makes much more sense. I completely misunderstood the use of the Apply button. I assumed that since it was active it was necessary to use it for the reserved ip changes to take effect. Much appreciated. And, tbh, I wouldn't worry too much about having the team put much effort into disabling the button if no pending LAN changes. It may be more beneficial to have time/effort directed to larger concerns. So a nice to have....