Hi Adze,
My questions might look very silly to you but please very badly m looking for the answer.
I'm not clear with mutiwan concept and testcase, can you please provide me any document related to this.
what is the diffrence between mwan3 and luci-mutilwan ?
And also i have taken mwan3 package compiled with latest openwrt trunk and booted the image.now i will tell you what all steps i have followed :
1. created two wan connection nas0,nas1 in dhcp mode with successfull configuration.i.e i conformed by executing below command.
ping -c 1 -I nas0 www.google.com
ping -c 1 -I nas0 www.google.com
both case ping was successful.
root@OpenWrt:/# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 200.200.59.1 0.0.0.0 UG 10 0 0 nas0
0.0.0.0 200.200.60.1 0.0.0.0 UG 20 0 0 nas1
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 br-lan
200.200.59.0 0.0.0.0 255.255.255.0 U 0 0 0 nas0
200.200.60.0 0.0.0.0 255.255.255.0 U 0 0 0 nas1
2.then configured mwan3 config file
config 'interface' 'wan1'
option 'enabled' '1'
list 'track_ip' '8.8.4.4'
list 'track_ip' '8.8.8.8'
list 'track_ip' '200.200.59.1'
list 'track_ip' '208.67.220.100'
option 'reliability' '2'
option 'count' '1'
option 'timeout' '2'
option 'interval' '5'
option 'down' '3'
option 'up' '8'
option 'reroute' '0'
config 'interface' 'wan2'
option 'enabled' '1'
list 'track_ip' '8.8.8.8'
list 'track_ip' '200.200.60.1'
list 'track_ip' '200.200.60.100'
option 'reliability' '1'
option 'count' '1'
option 'timeout' '2'
option 'interval' '5'
option 'down' '3'
option 'up' '8'
option 'reroute' '0'
# Next define a member and configure metric and weight values for this member.
# Each interface can have multiple member definitions. Give each member a correct
# name (A-Z, a-z, 0-9, "_" and no spaces).
config 'member' 'wan1_m1_w3'
option 'interface' 'wan1'
option 'metric' '1'
option 'weight' '3'
config 'member' 'wan1_m2_w3'
option 'interface' 'wan1'
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'
# After that create a routing policy. A routing policy consist of one or more
# members. Give each policy a correct name (A-Z, a-z, 0-9, "_" and no spaces). You
# can create multiple policies, so that it is possible for different traffic to
# have different primary and/or backup interfaces.
config 'policy' 'wan1_only'
list 'use_member' 'wan1_m1_w3'
config 'policy' 'wan2_only'
list 'use_member' 'wan2_m1_w2'
config 'policy' 'wan1_wan2_loadbalanced'
list 'use_member' 'wan1_m1_w3'
list 'use_member' 'wan2_m1_w2'
config 'policy' 'wan1_pri_wan2_sec'
list 'use_member' 'wan1_m1_w3'
list 'use_member' 'wan2_m2_w2'
config 'policy' 'wan2_pri_wan1_sec'
list 'use_member' 'wan1_m2_w3'
list 'use_member' 'wan2_m1_w2'
# And to finish the config define your traffic rules. Rules are matched in top to
# bottom order. If you define a rule and it matches, all following rules are ignored.
#
# If the option equalize is set, mwan3 will load-balance each new session to the same
# host. If not set, it will load-balance based on destination.
config 'rule' 'rule1'
option 'src_ip' '192.168.1.0/24'
option 'proto' 'tcp'
option 'dest_port' '563'
option 'use_policy' 'wan2_only'
config 'rule' 'rule2'
option 'src_ip' '192.168.1.0/24'
option 'proto' 'tcp'
option 'dest_port' '995'
option 'use_policy' 'wan1_only'
config 'rule' 'rule3'
option 'dest_ip' '200.200.0.0/16'
option 'proto' 'tcp'
option 'dest_port' '1024:65535'
option 'equalize' '1'
option 'use_policy' 'wan1_wan2_loadbalanced'
config 'rule' 'rule4'
option 'dest_ip' '200.200.59.0/24'
option 'proto' 'tcp'
option 'dest_port' '1024:65535'
option 'use_policy' 'wan1_pri_wan2_sec'
config 'rule' 'rule5'
option 'dest_ip' '200.200.60.0/16'
option 'proto' 'udp'
option 'dest_port' '5352'
option 'use_policy' 'wan2_pri_wan1_sec'
config 'rule' 'rule6'
option 'dest_ip' '0.0.0.0/0'
option 'use_policy' 'wan1_wan2_loadbalanced'
3. my network config files as below:
root@OpenWrt:/# 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 'fd9e:8265:7b25::/48'
config interface 'lan'
option ifname 'eth0'
option type 'bridge'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'
config atm-bridge 'atm'
option vci '32'
option encaps 'llc'
option payload 'bridged'
option vpi '0'
config interface 'wan6'
option ifname '@wan'
option proto 'dhcpv6'
config interface 'wan1'
option ifname 'nas0'
option _orig_ifname 'nas0'
option _orig_bridge 'false'
option proto 'dhcp'
option metric '10'
config atm-bridge
option unit '0'
option atmdev '0'
option encaps 'llc'
option payload 'bridged'
option vci '35'
option vpi '0'
config interface 'wan2'
option proto 'dhcp'
option ifname 'nas1'
option metric '20'
4. firewall config
config defaults
option syn_flood '1'
option input 'ACCEPT'
option output 'ACCEPT'
option forward 'REJECT'
config zone
option name 'lan'
option input 'ACCEPT'
option output 'ACCEPT'
option forward 'ACCEPT'
option network 'lan'
config zone
option name 'wan'
option network 'wan1 wan2'
option input 'REJECT'
option output 'ACCEPT'
option forward 'REJECT'
option masq '1'
option mtu_fix '1'
option network 'wan wan6
5. now rebooted the board and it comes up without any issue. nas0, nas1 got ip and i can see some TX,RX pkts in both the interfaces.
6. now what should be the test case to conform that mwan3 working or not working.