[FS#1029] mwan3 fails to turn off routing through offline interface

[LEDE Bugs]

A new Flyspray task has been opened.  Details are below. 

User who did this - Mauro Mozzarelli (ezplanet) 

Attached to Project - LEDE Project
Summary - mwan3 fails to turn off routing through offline interface
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - High
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - The device is BT Home Hub 5
The build is: LEDE Reboot SNAPSHOT r4883-ce53c0e (problem is present also in previous releases) mwan3 module built in.

The configuration is as follows:

dsl pppoa-wan configured as WAN interface, default route metric 2
eth0.2 configured as DMZ interface (red ethernet port), default route metric 1   

When WAN interface is down, luci shows the interface as offline, RED colour

# mwan3 status
Interface status:
 interface wan is unknown and tracking is active
 interface dmz is online and tracking is active

Current ipv4 policies:
balanced:
 dmz (100%)

dmz_only:
 dmz (100%)

dmz_wan:
 dmz (100%)

wan_dmz:
 dmz (100%)

wan_only:
 unreachable


Current ipv6 policies:
balanced:
 unreachable

dmz_only:
 unreachable

dmz_wan:
 unreachable

wan_dmz:
 unreachable

wan_only:
 unreachable

-------------------------
All is OK above when WAN interface is down, it is detected, routing goes through DMZ only


When DMZ interface is down instead, luci shows the interface as online tracking, GREEN
however mwan3 status reports:

Interface status:
 interface wan is online and tracking is active
 interface dmz is offline and tracking is active

Current ipv4 policies:
balanced:
 wan (100%)

dmz_only:
 unreachable

dmz_wan:
 wan (100%)

wan_dmz:
 wan (100%)

wan_only:
 wan (100%)


Current ipv6 policies:
balanced:
 unreachable

dmz_only:
 unreachable

dmz_wan:
 unreachable

wan_dmz:
 unreachable

wan_only:
 unreachable


Thus it looks like mwan3 status reports the interface as offline correctly, luci has it as online and routing is still attempted through it (thus failing).


----------------- mwan3 configuration ---------------
config rule 'http_tcp'
	option dest_port '80,8080'
	option proto 'tcp'
	option sticky '0'
	option use_policy 'balanced'
	option dest_ip '0.0.0.0/0 '

config rule 'http_udp'
	option dest_port '80,8080'
	option proto 'udp'
	option sticky '0'
	option use_policy 'balanced'
	option dest_ip '0.0.0.0/0 '

config rule 'https'
	option sticky '1'
	option dest_port '443'
	option proto 'tcp'
	option use_policy 'balanced'

config rule 'ezplanet_ssh'
	option dest_port '22'
	option proto 'tcp'
	option sticky '1'
	option use_policy 'dmz_wan'

config rule 'torrent1'
	option proto 'tcp'
	option sticky '0'
	option dest_port '6880:7000'
	option use_policy 'wan_dmz'

config rule 'torrent2'
	option dest_port '49300:49320'
	option proto 'tcp'
	option sticky '0'
	option use_policy 'wan_dmz'

config rule 'aMule_tcp'
	option dest_port '4662:4665'
	option proto 'tcp'
	option sticky '0'
	option use_policy 'wan_dmz'

config rule 'aMule_udp'
	option dest_port '4672'
	option proto 'udp'
	option sticky '0'
	option use_policy 'wan_dmz'

config rule 'default_rule'
	option dest_ip '0.0.0.0/0'
	option use_policy 'balanced'
	option proto 'all'
	option sticky '1'

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

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 'dmz_m1_w2'
	option interface 'dmz'
	option metric '1'
	option weight '2'

config member 'dmz_m2_w2'
	option interface 'dmz'
	option metric '2'
	option weight '2'

config policy 'wan_only'
	list use_member 'wan_m1_w3'

config policy 'dmz_only'
	list use_member 'dmz_m1_w2'

config policy 'balanced'
	list use_member 'wan_m1_w3'
	list use_member 'dmz_m1_w2'

config policy 'wan_dmz'
	list use_member 'wan_m1_w3'
	list use_member 'dmz_m2_w2'

config policy 'dmz_wan'
	list use_member 'wan_m2_w3'
	list use_member 'dmz_m1_w2'

config globals 'globals'
	option initial_source 'none'
	option local_source 'lan'
	option mmx_mask '0xff00'

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


More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=1029