# How to Configure a “Not Use VPN” Policy on Firmware v4.9

**URL:** <https://forum.gl-inet.com/t/how-to-configure-a-not-use-vpn-policy-on-firmware-v4-9/69074>\
**Category:** VPN, DNS, Leaks\
**Tags:** KB\
**Created:** [May 30, 2026, 10:14am UTC](https://forum.gl-inet.com/t/how-to-configure-a-not-use-vpn-policy-on-firmware-v4-9/69074 "2026-05-30T10:14:20Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**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:** [May 30, 2026, 10:14am UTC](https://forum.gl-inet.com/t/how-to-configure-a-not-use-vpn-policy-on-firmware-v4-9/69074/1 "2026-05-30T10:14:20Z")

</div>

# 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 VPN design logic introduced in v4.9. As a result, this mode was removed from the GUI.

This guide introduces several practical methods to achieve similar behavior on firmware v4.9.

* * *

> **Note:** If you already have existing **Not Use VPN** policies configured on firmware v4.8, they will be preserved after upgrading to firmware v4.9 (when keeping your configuration during the upgrade process). No additional reconfiguration is required.

* * *

## Method 1 (Recommended): Change the Route Policy to `novpn` via SSH

This is the recommended method for configuring a **Not Use VPN** policy on firmware v4.9.

### Step 1: Create Your VPN Dashboard Rules

First, create all required VPN Dashboard tunnels and policies in **Admin Panel → VPN → VPN Dashboard**.

For the tunnel that should behave as **Not Use VPN** , temporarily select any available VPN profile.

Example scenario:

- **Tunnel 1:** One device on the Main LAN network should bypass VPN.  

- **Tunnel 2:** All remaining devices on the Main LAN network should use VPN.  

- Guest and IoT networks should continue using the WAN connection normally.

### Step 2: Connect to the Router via SSH

Follow the guide below to log in to the router using SSH:

> **[SSH log in to the Router - GL.iNet Router Docs 4](https://docs.gl-inet.com/router/en/4/tutorials/ssh_log_in_to_the_router/)**
>
> Documentation for GL.iNet Router Productions

### Step 3: Modify the Tunnel Route Policy

Run the following commands to change the tunnel with **Priority 1** into a **Not Use VPN** policy:

```bash
uci set route_policy.@rule[0].via_type='novpn'
uci commit route_policy

/etc/init.d/vpn-client restart

```

If your target tunnel uses a different priority, adjust the rule index accordingly:

```plaintext
@rule[0] = Priority 1
@rule[1] = Priority 2
@rule[2] = Priority 3
@rule[3] = Priority 4
@rule[4] = Priority 5

```

### Step 4: Verify the Configuration

Return to the VPN Dashboard and confirm that the tunnel now displays **Not Use VPN** as its routing method.

 ![image](https://forum-static.gl-inet.com/original/3X/4/b/4b7022efc127615b59efe8f185a17e42e23af191.png)

### Step 5: Test the Result

Verify that:

- The device assigned to the **Not Use VPN** tunnel uses the WAN public IP address.  

- Other devices assigned to VPN tunnels continue using the VPN public IP address.  

* * *

## Method 2: Use a Non-Functional WireGuard Profile as a WAN Fallback

> **How this works:**  
> This method takes advantage of the fallback behavior that occurs when a WireGuard client cannot establish a connection while:
> 
> - **Kill Switch** is disabled, and
> - **All Other Traffic Policy** is set to **Allow Non-VPN Traffic**.
> 
> In this situation, matched traffic will automatically fall back to the WAN connection.

### Important Notes

- This method is only recommended for users who are not comfortable using SSH.

- Since the WireGuard profile is intentionally invalid, the system log will continuously contain WireGuard connection error messages.

* * *

### Step 1: Create an Invalid WireGuard Profile

You may create your own invalid WireGuard configuration or use the example below:

```ini
[Interface]
Address = 10.255.0.2/24
PrivateKey = sEl23GPd5tIb354D4fPew0Nat/i5a0szYsAH7MbF4Ek=
MTU = 1420

[Peer]
AllowedIPs = 0.0.0.0/32
Endpoint = 127.0.0.2:65535
PersistentKeepalive = 25
PublicKey = FcJBtXXGyrBaGUEAIfrruo/HJRPZf2X/DgOefStxWGo=

```

You may also download and import the attached profile directly:

[novpn.conf](https://forum.gl-inet.com/uploads/short-url/1jHrNxT4wrBuqbOyS70GFRV3pZV.conf) (256 Bytes)

* * *

### Step 2: Import the WireGuard Profile

Import the configuration as a WireGuard Client profile by following the guide below:

> **[Set Up WireGuard Client Manually (for other providers) - WireGuard Client -...](https://docs.gl-inet.com/router/en/4/interface_guide/wireguard_client/#set-up-wireguard-client-manually-for-other-providers)**
>
> Note: This guide applies to firmware v4.7 and later. For earlier versions, please refer here. | Documentation for GL.iNet Router Productions

* * *

### Step 3: Assign the Profile to the Desired Tunnel

In the VPN Dashboard:

1. Select the imported invalid WireGuard profile for the tunnel that should behave as **Not Use VPN**.  

2. Enable the tunnel.

> **Important:** Do not configure any fallback VPN profiles within this tunnel group. Otherwise, the traffic may switch to another VPN profile instead of falling back to WAN.

* * *

### Step 4: Disable Kill Switch

Open the tunnel settings and disable **Kill Switch**.

This is required to allow traffic to continue using WAN when the VPN connection fails.

 ![image](https://forum-static.gl-inet.com/original/3X/4/a/4a55d0e868d2745f5d268d60ed776dbd8354bcfa.png)

 ![image](https://forum-static.gl-inet.com/original/3X/2/b/2b476f6a6ef88bce207b9cce429f845315632600.png)

* * *

### Step 5: Allow Non-VPN Traffic

Navigate to the global VPN settings and ensure:

```plaintext
All Other Traffic Policy = Allow Non-VPN Traffic

```

 ![image](https://forum-static.gl-inet.com/original/3X/5/3/531426f4275d3c6a459bea142d3f20e23f4d9915.png)

When the invalid WireGuard profile fails to connect, matched traffic will automatically use the WAN connection.

* * *

## Verification

After configuration:

- Devices assigned to the special tunnel should access the Internet through the WAN connection.  

- Devices assigned to other VPN tunnels should continue using their respective VPN connections.  

- VPN Dashboard status may show the invalid WireGuard profile as **Connecting** , which is expected behavior for this workaround.

---

<div class="post-metadata">

**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:** [May 30, 2026, 10:14am UTC](https://forum.gl-inet.com/t/how-to-configure-a-not-use-vpn-policy-on-firmware-v4-9/69074/2 "2026-05-30T10:14:26Z")

</div>



---

<div class="post-metadata">

**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:** [June 1, 2026, 2:47am UTC](https://forum.gl-inet.com/t/how-to-configure-a-not-use-vpn-policy-on-firmware-v4-9/69074/4 "2026-06-01T02:47:54Z")

</div>



---

<div class="post-metadata">

**Author:** ![admon](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/admon/32/32880_2.png) [@admon](https://forum.gl-inet.com/u/admon)\
**Post date:** [June 25, 2026, 3:08pm UTC](https://forum.gl-inet.com/t/how-to-configure-a-not-use-vpn-policy-on-firmware-v4-9/69074/6 "2026-06-25T15:08:05Z")

</div>

We definitely need this to be added back.

Sometimes you need to avoid VPN for specific domains PLUS for specific devices.

For example, my own setup: Everything will be sent to VPN - excluding my projector (because Amazon Prime Video does not like VPN) and the domain for "Deutsche Post DHL" because they don't like VPN but I want to use the app on my iPhone.

---

<div class="post-metadata">

**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:** [June 26, 2026, 11:42am UTC](https://forum.gl-inet.com/t/how-to-configure-a-not-use-vpn-policy-on-firmware-v4-9/69074/7 "2026-06-26T11:42:13Z")

</div>

Let's gather some feedback on this request and discuss it further with the product team.

---

<div class="post-metadata">

**Author:** ![xize11](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/xize11/32/5340_2.png) [@xize11](https://forum.gl-inet.com/u/xize11)\
**Post date:** [June 26, 2026, 12:34pm UTC](https://forum.gl-inet.com/t/how-to-configure-a-not-use-vpn-policy-on-firmware-v4-9/69074/8 "2026-06-26T12:34:21Z")

</div>

Would having a poll vs a few posts not be a better way to get feedback?

I'm also against this change, and agree with everything @admon posted.

Edit:

Also on my own setup I heavily rely on this feature, since the identity verification on services in GB, alot of CDN threat vpn as their enemy even if you don't reside in GB.

It happens to banks having maintenance pages up (when in fact it is a block), to game services blocking access, some iot brands refuse to function because tuya/aqara block vpn as part of their region system, and indeed quite alot of DRM/streaming services are blocking vpns, you really want this function.

---

<div class="post-metadata">

**Author:** ![odhiambo](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/odhiambo/32/25648_2.png) [@odhiambo](https://forum.gl-inet.com/u/odhiambo)\
**Post date:** [June 26, 2026, 3:35pm UTC](https://forum.gl-inet.com/t/how-to-configure-a-not-use-vpn-policy-on-firmware-v4-9/69074/9 "2026-06-26T15:35:19Z")

</div>

On my Flint 3, I have two VPN tunnels - one for NordVPN and another to a VPS server where I run Wireguard. My VPN breakout in both cases is the US. The two tunnels are configured identically in all aspects, with kill-switch enabled

I use PBR in: ALL traffic goes through VPN except some destination domains/IPs which I prefer to be routed via WAN.  
This works, but:

1. There are sites I visit and much as they are accessed via VPN, then present to me data as if they know my country. This bothers me a lot. I wanted to ask where the information is leaking from.
2. With the same setting, I have also been wondering at what point the 2nd tunnel will ever get used. Is there some way for failover between the tunnels?
3. Using the Invalid WireGuard Profile as an example, if you create a valid tunnel with it, you cannot edit that tunnel config in v4.9. Why do we have the Edit option then?

---

<div class="post-metadata">

**Author:** ![BMV\_12](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/b/c6cbf5/32.png) [@BMV\_12](https://forum.gl-inet.com/u/BMV_12)\
**Post date:** [June 28, 2026, 6:18am UTC](https://forum.gl-inet.com/t/how-to-configure-a-not-use-vpn-policy-on-firmware-v4-9/69074/10 "2026-06-28T06:18:18Z")

</div>

This is a really poor decision to get rid of this feature. Something that was very straight forward and easy to achieve now requires a lot more work. I don’t understand why this feature was removed. I want to be able to exclude a set of IP addresses that go through the VPN tunnel that I use to be able to type in and it just worked. Now it is not very clear how I can achieve the same outcome, even after reading this post.

Also, why remove something that was already offered and working in the GUI and require the user to dive into SSH to achieve the same thing as before?

Very very poor decision to remove this. Please add this feature back!

---

<div class="post-metadata">

**Author:** ![ozsat](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/o/b5e925/32.png) [@ozsat](https://forum.gl-inet.com/u/ozsat)\
**Post date:** [June 29, 2026, 10:35am UTC](https://forum.gl-inet.com/t/how-to-configure-a-not-use-vpn-policy-on-firmware-v4-9/69074/11 "2026-06-29T10:35:19Z")

</div>

“Not Use VPN” was something I found useful on Flint 2 which configuring various VPNs but needing to rule out a couple of devices.

Now on Flint 3 and miss it

---

<div class="post-metadata">

**Author:** ![Nick-US](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/n/c37758/32.png) [@Nick-US](https://forum.gl-inet.com/u/Nick-US)\
**Post date:** [July 8, 2026, 4:19pm UTC](https://forum.gl-inet.com/t/how-to-configure-a-not-use-vpn-policy-on-firmware-v4-9/69074/12 "2026-07-08T16:19:33Z")

</div>

I agree this is not a great change. I used the not use VPN a lot and this is just extra steps to have to it via ssh. Reaching out internally to get more clarity on this

---

<div class="post-metadata">

**Author:** ![knee\_mountain523](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/k/ac91a4/32.png) [@knee\_mountain523](https://forum.gl-inet.com/u/knee_mountain523)\
**Post date:** [July 9, 2026, 8:25am UTC](https://forum.gl-inet.com/t/how-to-configure-a-not-use-vpn-policy-on-firmware-v4-9/69074/13 "2026-07-09T08:25:25Z")

</div>

I agree. This needs to be done. I have certain situations where not having a VPN makes my life much easier.

---

<div class="post-metadata">

**Author:** ![knee\_mountain523](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/k/ac91a4/32.png) [@knee\_mountain523](https://forum.gl-inet.com/u/knee_mountain523)\
**Post date:** [July 9, 2026, 8:27am UTC](https://forum.gl-inet.com/t/how-to-configure-a-not-use-vpn-policy-on-firmware-v4-9/69074/14 "2026-07-09T08:27:26Z")

</div>

Yeah, anytime SSH has to be used, it's a fail. It's way too complicated for non-networking people. GL.iNet needs to think more like Apple.

---

<div class="post-metadata">

**Author:** ![Nick-US](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/n/c37758/32.png) [@Nick-US](https://forum.gl-inet.com/u/Nick-US)\
**Post date:** [July 9, 2026, 1:06pm UTC](https://forum.gl-inet.com/t/how-to-configure-a-not-use-vpn-policy-on-firmware-v4-9/69074/15 "2026-07-09T13:06:52Z")

</div>

Agreed. I have brought it up internally with the devs and they are looking into it.

---

<div class="post-metadata">

**Author:** ![JFC1980](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/j/7bcc69/32.png) [@JFC1980](https://forum.gl-inet.com/u/JFC1980)\
**Post date:** [July 9, 2026, 6:39pm UTC](https://forum.gl-inet.com/t/how-to-configure-a-not-use-vpn-policy-on-firmware-v4-9/69074/16 "2026-07-09T18:39:14Z")

</div>

I’m NOT a fan of this latest change, nor of the (for me) overly complicated workaround methods listed above to simply restore having my router give an easy option to assign NO VPN by wifi band or device.

What I’d prefer is an EASY way to assign different VPN profiles to different wifi connections, so I can pick what kind of connection I’ll get (VPN for city 1, VPN for city 2, or NO VPN at all) based on different suitably named wifi connections, which can easily be chosen at the device level.

I kind of cobbled together this kind of approach on my newly installed Flint 2 router as follows:  
–set my main VPN tunnel and preferred city on my main router wifi connection, with the connection type set to only the wired LAN and primary wifi connections (NOT to all devices).

–set my secondary VPN tunnel and 2nd VPN city location, and assigned that to only route thru the Guest wifi connection (which can be separately selected 5G and or 2.4G wifi bands)

–and then lastly, set the city where I’m physically located as a VPN connection only for the IOT wifi connection, and assigned a VPN connection for that city to the IOT wifi band.

An easier way would simply be to add a new category under the “Select Client Source” field of “exclude ALL devices”, and then assign that routing to either the Guest or IOT wifi bands as desired to achieve the NO VPN effect on those bands.

---

<div class="post-metadata">

**Author:** ![Nick-US](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/n/c37758/32.png) [@Nick-US](https://forum.gl-inet.com/u/Nick-US)\
**Post date:** [July 10, 2026, 1:00pm UTC](https://forum.gl-inet.com/t/how-to-configure-a-not-use-vpn-policy-on-firmware-v4-9/69074/17 "2026-07-10T13:00:27Z")

</div>

I am working on it!

---

<div class="post-metadata">

**Author:** ![Nick-US](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/n/c37758/32.png) [@Nick-US](https://forum.gl-inet.com/u/Nick-US)\
**Post date:** [July 10, 2026, 1:01pm UTC](https://forum.gl-inet.com/t/how-to-configure-a-not-use-vpn-policy-on-firmware-v4-9/69074/18 "2026-07-10T13:01:59Z")

</div>

I agree. while I dont mind using ssh. this change was not great from a user perspective and the devs are already looking into a way to get this functionality back without breaking the new features and without funky workarounds.

---

<div class="post-metadata">

**Author:** ![Bogmonster](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/b/6bbea6/32.png) [@Bogmonster](https://forum.gl-inet.com/u/Bogmonster)\
**Post date:** [July 16, 2026, 3:10pm UTC](https://forum.gl-inet.com/t/how-to-configure-a-not-use-vpn-policy-on-firmware-v4-9/69074/19 "2026-07-16T15:10:24Z")

</div>

I had failed to notice this change as I kept my config on upgrade. Glad this is being reversed. Keeping the VPN config as easy as possible and hard to screw up is of primary importance to many of us I would think. My strong preference is to have to explicitly exclude devices using a ‘Do not use VPN’ policy. I was going to try OP24 to get channels 149 to 161 in UK but will put that on hold given I would need to ditch my config.

---

<div class="post-metadata">

**Author:** ![mirkohubtv](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/mirkohubtv/32/35547_2.png) [@mirkohubtv](https://forum.gl-inet.com/u/mirkohubtv)\
**Post date:** [August 10, 2026, 1:32am UTC](https://forum.gl-inet.com/t/how-to-configure-a-not-use-vpn-policy-on-firmware-v4-9/69074/20 "2026-08-10T01:32:13Z")

</div>

Is there anything we people can do to help move this particular issue forward?

---

<div class="post-metadata">

**Author:** ![aleem19875](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/a/c77e96/32.png) [@aleem19875](https://forum.gl-inet.com/u/aleem19875)\
**Post date:** [August 10, 2026, 7:17am UTC](https://forum.gl-inet.com/t/how-to-configure-a-not-use-vpn-policy-on-firmware-v4-9/69074/21 "2026-08-10T07:17:00Z")

</div>

What i do not understand is that it is possible using SSH commands, just not using the admin panel. so technically it’s possible all that left is build a nice GUI/buttons in the admin panel.

---

<div class="post-metadata">

**Author:** ![knee\_mountain523](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/k/ac91a4/32.png) [@knee\_mountain523](https://forum.gl-inet.com/u/knee_mountain523)\
**Post date:** [August 10, 2026, 10:10am UTC](https://forum.gl-inet.com/t/how-to-configure-a-not-use-vpn-policy-on-firmware-v4-9/69074/22 "2026-08-10T10:10:30Z")

</div>

What's the ETA now? I totally forgot about this and really want this to be added back to the GUI. The SSH method is bound to cause more trouble with newbies.

[Next page](https://forum.gl-inet.com/t/how-to-configure-a-not-use-vpn-policy-on-firmware-v4-9/69074.md?page=2)
