Temat: MWAN3 - problem w działaniu
witam,
od tygodnia męczę się z odpaleniem mwan3 na tp-link 1043nd, mam wgrany soft z luci.
w /etc/config/mwan3 mam wstawione:
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 'sticky_even'
option src_ip '0.0.0.0/0.0.0.1'
option dest_port '443'
option proto 'tcp'
option use_policy 'wan_only'
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 'wan_only'
config rule 'default_rule'
option dest_ip '0.0.0.0/0'
option use_policy 'balanced'w zakładce /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 'fd41:9548:69d9::/48'
config interface 'lan'
option ifname 'eth1'
option force_link '1'
option type 'bridge'
option proto 'static'
option netmask '255.255.255.0'
option ip6assign '60'
option ipaddr '192.168.0.1'
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '1'
option ports '0 1 2 3 4'
config switch_vlan
option device 'switch0'
option vlan '2'
option ports '5 6'
config interface 'wan'
option proto '3g'
option device '/dev/ttyUSB0'
option metric '1'
option peerdns '0'
option dns '8.8.8.8 8.8.4.4'
config interface 'wan2'
option proto 'dhcp'
option ifname 'eth2'
option metric '2'
option peerdns '0'
option dns '8.8.8.8 8.8.4.4'do routera podłączone mam dwa modemy poprzez aktywny hub, jeden to e398 a drugi 3272 hilink /z softem huawei/,
w chwili wysłania jakiegoś pakietu następuje automatyczne rozłączanie wan`ów i ich naprzmienne włączanie/ falowanie
Mon Nov 3 20:01:30 2014 user.notice mwan3: ifdown interface wan2 (unknown)
Mon Nov 3 20:01:29 2014 user.notice mwan3: ifdown interface wan2 (eth2)
Mon Nov 3 20:01:28 2014 user.notice mwan3track: Interface wan2 (eth2) is offline
Mon Nov 3 20:01:24 2014 user.notice mwan3: ifup interface wan (3g-wan)
Mon Nov 3 20:01:08 2014 user.notice mwan3: ifup interface wan2 (eth2)
Mon Nov 3 20:00:59 2014 user.notice mwan3: ifdown interface wan (3g-wan)
Mon Nov 3 20:00:58 2014 user.notice mwan3track: Interface wan (3g-wan) is offline
Mon Nov 3 20:00:57 2014 user.notice mwan3: ifdown interface wan2 (eth2)
Mon Nov 3 20:00:57 2014 user.notice mwan3track: Interface wan2 (eth2) is offline
Mon Nov 3 20:00:51 2014 user.notice mwan3: ifdown interface wan (unknown)
Mon Nov 3 20:00:48 2014 user.notice mwan3: ifdown interface wan2 (unknown)
Mon Nov 3 20:00:45 2014 user.notice mwan3: ifup interface wan2 (eth2)
osobiście nie mam już pomysłów gdzie może tkwić problem działania stabilnego oraz w load balanced.
dziękuję za wskazówki.
Pozdrawiam
szymek