# \[Bug\] GL GUI: Multi-WAN Interface Priority not honored/have effect **URL:** \ **Category:** Router\ **Created:** [July 16, 2023, 10:00am UTC](https://forum.gl-inet.com/t/bug-gl-gui-multi-wan-interface-priority-not-honored-have-effect/31443 "2023-07-16T10:00:47Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![bring.fringe18](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bring.fringe18/32/11777_2.png) [@bring.fringe18](https://forum.gl-inet.com/u/bring.fringe18)\ **Post date:** [July 16, 2023, 10:00am UTC](https://forum.gl-inet.com/t/bug-gl-gui-multi-wan-interface-priority-not-honored-have-effect/31443/1 "2023-07-16T10:00:47Z")
Device: Burme 2 (GL-MT2500) Firmware: 4.2.3 release 5 (OpenWrt 21.02-SNAPSHOT) # Goal `tethering` interface to be the primary Internet connection for the Multi-WAN setup while the Ethernet is also connected to the Burme 2's WAN port. # Issue The Ethernet takes priority for all Internet connections in a Multi-WAN setup but the tethered device offers a faster connection. Interface Priority is reported to have been adjusted within the GL GUI -\> Network -\> Multi-WAN -\> Interface Priority but does not seem to be honored/have an effect. # Diagnosis - Network configuration details for network interfaces are stored in the text file `/etc/config/network` - The Ethernet uses the `wan` network interface with a `metric` of `10`. This sets its priority over any other interfaces. - The tethered device uses the `tethering` network interface with a `metric` of `30`. Its higher value places it at a lower priority. # Proposed Resolution Manually inverse the metrics affecting the interface priorities. - Edit & save the `/etc/config/network` to set `tethering`'s metric to `10` & `wan`'s metric to `30`. - `nano /etc/config/network` - Restart the networking system - `service network reload` or `/etc/init.d/network reload` - Confirm the results - `ip route show` - [https://speedtest.net](https://speedtest.net) # Reported Result Tethered device now set as primary Internet connection; [SpeedTest.net](http://SpeedTest.net) now reports 363.09/57.18 Mbps up/down vs 50 Mbps Ethernet. # Further Details - Device runs OpenWrt 21.02-SNAPSHOT; 21.02.0 was released 2021 Sep 04. - On 2022 Aug 4 a bug report was filed to OpenWrt reporting `metrics` were not correctly processed on a `Target Platform: ipq806x/generic`. - [Option metric in /etc/config/network not correctly processed. #10384](https://github.com/openwrt/openwrt/issues/10384) - Issue is suspected to be relevant to GL GUI Interface Priority/Mutli-WAN configuration * * * Source thread: > [@MT2500 Failover not working](https://forum.gl-inet.com/t/mt2500-failover-not-working/31425): > > Hi I have a fixed VDSL on the WAN connection - that gives speeds of 50mb/s I have a 5G modem on a USB to LAN adaptor set as TETHERING - that’s gives speeds of 500mb/s I have failover set with the priority of TETHERING then WAN However it always connects via the VDSL WAN connection On load balance it also always connects on the VDSL WAN My connection never goes above 50mb/s unless I physically remove the WAN connection ---
**Author:** ![dxf](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/d/41988e/32.png) [@dxf](https://forum.gl-inet.com/u/dxf)\ **Post date:** [July 17, 2023, 3:14am UTC](https://forum.gl-inet.com/t/bug-gl-gui-multi-wan-interface-priority-not-honored-have-effect/31443/2 "2023-07-17T03:14:14Z")
Multi-WAN does not work via /etc/config/netowk, it works according to the iptable+ip route in mwan3. I retested the MT2500 v4.2.3 for tethering first priority and found that it worked fine. If you repeat this problem again, can you follow my screenshot to debug the message and share it? ![image](https://forum-static.gl-inet.com/original/2X/e/e360614d199176bf7912cd2be9481754a5cecd66.png) ---
**Author:** ![bring.fringe18](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bring.fringe18/32/11777_2.png) [@bring.fringe18](https://forum.gl-inet.com/u/bring.fringe18)\ **Post date:** [July 17, 2023, 3:48am UTC](https://forum.gl-inet.com/t/bug-gl-gui-multi-wan-interface-priority-not-honored-have-effect/31443/3 "2023-07-17T03:48:59Z")
> [@dxf](#): > > I retested the MT2500 v4.2.3 for tethering first priority and found that it worked fine. Would an active WireGuard Client session impact `mwan3` by holding/locking the interface to the current set of iptables + route & not allow `mwan3` to make the necessary adjustments? In the linked source thread there’s `ip route` output showing active WG while the `metric` was still `10` on `eth0` after confirming the GL GUI → Network → Multi-WAN → Interface Priority was set but was was reported to have not changed as desired. I overlooked the WG tunnel in the output at the time so I’m now wondering if the active WG Client was the true cause. > [@dxf](#): > > Multi-WAN does not work via /etc/config/netowk […] I had somewhat of a feeling it didn’t but I was under the impression GL GUI’s Interface Priority was already set but non-working so I went w/ what I knew. > [@dxf](#): > > If you repeat this problem again, can you follow my screenshot to debug the message and share it? See the source/originating thread. I’d think @scumball would be interested to know of a proper solution rather than my less than ideal workaround. ---
**Author:** ![jdh](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/j/67e7ee/32.png) [@jdh](https://forum.gl-inet.com/u/jdh)\ **Post date:** [July 17, 2023, 1:42pm UTC](https://forum.gl-inet.com/t/bug-gl-gui-multi-wan-interface-priority-not-honored-have-effect/31443/4 "2023-07-17T13:42:27Z")
I can confirm this also becomes an issue when you set up a Wireguard server in Multi-WAN in load balance mode. Unless you change to failover mode or manually edit the metric values in LuCI or /etc/config/network, the Wireguard server will only listen on the ethernet port. This was problematic in my case, since the ethernet port is actually plugged through a wireless bridge and as such less favourable than the direct WWAN. In order to get Wireguard to listen on WWAN, I had to edit the metric values for the interfaces /etc/config/network ---
**Author:** ![bring.fringe18](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bring.fringe18/32/11777_2.png) [@bring.fringe18](https://forum.gl-inet.com/u/bring.fringe18)\ **Post date:** [July 17, 2023, 2:51pm UTC](https://forum.gl-inet.com/t/bug-gl-gui-multi-wan-interface-priority-not-honored-have-effect/31443/5 "2023-07-17T14:51:09Z")
So I’m not as mistaken as I thought I was. Thank you. It seems to me this could be resolved by a GL GUI modal box/prompt notifying/warning the user _all_ interfaces in `/etc/config/network` would need to be force released before refreshing to allow `mwan3`’s updated configuration to take effect. I’d think the user would want to explicitly be informed beforehand & the option be present to cancel the change least there be inadvertent VPN leaks. ---
**Author:** ![bruce](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bruce/32/35649_2.png) [@bruce](https://forum.gl-inet.com/u/bruce)\ **Post date:** [October 29, 2025, 4:23am UTC](https://forum.gl-inet.com/t/bug-gl-gui-multi-wan-interface-priority-not-honored-have-effect/31443/6 "2025-10-29T04:23:06Z")