http://www.right.com.cn/forum/forum.php?mod=viewthread&tid=178799
 
# This is a mwan3 example config. For MWAN3 to work your need at least this is the MWAN3 Setup example. You need at least the following to run MWAN3)
#
#-2 Interfaces (2 connectors)
#-2 Members (2 member)
#-1 policy (one strategy)
# 1 rule (1 rules)
#
# The Define all your WAN interfaces. Interface name must match with the
# name used in your network configuration:
(All WAN ports must be set first, and the name of the WAN will be the same as the WAN port name in the network configuration file.)
Config ' interface ' wan1 '
Option ' enabled ' 1 '
List ' track_ip ' 8.8.4.4 ' (these IP are test IP, verify whether can ping the pass. There are 4 of them, the first two are free DNS servers provided by Google, and domestic access should be relatively slow. )
List ' track_ip ' 8.8.8.8 '
List ' track_ip ' 208.67.222.222 '
List ' track_ip ' 208.67.220.220 '
Option ' Reliability ' 2 ' (reliability, testing the reliability of the above IP, must be a number of responsive links. Simple is to ask the above IP several can ping pass)
Option ' count ' 1 ' (ping several times)
Option ' Timeout ' 2 ' (timeout after ping after a few seconds)
Option ' Interval ' 5 ' (time interval between multiple pings)
Option ' Down ' 3 ' (when a few pings are found, the WAN is off line)
Option ' Up ' 8 ' (when several ping can be successful, it is assumed that the line has been dropped and the WAN port is online)
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 '
# Next Define a and configure metric and weight values for this. (Then set the weight and hop value of a member)
# Each interface can have multiple member definitions. Give each member a correct, each interface can contain multiple membership definitions. Each member name must have the correct name)
# name (A-Z, A-Z, 0-9, "_" and no spaces).
Config ' member ' WAN1_M1_W3 '
Option ' interface ' Wan1 '
Option ' metric ' 1 ' (range of 1-1000)
Option ' Weight ' 3 ' (range of 1-1000)
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 this create a routing policy. A routing policy consist of one or more (and then creates a routing policy.) Includes one or several members. Each policy must have the correct name. Multiple policies can be created so that different traffic can take different primary/secondary WAN ports.
# members. Give each policy a correct name (A-Z, A-Z, 0-9, "_" and no spaces). You
# can create multiple policies, so this it is possible for different traffic to
# have different primary and/or backup interfaces.
Config ' policy ' wan1_only ' (Only go wan1)
List ' Use_member ' WAN1_M1_W3 '
Config ' policy ' wan2_only ' (Only go wan2)
List ' Use_member ' wan2_m1_w2 '
Config ' policy ' wan1_wan2_loadbalanced ' (wan1, wan2 load Balancing)
List ' Use_member ' WAN1_M1_W3 '
List ' Use_member ' wan2_m1_w2 '
Config ' policy ' wan1_pri_wan2_sec ' (Wan1 master, wan2 Times)
List ' Use_member ' WAN1_M1_W3 '
List ' Use_member ' wan2_m2_w2 '
Config ' policy ' wan2_pri_wan1_sec ' (wan2 master, wan1 Times)
List ' Use_member ' WAN1_M2_W3 '
List ' Use_member ' wan2_m1_w2 '
# and to finish the config define your traffic rules. The rules are matched in the top to (and finally sets the communication rule.) He is from the rules you set up to match from top to bottom, if you define a rule match, the following rules will be ignored. If the balance option has been set, MWAN3 will make each new package go to the same destination host address to load balance, if not set, then MWAN3 will automatically load balance according to the destination address.
# Bottom Order. If you are define a and it matches, all following rules are ignored.
#
# If The option equalize is set, mwan3 'll load-balance each new session to the same
# host. If not set, it would load-balance based on destination.
Config ' rule '
Option ' Src_ip ' 192.168.21.0/24 ' (source IP, support for network segment representation)
Option ' Proto ' TCP ' (Specify protocol)
Option ' Dest_port ' 563 ' (Destination port)
Option ' Use_policy ' wan2_only ' (Specify which strategy to go above)
Config ' rule '
Option ' src_ip ' 192.168.21.0/24 '
Option ' proto ' ' TCP '