Mwan3 backup wwan is used, but default wan has no downtime

I use a second wan (wwan 4g connection) as a backup in case the default wan has no connection.

But I see so now and then that my wwan is using a lot of data, so there is a route over the wwan, while the default wan is up al the time.

Is there something in the config not right? Maybe it kicks in to soon or something?

My /etc/config/mwan3

config globals 'globals'
	option mmx_mask '0x3F00'

config interface 'wan'
	option enabled '1'
	option family 'ipv4'
	option reliability '2'
	option initial_state 'online'
	option track_method 'ping'
	option count '1'
	option size '56'
	option max_ttl '60'
	option timeout '4'
	option interval '10'
	option failure_interval '5'
	option recovery_interval '5'
	option down '5'
	option up '5'
	list track_ip '1.1.1.1'
	list track_ip '1.0.0.1'
	option check_quality '0'

config member 'wan_m1_w3'
	option interface 'wan'
	option metric '1'
	option weight '3'

config policy 'wan_only'
	list use_member 'wan_m1_w3'
	list use_member 'wwan_m1_w3'
	option last_resort 'unreachable'

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'

config rule 'default_rule_v6'
	option dest_ip '::/0'
	option use_policy 'balanced'
	option family 'ipv6'

config interface 'wwan'
	option enabled '1'
	option initial_state 'online'
	option family 'ipv4'
	list track_ip '1.1.1.1'
	list track_ip '1.0.0.1'
	option track_method 'ping'
	option count '1'
	option size '56'
	option max_ttl '60'
	option timeout '4'
	option interval '10'
	option failure_interval '5'
	option recovery_interval '5'
	option down '5'
	option up '5'
	option reliability '2'

config member 'wwan_m1_w3'
	option interface 'wwan'
	option weight '3'
	option metric '2'


Balanced policy is nowhere to be found...

I guess this is the policy?

wan_m1-w3 member has a metric of 10
wwan_m1_w3 member has a metric of 20

Or do you mean something else maybe?

Name of the policy is badly chosen, should be backup_wan

I think I know what trickers it, not how to solve it.

When the wan is down, (that was because I was working on the lan cable for a minute) the wwan takes over, as expected. But when wan is up again it doesn’t take over from the wwan.

Any ideas?

You have 3 rules configured and all use balanced policy. But such a policy does not exist. There is only wan_only policy.

Oops.. changed that :wink: