I have configured my MT1300 to do “load-balance” between two providers (a) DSL as the primary (eth0.2) and (b) T-Mobile 5G Home Internet as the secondary (eth0.3).
On the T-Mobile path (eth0.3), the tracking method “ping” is unreliable and times out most of the time (100% packet loss). Thereby the second mwan3 connection remains down.
# ping -I eth0.3 -c5 1.1.1.1
PING 1.1.1.1 (1.1.1.1): 56 data bytes
--- 1.1.1.1 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
Testing from the MT 1300 CLI (ssh session)
httping -I eth0.3 -c5 instagram.com
PING instagram.com:80 (/):
connected to 31.13.70.174:80 (196 bytes), seq=0 time=134.34 ms
connected to 31.13.93.174:80 (196 bytes), seq=1 time=130.23 ms
connected to 31.13.93.174:80 (196 bytes), seq=2 time=150.19 ms
connected to 31.13.93.174:80 (196 bytes), seq=3 time=130.08 ms
connected to 31.13.93.174:80 (196 bytes), seq=4 time=140.24 ms
--- http://instagram.com/ ping statistics ---
5 connects, 5 ok, 0.00% failed, time 5734ms
round-trip min/avg/max = 130.1/137.0/150.2 ms
However, I am unable to set httping as the “tracking method” on the T-Mobile interface.
I get an error " * One or more required fields have no value!" without mentioning which exact fields are missing.
Any guidance to get past this error message would be appreciated.
Can you post the /etc/config/mwan file from the router?
I do not work for and I do not have formal association with GL.iNet
Here is my /etc/config/mwan3
config globals 'globals'
option mmx_mask '0x3F00'
config interface 'wan'
option family 'ipv4'
option enabled '1'
option initial_state 'online'
option size '56'
option interval '5'
option failure_interval '5'
option timeout '3'
option down '5'
option up '2'
option reliability '2'
option count '3'
option keep_failure_interval '1'
option recovery_interval '1'
list track_ip '1.0.0.1'
list track_ip '1.1.1.1'
list track_ip '8.8.8.8'
option track_method 'httping'
config interface 'wan2'
option family 'ipv4'
option enabled '1'
option initial_state 'online'
option size '56'
option interval '5'
option failure_interval '5'
option down '3'
option count '3'
option timeout '3'
option up '2'
option reliability '2'
option keep_failure_interval '1'
option recovery_interval '1'
option track_method 'ping'
option max_ttl '60'
option check_quality '0'
list track_ip '1.0.0.1'
list track_ip '1.1.1.1'
list track_ip '8.8.8.8'
config member 'wan_m1_w3'
option interface 'wan'
option metric '1'
option weight '3'
config member 'wan_m1_w3'
option interface 'wan'
option metric '1'
option weight '3'
config member 'wan_m2_w3'
option interface 'wan'
option metric '2'
option weight '3'
config member 'wan2_m1_w2'
option interface 'wan2'
option metric '1'
option weight '2'
config member 'wan2_m1_w3'
option interface 'wan2'
option metric '1'
option weight '3'
config member 'wan2_m2_w2'
option interface 'wan2'
option metric '2'
option weight '2'
config policy 'wan_only'
list use_member 'wan_m1_w3'
config policy 'wan2_only'
list use_member 'wan2_m1_w2'
config policy 'balanced'
list use_member 'wan_m1_w3'
list use_member 'wan2_m1_w3'
config policy 'wan_wan2'
list use_member 'wan_m1_w3'
list use_member 'wan2_m2_w2'
config policy 'wan2_wan'
list use_member 'wan_m2_w3'
list use_member 'wan2_m1_w2'
config rule 'https'
option sticky '1'
option dest_port '443'
option proto 'tcp'
option use_policy 'balanced'
config rule 'default_rule_v4'
option dest_ip '0.0.0.0/0'
option use_policy 'balanced'
option family 'ipv4'
alzhao
March 22, 2023, 5:07am
4
Is this on Luci?
What is the firmware version of MT1300?
Want to have a test but better do the same as yours. Can you post screenshot capturing all the fileds you filled?
Yes, the error is on the Luci web UI.
From what I have observed the “ping” tracking method has two items more than the “httping” method:
Max TTL and
Check link quality
See the screenshots below.
Ping options – screenshot
Httping options – screenshot
IMO, the bug is in the backend scripts and not in the Web UI. When I ssh into the unit, I see 'uci item not found."
FWIW, I have manually edited the /etc/config/mwan3 file to do “ping” on eth0.2 (DSL) and “httping” on eth0.3 (T-Mobile) and after some coaxing (mwan3 reload a few times) I got both the wan interfaces to be active.
1 Like
alzhao
March 24, 2023, 7:38am
6
I am glad that it is working normal now.
