# Firmware v4.9 Preview: What to Expect **URL:** \ **Category:** Router\ **Created:** [April 11, 2026, 3:35am UTC](https://forum.gl-inet.com/t/firmware-v4-9-preview-what-to-expect/68088 "2026-04-11T03:35:12Z")\ **Posts on this page:** 1\ **Showing post:** 655
**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:** [August 11, 2026, 8:00am UTC](https://forum.gl-inet.com/t/firmware-v4-9-preview-what-to-expect/68088/655 "2026-08-11T08:00:09Z")
> [@knee\_mountain523](#): > > @will.qiu, is there a reason why you didn't reply to my post? Wouldn't it be more consumer-friendly to have the no VPN tunnel available without resorting to using SSH? I skipped this question because **slubman** had already answered the questions related to **Not Use VPN**. Regarding why this option is no longer available in the UI, please refer to: > [@How to Configure a “Not Use VPN” Policy on Firmware v4.9](https://forum.gl-inet.com/t/how-to-configure-a-not-use-vpn-policy-on-firmware-v4-9/69074/1): > > Starting from firmware v4.9, the VPN subsystem has been redesigned. The previous **Not Use VPN** mode conflicts with the VPN design logic introduced in v4.9. As a result, this mode was removed from the GUI. We are also discussing with the product team whether this option can be added back in the future: > [@How to Configure a “Not Use VPN” Policy on Firmware v4.9](https://forum.gl-inet.com/t/how-to-configure-a-not-use-vpn-policy-on-firmware-v4-9/69074/7): > > Let's gather some feedback on this request and discuss it further with the product team. > [@knee\_mountain523](#): > > Would it be safe security-wise to flash back to the latest v4.8 series firmware, configure the VPN section, then upgrade to v4.9 to have the no-VPN tunnel rather than using SSH to create it? Then I'll fine-tune the settings in the other sections of the GUI. As a total newbie who isn't comfortable with SSH, is this the "easiest" way to add back the no VPN tunnel? In our previous guide, we also provided another method: **"Use a Non-Functional WireGuard Profile as a WAN Fallback"** , which allows users who are not familiar with SSH to achieve a similar result: > [@How to Configure a “Not Use VPN” Policy on Firmware v4.9](https://forum.gl-inet.com/t/how-to-configure-a-not-use-vpn-policy-on-firmware-v4-9/69074#p-280746-method-2-use-a-non-functional-wireguard-profile-as-a-wan-fallback-9): > > How to Configure a "Not Use VPN" Policy on Firmware v4.9 Introduction In firmware v4.8, the VPN Policy page allowed users to create rules with the routing method set to Not Use VPN. This was useful when you wanted most traffic to go through a VPN tunnel while allowing specific devices, domains, interfaces, or IP ranges to access the Internet directly through the WAN connection. Starting from firmware v4.9, the VPN subsystem has been redesigned. The previous Not Use VPN mode conflicts with the V… Of course, downgrading to **v4.8** and then upgrading to **v4.9 while keeping the configuration** is also an option. --- _[View the full topic](https://forum.gl-inet.com/t/firmware-v4-9-preview-what-to-expect/68088)._