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
Okay this is going to sound redundant because you’ve already clearly stated what you’ve done… but you have the Interface Priority adjusted per GL GUI → Network → Multi-WAN → Interface Priority → [drag to sort]?
What firmware version are you using? Is it the most recent stable release (GL GUI → System → Upgrade)?
Thanks for the reply
Yes priority is set as
TETHERING
WAN
On the latest 4.2.3 release 5
I think I’m onto something but I’m still speculating. Can you ssh into your Burme 2 & post the output of cat /etc/config/network? I’m looking to see what’s set for the metric of your various interfaces.
Also if you could install LuCI & confim the version of OpenWrt @ its status page (GL GUI → System → Advanced Settings). Default pwd is same as the GL GUI, username root .
Info below and removed from pastebin
(Oh gawd, pastebin… next time could you just post directly into your response? You can format codeblocks by putting them between three ‘backticks’ on lines before & after the output (the key up buy the 1 key on the keyboard). It helps others follow along if they stumble on this thread for a similar issue)
Thanks for confirming the OWRT version.
There’s missing lines from that output. It should start w/
root@GL-AXT1800:~# cat /etc/config/network
config interface 'loopback'
option device 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
… & so on. Part of what I’m looking for is shown in your pastebin but I need the full output.
Try echo "### beginning of network conf file ###" && cat /etc/config/network && echo "### // end of network conf ###"
Then pls execute & post the output of echo "### begin ip routes ###" && ip route show && echo "### // end of ip routes ###"
That should give me everything I need to see what’s going on.
root@192.168.2.1's password:
BusyBox v1.33.2 (2023-07-06 05:09:44 UTC) built-in shell (ash)
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt 21.02-SNAPSHOT, r15812+879-46b6ee7ffc
-----------------------------------------------------
root@GL-MT2500:~# echo "### beginning of network conf file ###" && cat /etc/conf
ig/network && echo "### // end of network conf ###"
### beginning of network conf file ###
config interface 'loopback'
option device 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fd1a:3d38:a70f::/48'
config device
option name 'br-lan'
option type 'bridge'
list ports 'eth1'
config device
option name 'eth1'
option macaddr '94:83:c4:2f:38:37'
config interface 'lan'
option device 'br-lan'
option proto 'static'
option netmask '255.255.255.0'
option ip6assign '60'
option isolate '0'
option ipaddr '192.168.2.1'
config device
option name 'eth0'
option macaddr '94:83:c4:2f:38:36'
config interface 'wan'
option device 'eth0'
option force_link '0'
option ipv6 '0'
option metric '10'
option proto 'static'
option netmask '255.255.255.0'
option peerdns '0'
option ipaddr '192.168.1.1'
option gateway '192.168.1.254'
option dns '76.76.2.2 76.76.10.2'
config interface 'wan6'
option proto 'dhcpv6'
option disabled '1'
option device '@wan'
config interface 'tethering6'
option proto 'dhcpv6'
option disabled '1'
option device '@tethering'
config interface 'wwan6'
option proto 'dhcpv6'
option disabled '1'
option device '@wwan'
config rule 'policy_bypass_vpn'
option mark '0x60000/0x60000'
option lookup '53'
option priority '53'
config rule 'policy_via_vpn'
option mark '0x80000/0x80000'
option lookup '52'
option priority '52'
config rule 'policy_dns'
option mark '0x100000/0x100000'
option lookup '51'
option priority '51'
config interface 'wgserver'
option proto 'wgserver'
option config 'main_server'
option disabled '0'
config interface 'modem_1_1_6'
option proto 'dhcpv6'
option disabled '1'
option device '@modem_1_1'
config interface 'modem_2_1_6'
option proto 'dhcpv6'
option disabled '1'
option device '@modem_2_1'
config interface 'wgclient'
option proto 'wgclient'
option config 'peer_2010'
option disabled '0'
config interface 'tethering'
option proto 'dhcp'
option ifname 'eth2'
option metric '30'
### // end of network conf ###
root@GL-MT2500:~#
root@192.168.2.1's password:
BusyBox v1.33.2 (2023-07-06 05:09:44 UTC) built-in shell (ash)
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt 21.02-SNAPSHOT, r15812+879-46b6ee7ffc
-----------------------------------------------------
root@GL-MT2500:~# echo "### begin ip routes ###" && ip route show && echo "### /
/ end of ip routes ###"
### begin ip routes ###
0.0.0.0/1 dev wgclient scope link
default via 192.168.1.254 dev eth0 proto static metric 10
default via 192.168.8.1 dev eth2 proto static src 192.168.8.100 metric 30
10.0.0.0/24 dev wgserver proto kernel scope link src 10.0.0.1
45.9.248.4 via 192.168.1.254 dev eth0 proto static metric 10
128.0.0.0/1 dev wgclient scope link
192.168.1.0/24 dev eth0 proto static scope link metric 10
192.168.2.0/24 dev br-lan proto kernel scope link src 192.168.2.1
192.168.8.0/24 dev eth2 proto static scope link metric 30
### // end of ip routes ###
root@GL-MT2500:~#
Can I get echo echo "### begin ip routes ###" && ip route show && echo "### // end of ip routes ###" , too?
Okay, we’re going to need to adjust a couple of the metric values by editing the /etc/config/network . If you’re not comfortable w/ vi, the nano editor is far easier. opkg update && opkg install nano .
OK i’ll have a go - nano installed
Great, so to recap:
Device: Burme 2 (GL-MT2500)
Firmware: 4.2.3 release 5 (OpenWrt 21.02-SNAPSHOT)
You want your tethering interface to be the primary Internet connection for your Multi-WAN setup while the Ethernet is also connected to your Burme 2’s WAN port.
The Ethernet takes priority for all Internet connections in a Multi-WAN setup but the tethered device offers a faster connection. Interface Priority has been adjusted within the GL GUI → Network → Multi-WAN → Interface Priority but does not seem to be honored/have an effect.
/etc/config/networkwan network interface with a metric of 10. This sets its priority over any other interfaces.tethering network interface with a metric of 30. Its higher value places it at a lower priority./etc/config/network to set tethering’s metric to 10 & wan’s metric to 30.
nano /etc/config/networkservice network reload or /etc/init.d/network reloadip route showIssue filed:
Yes all correct
I did as you said and lost access to the internet
Both interfaces were showing red and failing ping tests
I put it back and they came back on
root@192.168.2.1's password:
BusyBox v1.33.2 (2023-07-06 05:09:44 UTC) built-in shell (ash)
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt 21.02-SNAPSHOT, r15812+879-46b6ee7ffc
-----------------------------------------------------
root@GL-MT2500:~# nano /etc/config/network
root@GL-MT2500:~# nano /etc/config/network
root@GL-MT2500:~# service network reload
root@GL-MT2500:~# ip route show
0.0.0.0/1 dev wgclient scope link
default via 192.168.8.1 dev eth2 proto static src 192.168.8.100 metric 10
default via 192.168.1.254 dev eth0 proto static metric 30
10.0.0.0/24 dev wgserver proto kernel scope link src 10.0.0.1
128.0.0.0/1 dev wgclient scope link
192.168.1.0/24 dev eth0 proto static scope link metric 30
192.168.2.0/24 dev br-lan proto kernel scope link src 192.168.2.1
192.168.8.0/24 dev eth2 proto static scope link metric 10
root@GL-MT2500:~# ip route show
0.0.0.0/1 dev wgclient scope link
default via 192.168.8.1 dev eth2 proto static src 192.168.8.100 metric 10
default via 192.168.1.254 dev eth0 proto static metric 30
10.0.0.0/24 dev wgserver proto kernel scope link src 10.0.0.1
128.0.0.0/1 dev wgclient scope link
192.168.1.0/24 dev eth0 proto static scope link metric 30
192.168.2.0/24 dev br-lan proto kernel scope link src 192.168.2.1
192.168.8.0/24 dev eth2 proto static scope link metric 10
root@GL-MT2500:~# nano /etc/config/network
root@GL-MT2500:~# service network reload
root@GL-MT2500:~# ip route show
0.0.0.0/1 dev wgclient scope link
default via 192.168.1.254 dev eth0 proto static metric 10
default via 192.168.8.1 dev eth2 proto static src 192.168.8.100 metric 30
10.0.0.0/24 dev wgserver proto kernel scope link src 10.0.0.1
128.0.0.0/1 dev wgclient scope link
192.168.1.0/24 dev eth0 proto static scope link metric 10
192.168.2.0/24 dev br-lan proto kernel scope link src 192.168.2.1
192.168.8.0/24 dev eth2 proto static scope link metric 30
root@GL-MT2500:~# nano /etc/config/network
root@GL-MT2500:~# service network reload
root@GL-MT2500:~# ip route show
0.0.0.0/1 dev wgclient scope link
default via 192.168.8.1 dev eth2 proto static src 192.168.8.100 metric 10
default via 192.168.1.254 dev eth0 proto static metric 30
10.0.0.0/24 dev wgserver proto kernel scope link src 10.0.0.1
128.0.0.0/1 dev wgclient scope link
192.168.1.0/24 dev eth0 proto static scope link metric 30
192.168.2.0/24 dev br-lan proto kernel scope link src 192.168.2.1
192.168.8.0/24 dev eth2 proto static scope link metric 10
root@GL-MT2500:~# ip route show
0.0.0.0/1 dev wgclient scope link
default via 192.168.8.1 dev eth2 proto static src 192.168.8.100 metric 10
default via 192.168.1.254 dev eth0 proto static metric 30
10.0.0.0/24 dev wgserver proto kernel scope link src 10.0.0.1
128.0.0.0/1 dev wgclient scope link
192.168.1.0/24 dev eth0 proto static scope link metric 30
192.168.2.0/24 dev br-lan proto kernel scope link src 192.168.2.1
192.168.8.0/24 dev eth2 proto static scope link metric 10
root@GL-MT2500:~#```Run a https://speedtest.net & see if you’re getting the speed difference.
Losing the 'net access should be temporary due to restarting the network processes. IDK about the red or why they’d be failing ping tests.
If there’s no 'net access at all set your wan back to 10, tethering back to 30 & reboot; that should restore it back to the way it was.
This situation looks very much like a bug.
Now I have put it back my IP is registered as my WAN/VDSL and the same on Speedtest with the same 50mb/s result.
Okay, I’m going to link this thread into a suspected bug report. GL reps will see it & comment further I’m sure.
Thanks for everything
I think it’s worked!
I had a VPN client running - that my PC wasn’t going through - but stopping the VPN and restarting has brought the PC back online with the new settings
Thanks for all the help - looks like its working - but still a bug I guess that you can’t do it through the glinet UI when it suggests you can.
Yeah, it’s still a bug due to the GL GUI just as you say.
Can you post a screenshot of your speedtest.net results?
If it works can you please mark my ‘recap’ post as ‘Solution’? TIA.
