Cannot get MWAN3 to fail back on LTE interface

Installing and Using OpenWrt Network and Wireless Configuration
1

Hi Group

Configuration as below:

root@OpenWrt_Lab:~# cat /etc/config/mwan3

config globals 'globals'
	option enabled '1'
	option local_source 'lan'
	option mmx_mask '0x3F00'

config interface 'wan'
	list track_ip '8.8.4.4'
	list track_ip '4.2.2.3'
	option enabled '1'
	option reliability '1'
	option count '1'
	option timeout '2'
	option interval '5'
	option down '3'
	option up '8'
	option initial_state 'online'
	option family 'ipv4'
	option track_method 'ping'
	option size '56'
	option check_quality '0'
	option failure_interval '5'
	option recovery_interval '5'
	option flush_conntrack 'never'

config interface 'lte'
	option enabled '1'
	option reliability '1'
	option count '1'
	option timeout '2'
	option initial_state 'online'
	option family 'ipv4'
	option track_method 'ping'
	option size '56'
	option check_quality '0'
	option recovery_interval '5'
	option flush_conntrack 'never'
	list track_ip '8.8.4.4'
	list track_ip '4.2.2.3'
	option down '3'
	option interval '5'
	option failure_interval '5'
	option up '8'

config policy 'wan_lte'
	list use_member 'wan_m1_w1'
	list use_member 'lte_m2_w2'
	option last_resort 'unreachable'

config member 'wan_m1_w1'
	option interface 'wan'
	option metric '1'
	option weight '1'

config member 'lte_m2_w2'
	option interface 'lte'
	option metric '2'
	option weight '2'

config rule 'default'
	option proto 'all'
	option sticky '0'
	option use_policy 'wan_lte'
	option dest_ip '0.0.0.0/0'

It fails over to the LTE interface fine but does not seem to come back in a reasonable period of time.
It does come back eventually but certainly not in the time I would be expecting from the parameters configured.

Any ideas?

Thanks
Mike

2

Seems to work fine now that I set Flush conntrack table: always on the primary interface.
Is this correct?

Thanks
Mike

3

Bump: The mwan3 guide mentions nothing about flushing conntrack! https://openwrt.org/docs/guide-user/network/wan/multiwan/mwan3

I think I have the same problem and I'm working to troubleshoot it, but someone who actually knows about mwan3 and conntrack and can edit the wiki should check this!

4

For anyone coming across this in future. The conntrack information was missing from the documentation. It has now been added. A specific entry about conntrack is now under the interface configuration information:

Is has been observed that for some cases with inbound traffic flushing conntrack is required.