Thanks very much to you and Arfett for creating mwan3 and the luci plugin.
I have tested it with two cable modem connections (one with DHCP, one static IPs) with static source IP policy-based routing, and it is working well overall. This is with a TPLink WR1043ND using the ar71xx packages from your web site running on OpenWrt 12.09 beta 1.
I have some questions on usage:
1. Is there a way to specific which WAN IP outgoing traffic should come from? For example, on the interface with the static IPs, I have five public IPs assigned and would like specified internal servers go to out IP1, IP2, etc. matching up to public DNS names pointing to IP1, IP2, etc. However, when I direct traffic from server1 and server2 out this interface, all traffic comes from a single source IP, the main IP of the interface. (I have added the four other IPs as IP aliases on the interface.) I tried using Source NATing for this, but it didn't work at least initially. If you have any advice on how to do this, that would be appreciated.
2. If I want all IPs in a given subnet to always send traffic out interface WAN2 except that, if WAN2 is down, then they should use WAN1, is the policy "wan2_pri_wan1_sec" the correct one to use?
3. The rules have autogenerated names such as cfg0d92bd. Is it OK to change these to use more descriptive rule names such as "DMZ subnet source to use WAN2"?
4. If an interface fails the ping test, I would like to get an alert of some kind. Is there a suggested way to get this? Send the syslog to a remote syslog server and look for a specific syslog alert string there?
5. To control the time for an interface failover, is it (Ping interval+Ping timeout) in seconds x Interface down number of pings? For example, the default configuration is a 2 second ping timeout and a 5 second ping interval, and 3 failed pings to mark an interface down, so the sequence would be ping 1 works, interface fails right after, wait 5 sec, ping 2 fails (2 sec timeout), wait 5 sec, ping 3 fails (2 sec timeout), wait 5 sec, ping 4 fails (2 sec), initiate failover to other interface? This would be 21 seconds plus the failover time.
6. LUCI item: In the "Multiwan policy configuration" and "Multiwan rule configuration" LuCI pages, it would be nice to have the "Member used" and "Policy assigned" fields be drop-down lists to avoid typos.
7. LUCI item: In "Multiwan interface configuration", just the first Test IP shows in the web page.
8. Any news on getting these packages into the opkg repository for Attitude Adjustment?