Topic: mwan3; multi-wan policy routing (general topic)

The content of this topic has been archived between 22 May 2013 and 6 May 2018. Unfortunately there are posts – most likely complete pages – missing.

Page 65 of 65

Post #1601

Deus3X

24 Feb 2017, 00:07

hi @Adze, hi openwrt members,
i was using mwan3 from 2 years with BB on an archer C7 v1
now i switched on dir-860L
i'm trying to replace the same configuration that i was using on BB but i having lots of problem.
mwan3 is working fine with ethernet interface but it does don't want to work with l2tp vpn client.
wan4 is the l2tp interface with metric 40.
The interface is online and is working if i uninstall mwan3.
mwan3 does not set ip rule and ip routing for that device and ofcorse is not able to ping and is marked ad offline.
the strange thing is that if i set the wan4 with metric 10 it will have ip rule and ip routing setting but the other interface will be marked as offline.

i have sent your test commands and this is the result:

root@DIR-860L:~# ACTION=ifup INTERFACE=wan4 /etc/hotplug.d/iface/15-mwan3
root@DIR-860L:~# echo $?
3

this is my configuration:

Software versions : 

OpenWrt - LEDE Reboot 17.01.0 r3205-59508e3
LuCI - git-17.051.53299-a100738

mwan3 - 2.0-3
mwan3-luci - 1.4-5

Output of "cat /etc/config/mwan3" : 

config interface 'wan'
    option enabled '1'
    list track_ip '8.8.4.4'
    list track_ip '8.8.8.8'
    list track_ip '208.67.222.222'
    list track_ip '208.67.220.220'
    option count '1'
    option timeout '2'
    option interval '5'
    option down '3'
    option up '8'
    option reliability '1'

config interface 'wan2'
    option reliability '1'
    option count '1'
    option timeout '2'
    option interval '5'
    option down '3'
    option up '8'
    option enabled '1'
    list track_ip '8.8.4.4'
    list track_ip '8.8.8.8'
    list track_ip '208.67.222.222'
    list track_ip '208.67.220.220'

config interface 'wan3'
    option enabled '1'
    option reliability '1'
    option count '1'
    option timeout '2'
    option interval '5'
    option down '3'
    option up '8'
    list track_ip '8.8.4.4'
    list track_ip '8.8.8.8'
    list track_ip '208.67.222.222'
    list track_ip '208.67.220.220'

config interface 'wan4'
    option enabled '1'
    option reliability '1'
    option count '1'
    option timeout '2'
    option interval '5'
    option down '3'
    option up '8'
    list track_ip '8.8.4.4'
    list track_ip '8.8.8.8'
    list track_ip '208.67.222.222'
    list track_ip '208.67.220.220'

config interface 'wan5'
    option enabled '1'
    list track_ip '8.8.4.4'
    list track_ip '8.8.8.8'
    list track_ip '208.67.222.222'
    list track_ip '208.67.220.220'
    option reliability '1'
    option count '1'
    option timeout '2'
    option interval '5'
    option down '3'
    option up '8'

config interface 'wan6'
    option enabled '1'
    list track_ip '8.8.4.4'
    list track_ip '8.8.8.8'
    list track_ip '208.67.222.222'
    list track_ip '208.67.220.220'
    option reliability '1'
    option count '1'
    option timeout '2'
    option interval '5'
    option down '3'
    option up '8'

config member 'wan_m1_w6'
    option interface 'wan'
    option metric '1'
    option weight '6'

config member 'wan_m2_w6'
    option interface 'wan'
    option metric '2'
    option weight '6'

config member 'wan_m3_w6'
    option interface 'wan'
    option metric '3'
    option weight '6'

config member 'wan_m4_w6'
    option interface 'wan'
    option metric '4'
    option weight '6'

config member 'wan_m5_w6'
    option interface 'wan'
    option metric '5'
    option weight '6'

config member 'wan_m6_w6'
    option interface 'wan'
    option metric '6'
    option weight '6'

config member 'wan2_m1_w5'
    option interface 'wan2'
    option metric '1'
    option weight '5'

config member 'wan2_m2_w5'
    option interface 'wan2'
    option metric '2'
    option weight '5'

config member 'wan2_m3_w5'
    option interface 'wan2'
    option metric '3'
    option weight '5'

config member 'wan2_m4_w5'
    option interface 'wan2'
    option metric '4'
    option weight '5'

config member 'wan2_m5_w5'
    option interface 'wan2'
    option metric '5'
    option weight '5'

config member 'wan2_m6_w5'
    option interface 'wan2'
    option metric '6'
    option weight '5'

config member 'wan3_m1_w4'
    option interface 'wan3'
    option metric '1'
    option weight '4'

config member 'wan3_m2_w4'
    option interface 'wan3'
    option metric '2'
    option weight '4'

config member 'wan3_m3_w4'
    option interface 'wan3'
    option metric '3'
    option weight '4'

config member 'wan3_m4_w4'
    option interface 'wan3'
    option metric '4'
    option weight '4'

config member 'wan3_m5_w4'
    option interface 'wan3'
    option metric '5'
    option weight '4'

config member 'wan3_m6_w4'
    option interface 'wan3'
    option metric '6'
    option weight '4'

config member 'wan4_m1_w3'
    option interface 'wan4'
    option metric '1'
    option weight '3'

config member 'wan4_m2_w3'
    option interface 'wan4'
    option metric '2'
    option weight '3'

config member 'wan4_m3_w3'
    option interface 'wan4'
    option metric '3'
    option weight '3'

config member 'wan4_m4_w3'
    option interface 'wan4'
    option metric '4'
    option weight '3'

config member 'wan4_m5_w3'
    option interface 'wan4'
    option metric '5'
    option weight '3'

config member 'wan4_m6_w3'
    option interface 'wan4'
    option metric '6'
    option weight '3'

config member 'wan5_m1_w2'
    option interface 'wan5'
    option metric '1'
    option weight '2'

config member 'wan5_m2_w2'
    option interface 'wan5'
    option metric '2'
    option weight '2'

config member 'wan5_m3_w2'
    option interface 'wan5'
    option metric '3'
    option weight '2'

config member 'wan5_m4_w2'
    option interface 'wan5'
    option metric '4'
    option weight '2'

config member 'wan5_m5_w2'
    option interface 'wan5'
    option metric '5'
    option weight '2'

config member 'wan5_m6_w2'
    option interface 'wan5'
    option metric '6'
    option weight '2'

config member 'wan6_m1_w1'
    option interface 'wan6'
    option metric '1'
    option weight '1'

config member 'wan6_m2_w1'
    option interface 'wan6'
    option metric '2'
    option weight '1'

config member 'wan6_m3_w1'
    option interface 'wan6'
    option metric '3'
    option weight '1'

config member 'wan6_m4_w1'
    option interface 'wan6'
    option metric '4'
    option weight '1'

config member 'wan6_m5_w1'
    option interface 'wan6'
    option metric '5'
    option weight '1'

config member 'wan6_m6_w1'
    option interface 'wan6'
    option metric '6'
    option weight '1'

config policy 'wan_only'
    list use_member 'wan_m1_w6'

config policy 'wan2_only'
    list use_member 'wan2_m1_w5'

config policy 'wan3_only'
    list use_member 'wan3_m1_w4'

config policy 'wan4_only'
    list use_member 'wan4_m1_w3'

config policy 'wan5_only'
    list use_member 'wan5_m1_w2'

config policy 'wan6_only'
    list use_member 'wan6_m1_w1'

config policy 'balanced'
    list use_member 'wan_m1_w6'
    list use_member 'wan2_m1_w5'
    list use_member 'wan3_m1_w4'

config policy 'wn_wn2_wn3'
    list use_member 'wan_m1_w6'
    list use_member 'wan2_m2_w5'
    list use_member 'wan3_m3_w4'

config policy 'wn3_wn2_wn'
    list use_member 'wan3_m1_w4'
    list use_member 'wan2_m2_w5'
    list use_member 'wan_m3_w6'

config policy 'wn_wn2'
    list use_member 'wan_m1_w6'
    list use_member 'wan2_m2_w5'

config policy 'wn_wn3'
    list use_member 'wan_m1_w6'
    list use_member 'wan3_m2_w4'

config policy 'wn_wn4'
    list use_member 'wan_m1_w6'
    list use_member 'wan4_m2_w3'

config policy 'wn_wn5'
    list use_member 'wan_m1_w6'
    list use_member 'wan5_m2_w2'

config policy 'wn_wn6'
        list use_member 'wan_m1_w6'
        list use_member 'wan6_m2_w1'

config policy 'wn2_wn'
    list use_member 'wan2_m1_w5'
    list use_member 'wan_m2_w6'

config policy 'wn3_wn'
    list use_member 'wan3_m1_w4'
    list use_member 'wan_m2_w6'

config policy 'wn4_wn'
    list use_member 'wan4_m1_w3'
    list use_member 'wan_m2_w6'

config policy 'wn4_wn2'
    list use_member 'wan4_m1_w3'
    list use_member 'wan2_m2_w5'

config policy 'wn4_wn3'
    list use_member 'wan4_m1_w3'
    list use_member 'wan3_m2_w4'

config policy 'wn5_wn'
    list use_member 'wan5_m1_w2'
    list use_member 'wan_m2_w6'

config policy 'wn5_wn2'
    list use_member 'wan5_m1_w2'
    list use_member 'wan2_m2_w5'

config policy 'wn5_wn3'
    list use_member 'wan5_m1_w2'
    list use_member 'wan3_m2_w4'

config policy 'wn6_wn'
        list use_member 'wan6_m1_w1'
        list use_member 'wan_m2_w6'

config policy 'wn6_wn2'
        list use_member 'wan6_m1_w1'
        list use_member 'wan2_m2_w5'

config policy 'wn6_wn3'
        list use_member 'wan6_m1_w1'
        list use_member 'wan3_m2_w4'

config policy 'wn4_wn_wn2_wn3'
    list use_member 'wan4_m1_w3'
    list use_member 'wan_m2_w6'
    list use_member 'wan2_m3_w5'
    list use_member 'wan3_m4_w4'

config policy 'wn5_wn_wn2_wn3'
    list use_member 'wan5_m1_w2'
    list use_member 'wan_m2_w6'
    list use_member 'wan2_m3_w5'
    list use_member 'wan3_m4_w4'

config policy 'wn6_wn_wn2_wn3'
        list use_member 'wan6_m1_w1'
        list use_member 'wan_m2_w6'
        list use_member 'wan2_m3_w5'
        list use_member 'wan3_m4_w4'

config rule 'Vodafone'
    option dest_ip '192.168.4.1'
    option proto 'all'
    option use_policy 'wan2_only'

config rule 'DNS_WAN1'
    option proto 'all'
    option use_policy 'wan_only'
    option dest_ip 'checkip.dyndns.com'

config rule 'DNS_WAN2'
    option proto 'all'
    option use_policy 'wan2_only'
    option dest_ip 'ipv4.ident.me'

config rule 'DNS_WAN3'
    option proto 'all'
    option use_policy 'wan3_only'
    option dest_ip 'ipv4.icanhazip.com'

config rule 'SKY_Francesco'
    option src_ip '192.168.2.24'
    option proto 'all'
    option use_policy 'wan_only'

config rule 'SKY_Soggiorno'
    option src_ip '192.168.2.25'
    option proto 'all'
    option use_policy 'wan_only'

config rule 'TV_Francesco'
    option src_ip '192.168.2.22'
    option proto 'all'
    option use_policy 'wan4_only'

config rule 'TV_Emanuele'
    option src_ip '192.168.2.23'
    option proto 'all'
    option use_policy 'wan4_only'

config rule 'NAS'
    option src_ip '192.168.2.44'
    option proto 'all'
    option use_policy 'wan4_only'

config rule 'NAS_2'
    option dest_ip '192.168.2.44'
    option proto 'all'
    option use_policy 'wan4_only'

config rule 'Vodafone_3G'
    option dest_ip 'contatori.vodafone.it'
    option proto 'all'
    option use_policy 'wan3_only'

config rule 'Francesco'
    option src_ip '192.168.2.2'
    option proto 'all'
    option use_policy 'wn_wn2_wn3'

config rule 'Francesco_2'
    option src_ip '192.168.2.4'
    option proto 'all'
    option use_policy 'wn_wn2_wn3'

config rule 'default_rule'
    option dest_ip '0.0.0.0/0'
    option proto 'all'
    option use_policy 'wn4_wn_wn2_wn3'

Output of "cat /etc/config/network" : 

config interface 'loopback'
    option ifname 'lo'
    option proto 'static'
    option ipaddr '127.0.0.1'
    option netmask '255.0.0.0'

config globals 'globals'
    option ula_prefix 'fdfd:ad9b:27bf::/48'

config switch
    option name 'switch0'
    option reset '1'
    option enable_vlan '1'

config switch_vlan
    option device 'switch0'
    option vlan '1'
    option vid '1'
    option ports '2 3 4 6t'

config switch_vlan
    option device 'switch0'
    option vlan '2'
    option ports '0 6t'
    option vid '2'

config switch_vlan
    option device 'switch0'
    option vlan '3'
    option vid '3'
    option ports '1 6t'

config interface 'lan'
    option type 'bridge'
    option ifname 'eth0.1'
    option proto 'static'
    option netmask '255.255.255.0'
    option delegate '0'
    option ipaddr '192.168.2.1'
    option dns '8.8.8.8 8.8.4.4'

config device 'lan_dev'
    option name 'eth0.1'
    option macaddr 'e4:6f:13:2e:a5:10'

config interface 'wan'
    option ifname 'eth0.2'
    option proto 'dhcp'
    option delegate '0'
    option peerdns '0'
    option dns '8.8.8.8 8.8.4.4'
    option metric '10'

config device 'wan_dev'
    option name 'eth0.2'
    option macaddr 'e4:6f:13:2e:a5:13'

config interface 'wan2'
    option proto 'static'
    option ifname 'eth0.3'
    option delegate '0'
    option ipaddr '192.168.5.2'
    option netmask '255.255.255.0'
    option gateway '192.168.5.1'
    option dns '8.8.8.8 8.8.4.4'
    option metric '20'

config interface 'wan3'
    option proto '3g'
    option delegate '0'
    option device '/dev/ttyUSB0'
    option service 'umts_only'
    option app 'APN'
    option pincode '5204'
    option dialnumber '*99#'
    option ipv6 '0'
    option metric '30'
    option peerdns '0'
    option dns '8.8.8.8 8.8.4.4'

config interface 'wan4'
    option proto 'l2tp'
    option ifname 'eth0'
    option delegate '0'
    option server 'SERVER_IP'
    USERNAME HIDDEN
    PASSWORD HIDDEN
    option metric '40'
    option peerdns '0'
    option dns '8.8.8.8 8.8.4.4'
    option ipv6 '0'

config interface 'vpn'
    option proto 'none'
    option ifname 'tun0'
    option auto '1'
    option delegate '0'

config interface 'guest'
    option type 'bridge'
    option proto 'static'
    option delegate '0'
    option ipaddr '10.0.0.1'
    option netmask '255.255.255.0'
    option dns '8.8.8.8 8.8.4.4'

Output of "cat /etc/config/wireless" : 

config wifi-device 'radio0'
    option type 'mac80211'
    option hwmode '11a'
    option path 'pci0000:00/0000:00:00.0/0000:01:00.0'
    option htmode 'VHT80'
    option country '00'
    option txpower '20'
    option channel '40'

config wifi-iface 'default_radio0'
    option device 'radio0'
    option network 'lan'
    option mode 'ap'
    option encryption 'psk2'
    KEY HIDDEN
    option ssid 'PARADISE 5GHz'

config wifi-device 'radio1'
    option type 'mac80211'
    option hwmode '11g'
    option path 'pci0000:00/0000:00:01.0/0000:02:00.0'
    option htmode 'HT20'
    option channel '5'
    option txpower '20'
    option country '00'

config wifi-iface 'default_radio1'
    option device 'radio1'
    option network 'lan'
    option mode 'ap'
    option ssid 'PARADISE'
    option encryption 'psk2'
    KEY HIDDEN

config wifi-iface
    option device 'radio0'
    option mode 'ap'
    option ssid 'HEAVEN 5GHz'
    option encryption 'psk2'
    KEY HIDDEN
    option network 'guest'

config wifi-iface
    option device 'radio1'
    option mode 'ap'
    option ssid 'HEAVEN'
    option encryption 'psk2'
    KEY HIDDEN
    option network 'guest'

Output of "ifconfig" : 

3g-wan3   Link encap:Point-to-Point Protocol  
          inet addr:5.92.1.146  P-t-P:10.64.64.64  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:1305 errors:2060 dropped:0 overruns:0 frame:0
          TX packets:1319 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3 
          RX bytes:109737 (107.1 KiB)  TX bytes:109521 (106.9 KiB)

br-guest  Link encap:Ethernet  HWaddr E6:6F:13:2E:A5:10  
          inet addr:10.0.0.1  Bcast:10.0.0.255  Mask:255.255.255.0
          inet6 addr: fe80::e46f:13ff:fe2e:a510/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:1080 (1.0 KiB)

br-lan    Link encap:Ethernet  HWaddr E4:6F:13:2E:A5:10  
          inet addr:192.168.2.1  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::e66f:13ff:fe2e:a510/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:844640 errors:0 dropped:0 overruns:0 frame:0
          TX packets:633598 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:853271271 (813.7 MiB)  TX bytes:458891085 (437.6 MiB)

eth0      Link encap:Ethernet  HWaddr BA:BB:F0:29:F9:D3  
          inet6 addr: fe80::b8bb:f0ff:fe29:f9d3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1485563 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1473084 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1330817566 (1.2 GiB)  TX bytes:1334221310 (1.2 GiB)
          Interrupt:10 

eth0.1    Link encap:Ethernet  HWaddr E4:6F:13:2E:A5:10  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:844677 errors:0 dropped:0 overruns:0 frame:0
          TX packets:633599 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:853290865 (813.7 MiB)  TX bytes:458891105 (437.6 MiB)

eth0.2    Link encap:Ethernet  HWaddr E4:6F:13:2E:A5:13  
          inet addr:192.168.3.1  Bcast:192.168.3.255  Mask:255.255.255.0
          inet6 addr: fe80::e66f:13ff:fe2e:a513/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:23565 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19985 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:21854352 (20.8 MiB)  TX bytes:5926022 (5.6 MiB)

eth0.3    Link encap:Ethernet  HWaddr BA:BB:F0:29:F9:D3  
          inet addr:192.168.5.2  Bcast:192.168.5.255  Mask:255.255.255.0
          inet6 addr: fe80::b8bb:f0ff:fe29:f9d3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:617000 errors:0 dropped:0 overruns:0 frame:0
          TX packets:818781 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:428914826 (409.0 MiB)  TX bytes:857536986 (817.8 MiB)

ifb0      Link encap:Ethernet  HWaddr B2:58:B3:36:89:04  
          inet6 addr: fe80::b058:b3ff:fe36:8904/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:23561 errors:0 dropped:0 overruns:0 frame:0
          TX packets:23561 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:32 
          RX bytes:22182430 (21.1 MiB)  TX bytes:22182430 (21.1 MiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:511 errors:0 dropped:0 overruns:0 frame:0
          TX packets:511 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:42069 (41.0 KiB)  TX bytes:42069 (41.0 KiB)

tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          inet addr:192.168.100.1  P-t-P:192.168.100.1  Mask:255.255.255.0
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan0     Link encap:Ethernet  HWaddr E4:6F:13:2E:A5:12  
          inet6 addr: fe80::e66f:13ff:fe2e:a512/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7652 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:1959250 (1.8 MiB)

wlan0-1   Link encap:Ethernet  HWaddr E6:6F:13:2E:A5:12  
          inet6 addr: fe80::e46f:13ff:fe2e:a512/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:1824 (1.7 KiB)

wlan1     Link encap:Ethernet  HWaddr E4:6F:13:2E:A5:10  
          inet6 addr: fe80::e66f:13ff:fe2e:a510/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7670 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:474 (474.0 B)  TX bytes:1961505 (1.8 MiB)

wlan1-1   Link encap:Ethernet  HWaddr E6:6F:13:2E:A5:10  
          inet6 addr: fe80::e46f:13ff:fe2e:a510/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:1736 (1.6 KiB)

Output of "route -n" : 

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.3.254   0.0.0.0         UG    10     0        0 eth0.2
0.0.0.0         192.168.5.1     0.0.0.0         UG    20     0        0 eth0.3
0.0.0.0         10.64.64.64     0.0.0.0         UG    30     0        0 3g-wan3
10.0.0.0        0.0.0.0         255.255.255.0   U     0      0        0 br-guest
10.64.64.64     0.0.0.0         255.255.255.255 UH    0      0        0 3g-wan3
94.242.246.38   192.168.3.254   255.255.255.255 UGH   10     0        0 eth0.2
94.242.246.45   192.168.3.254   255.255.255.255 UGH   10     0        0 eth0.2
94.242.246.46   192.168.3.254   255.255.255.255 UGH   10     0        0 eth0.2
94.242.246.47   192.168.3.254   255.255.255.255 UGH   10     0        0 eth0.2
192.168.2.0     0.0.0.0         255.255.255.0   U     0      0        0 br-lan
192.168.3.0     0.0.0.0         255.255.255.0   U     10     0        0 eth0.2
192.168.3.254   0.0.0.0         255.255.255.255 UH    10     0        0 eth0.2
192.168.5.0     0.0.0.0         255.255.255.0   U     20     0        0 eth0.3
192.168.15.0    192.168.100.2   255.255.255.0   UG    0      0        0 tun0
192.168.100.0   0.0.0.0         255.255.255.0   U     0      0        0 tun0

Output of "ip rule show" : 

0:    from all lookup local 
1001:    from all iif eth0.2 lookup main 
1002:    from all iif eth0.3 lookup main 
1003:    from all iif 3g-wan3 lookup main 
2001:    from all fwmark 0x100/0xff00 lookup 1 
2002:    from all fwmark 0x200/0xff00 lookup 2 
2003:    from all fwmark 0x300/0xff00 lookup 3 
2253:    from all fwmark 0xfd00/0xff00 blackhole
2254:    from all fwmark 0xfe00/0xff00 unreachable
32766:    from all lookup main 
32767:    from all lookup default

Output of "ip route list table 1-250" : 

1
default via 192.168.3.254 dev eth0.2 
2
default via 192.168.5.1 dev eth0.3 
3
default via 10.64.64.64 dev 3g-wan3

Firewall default output policy (must be ACCEPT) : 

ACCEPT

Output of "iptables -L -t mangle -v -n" : 

Chain PREROUTING (policy ACCEPT 1468K packets, 1294M bytes)
 pkts bytes target     prot opt in     out     source               destination         
1480K 1304M mwan3_hook  all  --  *      *       0.0.0.0/0            0.0.0.0/0           

Chain INPUT (policy ACCEPT 11208 packets, 1063K bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain FORWARD (policy ACCEPT 1449K packets, 1290M bytes)
 pkts bytes target     prot opt in     out     source               destination         
15317 5211K qos_Default  all  --  *      eth0.2  0.0.0.0/0            0.0.0.0/0           
  390 22828 TCPMSS     tcp  --  *      eth0.2  0.0.0.0/0            0.0.0.0/0            tcp flags:0x06/0x02 /* !fw3: wan (mtu_fix) */ TCPMSS clamp to PMTU
   35  2112 TCPMSS     tcp  --  *      eth0.3  0.0.0.0/0            0.0.0.0/0            tcp flags:0x06/0x02 /* !fw3: wan (mtu_fix) */ TCPMSS clamp to PMTU
    0     0 TCPMSS     tcp  --  *      3g-wan3  0.0.0.0/0            0.0.0.0/0            tcp flags:0x06/0x02 /* !fw3: wan (mtu_fix) */ TCPMSS clamp to PMTU
    0     0 TCPMSS     tcp  --  *      br-guest  0.0.0.0/0            0.0.0.0/0            tcp flags:0x06/0x02 /* !fw3: guest (mtu_fix) */ TCPMSS clamp to PMTU

Chain OUTPUT (policy ACCEPT 10844 packets, 2057K bytes)
 pkts bytes target     prot opt in     out     source               destination         
 4663  441K qos_Default  all  --  *      eth0.2  0.0.0.0/0            0.0.0.0/0           
11898 2168K mwan3_hook  all  --  *      *       0.0.0.0/0            0.0.0.0/0           

Chain POSTROUTING (policy ACCEPT 1460K packets, 1292M bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain mwan3_connected (2 references)
 pkts bytes target     prot opt in     out     source               destination         
31489   24M MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            match-set mwan3_connected dst MARK or 0xff00

Chain mwan3_hook (2 references)
 pkts bytes target     prot opt in     out     source               destination         
1492K 1306M CONNMARK   all  --  *      *       0.0.0.0/0            0.0.0.0/0            CONNMARK restore mask 0xff00
15096 3601K mwan3_ifaces_in  all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00
11489 2132K mwan3_connected  all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00
 6797  530K mwan3_ifaces_out  all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00
 1538  101K mwan3_rules  all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00
1492K 1306M CONNMARK   all  --  *      *       0.0.0.0/0            0.0.0.0/0            CONNMARK save mask 0xff00
50885   28M mwan3_connected  all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match ! 0xff00/0xff00

Chain mwan3_iface_in_wan (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    1    36 MARK       all  --  eth0.2 *       0.0.0.0/0            0.0.0.0/0            match-set mwan3_connected src mark match 0x0/0xff00 /* default */ MARK or 0xff00
  138 53629 MARK       all  --  eth0.2 *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan */ MARK xset 0x100/0xff00

Chain mwan3_iface_in_wan2 (1 references)
 pkts bytes target     prot opt in     out     source               destination         
 3429 1411K MARK       all  --  eth0.3 *       0.0.0.0/0            0.0.0.0/0            match-set mwan3_connected src mark match 0x0/0xff00 /* default */ MARK or 0xff00
   39  3065 MARK       all  --  eth0.3 *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan2 */ MARK xset 0x200/0xff00

Chain mwan3_iface_in_wan3 (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MARK       all  --  3g-wan3 *       0.0.0.0/0            0.0.0.0/0            match-set mwan3_connected src mark match 0x0/0xff00 /* default */ MARK or 0xff00
    0     0 MARK       all  --  3g-wan3 *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan3 */ MARK xset 0x300/0xff00

Chain mwan3_iface_out_wan (1 references)
 pkts bytes target     prot opt in     out     source               destination         
 2494  197K MARK       all  --  *      *       192.168.3.1          0.0.0.0/0            mark match 0x0/0xff00 /* wan */ MARK xset 0x100/0xff00

Chain mwan3_iface_out_wan2 (1 references)
 pkts bytes target     prot opt in     out     source               destination         
 1478  124K MARK       all  --  *      *       192.168.5.2          0.0.0.0/0            mark match 0x0/0xff00 /* wan2 */ MARK xset 0x200/0xff00

Chain mwan3_iface_out_wan3 (1 references)
 pkts bytes target     prot opt in     out     source               destination         
 1274  107K MARK       all  --  *      *       5.92.1.146           0.0.0.0/0            mark match 0x0/0xff00 /* wan3 */ MARK xset 0x300/0xff00

Chain mwan3_ifaces_in (1 references)
 pkts bytes target     prot opt in     out     source               destination         
14970 3580K mwan3_iface_in_wan  all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00
14695 3509K mwan3_iface_in_wan3  all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00
13990 3369K mwan3_iface_in_wan2  all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00

Chain mwan3_ifaces_out (1 references)
 pkts bytes target     prot opt in     out     source               destination         
 6741  524K mwan3_iface_out_wan  all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00
 4232  326K mwan3_iface_out_wan3  all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00
 2830  206K mwan3_iface_out_wan2  all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00

Chain mwan3_policy_balanced (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 statistic mode random probability 0.26599999983 /* wan3 4 15 */ MARK xset 0x300/0xff00
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 statistic mode random probability 0.45399999991 /* wan2 5 11 */ MARK xset 0x200/0xff00
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan 6 6 */ MARK xset 0x100/0xff00

Chain mwan3_policy_wan2_only (2 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan2 5 5 */ MARK xset 0x200/0xff00

Chain mwan3_policy_wan3_only (5 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan3 4 4 */ MARK xset 0x300/0xff00

Chain mwan3_policy_wan4_only (4 references)
 pkts bytes target     prot opt in     out     source               destination         
  664 39840 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* unreachable */ MARK xset 0xfe00/0xff00

Chain mwan3_policy_wan5_only (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* unreachable */ MARK xset 0xfe00/0xff00

Chain mwan3_policy_wan6_only (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* unreachable */ MARK xset 0xfe00/0xff00

Chain mwan3_policy_wan_only (5 references)
 pkts bytes target     prot opt in     out     source               destination         
   15   900 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan 6 6 */ MARK xset 0x100/0xff00

Chain mwan3_policy_wn2_wn (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan2 5 5 */ MARK xset 0x200/0xff00

Chain mwan3_policy_wn3_wn (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan3 4 4 */ MARK xset 0x300/0xff00

Chain mwan3_policy_wn3_wn2_wn (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan3 4 4 */ MARK xset 0x300/0xff00

Chain mwan3_policy_wn4_wn (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan 6 6 */ MARK xset 0x100/0xff00

Chain mwan3_policy_wn4_wn2 (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan2 5 5 */ MARK xset 0x200/0xff00

Chain mwan3_policy_wn4_wn3 (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan3 4 4 */ MARK xset 0x300/0xff00

Chain mwan3_policy_wn4_wn_wn2_wn3 (1 references)
 pkts bytes target     prot opt in     out     source               destination         
  300 17211 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan 6 6 */ MARK xset 0x100/0xff00

Chain mwan3_policy_wn5_wn (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan 6 6 */ MARK xset 0x100/0xff00

Chain mwan3_policy_wn5_wn2 (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan2 5 5 */ MARK xset 0x200/0xff00

Chain mwan3_policy_wn5_wn3 (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan3 4 4 */ MARK xset 0x300/0xff00

Chain mwan3_policy_wn5_wn_wn2_wn3 (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan 6 6 */ MARK xset 0x100/0xff00

Chain mwan3_policy_wn6_wn (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan 6 6 */ MARK xset 0x100/0xff00

Chain mwan3_policy_wn6_wn2 (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan2 5 5 */ MARK xset 0x200/0xff00

Chain mwan3_policy_wn6_wn3 (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan3 4 4 */ MARK xset 0x300/0xff00

Chain mwan3_policy_wn6_wn_wn2_wn3 (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan 6 6 */ MARK xset 0x100/0xff00

Chain mwan3_policy_wn_wn2 (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan 6 6 */ MARK xset 0x100/0xff00

Chain mwan3_policy_wn_wn2_wn3 (2 references)
 pkts bytes target     prot opt in     out     source               destination         
  368 24172 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan 6 6 */ MARK xset 0x100/0xff00

Chain mwan3_policy_wn_wn3 (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan 6 6 */ MARK xset 0x100/0xff00

Chain mwan3_policy_wn_wn4 (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan 6 6 */ MARK xset 0x100/0xff00

Chain mwan3_policy_wn_wn5 (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan 6 6 */ MARK xset 0x100/0xff00

Chain mwan3_policy_wn_wn6 (0 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* wan 6 6 */ MARK xset 0x100/0xff00

Chain mwan3_rules (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 mwan3_policy_wan2_only  all  --  *      *       0.0.0.0/0            192.168.4.1          mark match 0x0/0xff00 /* Vodafone */
    0     0 mwan3_policy_wan_only  all  --  *      *       0.0.0.0/0            216.146.38.70        mark match 0x0/0xff00 /* DNS_WAN1 */
    0     0 mwan3_policy_wan_only  all  --  *      *       0.0.0.0/0            91.198.22.70         mark match 0x0/0xff00 /* DNS_WAN1 */
    0     0 mwan3_policy_wan_only  all  --  *      *       0.0.0.0/0            216.146.43.70        mark match 0x0/0xff00 /* DNS_WAN1 */
    0     0 mwan3_policy_wan2_only  all  --  *      *       0.0.0.0/0            176.58.123.25        mark match 0x0/0xff00 /* DNS_WAN2 */
    0     0 mwan3_policy_wan3_only  all  --  *      *       0.0.0.0/0            64.182.208.182       mark match 0x0/0xff00 /* DNS_WAN3 */
    0     0 mwan3_policy_wan3_only  all  --  *      *       0.0.0.0/0            64.182.208.183       mark match 0x0/0xff00 /* DNS_WAN3 */
    0     0 mwan3_policy_wan3_only  all  --  *      *       0.0.0.0/0            64.182.208.181       mark match 0x0/0xff00 /* DNS_WAN3 */
    0     0 mwan3_policy_wan3_only  all  --  *      *       0.0.0.0/0            64.182.208.184       mark match 0x0/0xff00 /* DNS_WAN3 */
    7   420 mwan3_policy_wan_only  all  --  *      *       192.168.2.24         0.0.0.0/0            mark match 0x0/0xff00 /* SKY_Francesco */
    8   480 mwan3_policy_wan_only  all  --  *      *       192.168.2.25         0.0.0.0/0            mark match 0x0/0xff00 /* SKY_Soggiorno */
    0     0 mwan3_policy_wan4_only  all  --  *      *       192.168.2.22         0.0.0.0/0            mark match 0x0/0xff00 /* TV_Francesco */
  664 39840 mwan3_policy_wan4_only  all  --  *      *       192.168.2.23         0.0.0.0/0            mark match 0x0/0xff00 /* TV_Emanuele */
    0     0 mwan3_policy_wan4_only  all  --  *      *       192.168.2.44         0.0.0.0/0            mark match 0x0/0xff00 /* NAS */
    0     0 mwan3_policy_wan4_only  all  --  *      *       0.0.0.0/0            192.168.2.44         mark match 0x0/0xff00 /* NAS_2 */
    0     0 mwan3_policy_wan3_only  all  --  *      *       0.0.0.0/0            195.232.255.190      mark match 0x0/0xff00 /* Vodafone_3G */
  368 24172 mwan3_policy_wn_wn2_wn3  all  --  *      *       192.168.2.2          0.0.0.0/0            mark match 0x0/0xff00 /* Francesco */
    0     0 mwan3_policy_wn_wn2_wn3  all  --  *      *       192.168.2.4          0.0.0.0/0            mark match 0x0/0xff00 /* Francesco_2 */
  300 17211 mwan3_policy_wn4_wn_wn2_wn3  all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xff00 /* default_rule */

Chain qos_Default (2 references)
 pkts bytes target     prot opt in     out     source               destination         
19980 5651K CONNMARK   all  --  *      *       0.0.0.0/0            0.0.0.0/0            CONNMARK restore mask 0xf
 3386  259K qos_Default_ct  all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xf
 2855  313K MARK       icmp --  *      *       0.0.0.0/0            0.0.0.0/0            MARK xset 0x11/0xff
19980 5651K CONNMARK   all  --  *      *       0.0.0.0/0            0.0.0.0/0            CONNMARK save mask 0xff

Chain qos_Default_ct (1 references)
 pkts bytes target     prot opt in     out     source               destination         
   16  3451 MARK       all  --  *      *       192.168.2.40         0.0.0.0/0            mark match 0x0/0xf /* VoIP */ MARK xset 0x33/0xff
    0     0 MARK       all  --  *      *       0.0.0.0/0            192.168.2.40         mark match 0x0/0xf /* VoIP_2 */ MARK xset 0x33/0xff
 3370  255K MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x0/0xf /* TOTALE */ MARK xset 0x44/0xff
 3386  259K CONNMARK   all  --  *      *       0.0.0.0/0            0.0.0.0/0            CONNMARK save mask 0xff

tnx for your great work

(Last edited by Deus3X on 24 Feb 2017, 00:15)

Post #1602

junari

15 Mar 2017, 09:50

Hi all, I have some problem with balancing and reserving wire internet and 3g via mwan3.
When eth channel down, 3g down too after some time.
I go to mwan3track script:

ping -I $2 -c $4 -W $5 -s 8 -q $track_ip &> /dev/null

and increase -s the parameter from 4 bytes to 8 bytes, because my mobile operator not skip so small packetsize.
After that 3g don't falling, but the eth is up and down arbitrarily (when eth must be down).
I added debug messages:

for track_ip in $track_ips; do
    ping -I $2 -c $4 -W $5 -s 8 -q $track_ip &> /dev/null
    if [ $? -eq 0 ]; then
        let host_up_count++
        logger -t mwan3track -p notice "Up count $2: $host_up_c$
    else
        let lost++
        logger -t mwan3track -p notice "Lost $2: $lost"
    fi
done

Then noticed that sometimes the ping succesful on the down interface, if the second active.
My ping command provided by busybox, if it important.
I change ping to /bin/ping and after that I don't have the same problem.

/bin/ping -I $2 -c $4 -W $5 -s 8 -q $track_ip &> /dev/null

Perhaps this information will be useful for someone.
PS: Sorry for my English.

(Last edited by junari on 15 Mar 2017, 10:26)

Post #1603

wazaa

18 Mar 2017, 23:32

Hello and thank you very much for mwan3! I have a small problem, when an interface goes offline, I see the correct message in the log (via logread): "... mwan3track: Interface wan4g1 (wwan1) is offline" but when the interface comes back online, I don't see the message "... mwan3track: Interface wan4g1 (wwan1) is online" anymore. It happens with all interfaces. I used to see the "online" log entries but not anymore. Any idea of what happened? FYI, If I comment

if [ $score -gt $8 ]; then score=$(($7+$8)); fi
if [ $score -eq $8 ]; then

in /usr/sbin/mwan3track, I do see the online messages. So it must be a problem with the $score evaluation

Thanks for any help

(Last edited by wazaa on 19 Mar 2017, 00:56)

Post #1604

junari

19 Mar 2017, 09:06

wazaa, you can try added debug messages like me

Post #1605

wazaa

20 Mar 2017, 09:39

@januari, can you explain more?

Post #1606

junari

20 Mar 2017, 13:13

Replace in mwan3track

for track_ip in $track_ips; do
    ping -I $2 -c $4 -W $5 -s 4 -q $track_ip &> /dev/null
    if [ $? -eq 0 ]; then
        let host_up_count++
    else
        let lost++
    fi
done

for track_ip in $track_ips; do
    ping -I $2 -c $4 -W $5 -s 8 -q $track_ip &> /dev/null
    if [ $? -eq 0 ]; then
        let host_up_count++
        logger -t mwan3track -p notice "Up count $2: $host_up_count"
    else
        let lost++
        logger -t mwan3track -p notice "Lost $2: $lost"
    fi
done

And you can see what is happening with the interface

Post #1607

wazaa

20 Mar 2017, 16:48

@junari, thanks it's a great idea! So I replaced the code in /usr/sbin/mwan3track and I monitored the logs while I had the USB hub (where all 4x LTE dongles are attached) turned ON, then turned OFF (at 16:25:10), then turned ON again (at 16:25:55). Here is the result:

root@OpenWrt:/usr/sbin# logread -f -e mwan3track
Mon Mar 20 16:25:00 2017 user.notice mwan3track: Up count wwan2: 1
Mon Mar 20 16:25:00 2017 user.notice mwan3track: Up count wwan2: 2
Mon Mar 20 16:25:00 2017 user.notice mwan3track: Up count wwan2: 3
Mon Mar 20 16:25:00 2017 user.notice mwan3track: Up count wwan2: 4
Mon Mar 20 16:25:02 2017 user.notice mwan3track: Up count wwan3: 1
Mon Mar 20 16:25:02 2017 user.notice mwan3track: Up count wwan3: 2
Mon Mar 20 16:25:02 2017 user.notice mwan3track: Up count wwan3: 3
Mon Mar 20 16:25:02 2017 user.notice mwan3track: Up count wwan3: 4
Mon Mar 20 16:25:03 2017 user.notice mwan3track: Up count wwan0: 1
Mon Mar 20 16:25:03 2017 user.notice mwan3track: Up count wwan0: 2
Mon Mar 20 16:25:03 2017 user.notice mwan3track: Up count wwan0: 3
Mon Mar 20 16:25:03 2017 user.notice mwan3track: Up count wwan0: 4
Mon Mar 20 16:25:03 2017 user.notice mwan3track: Up count wwan1: 1
Mon Mar 20 16:25:03 2017 user.notice mwan3track: Up count wwan1: 2
Mon Mar 20 16:25:03 2017 user.notice mwan3track: Up count wwan1: 3
Mon Mar 20 16:25:03 2017 user.notice mwan3track: Up count wwan1: 4
Mon Mar 20 16:25:04 2017 user.notice mwan3track: Up count eth0.2: 1
Mon Mar 20 16:25:04 2017 user.notice mwan3track: Up count eth0.2: 2
Mon Mar 20 16:25:04 2017 user.notice mwan3track: Up count eth0.2: 3
Mon Mar 20 16:25:04 2017 user.notice mwan3track: Up count eth0.2: 4
Mon Mar 20 16:25:05 2017 user.notice mwan3track: Up count wwan2: 1
Mon Mar 20 16:25:05 2017 user.notice mwan3track: Up count wwan2: 2
Mon Mar 20 16:25:05 2017 user.notice mwan3track: Up count wwan2: 3
Mon Mar 20 16:25:05 2017 user.notice mwan3track: Up count wwan2: 4
Mon Mar 20 16:25:07 2017 user.notice mwan3track: Up count wwan3: 1
Mon Mar 20 16:25:07 2017 user.notice mwan3track: Up count wwan3: 2
Mon Mar 20 16:25:07 2017 user.notice mwan3track: Up count wwan3: 3
Mon Mar 20 16:25:07 2017 user.notice mwan3track: Up count wwan3: 4
Mon Mar 20 16:25:08 2017 user.notice mwan3track: Up count wwan0: 1
Mon Mar 20 16:25:08 2017 user.notice mwan3track: Up count wwan0: 2
Mon Mar 20 16:25:08 2017 user.notice mwan3track: Up count wwan0: 3
Mon Mar 20 16:25:08 2017 user.notice mwan3track: Up count wwan0: 4
Mon Mar 20 16:25:08 2017 user.notice mwan3track: Up count wwan1: 1
Mon Mar 20 16:25:08 2017 user.notice mwan3track: Up count wwan1: 2
Mon Mar 20 16:25:08 2017 user.notice mwan3track: Up count wwan1: 3
Mon Mar 20 16:25:08 2017 user.notice mwan3track: Up count wwan1: 4
Mon Mar 20 16:25:09 2017 user.notice mwan3track: Up count eth0.2: 1
Mon Mar 20 16:25:09 2017 user.notice mwan3track: Up count eth0.2: 2
Mon Mar 20 16:25:09 2017 user.notice mwan3track: Up count eth0.2: 3
Mon Mar 20 16:25:09 2017 user.notice mwan3track: Up count eth0.2: 4
Mon Mar 20 16:25:10 2017 user.notice mwan3track: Lost wwan2: 1
Mon Mar 20 16:25:10 2017 user.notice mwan3track: Lost wwan2: 2
Mon Mar 20 16:25:11 2017 user.notice mwan3track: Lost wwan2: 3
Mon Mar 20 16:25:11 2017 user.notice mwan3track: Lost wwan2: 4
Mon Mar 20 16:25:12 2017 user.notice mwan3track: Lost wwan3: 1
Mon Mar 20 16:25:12 2017 user.notice mwan3track: Lost wwan3: 2
Mon Mar 20 16:25:12 2017 user.notice mwan3track: Lost wwan3: 3
Mon Mar 20 16:25:12 2017 user.notice mwan3track: Lost wwan3: 4
Mon Mar 20 16:25:13 2017 user.notice mwan3track: Lost wwan0: 1
Mon Mar 20 16:25:13 2017 user.notice mwan3track: Lost wwan0: 2
Mon Mar 20 16:25:13 2017 user.notice mwan3track: Lost wwan0: 3
Mon Mar 20 16:25:13 2017 user.notice mwan3track: Lost wwan0: 4
Mon Mar 20 16:25:13 2017 user.notice mwan3track: Lost wwan1: 1
Mon Mar 20 16:25:13 2017 user.notice mwan3track: Lost wwan1: 2
Mon Mar 20 16:25:13 2017 user.notice mwan3track: Lost wwan1: 3
Mon Mar 20 16:25:13 2017 user.notice mwan3track: Lost wwan1: 4
Mon Mar 20 16:25:14 2017 user.notice mwan3track: Up count eth0.2: 1
Mon Mar 20 16:25:14 2017 user.notice mwan3track: Up count eth0.2: 2
Mon Mar 20 16:25:15 2017 user.notice mwan3track: Up count eth0.2: 3
Mon Mar 20 16:25:15 2017 user.notice mwan3track: Up count eth0.2: 4
Mon Mar 20 16:25:16 2017 user.notice mwan3track: Lost wwan2: 5
Mon Mar 20 16:25:16 2017 user.notice mwan3track: Lost wwan2: 6
Mon Mar 20 16:25:16 2017 user.notice mwan3track: Lost wwan2: 7
Mon Mar 20 16:25:16 2017 user.notice mwan3track: Lost wwan2: 8
Mon Mar 20 16:25:17 2017 user.notice mwan3track: Lost wwan3: 5
Mon Mar 20 16:25:17 2017 user.notice mwan3track: Lost wwan3: 6
Mon Mar 20 16:25:17 2017 user.notice mwan3track: Lost wwan3: 7
Mon Mar 20 16:25:17 2017 user.notice mwan3track: Lost wwan3: 8
Mon Mar 20 16:25:18 2017 user.notice mwan3track: Lost wwan0: 5
Mon Mar 20 16:25:18 2017 user.notice mwan3track: Lost wwan0: 6
Mon Mar 20 16:25:18 2017 user.notice mwan3track: Lost wwan0: 7
Mon Mar 20 16:25:18 2017 user.notice mwan3track: Lost wwan0: 8
Mon Mar 20 16:25:19 2017 user.notice mwan3track: Lost wwan1: 5
Mon Mar 20 16:25:19 2017 user.notice mwan3track: Lost wwan1: 6
Mon Mar 20 16:25:19 2017 user.notice mwan3track: Lost wwan1: 7
Mon Mar 20 16:25:19 2017 user.notice mwan3track: Lost wwan1: 8
Mon Mar 20 16:25:20 2017 user.notice mwan3track: Up count eth0.2: 1
Mon Mar 20 16:25:20 2017 user.notice mwan3track: Up count eth0.2: 2
Mon Mar 20 16:25:20 2017 user.notice mwan3track: Up count eth0.2: 3
Mon Mar 20 16:25:20 2017 user.notice mwan3track: Up count eth0.2: 4
Mon Mar 20 16:25:21 2017 user.notice mwan3track: Lost wwan2: 9
Mon Mar 20 16:25:21 2017 user.notice mwan3track: Lost wwan2: 10
Mon Mar 20 16:25:21 2017 user.notice mwan3track: Lost wwan2: 11
Mon Mar 20 16:25:21 2017 user.notice mwan3track: Lost wwan2: 12
Mon Mar 20 16:25:21 2017 user.notice mwan3track: Interface wan4g2 (wwan2) is offline
Mon Mar 20 16:25:23 2017 user.notice mwan3track: Lost wwan3: 9
Mon Mar 20 16:25:23 2017 user.notice mwan3track: Lost wwan3: 10
Mon Mar 20 16:25:23 2017 user.notice mwan3track: Lost wwan3: 11
Mon Mar 20 16:25:23 2017 user.notice mwan3track: Lost wwan3: 12
Mon Mar 20 16:25:23 2017 user.notice mwan3track: Interface wan4g3 (wwan3) is offline
Mon Mar 20 16:25:23 2017 user.notice mwan3track: Lost wwan0: 9
Mon Mar 20 16:25:24 2017 user.notice mwan3track: Lost wwan0: 10
Mon Mar 20 16:25:24 2017 user.notice mwan3track: Lost wwan0: 11
Mon Mar 20 16:25:24 2017 user.notice mwan3track: Lost wwan0: 12
Mon Mar 20 16:25:24 2017 user.notice mwan3track: Interface wan4g0 (wwan0) is offline
Mon Mar 20 16:25:24 2017 user.notice mwan3track: Lost wwan1: 9
Mon Mar 20 16:25:24 2017 user.notice mwan3track: Lost wwan1: 10
Mon Mar 20 16:25:24 2017 user.notice mwan3track: Lost wwan1: 11
Mon Mar 20 16:25:24 2017 user.notice mwan3track: Lost wwan1: 12
Mon Mar 20 16:25:24 2017 user.notice mwan3track: Interface wan4g1 (wwan1) is offline
Mon Mar 20 16:25:25 2017 user.notice mwan3track: Up count eth0.2: 1
Mon Mar 20 16:25:25 2017 user.notice mwan3track: Up count eth0.2: 2
Mon Mar 20 16:25:25 2017 user.notice mwan3track: Up count eth0.2: 3
Mon Mar 20 16:25:25 2017 user.notice mwan3track: Up count eth0.2: 4
Mon Mar 20 16:25:30 2017 user.notice mwan3track: Up count eth0.2: 1
Mon Mar 20 16:25:30 2017 user.notice mwan3track: Up count eth0.2: 2
Mon Mar 20 16:25:31 2017 user.notice mwan3track: Up count eth0.2: 3
Mon Mar 20 16:25:31 2017 user.notice mwan3track: Up count eth0.2: 4
Mon Mar 20 16:25:36 2017 user.notice mwan3track: Up count eth0.2: 1
Mon Mar 20 16:25:36 2017 user.notice mwan3track: Up count eth0.2: 2
Mon Mar 20 16:25:36 2017 user.notice mwan3track: Up count eth0.2: 3
Mon Mar 20 16:25:36 2017 user.notice mwan3track: Up count eth0.2: 4
Mon Mar 20 16:25:38 2017 user.notice mwan3track: Lost wwan2: 13
Mon Mar 20 16:25:38 2017 user.notice mwan3track: Lost wwan2: 14
Mon Mar 20 16:25:38 2017 user.notice mwan3track: Lost wwan2: 15
Mon Mar 20 16:25:38 2017 user.notice mwan3track: Lost wwan2: 16
Mon Mar 20 16:25:41 2017 user.notice mwan3track: Up count eth0.2: 1
Mon Mar 20 16:25:41 2017 user.notice mwan3track: Up count eth0.2: 2
Mon Mar 20 16:25:41 2017 user.notice mwan3track: Up count eth0.2: 3
Mon Mar 20 16:25:41 2017 user.notice mwan3track: Up count eth0.2: 4
Mon Mar 20 16:25:43 2017 user.notice mwan3track: Lost wwan2: 17
Mon Mar 20 16:25:43 2017 user.notice mwan3track: Lost wwan2: 18
Mon Mar 20 16:25:43 2017 user.notice mwan3track: Lost wwan2: 19
Mon Mar 20 16:25:43 2017 user.notice mwan3track: Lost wwan2: 20
Mon Mar 20 16:25:46 2017 user.notice mwan3track: Lost wwan3: 13
Mon Mar 20 16:25:46 2017 user.notice mwan3track: Lost wwan3: 14
Mon Mar 20 16:25:46 2017 user.notice mwan3track: Lost wwan3: 15
Mon Mar 20 16:25:46 2017 user.notice mwan3track: Lost wwan3: 16
Mon Mar 20 16:25:46 2017 user.notice mwan3track: Up count eth0.2: 1
Mon Mar 20 16:25:46 2017 user.notice mwan3track: Up count eth0.2: 2
Mon Mar 20 16:25:46 2017 user.notice mwan3track: Up count eth0.2: 3
Mon Mar 20 16:25:47 2017 user.notice mwan3track: Up count eth0.2: 4
Mon Mar 20 16:25:52 2017 user.notice mwan3track: Up count eth0.2: 1
Mon Mar 20 16:25:52 2017 user.notice mwan3track: Up count eth0.2: 2
Mon Mar 20 16:25:52 2017 user.notice mwan3track: Up count eth0.2: 3
Mon Mar 20 16:25:52 2017 user.notice mwan3track: Up count eth0.2: 4
Mon Mar 20 16:25:52 2017 user.notice mwan3track: Lost wwan2: 21
Mon Mar 20 16:25:53 2017 user.notice mwan3track: Lost wwan0: 13
Mon Mar 20 16:25:55 2017 user.notice mwan3track: Lost wwan3: 17
Mon Mar 20 16:25:55 2017 user.notice mwan3track: Up count wwan3: 1
Mon Mar 20 16:25:55 2017 user.notice mwan3track: Up count wwan3: 2
Mon Mar 20 16:25:55 2017 user.notice mwan3track: Up count wwan3: 3
Mon Mar 20 16:25:55 2017 user.info mwan3track: Lost 17 ping(s) on interface wan4g3 (wwan3)
Mon Mar 20 16:25:56 2017 user.notice mwan3track: Lost wwan2: 22
Mon Mar 20 16:25:57 2017 user.notice mwan3track: Up count eth0.2: 1
Mon Mar 20 16:25:57 2017 user.notice mwan3track: Up count eth0.2: 2
Mon Mar 20 16:25:57 2017 user.notice mwan3track: Up count eth0.2: 3
Mon Mar 20 16:25:57 2017 user.notice mwan3track: Up count eth0.2: 4
Mon Mar 20 16:25:57 2017 user.notice mwan3track: Lost wwan0: 14
Mon Mar 20 16:26:00 2017 user.notice mwan3track: Lost wwan2: 23
Mon Mar 20 16:26:00 2017 user.notice mwan3track: Up count wwan3: 1
Mon Mar 20 16:26:00 2017 user.notice mwan3track: Up count wwan3: 2
Mon Mar 20 16:26:00 2017 user.notice mwan3track: Up count wwan3: 3
Mon Mar 20 16:26:00 2017 user.notice mwan3track: Up count wwan3: 4
Mon Mar 20 16:26:01 2017 user.notice mwan3track: Up count wwan1: 1
Mon Mar 20 16:26:01 2017 user.notice mwan3track: Up count wwan1: 2
Mon Mar 20 16:26:01 2017 user.notice mwan3track: Up count wwan1: 3
Mon Mar 20 16:26:01 2017 user.notice mwan3track: Up count wwan1: 4
Mon Mar 20 16:26:01 2017 user.info mwan3track: Lost 12 ping(s) on interface wan4g1 (wwan1)
Mon Mar 20 16:26:02 2017 user.notice mwan3track: Lost wwan0: 15
Mon Mar 20 16:26:02 2017 user.notice mwan3track: Up count wwan0: 1
Mon Mar 20 16:26:02 2017 user.info mwan3track: Lost 15 ping(s) on interface wan4g0 (wwan0)
Mon Mar 20 16:26:03 2017 user.notice mwan3track: Up count eth0.2: 1
Mon Mar 20 16:26:03 2017 user.notice mwan3track: Up count eth0.2: 2
Mon Mar 20 16:26:03 2017 user.notice mwan3track: Up count eth0.2: 3
Mon Mar 20 16:26:03 2017 user.notice mwan3track: Up count eth0.2: 4
Mon Mar 20 16:26:03 2017 user.notice mwan3track: Up count wwan3: 1
Mon Mar 20 16:26:03 2017 user.notice mwan3track: Up count wwan3: 2
Mon Mar 20 16:26:03 2017 user.notice mwan3track: Up count wwan3: 3
Mon Mar 20 16:26:03 2017 user.notice mwan3track: Up count wwan3: 4
Mon Mar 20 16:26:04 2017 user.notice mwan3track: Lost wwan2: 24
Mon Mar 20 16:26:06 2017 user.notice mwan3track: Up count wwan1: 1
Mon Mar 20 16:26:06 2017 user.notice mwan3track: Up count wwan1: 2
Mon Mar 20 16:26:06 2017 user.notice mwan3track: Up count wwan1: 3
Mon Mar 20 16:26:06 2017 user.notice mwan3track: Up count wwan1: 4
Mon Mar 20 16:26:07 2017 user.notice mwan3track: Up count wwan0: 1
Mon Mar 20 16:26:07 2017 user.notice mwan3track: Up count wwan0: 2
Mon Mar 20 16:26:07 2017 user.notice mwan3track: Up count wwan0: 3
Mon Mar 20 16:26:07 2017 user.notice mwan3track: Up count wwan0: 4
Mon Mar 20 16:26:08 2017 user.notice mwan3track: Up count eth0.2: 1
Mon Mar 20 16:26:08 2017 user.notice mwan3track: Up count eth0.2: 2
Mon Mar 20 16:26:08 2017 user.notice mwan3track: Up count eth0.2: 3
Mon Mar 20 16:26:08 2017 user.notice mwan3track: Up count eth0.2: 4
Mon Mar 20 16:26:08 2017 user.notice mwan3track: Up count wwan3: 1
Mon Mar 20 16:26:08 2017 user.notice mwan3track: Up count wwan3: 2
Mon Mar 20 16:26:08 2017 user.notice mwan3track: Up count wwan3: 3
Mon Mar 20 16:26:08 2017 user.notice mwan3track: Up count wwan3: 4
Mon Mar 20 16:26:10 2017 user.notice mwan3track: Up count wwan2: 1
Mon Mar 20 16:26:10 2017 user.notice mwan3track: Up count wwan2: 2
Mon Mar 20 16:26:10 2017 user.notice mwan3track: Up count wwan2: 3
Mon Mar 20 16:26:10 2017 user.notice mwan3track: Up count wwan2: 4
Mon Mar 20 16:26:10 2017 user.info mwan3track: Lost 24 ping(s) on interface wan4g2 (wwan2)
Mon Mar 20 16:26:10 2017 user.notice mwan3track: Up count wwan1: 1
Mon Mar 20 16:26:10 2017 user.notice mwan3track: Up count wwan1: 2
Mon Mar 20 16:26:10 2017 user.notice mwan3track: Up count wwan1: 3
Mon Mar 20 16:26:10 2017 user.notice mwan3track: Up count wwan1: 4
Mon Mar 20 16:26:12 2017 user.notice mwan3track: Up count wwan0: 1
Mon Mar 20 16:26:12 2017 user.notice mwan3track: Up count wwan0: 2
Mon Mar 20 16:26:12 2017 user.notice mwan3track: Up count wwan0: 3
Mon Mar 20 16:26:12 2017 user.notice mwan3track: Up count wwan0: 4
Mon Mar 20 16:26:12 2017 user.notice mwan3track: Interface wan4g0 (wwan0) is online
Mon Mar 20 16:26:13 2017 user.notice mwan3track: Up count eth0.2: 1
Mon Mar 20 16:26:13 2017 user.notice mwan3track: Up count eth0.2: 2
Mon Mar 20 16:26:13 2017 user.notice mwan3track: Up count eth0.2: 3
Mon Mar 20 16:26:13 2017 user.notice mwan3track: Up count eth0.2: 4
Mon Mar 20 16:26:14 2017 user.notice mwan3track: Up count wwan3: 1
Mon Mar 20 16:26:14 2017 user.notice mwan3track: Up count wwan3: 2
Mon Mar 20 16:26:14 2017 user.notice mwan3track: Up count wwan3: 3
Mon Mar 20 16:26:14 2017 user.notice mwan3track: Up count wwan3: 4
Mon Mar 20 16:26:15 2017 user.notice mwan3track: Up count wwan2: 1
Mon Mar 20 16:26:15 2017 user.notice mwan3track: Up count wwan2: 2
Mon Mar 20 16:26:15 2017 user.notice mwan3track: Up count wwan2: 3
Mon Mar 20 16:26:15 2017 user.notice mwan3track: Up count wwan2: 4
Mon Mar 20 16:26:15 2017 user.notice mwan3track: Up count wwan1: 1
Mon Mar 20 16:26:15 2017 user.notice mwan3track: Up count wwan1: 2
Mon Mar 20 16:26:15 2017 user.notice mwan3track: Up count wwan1: 3
Mon Mar 20 16:26:15 2017 user.notice mwan3track: Up count wwan1: 4
Mon Mar 20 16:26:18 2017 user.notice mwan3track: Up count wwan0: 1
Mon Mar 20 16:26:18 2017 user.notice mwan3track: Up count eth0.2: 1
Mon Mar 20 16:26:18 2017 user.notice mwan3track: Up count wwan0: 2
Mon Mar 20 16:26:18 2017 user.notice mwan3track: Up count eth0.2: 2
Mon Mar 20 16:26:18 2017 user.notice mwan3track: Up count wwan0: 3
Mon Mar 20 16:26:18 2017 user.notice mwan3track: Up count eth0.2: 3
Mon Mar 20 16:26:19 2017 user.notice mwan3track: Up count wwan0: 4
Mon Mar 20 16:26:19 2017 user.notice mwan3track: Up count eth0.2: 4
Mon Mar 20 16:26:19 2017 user.notice mwan3track: Up count wwan3: 1
Mon Mar 20 16:26:19 2017 user.notice mwan3track: Up count wwan3: 2
Mon Mar 20 16:26:19 2017 user.notice mwan3track: Up count wwan3: 3
Mon Mar 20 16:26:19 2017 user.notice mwan3track: Up count wwan3: 4
Mon Mar 20 16:26:20 2017 user.notice mwan3track: Up count wwan2: 1
Mon Mar 20 16:26:20 2017 user.notice mwan3track: Up count wwan2: 2
Mon Mar 20 16:26:20 2017 user.notice mwan3track: Up count wwan2: 3
Mon Mar 20 16:26:20 2017 user.notice mwan3track: Up count wwan2: 4
Mon Mar 20 16:26:20 2017 user.notice mwan3track: Interface wan4g2 (wwan2) is online
Mon Mar 20 16:26:20 2017 user.notice mwan3track: Up count wwan1: 1
Mon Mar 20 16:26:21 2017 user.notice mwan3track: Up count wwan1: 2
Mon Mar 20 16:26:21 2017 user.notice mwan3track: Up count wwan1: 3
Mon Mar 20 16:26:21 2017 user.notice mwan3track: Up count wwan1: 4
Mon Mar 20 16:26:24 2017 user.notice mwan3track: Up count wwan0: 1
Mon Mar 20 16:26:24 2017 user.notice mwan3track: Up count eth0.2: 1
Mon Mar 20 16:26:24 2017 user.notice mwan3track: Up count wwan0: 2
Mon Mar 20 16:26:24 2017 user.notice mwan3track: Up count eth0.2: 2
Mon Mar 20 16:26:24 2017 user.notice mwan3track: Up count wwan0: 3
Mon Mar 20 16:26:24 2017 user.notice mwan3track: Up count eth0.2: 3
Mon Mar 20 16:26:24 2017 user.notice mwan3track: Up count wwan0: 4
Mon Mar 20 16:26:24 2017 user.notice mwan3track: Up count eth0.2: 4
Mon Mar 20 16:26:24 2017 user.notice mwan3track: Up count wwan3: 1
Mon Mar 20 16:26:24 2017 user.notice mwan3track: Up count wwan3: 2
Mon Mar 20 16:26:24 2017 user.notice mwan3track: Up count wwan3: 3
Mon Mar 20 16:26:24 2017 user.notice mwan3track: Up count wwan3: 4
Mon Mar 20 16:26:26 2017 user.notice mwan3track: Up count wwan1: 1
Mon Mar 20 16:26:26 2017 user.notice mwan3track: Up count wwan1: 2
Mon Mar 20 16:26:26 2017 user.notice mwan3track: Up count wwan1: 3
Mon Mar 20 16:26:26 2017 user.notice mwan3track: Up count wwan1: 4
Mon Mar 20 16:26:26 2017 user.notice mwan3track: Up count wwan0: 1
Mon Mar 20 16:26:26 2017 user.notice mwan3track: Up count wwan0: 2
Mon Mar 20 16:26:26 2017 user.notice mwan3track: Up count wwan0: 3
Mon Mar 20 16:26:26 2017 user.notice mwan3track: Up count wwan0: 4
Mon Mar 20 16:26:29 2017 user.notice mwan3track: Up count eth0.2: 1
Mon Mar 20 16:26:29 2017 user.notice mwan3track: Up count eth0.2: 2
Mon Mar 20 16:26:29 2017 user.notice mwan3track: Up count eth0.2: 3
Mon Mar 20 16:26:29 2017 user.notice mwan3track: Up count eth0.2: 4
Mon Mar 20 16:26:29 2017 user.notice mwan3track: Up count wwan3: 1
Mon Mar 20 16:26:29 2017 user.notice mwan3track: Up count wwan3: 2
Mon Mar 20 16:26:29 2017 user.notice mwan3track: Up count wwan3: 3
Mon Mar 20 16:26:29 2017 user.notice mwan3track: Up count wwan3: 4
Mon Mar 20 16:26:31 2017 user.notice mwan3track: Up count wwan1: 1
Mon Mar 20 16:26:31 2017 user.notice mwan3track: Up count wwan1: 2
Mon Mar 20 16:26:31 2017 user.notice mwan3track: Up count wwan1: 3
Mon Mar 20 16:26:31 2017 user.notice mwan3track: Up count wwan1: 4
Mon Mar 20 16:26:31 2017 user.notice mwan3track: Up count wwan0: 1
Mon Mar 20 16:26:31 2017 user.notice mwan3track: Up count wwan0: 2
Mon Mar 20 16:26:31 2017 user.notice mwan3track: Up count wwan0: 3
Mon Mar 20 16:26:31 2017 user.notice mwan3track: Up count wwan0: 4
Mon Mar 20 16:26:34 2017 user.notice mwan3track: Up count eth0.2: 1
Mon Mar 20 16:26:34 2017 user.notice mwan3track: Up count eth0.2: 2
Mon Mar 20 16:26:34 2017 user.notice mwan3track: Up count eth0.2: 3
Mon Mar 20 16:26:34 2017 user.notice mwan3track: Up count eth0.2: 4
Mon Mar 20 16:26:34 2017 user.notice mwan3track: Up count wwan3: 1
Mon Mar 20 16:26:35 2017 user.notice mwan3track: Up count wwan3: 2
Mon Mar 20 16:26:35 2017 user.notice mwan3track: Up count wwan3: 3
Mon Mar 20 16:26:35 2017 user.notice mwan3track: Up count wwan3: 4
Mon Mar 20 16:26:35 2017 user.notice mwan3track: Up count wwan2: 1
Mon Mar 20 16:26:35 2017 user.notice mwan3track: Up count wwan2: 2
Mon Mar 20 16:26:35 2017 user.notice mwan3track: Up count wwan2: 3
Mon Mar 20 16:26:35 2017 user.notice mwan3track: Up count wwan2: 4
Mon Mar 20 16:26:36 2017 user.notice mwan3track: Up count wwan1: 1
Mon Mar 20 16:26:36 2017 user.notice mwan3track: Up count wwan1: 2
Mon Mar 20 16:26:36 2017 user.notice mwan3track: Up count wwan1: 3
Mon Mar 20 16:26:36 2017 user.notice mwan3track: Up count wwan1: 4
Mon Mar 20 16:26:37 2017 user.notice mwan3track: Up count wwan0: 1
Mon Mar 20 16:26:37 2017 user.notice mwan3track: Up count wwan0: 2
Mon Mar 20 16:26:37 2017 user.notice mwan3track: Up count wwan0: 3
Mon Mar 20 16:26:37 2017 user.notice mwan3track: Up count wwan0: 4
Mon Mar 20 16:26:39 2017 user.notice mwan3track: Up count eth0.2: 1
Mon Mar 20 16:26:39 2017 user.notice mwan3track: Up count eth0.2: 2
Mon Mar 20 16:26:39 2017 user.notice mwan3track: Up count eth0.2: 3
Mon Mar 20 16:26:40 2017 user.notice mwan3track: Up count eth0.2: 4
Mon Mar 20 16:26:40 2017 user.notice mwan3track: Up count wwan3: 1
Mon Mar 20 16:26:40 2017 user.notice mwan3track: Up count wwan3: 2
Mon Mar 20 16:26:40 2017 user.notice mwan3track: Up count wwan3: 3
Mon Mar 20 16:26:40 2017 user.notice mwan3track: Up count wwan2: 1
Mon Mar 20 16:26:40 2017 user.notice mwan3track: Up count wwan3: 4
Mon Mar 20 16:26:40 2017 user.notice mwan3track: Up count wwan2: 2
Mon Mar 20 16:26:40 2017 user.notice mwan3track: Up count wwan2: 3
Mon Mar 20 16:26:40 2017 user.notice mwan3track: Up count wwan2: 4
Mon Mar 20 16:26:41 2017 user.notice mwan3track: Up count wwan1: 1
Mon Mar 20 16:26:41 2017 user.notice mwan3track: Up count wwan1: 2
Mon Mar 20 16:26:42 2017 user.notice mwan3track: Up count wwan1: 3
Mon Mar 20 16:26:42 2017 user.notice mwan3track: Up count wwan1: 4
Mon Mar 20 16:26:42 2017 user.notice mwan3track: Up count wwan0: 1
Mon Mar 20 16:26:42 2017 user.notice mwan3track: Up count wwan0: 2
Mon Mar 20 16:26:42 2017 user.notice mwan3track: Up count wwan0: 3
Mon Mar 20 16:26:42 2017 user.notice mwan3track: Up count wwan0: 4
Mon Mar 20 16:26:43 2017 user.notice mwan3track: Up count wwan2: 1
Mon Mar 20 16:26:43 2017 user.notice mwan3track: Up count wwan2: 2
Mon Mar 20 16:26:43 2017 user.notice mwan3track: Up count wwan2: 3
Mon Mar 20 16:26:43 2017 user.notice mwan3track: Up count wwan2: 4
Mon Mar 20 16:26:45 2017 user.notice mwan3track: Up count eth0.2: 1
Mon Mar 20 16:26:45 2017 user.notice mwan3track: Up count eth0.2: 2
Mon Mar 20 16:26:45 2017 user.notice mwan3track: Up count eth0.2: 3
Mon Mar 20 16:26:45 2017 user.notice mwan3track: Up count eth0.2: 4
Mon Mar 20 16:26:45 2017 user.notice mwan3track: Up count wwan3: 1
Mon Mar 20 16:26:45 2017 user.notice mwan3track: Up count wwan3: 2
Mon Mar 20 16:26:45 2017 user.notice mwan3track: Up count wwan3: 3
Mon Mar 20 16:26:45 2017 user.notice mwan3track: Up count wwan3: 4
Mon Mar 20 16:26:47 2017 user.notice mwan3track: Up count wwan1: 1
Mon Mar 20 16:26:47 2017 user.notice mwan3track: Up count wwan1: 2
Mon Mar 20 16:26:47 2017 user.notice mwan3track: Up count wwan1: 3
Mon Mar 20 16:26:47 2017 user.notice mwan3track: Up count wwan1: 4
Mon Mar 20 16:26:47 2017 user.notice mwan3track: Up count wwan0: 1
Mon Mar 20 16:26:47 2017 user.notice mwan3track: Up count wwan0: 2
Mon Mar 20 16:26:47 2017 user.notice mwan3track: Up count wwan0: 3
Mon Mar 20 16:26:47 2017 user.notice mwan3track: Up count wwan0: 4
Mon Mar 20 16:26:48 2017 user.notice mwan3track: Up count wwan2: 1
Mon Mar 20 16:26:48 2017 user.notice mwan3track: Up count wwan2: 2
Mon Mar 20 16:26:48 2017 user.notice mwan3track: Up count wwan2: 3
Mon Mar 20 16:26:48 2017 user.notice mwan3track: Up count wwan2: 4
Mon Mar 20 16:26:50 2017 user.notice mwan3track: Up count eth0.2: 1
Mon Mar 20 16:26:50 2017 user.notice mwan3track: Up count eth0.2: 2
Mon Mar 20 16:26:50 2017 user.notice mwan3track: Up count eth0.2: 3
Mon Mar 20 16:26:50 2017 user.notice mwan3track: Up count eth0.2: 4
Mon Mar 20 16:26:50 2017 user.notice mwan3track: Up count wwan3: 1
Mon Mar 20 16:26:50 2017 user.notice mwan3track: Up count wwan3: 2
Mon Mar 20 16:26:50 2017 user.notice mwan3track: Up count wwan3: 3
Mon Mar 20 16:26:50 2017 user.notice mwan3track: Up count wwan3: 4
Mon Mar 20 16:26:52 2017 user.notice mwan3track: Up count wwan1: 1
Mon Mar 20 16:26:52 2017 user.notice mwan3track: Up count wwan1: 2
Mon Mar 20 16:26:52 2017 user.notice mwan3track: Up count wwan1: 3
Mon Mar 20 16:26:52 2017 user.notice mwan3track: Up count wwan1: 4
Mon Mar 20 16:26:52 2017 user.notice mwan3track: Up count wwan0: 1
Mon Mar 20 16:26:52 2017 user.notice mwan3track: Up count wwan0: 2
Mon Mar 20 16:26:52 2017 user.notice mwan3track: Up count wwan0: 3
Mon Mar 20 16:26:52 2017 user.notice mwan3track: Up count wwan0: 4
Mon Mar 20 16:26:53 2017 user.notice mwan3track: Up count wwan2: 1
Mon Mar 20 16:26:53 2017 user.notice mwan3track: Up count wwan2: 2
Mon Mar 20 16:26:53 2017 user.notice mwan3track: Up count wwan2: 3
Mon Mar 20 16:26:53 2017 user.notice mwan3track: Up count wwan2: 4
Mon Mar 20 16:26:55 2017 user.notice mwan3track: Up count eth0.2: 1
Mon Mar 20 16:26:55 2017 user.notice mwan3track: Up count eth0.2: 2
Mon Mar 20 16:26:55 2017 user.notice mwan3track: Up count eth0.2: 3
Mon Mar 20 16:26:55 2017 user.notice mwan3track: Up count eth0.2: 4
Mon Mar 20 16:26:56 2017 user.notice mwan3track: Up count wwan3: 1
Mon Mar 20 16:26:56 2017 user.notice mwan3track: Up count wwan3: 2
Mon Mar 20 16:26:56 2017 user.notice mwan3track: Up count wwan3: 3
Mon Mar 20 16:26:56 2017 user.notice mwan3track: Up count wwan3: 4
Mon Mar 20 16:26:57 2017 user.notice mwan3track: Up count wwan1: 1
Mon Mar 20 16:26:57 2017 user.notice mwan3track: Up count wwan1: 2
Mon Mar 20 16:26:57 2017 user.notice mwan3track: Up count wwan1: 3
Mon Mar 20 16:26:57 2017 user.notice mwan3track: Up count wwan1: 4
Mon Mar 20 16:26:57 2017 user.notice mwan3track: Up count wwan0: 1
Mon Mar 20 16:26:58 2017 user.notice mwan3track: Up count wwan0: 2
Mon Mar 20 16:26:58 2017 user.notice mwan3track: Up count wwan0: 3
Mon Mar 20 16:26:58 2017 user.notice mwan3track: Up count wwan0: 4
Mon Mar 20 16:26:58 2017 user.notice mwan3track: Up count wwan2: 1
Mon Mar 20 16:26:58 2017 user.notice mwan3track: Up count wwan2: 2
Mon Mar 20 16:26:59 2017 user.notice mwan3track: Up count wwan2: 3
Mon Mar 20 16:26:59 2017 user.notice mwan3track: Up count wwan2: 4
Mon Mar 20 16:27:00 2017 user.notice mwan3track: Up count eth0.2: 1
Mon Mar 20 16:27:00 2017 user.notice mwan3track: Up count eth0.2: 2
Mon Mar 20 16:27:00 2017 user.notice mwan3track: Up count eth0.2: 3
Mon Mar 20 16:27:00 2017 user.notice mwan3track: Up count eth0.2: 4
Mon Mar 20 16:27:01 2017 user.notice mwan3track: Up count wwan3: 1
Mon Mar 20 16:27:01 2017 user.notice mwan3track: Up count wwan3: 2
Mon Mar 20 16:27:01 2017 user.notice mwan3track: Up count wwan3: 3
Mon Mar 20 16:27:01 2017 user.notice mwan3track: Up count wwan3: 4
Mon Mar 20 16:27:02 2017 user.notice mwan3track: Up count wwan1: 1
Mon Mar 20 16:27:02 2017 user.notice mwan3track: Up count wwan1: 2
Mon Mar 20 16:27:02 2017 user.notice mwan3track: Up count wwan1: 3
Mon Mar 20 16:27:02 2017 user.notice mwan3track: Up count wwan1: 4
Mon Mar 20 16:27:03 2017 user.notice mwan3track: Up count wwan0: 1
Mon Mar 20 16:27:03 2017 user.notice mwan3track: Up count wwan0: 2
Mon Mar 20 16:27:03 2017 user.notice mwan3track: Up count wwan0: 3
Mon Mar 20 16:27:03 2017 user.notice mwan3track: Up count wwan0: 4
Mon Mar 20 16:27:04 2017 user.notice mwan3track: Up count wwan2: 1
Mon Mar 20 16:27:04 2017 user.notice mwan3track: Up count wwan2: 2
Mon Mar 20 16:27:04 2017 user.notice mwan3track: Up count wwan2: 3
Mon Mar 20 16:27:04 2017 user.notice mwan3track: Up count wwan2: 4
Mon Mar 20 16:27:05 2017 user.notice mwan3track: Up count eth0.2: 1
Mon Mar 20 16:27:05 2017 user.notice mwan3track: Up count eth0.2: 2
Mon Mar 20 16:27:06 2017 user.notice mwan3track: Up count eth0.2: 3
Mon Mar 20 16:27:06 2017 user.notice mwan3track: Up count eth0.2: 4
Mon Mar 20 16:27:06 2017 user.notice mwan3track: Up count wwan3: 1
Mon Mar 20 16:27:06 2017 user.notice mwan3track: Up count wwan3: 2
Mon Mar 20 16:27:06 2017 user.notice mwan3track: Up count wwan3: 3
Mon Mar 20 16:27:06 2017 user.notice mwan3track: Up count wwan3: 4
Mon Mar 20 16:27:08 2017 user.notice mwan3track: Up count wwan1: 1
Mon Mar 20 16:27:08 2017 user.notice mwan3track: Up count wwan1: 2
Mon Mar 20 16:27:08 2017 user.notice mwan3track: Up count wwan1: 3
Mon Mar 20 16:27:08 2017 user.notice mwan3track: Up count wwan1: 4
Mon Mar 20 16:27:08 2017 user.notice mwan3track: Up count wwan0: 1
Mon Mar 20 16:27:08 2017 user.notice mwan3track: Up count wwan0: 2
Mon Mar 20 16:27:08 2017 user.notice mwan3track: Up count wwan0: 3
Mon Mar 20 16:27:08 2017 user.notice mwan3track: Up count wwan0: 4
Mon Mar 20 16:27:09 2017 user.notice mwan3track: Up count wwan2: 1
Mon Mar 20 16:27:09 2017 user.notice mwan3track: Up count wwan2: 2
Mon Mar 20 16:27:09 2017 user.notice mwan3track: Up count wwan2: 3
Mon Mar 20 16:27:09 2017 user.notice mwan3track: Up count wwan2: 4
Mon Mar 20 16:27:11 2017 user.notice mwan3track: Up count eth0.2: 1
Mon Mar 20 16:27:11 2017 user.notice mwan3track: Up count eth0.2: 2
Mon Mar 20 16:27:11 2017 user.notice mwan3track: Up count eth0.2: 3
Mon Mar 20 16:27:11 2017 user.notice mwan3track: Up count eth0.2: 4
Mon Mar 20 16:27:11 2017 user.notice mwan3track: Up count wwan3: 1
Mon Mar 20 16:27:11 2017 user.notice mwan3track: Up count wwan3: 2
Mon Mar 20 16:27:11 2017 user.notice mwan3track: Up count wwan3: 3
Mon Mar 20 16:27:11 2017 user.notice mwan3track: Up count wwan3: 4
Mon Mar 20 16:27:13 2017 user.notice mwan3track: Up count wwan1: 1
Mon Mar 20 16:27:13 2017 user.notice mwan3track: Up count wwan1: 2
Mon Mar 20 16:27:13 2017 user.notice mwan3track: Up count wwan1: 3
Mon Mar 20 16:27:13 2017 user.notice mwan3track: Up count wwan1: 4
Mon Mar 20 16:27:13 2017 user.notice mwan3track: Up count wwan0: 1
Mon Mar 20 16:27:13 2017 user.notice mwan3track: Up count wwan0: 2
Mon Mar 20 16:27:13 2017 user.notice mwan3track: Up count wwan0: 3
Mon Mar 20 16:27:13 2017 user.notice mwan3track: Up count wwan0: 4
Mon Mar 20 16:27:14 2017 user.notice mwan3track: Up count wwan2: 1
Mon Mar 20 16:27:14 2017 user.notice mwan3track: Up count wwan2: 2
Mon Mar 20 16:27:14 2017 user.notice mwan3track: Up count wwan2: 3
Mon Mar 20 16:27:14 2017 user.notice mwan3track: Up count wwan2: 4

as you can see it is weird because I see the "is online" message for wwan0 and wwan2 but not for wwan1 and wwan3 while they both came back to an "Up count" of 4. Here is a filter on the lines of wwan1:

Mon Mar 20 16:25:08 2017 user.notice mwan3track: Up count wwan1: 1
Mon Mar 20 16:25:08 2017 user.notice mwan3track: Up count wwan1: 2
Mon Mar 20 16:25:08 2017 user.notice mwan3track: Up count wwan1: 3
Mon Mar 20 16:25:08 2017 user.notice mwan3track: Up count wwan1: 4
Mon Mar 20 16:25:13 2017 user.notice mwan3track: Lost wwan1: 1
Mon Mar 20 16:25:13 2017 user.notice mwan3track: Lost wwan1: 2
Mon Mar 20 16:25:13 2017 user.notice mwan3track: Lost wwan1: 3
Mon Mar 20 16:25:13 2017 user.notice mwan3track: Lost wwan1: 4
Mon Mar 20 16:25:19 2017 user.notice mwan3track: Lost wwan1: 5
Mon Mar 20 16:25:19 2017 user.notice mwan3track: Lost wwan1: 6
Mon Mar 20 16:25:19 2017 user.notice mwan3track: Lost wwan1: 7
Mon Mar 20 16:25:19 2017 user.notice mwan3track: Lost wwan1: 8
Mon Mar 20 16:25:24 2017 user.notice mwan3track: Lost wwan1: 9
Mon Mar 20 16:25:24 2017 user.notice mwan3track: Lost wwan1: 10
Mon Mar 20 16:25:24 2017 user.notice mwan3track: Lost wwan1: 11
Mon Mar 20 16:25:24 2017 user.notice mwan3track: Lost wwan1: 12
Mon Mar 20 16:25:24 2017 user.notice mwan3track: Interface wan4g1 (wwan1) is offline
Mon Mar 20 16:26:01 2017 user.notice mwan3track: Up count wwan1: 1
Mon Mar 20 16:26:01 2017 user.notice mwan3track: Up count wwan1: 2
Mon Mar 20 16:26:01 2017 user.notice mwan3track: Up count wwan1: 3
Mon Mar 20 16:26:01 2017 user.notice mwan3track: Up count wwan1: 4
Mon Mar 20 16:26:01 2017 user.info mwan3track: Lost 12 ping(s) on interface wan4g1 (wwan1)
Mon Mar 20 16:26:06 2017 user.notice mwan3track: Up count wwan1: 1
Mon Mar 20 16:26:06 2017 user.notice mwan3track: Up count wwan1: 2
Mon Mar 20 16:26:06 2017 user.notice mwan3track: Up count wwan1: 3
Mon Mar 20 16:26:06 2017 user.notice mwan3track: Up count wwan1: 4
Mon Mar 20 16:26:10 2017 user.notice mwan3track: Up count wwan1: 1
Mon Mar 20 16:26:10 2017 user.notice mwan3track: Up count wwan1: 2
Mon Mar 20 16:26:10 2017 user.notice mwan3track: Up count wwan1: 3
Mon Mar 20 16:26:10 2017 user.notice mwan3track: Up count wwan1: 4

Here is my config on these interfaces:

config interface 'wan'
    option enabled '1'
    option reliability '1'
    option count '1'
    option timeout '4'
    option interval '5'
    option down '3'
    option up '3'
    list track_ip '8.8.4.4'
    list track_ip '208.67.222.222'
    list track_ip '8.8.8.8'
    list track_ip '208.67.220.220'

config interface 'wan4g0'
    option enabled '1'
    option reliability '1'
        option count '1'
    option timeout '4'
    option interval '5'
    option down '3'
    option up '3'
    list track_ip '208.67.220.220'
    list track_ip '8.8.4.4'
    list track_ip '208.67.222.222'
    list track_ip '8.8.8.8'

config interface 'wan4g1'
    option enabled '1'
    option reliability '1'
        option count '1'
    option timeout '4'
    option interval '5'
    option down '3'
    option up '3'
    list track_ip '8.8.8.8'
    list track_ip '208.67.220.220'
    list track_ip '8.8.4.4'
    list track_ip '208.67.222.222'

config interface 'wan4g2'
    option enabled '1'
    option reliability '1'
        option count '1'
    option timeout '4'
    option interval '5'
    option down '3'
    option up '3'
    list track_ip '208.67.222.222'
    list track_ip '8.8.8.8'
    list track_ip '208.67.220.220'
    list track_ip '8.8.4.4'

config interface 'wan4g3'
    option enabled '1'
    option reliability '1'
        option count '1'
    option timeout '4'
    option interval '5'
    option down '3'
    option up '3'
    list track_ip '8.8.4.4'
    list track_ip '208.67.222.222'
    list track_ip '8.8.8.8'
    list track_ip '208.67.220.220'

FYI: wan4g0=wwan0, wan4g1=wwan1, wan4g2=wwan2, wan4g3=wwan3.
Do you understand why I don't see the "is online" message in the logs for wwan1 and wwan3??

(Last edited by wazaa on 20 Mar 2017, 17:04)

Post #1608

salatiel

25 Mar 2017, 13:25

Hi, guys, i have a DSL (50M/10M) ISP that blocks inbound connections and one 3g (1M/512kbit ) that allows inbound connections used as backup. Is there a way to make packets incoming from the 3g connections be replied by the DSL connection so i could for example download from a small webserver faster ? If i remember correctly , there was a time when the packets coming from some interface wouldn't be replied by it , but this behaviour appears to have changed.
I'm using chaos calmer version

Post #1609

harley77

26 Mar 2017, 16:55

Hello all, they are two days that I'm trying to understand why wan2 goes offline. I followed several forum posts, but nothing to fare. I hope someone can help me to understod where I'm wrong. Post my configuration:

Interface status:
interface wan is online (tracking active)
interface wan2 is offline (tracking active)
Policy balanced:
wan (100%)
Policy wan2_only:
unreachable
Policy wan2_wan:
wan (100%)
Policy wan_only:
wan (100%)
Policy wan_wan2:
wan (100%)
Known networks:
192.168.1.0
224.0.0.0/3
127.0.0.0/8
10.96.255.255
10.1.0.0/23
192.168.1.1
192.168.1.255
192.168.1.25
10.1.0.0
10.96.0.0/16
127.0.0.0
127.255.255.255
10.1.0.1
127.0.0.1
192.168.1.164
192.168.1.0/24
10.96.0.0
10.1.1.255
10.96.81.123
---------------------------------------------------------------------
/etc/config/mwan3

config interface 'wan'
option enabled '1'
option reliability '2'
option count '1'
option timeout '2'
option interval '5'
option down '3'
option up '8'
list track_ip '8.8.8.8'
list track_ip '8.8.4.4'
config interface 'wan2'
option enabled '1'
option count '1'
option timeout '2'
option interval '5'
option down '3'
option up '8'
option reliability '2'
list track_ip '8.8.8.8'
list track_ip '8.8.4.4'
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_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'
option last_resort 'unreachable'
config policy 'balanced'
list use_member 'wan_m1_w3'
list use_member 'wan2_m1_w2'
option last_resort 'unreachable'
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 'youtube'
option sticky '1'
option ipset 'youtube'
option dest_port '80,443'
option proto 'tcp'
option use_policy 'balanced'
config rule 'h t t p s'
option sticky '1'
option dest_port '443'
option proto 'tcp'
option use_policy 'balanced'
config rule 'default_rule'
option dest_ip '0.0.0.0/0'
option use_policy 'balanced'
----------------------------------------------------------------
/etc/config/network
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fd8f:e9b4:fc09::/48'
config interface 'wan'
option ifname 'eth1'
option proto 'dhcp'
option peerdns '0'
option dns '8.8.8.8 8.8.4.4'
option metric '10'
config interface 'wan2'
option ifname 'eth2'
option proto 'dhcp'
option peerdns '0'
option dns '8.8.8.8 8.8.4.4'
option metric '20'
config interface 'lan'
option ifname 'eth0'
option force_link '1'
option type 'bridge'
option netmask '255.255.255.0'
option ip6assign '60'
option proto 'none'
option ipaddr '0.0.0.0'
config interface 'chilli'
option ifname 'tun1'
option proto 'none'
config interface 'vpn'
option ifname 'tun0'
option proto 'none'

I used the mwan3 version 1.6-2
Chaos Calmer 15.05.01,r48532 on ubiquity erlite3

From eth2
root@AP:~# ping -I eth2 w w w google com
PING w w w google com (172.217.16.3): 56 data bytes
Froma eth1
root@AP:~# ping -I eth1 w w w google com
PING w w w google com (172.217.16.3): 56 data bytes
64 bytes from 172.217.16.3: seq=0 ttl=53 time=35.344 ms
64 bytes from 172.217.16.3: seq=1 ttl=53 time=35.677 ms
64 bytes from 172.217.16.3: seq=2 ttl=53 time=35.189 ms
64 bytes from 172.217.16.3: seq=3 ttl=53 time=40.234 ms
64 bytes from 172.217.16.3: seq=4 ttl=53 time=35.286 ms
The following is my routing table:
root@AP:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default my.firewall 0.0.0.0 UG 10 0 0 eth1
default my.firewall 0.0.0.0 UG 20 0 0 eth2
10.1.0.0 * 255.255.254.0 U 0 0 0 tun1
10.96.0.0 * 255.255.0.0 U 0 0 0 tun0
192.168.1.0 * 255.255.255.0 U 10 0 0 eth1
192.168.1.0 * 255.255.255.0 U 20 0 0 eth2
192.168.1.1 * 255.255.255.255 UH 10 0 0 eth1
192.168.1.1 * 255.255.255.255 UH 20 0 0 eth2

I hope someone can help me. Thank you

Post #1610

bobptz

27 Mar 2017, 23:15

I have 2 interfaces, but when I test the speed of the combined setup at http://www.dslreports.com/speedtest, what I get seems to be the result of only one interface.

Could you tell me what I should check? Some diagnostics to run?

Post #1611

antsec3

31 Mar 2017, 00:57

I'm trying to set up mwan 3 for a failover setup only. I have 2 wans, a wan1 which is cable internet and a wan2 usb 4g dongle for backup (failover). I installed everything and both interfaces are working when i connect them separately, but when i run mwan3 and connect both interfaces it says wan1 is up but wan2(4g) is down.
I think that wan2(4g) doesnt have a routing table and i cant figure out where to configure it, Im triying to fix this but i cant figure it out.
Please can somebody help me,thank you!
Here are configs and tests:

ping default gateway:

ping -c 3 -W 2 -I wwan0 77.219.44.177

PING 77.219.44.177 (77.219.44.177): 56 data bytes
64 bytes from 77.219.44.177: seq=0 ttl=63 time=1224.562 ms
64 bytes from 77.219.44.177: seq=1 ttl=63 time=904.298 ms
64 bytes from 77.219.44.177: seq=2 ttl=63 time=873.987 ms

--- 77.219.44.177 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 873.987/1000.949/1224.562 ms

Check ip rules
Missing both of the required interface IP rules

Check routing table
Missing required interface routing table 1

etc/config/network:
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'

config globals 'globals'
option ula_prefix 'fd9d:a35f:17dc::/48'

config interface 'lan'
option ifname 'eth1'
option force_link '1'
option type 'bridge'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'

config interface 'wan'
option ifname 'eth0'
option proto 'dhcp'
option peerdns '0'
option dns '8.8.8.8 8.8.4.4'
option metric '10'

config interface 'wan6'
option ifname 'eth0'
option proto 'dhcpv6'

config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'

config switch_vlan
option device 'switch0'
option vlan '1'
option ports '0 2 3 4 5'

config switch_vlan
option device 'switch0'
option vlan '2'
option ports '1 6'

config interface 'LTE'
option _orig_ifname 'wwan0'
option _orig_bridge 'false'
option proto 'qmi'
option device '/dev/cdc-wdm0'
option apn 'internet.tele2.hr'
option auth 'none'
option metric '20'
option delegate '0'

/etc/config/mwan3:

config interface 'LTE'
option enabled '1'
list track_ip '8.8.4.4'
list track_ip '8.8.8.8'
list track_ip '208.67.220.220'
option reliability '1'
option count '1'
option timeout '5'
option interval '10'
option down '3'
option up '3'

config interface 'wan'
option enabled '1'
list track_ip '8.8.4.4'
list track_ip '8.8.8.8'
list track_ip '208.67.220.220'
option reliability '1'
option count '1'
option timeout '5'
option interval '10'
option down '2'
option up '2'

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

config member 'LTE_m2_w4'
option interface 'LTE'
option metric '2'
option weight '4'

config policy 'wan_only'
list use_member 'wan_m1_w3'

config policy 'LTE_only'
list use_member 'LTE_m2_w4'

config policy 'balanced'
list use_member 'wan_m1_w3'
list use_member 'LTE_m2_w4'

config policy 'wan_wan2'
list use_member 'wan_m1_w3'
list use_member 'LTE_m2_w4'

config policy 'wan2_wan'
list use_member 'LTE_m2_w4'
list use_member 'wan_m1_w3'

config rule 'sticky_even'
option src_ip '0.0.0.0/0.0.0.1'
option dest_port '443'
option proto 'tcp'
option use_policy 'wan_wan2'

config rule 'sticky_odd'
option src_ip '0.0.0.1/0.0.0.1'
option dest_port '443'
option proto 'tcp'
option use_policy 'wan2_wan'

config rule 'default_rule'
option dest_ip '0.0.0.0/0'
option use_policy 'wan_wan2'

mwan3:

Interface status:
interface LTE is offline and tracking is down
interface wan is online and tracking is active

Current ipv4 policies:
LTE_only:
unreachable

balanced:
wan (100%)

wan2_wan:
wan (100%)

wan_only:
wan (100%)

wan_wan2:
wan (100%)

Current ipv6 policies:
LTE_only:
unreachable

balanced:
unreachable

wan2_wan:
unreachable

wan_only:
unreachable

wan_wan2:
unreachable

Directly connected ipv4 networks:
77.219.52.103
46.163.0.255
127.0.0.0/8
192.168.1.1
77.219.52.100
127.255.255.255
192.168.1.0/24
77.219.52.100/30
77.219.52.101
46.163.0.138
192.168.1.0
46.163.0.1
127.0.0.1
224.0.0.0/3
127.0.0.0
46.163.0.0/24
77.219.52.102
46.163.0.0
192.168.1.255

Directly connected ipv6 networks:
fd9d:a35f:17dc::/64
fd9d:a35f:17dc:4::/62
fe80::/64

Active ipv4 user rules:
8 504 - wan_wan2 tcp -- * * 0.0.0.0/0.0.0.1 0.0.0.0/0 multiport sports 0:65535 multiport dports 443
171 10425 - wan2_wan tcp -- * * 0.0.0.1/0.0.0.1 0.0.0.0/0 multiport sports 0:65535 multiport dports 443
220 16913 - wan_wan2 all -- * * 0.0.0.0/0 0.0.0.0/0

Active ipv6 user rules:
313 122K - wan_wan2 all * * ::/0 ::/0

(Last edited by antsec3 on 31 Mar 2017, 01:01)

Post #1612

greek

31 Mar 2017, 12:11

salatiel wrote:

Hi, guys, i have a DSL (50M/10M) ISP that blocks inbound connections and one 3g (1M/512kbit ) that allows inbound connections used as backup. Is there a way to make packets incoming from the 3g connections be replied by the DSL connection so i could for example download from a small webserver faster ? If i remember correctly , there was a time when the packets coming from some interface wouldn't be replied by it , but this behaviour appears to have changed.
I'm using chaos calmer version

If my Net-fu is not rusty, I would think that is not possible.
It may be possible to configure the router to reply the 3G incoming Packets through the DSL, but the server would suddenly be getting packets from the DSL IP, whareas he expects the 3G IP and not know what to do with them.
Maybe possible for stateless protocols, but the server has to support it.

(Last edited by greek on 31 Mar 2017, 12:15)

Post #1613

gsmtools

10 May 2017, 06:47

Hello,

anybody have working configuration file - mwan3 which use second WAN LTE connection as backup only?

I am using as primary WAN UPC cable internet, which is fast and stable.
As a backup I would like use LTE WAN connection (which is slower, I get different IP address and I am paying for internet traffic)

When primary UPC internet is not working, mwan3 should automaticly switch to LTE second WAN.
When first WAN (=UPC) is available again, it should automaticly switch back to first WAN

This settings is able very fast switch WAN connection from WAN2 (LTE backup connection) back to WAN (fast UPC cable connection)
when it is available again.

when primary connection - WAN (UPC cable connection is not working)
then MWAN3 immediately detects WAN is not working but it doesn't swich connection to WAN2 (LTE backup connection)

All computers in Turris omnia network are without internet connection.

What should I change or add to my mwan3 configuration file?

config interface 'wan'
option enabled '1'
list track_ip '8.8.4.4'
list track_ip '8.8.8.8'
list track_ip '208.67.222.222'
list track_ip '208.67.220.220'
option reliability '2'
option count '1'
option timeout '2'
option interval '5'
option down '3'
option up '8'

config interface 'wan2'
option enabled '1'
list track_ip '8.8.8.8'
list track_ip '208.67.220.220'
option reliability '1'
option count '1'
option timeout '2'
option interval '5'
option down '3'
option up '8'

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_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_w2'

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 'default_rule'
option dest_ip '0.0.0.0/0'
option use_policy 'wan_wan2'

Best regards

Jan

Post #1614

spybond08

8 Jun 2017, 13:04

Hello!
I have the same problem with lte modem via qmi.
When I use mwan3 with default setting for 1 wired WAN and 1 lte modem in balanced I get err
user.warn mwan3: Could not find gateway for interface wwan1

So I add follow lines to /etc/config/network:

config 'route' 'default_wwan1'
option 'interface' 'wwan1'
option 'target' '0.0.0.0'
option 'netmask' '0.0.0.0'
option 'gateway' '10.189.113.246'
option 'metric' '20'

but that's not working for me although luci shows Online (tracking active) status for lte modem in balanced (there is no defroute for wwan1 in output "ip route show"). And does not work at all in wwan1_wan mode (wwan1 Offline)
Also option gateway for lte has to be changed after reboot system.

But that works ( wwan1_wan mode) if I manualy add:

ip route replace default via 10.189.113.246 dev wwan1 metric 10
ip route replace default via 192.168.1.1 dev eth1 metric 20

May be any ideas?

(Last edited by spybond08 on 8 Jun 2017, 13:27)

Post #1615

Alex013

30 Jun 2017, 18:20

I'm sorry if I ask old or stupid questions. I do not know English so well that I would be able to use search in this forum.
I have two questions.

1. I use mwan3 only for faileower mode. My router is connected to the power via UPS. The equipment of my ISP is connected to the power without UPS. Because of this, it happens that the my router is turned on, and at the same time the equipment of my ISP is turned off. In this case, mwan3 is hangs. In this case, mwan3 does not see that the Internet has already appeared in wan and wan2. In this case i do restart mwan3, and this helps. To not have this problem, I use a script that runs every three minutes through cron:

#!/bin/sh /etc/rc.common
 
    tries=0
    while [[ $tries -lt 5 ]]
    do
    if /bin/ping -c 1 8.8.8.8 >/dev/null
    then
        exit 0
    fi
    tries=$((tries+1))
    done
 
    mwan3 restart

I understand that this is a bad decision. I tried to make a similar script, and run it via mwan3 hotplug script, but I did not succeed. Maybe Adze will add such functionality to mwan3?

2. I have a VPN tunnel to my friend. I would like to see in the interface of my router that this VPN tunnel is really active. For this, I made a fake network interface, and pointed it to mwan3. For this interface, I set the tracking IP address as the IP address of my friend's router, which is received through the VPN. Everything is working. The mwan3 indicator for this interface turns green. But mwan3 reports an error: "some interfaces have no default route in the main routing table!". Teach me how to avoid this error. How can I make the default route in the main routing table for this interface?

(Last edited by Alex013 on 30 Jun 2017, 18:22)

Post #1616

slackert

26 Jul 2017, 22:05

I have the basic mwan setup working, however I'm not sure I'm having much luck on the ipset portion. Going with the default example of youtube and adding "ipset=/youtube.com/youtube" to /etc/dnsmasq.conf, I don't see the rule I created being followed. Reading up on dnsmasq support for ipset, it looks like only the dnsmasq-full package has support for ipset and hostnames. Do I need to upgrade from dnsmasq to dnsmasq-full in order to get the default youtube ipset rule to function?

And yes, I have rebooted after all of these changes.

Thanks!

Also seeing this in system log:

Wed Jul 26 21:08:17 2017 daemon.crit dnsmasq[16048]: recompile with HAVE_IPSET defined to enable ipset directives at line 47 of /etc/dnsmasq.conf
Wed Jul 26 21:08:17 2017 daemon.crit dnsmasq[16048]: FAILED to start up

And get this if I try to install dnsmasq-full:

# opkg install dnsmasq-full
Installing dnsmasq-full (2.73-1) to root...
Downloading downloads.openwrt.org/chaos_calmer/15.05.1/mvebu/generic/packages/base/dnsmasq-full_2.73-1_mvebu.ipk. 
Collected errors:
 * check_data_file_clashes: Package dnsmasq-full wants to install file /usr/sbin/dnsmasq
        But that file is already provided by package  * dnsmasq
 * check_data_file_clashes: Package dnsmasq-full wants to install file /etc/init.d/dnsmasq
        But that file is already provided by package  * dnsmasq
 * check_data_file_clashes: Package dnsmasq-full wants to install file /etc/hotplug.d/iface/25-dnsmasq
        But that file is already provided by package  * dnsmasq
 * opkg_install_cmd: Cannot install package dnsmasq-full.

(Last edited by slackert on 26 Jul 2017, 22:14)

Post #1617

20 Sep 2017, 20:32

Hello, I'm new here, so I'm sorry if I do anything wrong

I attempt to use mwan3 in my setup which is: OpenWRT Chaos Chalmer, IF: wan being cable connection over eth0 and wan2 being LTE connection using NCM-mode LTE-modem (wwan0).
According to the instructions, both wan IFs are setup correctly (metrics set). ip a output (provided below) shows two proper IFs. Ping goes nicely through -I eth0 and -I wwan0. Route -n output listed below shows that there are two default entries, for each of the two interfaces.

Still, even a default config for mwan3 does not work, because it says:

root@LEDE:~# mwan3 interfaces

Interface status:
 interface wan is online and tracking is active
 interface wan2 is offline and tracking is down

The question is - why wan2 is considered offline and additionally tracking is down. Running ps indeed shows that mwan3track is started only for wan - why not for wan2 if the interface actually works?
As I mentioned, wan and wan2 configuration is default from mwan3. Track ips are google dnses, but I guess it doesn't matter- the problem is that mwan3 considers incorrectly wan2 as being down. mwan3 ifup wan2 doesn't help, no errors are returned, but mwan3 interfaces executed afterwards still says wan2 is offline and tracking is down.

Any ideas guys?

root@LEDE:~# ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether e8:94:f6:68:d0:91 brd ff:ff:ff:ff:ff:ff
    inet 192.168.3.252/24 brd 192.168.3.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::ea94:f6ff:fe68:d091/64 scope link 
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br-lan state UP group default qlen 1000
    link/ether e8:94:f6:68:d0:90 brd ff:ff:ff:ff:ff:ff
4: wwan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether 00:1e:10:1f:00:00 brd ff:ff:ff:ff:ff:ff
    inet 10.183.120.111/27 brd 10.183.120.127 scope global wwan0
       valid_lft forever preferred_lft forever
    inet6 fe80::21e:10ff:fe1f:0/64 scope link 
       valid_lft forever preferred_lft forever
6: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether e8:94:f6:68:d0:90 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.1/24 brd 192.168.1.255 scope global br-lan
       valid_lft forever preferred_lft forever
    inet6 fd1c:71b:dca5::1/60 scope global noprefixroute 
       valid_lft forever preferred_lft forever
    inet6 fe80::ea94:f6ff:fe68:d090/64 scope link 
       valid_lft forever preferred_lft forever
7: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-lan state UP group default qlen 1000
    link/ether e8:94:f6:68:d0:90 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::ea94:f6ff:fe68:d090/64 scope link 
       valid_lft forever preferred_lft forever

root@LEDE:~# route -n

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.3.1     0.0.0.0         UG    10     0        0 eth0
0.0.0.0         10.183.120.97   0.0.0.0         UG    20     0        0 wwan0
10.183.120.96   0.0.0.0         255.255.255.224 U     20     0        0 wwan0
10.183.120.97   0.0.0.0         255.255.255.255 UH    20     0        0 wwan0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 br-lan
192.168.3.0     0.0.0.0         255.255.255.0   U     10     0        0 eth0
192.168.3.1     0.0.0.0         255.255.255.255 UH    10     0        0 eth0

Post #1618

21 Sep 2017, 10:29

Problem solved, I had to trace a little bit the mwan3 scripts in hotplug.d. The result is that my wan2 IF was not the right one.

After wan2 is up it does not have a gateway assigned ( found using: ubus call network.interface dump). There is another wan2_4 (dynamically) created, that has the actual IP configuration. I guess this is because of the modem specifics, and the NCM protocol that it uses... After adding wan2_4 to /etc/config/network, and changing wan2 to wan2_4 in /etc/config/mwan3, mwan3 it started working.

Post #1619

arfett

12 Nov 2017, 03:20

I've loaded LEDE on my router and can continue to work a bit on the mwan3-luci package again.

Is there anyone successfully using mwan3 with IPv6 traffic? I'd like to start playing around with this and have some questions about a working setup.

Post #1620

Sorbe

29 Dec 2017, 09:26

(First of all, let me say that I like AND use MWAN2/MWAN3 every day, but the basic config learning curve is a problem. I'm sure some of you will flame me for advocating for making MWAN3 easy because you already figured it out, but this comment is for helping those that have not figured this out and then have to post over and over again for help.).

The problem with all of the MWAN* packages has been "partial configuration" resulting in non-working configs.
Basically, the fundamental setup stuff like metrics and routes, are not obvious -- same for using DHCP correclty from the WAN modems (hint the dynamic routing table metrics are not set "correctlly" for MWAN by just using DHCP).

It's really a matter of software design philosophy -- do you simply report config errors or do you provide fixes to problems.
Similarly, while the package works great if EVERYTHING is configured properly, often basic stuff is not configured.
Just setting up the VLANs with correct tagging is also non-intuitive for the typical user and can easily screw you.
For example, I like to have 4 WAN ports and just 1 LAN port, where the physical ports are just the oppposite of normal.

Basically, what everyone needs is the "easy button" for settting up commonly used MWAN3 router configurations.
What would have been awesome is some easy configuration options such as 2 WAN+3LAN, or 1LAN+4WAN.
I know that configuring the basic networking interface is not what MWAN was built for, but getting this right is not easy.
Just because system software was hard to write doesn't mean it should be hard to set up or use.

You already know from experience and the diagnostics, what everyone gets wrong: the basic routing tables and vlans
Please consider making the configuration part of the overall MULTIWAN setup process be WAY easier for everyone.

(Last edited by Sorbe on 6 Jan 2018, 11:50)

Post #1621

lomtev

10 Jan 2018, 18:20

OpenWrt +mwan3 – need help in solving one problem
I’m using mwan3 for 2 months on Netgear wndr3800 + OpenWrt Chaos Calmer 15.05/LuCI. Configuration of the net: 3WAN+LAN.
Wan: 3GSM-Routers Huawei-310B phone+4GLTE which are connected to Netgear by ethernet connections.
WAN, eth1, 192.168.8.1 (GSM 1)
WAN1, eth2, 192.168.9.1 (GSM2)
WAN2, eth3, 192.168.10.1 (GSM3)
LAN eth0, 192.168.99.1

For example:
Situation 1 (ok):
If WAN1, or WAN2 will have any problems, mwan3 will put them into offline mode – and internet will work thru WAN.
Situation 2 (ok):
If I’ll physically take off cable from eth1 port (WAN) then in LuCi in Network, IPv4 WAN Status eth1
Type: dhcp
Address: 192.168.9.100
Netmask: 255.255.255.0
Gateway: 192.168.9.1
DNS 1: 192.168.9.1
DNS 2: 192.168.9.1
will change for eth2 or eth3 – and also internet will work
eth2
Type: dhcp
Address: 192.168.9.100
Netmask: 255.255.255.0
Gateway: 192.168.9.1
DNS 1: 192.168.9.1
DNS 2: 192.168.9.1

Or
eth3
Type: dhcp
Address: 192.168.10.100
Netmask: 255.255.255.0
Gateway: 192.168.10.1
DNS 1: 192.168.10.1
DNS 2: 192.168.10.1

Situation 3 (fail):
But if there’ll any problems (for example: I’m reaching traffic limit) with GSM 1 (192.168.8.1) when
In LuCi in Overview
Network, IPv4 WAN Status, eth1 I see:
Type: dhcp
Address: 192.168.8.100
Netmask: 255.255.255.0
Gateway: 192.168.8.1
DNS 1: 192.168.8.1
DNS 2: 192.168.8.1
Mwan3 puts WAN in offline mode (thus pings do not pass thru that interface) but doesn’t changes here eth1 with eth2 or eth3 and of course internet stops.
I don’t know how to solve that problem.
Does anyone can help me?

Post #1622

tuthieu

14 Jan 2018, 16:49

Hello,I have got a problem with gateway.
I have 3 wans,all are same gateway configured by ISP.
WAN1 is lan
WAN2 and WAN3 are wlan
I can only combine 1 lan and 1 wlan.
But can't combine 2 wlan.

The discussion might have continued from here.

Page 65 of 65