Oh that's awesome. What about luci-app-multiwan?
Topic: Multi-WAN Load Balancing
The content of this topic has been archived between 29 Mar 2018 and 3 May 2018. Unfortunately there are posts – most likely complete pages – missing.
Page 12 of 14
skerit wrote:
Oh that's awesome. What about luci-app-multiwan?
yup, same place. If you just install 10.03.1-rc4 on your device both applications should be available through the opkg package manager by default.
I installed multiwan, but somehow luci-app-multiwan is not in there.
I also can't find it in http://downloads.openwrt.org/backfire/1 … /packages/
skerit wrote:
I installed multiwan, but somehow luci-app-multiwan is not in there.
I also can't find it in http://downloads.openwrt.org/backfire/1 … /packages/
I thought it was in there looks like you might have to build it for yourself.
How do I setup multiwan when the second wan link is actually a vpn established over the first wan link. Namely a tap tunnel with openvpn.
During boot the tap device is nonexistent (I configure the address with an "up" script), so I cant really define 'wan2' in config/network.
Hi
I have a new openwrt build (trunk) with one lan connection, one ethernet wan connection and two possible 3g connections, depending
on what USB dongle is inserted in the router.
I have configured multiwan with all three interfaces, with wan failing over to 3g-1 failing over to 3g-2 failing over to wan.
When the system starts, none of the connections are active.
If I plug in one of the 3g cards, the link comes up fine, and the route appears in the routing table, but multiwan never sees it
come up.
Any hints?
Hi,
i'm trying to configure multiwan with a package for wireless mesh networking (wing). Wing creates a new section in /etc/config/network that looks like:
config 'interface' 'mesh'
option 'proto' 'wing'
option 'profile' 'bulk'
option 'rc' 'minstrel'
option 'ls' 'fcfs'
option 'metric' 'wcett'
option 'prefix' '6'
option 'period' '10000'
option 'tau' '100000'
option 'debug' 'false'
The multiwan config that I'm using is:
config 'multiwan' 'config'
option 'default_route' 'wan'
option 'debug' '1'
config 'interface' 'wan'
option 'weight' '10'
option 'health_interval' '10'
option 'icmp_hosts' 'dns'
option 'icmp_count' '3'
option 'timeout' '3'
option 'health_fail_retries' '3'
option 'health_recovery_retries' '5'
option 'failover_to' 'mesh'
option 'dns' 'auto'
config 'interface' 'mesh'
option 'weight' '10'
option 'health_interval' '10'
option 'icmp_hosts' '127.0.0.1'
option 'timeout' '3'
option 'health_fail_retries' '3'
option 'health_recovery_retries' '5'
option 'dns' '208.67.222.222 208.67.220.220'
basically I would like to fallback to the mesh interface when the wan fails. However in the logs I get:
Jan 1 19:43:33 Wing user.notice multiwan: mesh has failed and is currently offline.
Which requirements shall an interface satisfy in order to be marker as available by multiwan?
R.
can you $>ping -I mesh 127.0.0.1
instead of using icmp_hosts 127.0.0.1 use icmp_hosts disabled
that's all i got...
same result with icmp_hosts set to disabled:
config 'interface' 'mesh'
option 'weight' '10'
option 'health_interval' '10'
option 'icmp_hosts' 'disabled'
option 'timeout' '3'
option 'health_fail_retries' '3'
option 'health_recovery_retries' '5'
option 'dns' '208.67.222.222 208.67.220.220'
In the log I still get:
Apr 22 17:04:11 Wing user.notice multiwan: Succesfully Initialized on Fri, 22 Apr 2011 17:04:11 +0000.
Apr 22 17:04:12 Wing user.notice multiwan: mesh has failed and is currently offline.
I do not know if this can help:
root@Wing:/tmp/state# uci -p /var/state/ show network.mesh
network.mesh=interface
network.mesh.proto=wing
network.mesh.profile=bulk
network.mesh.rc=minstrel
network.mesh.ls=fcfs
network.mesh.metric=wcett
network.mesh.prefix=6
network.mesh.period=10000
network.mesh.tau=100000
network.mesh.debug=false
network.mesh.ifname=wing-mesh
network.mesh.device=wing-mesh
Shall the DNSes specified in the multiwan configuration be reachable over a certain interface in order to have that interface marked as available by multiwan?
Is there any way to use a 3G stick as backup connection? I have two DSL connections. In the case both are not working I want so switch to 3G/ UMTS stick. Cause of connection cost I don't want the 3G to be active all the time. It should only be enabled on demand.
Thanks,
Gunnar
hamvil wrote:
Shall the DNSes specified in the multiwan configuration be reachable over a certain interface in order to have that interface marked as available by multiwan?
I believe that the DNS addresses that you list are the ones that are used (for DNS) when that connection is active, be it for load balancing or in the failover chain.
I also believe that they can be used for viability testing if the icmp_host is set to DNS for the interface. icmp_host can be either gateway, dns, disable, or explicit ip address.
I have no experience with mesh, so I'm not entirely sure what the problem coule be. If you search through the multiwan script (/usr/bin/multiwan) you can find that the viability checking is done using this function
ping_test() {
echo "$icmp_hosts" | while read icmp_test_host; do
ping -c "$icmp_count" -W $timeout -I $ifname $icmp_test_host 2>&1 | grep -o "round-trip"
done
}So if you can >ping -I mesh <ping_destination> then the interface should not be turning up as offline.
... Actually now that I look at it I think the grep in this function might be wrong. If you change it to grep -o "ttl=" you might get a better result.
sur4die wrote:
I also believe that they can be used for viability testing if the icmp_host is set to DNS for the interface. icmp_host can be either gateway, dns, disable, or explicit ip address.
I've set icmp_host to disabled, so the script should not try to ping anything, right?
hamvil wrote:
sur4die wrote:I also believe that they can be used for viability testing if the icmp_host is set to DNS for the interface. icmp_host can be either gateway, dns, disable, or explicit ip address.
I've set icmp_host to disabled, so the script should not try to ping anything, right?
actually, my bad. health_interval must equal 0 or "disable" to turn of the viability test.
(Last edited by sur4die on 28 Apr 2011, 15:35)
Actually it seems to me that the scripts requires that the gateway field is set for a certain interface:
uci -P /var/state/ show network.wan.gateway
network.wan.gateway=192.168.9.254
But for my mesh interface I have:
uci -P /var/state/ show network.mesh.gateway
uci: Entry not found
Could this be the problem?
(the mesh does not have a gateway in that the best gateway is choosen dinamically by the routing daemon. I could set it to a static value, for example the interface address. Would this be compatible with the logic of the script.
Installing the multiwan package from the FTP site(ftp://ftp.netlab7.com/multiwan_1.0.18.ipk) works on the arokh version (r26801) build for the WNDR3700. Installing the luci package (ftp://ftp.netlab7.com/luci-app-multiwan_1.0.16.ipk) however gives:
/usr/lib/lua/luci/template.lua:102: Error in template admin_system/packages: /usr/lib/lua/luci/ccache.lua:81: error loading module 'luci.tools.webadmin' from file '/usr/lib/lua/luci/tools/webadmin.lua':
/usr/lib/lua/luci/tools/webadmin.lua: bad header in precompiled chunk
stack traceback:
[C]: in function 'error'
/usr/lib/lua/luci/template.lua:102: in function </usr/lib/lua/luci/template.lua:90>
(tail call): ?
/usr/lib/lua/luci/controller/admin/system.lua:100: in function </usr/lib/lua/luci/controller/admin/system.lua:45>
(tail call): ?
/usr/lib/lua/luci/dispatcher.lua:384: in function 'dispatch'
/usr/lib/lua/luci/dispatcher.lua:146: in function </usr/lib/lua/luci/dispatcher.lua:145>Once you do this, your router is semi-bricked. I had to TFTP flash the router back to the factory image and then up again to the AA (r26801) build.
(Last edited by Sorbe on 4 May 2011, 09:22)
Sorbe, the luci component is long outdated and has a now incompatible binary format. Just use the official ones:
http://downloads.openwrt.org/snapshots/ … ar71xx.ipk
But that's the arm package, not one for broadcom 2.4, which doesn't have a luci-app-multiwan package in the repos.
sur4die wrote:
hamvil wrote:sur4die wrote:I also believe that they can be used for viability testing if the icmp_host is set to DNS for the interface. icmp_host can be either gateway, dns, disable, or explicit ip address.
I've set icmp_host to disabled, so the script should not try to ping anything, right?
actually, my bad. health_interval must equal 0 or "disable" to turn of the viability test.
Nope, even with this param set to 0 I still get:
mesh has failed and is currently offline.
I've modified the mesh daemon in such a way to set the gateway to 0.0.0.0:
network.mesh.gateway=0.0.0.0
BTW the script that brings up the mesh routing daemon runs the following command after initializing the daemon:
route add default dev wing-mesh
where "wing-mesh" is the name of the device.
Hello,
I have a problem setting up MultiWan script and VPNC.
The story:
I have 2 ISPs connected to my router ASUS Wl500gpV2, running Backfire 10.03
Installed multiwan script 1.0.18, works like a magic - I only set up 2 ISP interfaces in /etc/config/network and used standard /etc/config/multiwan - just added few rules for specific networks.
Now I'm trying to make outgoing VPNC connection running. Took my old good VPNC config file and run vpnc /etc/vpnc/myconfig.conf.
VPNC reported that it started in background and I see new route in "route" command output.
But actually new VPNC connection doesn't work, servers nehind the vpn are not reachable.
If I disable multiwan script and reboot - VPNC works perfectly. If I start it before multiwan - it works too, until it has to be restarted by timeout. Then it stops working.
The same situation happens with OpenVPN. It connects OK, create new routes via tunnel interface, but that's all - i cannot access computers behind any VPN connection.
Could anybody point me into right direction is solving my problem? I admit it should be something easy to fix, yes?
(Last edited by sergei18 on 17 May 2011, 01:17)
sergei18 wrote:
Hello,
I have a problem setting up MultiWan script and VPNC.
The story:I have 2 ISPs connected to my router ASUS Wl500gpV2, running Backfire 10.03
Installed multiwan script 1.0.18, works like a magic - I only set up 2 ISP interfaces in /etc/config/network and used standard /etc/config/multiwan - just added few rules for specific networks.Now I'm trying to make outgoing VPNC connection running. Took my old good VPNC config file and run vpnc /etc/vpnc/myconfig.conf.
VPNC reported that it started in background and I see new route in "route" command output.
But actually new VPNC connection doesn't work, servers nehind the vpn are not reachable.If I disable multiwan script and reboot - VPNC works perfectly. If I start it before multiwan - it works too, until it has to be restarted by timeout. Then it stops working.
The same situation happens with OpenVPN. It connects OK, create new routes via tunnel interface, but that's all - i cannot access computers behind any VPN connection.
Could anybody point me into right direction is solving my problem? I admit it should be something easy to fix, yes?
I'm having a similar issue with tincd+olsrd.
I tried with a custom script, first starts tincd+olsrd from one wan, then i have to wait for routes.
Only when routes are loaded i start multiwan and seems to work.
If i try to put this in a script in rc.d (start tinc, start olsr, wait for ~30 secs and the start multiwan) it partially works..some routes are still redirected to one wan, but the others are ok.
#!/bin/sh /etc/rc.common
START=99
EXTRA_COMMANDS="single"
#to restore: ln -s /etc/init.d/multiwan /etc/rc.d/S99multiwan
start () {
#if not available, add route to 192.168.13.1 (wan gw)
route add default gw 192.168.13.1
#start tincd
/etc/init.d/tinc start &
#start olsrd
/etc/init.d/olsrd start &
#now wait for routes and then start multiwan
sleep 35
/usr/bin/multiwan agent &
}
stop () {
sh /usr/bin/multiwan stop
}
restart () {
/usr/bin/multiwan restart &
}
single () {
/usr/bin/multiwan single &
}Try to replace tincd and olsrd with your vpn, here works partially 
I have another issue: most traffic is redirected through wan2 (wan== eth0.1 on my wrt54gs, wan2 == wifi on my wrt54gs used and configured as wan).
What exactly means weight?
config 'multiwan' 'config'
option 'default_route' 'balancer'
# option 'resolv_conf' '/tmp/resolv.conf.auto'
option 'health_monitor' 'serial'
# option 'debug' '1'
# wan (eth0.1)
config 'interface' 'wan'
option 'health_interval' '10'
option 'icmp_hosts' '8.8.8.8'
option 'timeout' '5'
option 'icmp_count' '3'
option 'health_fail_retries' '3'
option 'health_recovery_retries' '5'
option 'failover_to' 'wan2'
option 'dns' 'auto'
option 'weight' '1'
# wrt54gs wifi
config 'interface' 'wan2'
option 'health_interval' '10'
option 'icmp_hosts' '8.8.8.8'
option 'icmp_count' '3'
option 'timeout' '7'
option 'health_fail_retries' '7'
option 'health_recovery_retries' '5'
option 'failover_to' 'wan'
option 'dns' 'auto'
option 'weight' '1'
config 'mwanfw'
option 'dst' 'www.whatismyip.com'
option 'wanrule' 'wan2'Maybe somthing is wrong here..i tried with various weight, i simply want to balance traffic..both wans are "equal".
I have also qos-script enabled but nothing changes if i turn it off.
I'm running openwrt trunk r27153.
Hello,
I use Multi-WAN for failover. So in the case wan1 fails it switches over to wan2. But in the case wan1 is working I can't reach any hosts in the subnet of wan2.
Wan1: 11.22.33.44 / 255.255.255.0
Wan2: 22.33.44.55 / 255.255.255.0
Ping to 22.33.44.60 from a computer behind the router: host not reachable
I can ssh to the router and ping the host successfully. But I want to reach the hosts in network 22.33.44.0 from my computers in the lan.
Somebody with an idea to solve that problem?
Regards,
Gunnar
(Last edited by speedy on 24 Jun 2011, 09:46)
Hello,
When i try to run multiwan i've got a strange output:
/usr/bin/multiwan: eval: line 1: uci_get_state: not found
/usr/bin/multiwan: eval: line 1: uci_get_state: not found
/usr/bin/multiwan: eval: line 1: uci_get_state: not found
/usr/bin/multiwan: eval: line 1: uci_get_state: not found
/usr/bin/multiwan: eval: line 1: uci_get_state: not found
/usr/bin/multiwan: eval: line 1: uci_get_state: not found
i've backfire/10.03/brcm47xx/ installed.
Can it be because of manual installation? i don't find pakage in backfire/10.03/brcm47xx/packages, so i've downloaded it from snapshots/backfire/10.03.1-RC5-testing/brcm47xx/packages/
Is there any other or right way to install multiwan on 10.03/brcm47xx ?
Hi everybody!
Can somebody pleaseeee help me about multiwan?
I have installed Backfire 10.03.1-rc4 on MikroTik RB433AH. When I installed and set-up multiwan it was not working! I think, but I'm not sure, that I have a problem with my mangle table. I read all posts on this topic, but I can't see that people had problems with that. I don't know how to solve this problem, so please help me. Below, you can find my config files:
routing tables:
root@OpenWrt:/# cat /etc/iproute2/rt_tables
#
# reserved values
#
255 local
254 main
253 default
0 unspec
#
# local
#
#1 inr.ruhep
#
170 LoadBalancer
171 MWAN1
172 MWAN2
root@OpenWrt:/#MWAN1 routing table:
root@OpenWrt:/# ip route show table MWAN1
192.168.1.0/24 dev ath1 proto kernel scope link src 192.168.1.101
192.168.0.0/24 dev ath2 proto kernel scope link src 192.168.0.2
192.168.10.0/24 dev br-lan proto kernel scope link src 192.168.10.1
default via 192.168.1.1 dev ath1 proto static src 192.168.1.101
root@OpenWrt:/#MWAN2:
root@OpenWrt:/# ip route show table MWAN2
192.168.1.0/24 dev ath1 proto kernel scope link src 192.168.1.101
192.168.0.0/24 dev ath2 proto kernel scope link src 192.168.0.2
192.168.10.0/24 dev br-lan proto kernel scope link src 192.168.10.1
default via 192.168.0.1 dev ath2 proto static src 192.168.0.2
root@OpenWrt:/#LoadBalancing table:
root@OpenWrt:/# ip route show table LoadBalancer
192.168.1.0/24 dev ath1 proto kernel scope link src 192.168.1.101
192.168.0.0/24 dev ath2 proto kernel scope link src 192.168.0.2
192.168.10.0/24 dev br-lan proto kernel scope link src 192.168.10.1
default proto static
nexthop via 192.168.1.1 dev ath1 weight 10
nexthop via 192.168.0.1 dev ath2 weight 10
root@OpenWrt:/#RPDB:
root@OpenWrt:/# ip rule show
0: from all lookup local
9: from all fwmark 0x1 lookup LoadBalancer
10: from 192.168.1.101 lookup MWAN1
11: from all fwmark 0x10 lookup MWAN1
20: from 192.168.0.2 lookup MWAN2
21: from all fwmark 0x20 lookup MWAN2
32766: from all lookup main
32767: from all lookup default
root@OpenWrt:/#mangle table:
root@OpenWrt:/# iptables -t mangle -L
Chain PREROUTING (policy ACCEPT)
target prot opt source destination
MultiWan all -- anywhere anywhere
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
MultiWan all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
MultiWan all -- anywhere anywhere
Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
MultiWan all -- anywhere anywhere
Chain FW1MARK (5 references)
target prot opt source destination
Chain FW2MARK (3 references)
target prot opt source destination
Chain FastBalancer (0 references)
target prot opt source destination
Chain LoadBalancer (0 references)
target prot opt source destination
Chain MultiWan (4 references)
target prot opt source destination
MultiWanPreHandler all -- anywhere anywhere
MultiWanRules all -- anywhere anywhere
MultiWanLoadBalancer all -- anywhere anywhere
MultiWanDNS all -- anywhere anywhere
MultiWanPostHandler all -- anywhere anywhere
Chain MultiWanDNS (1 references)
target prot opt source destination
FW1MARK tcp -- anywhere dns6.sbb.rs tcp dpt:53
FW1MARK udp -- anywhere dns6.sbb.rs udp dpt:53
FW1MARK tcp -- anywhere dns7.sbb.rs tcp dpt:53
FW1MARK udp -- anywhere dns7.sbb.rs udp dpt:53
FW2MARK tcp -- anywhere 192.168.0.1 tcp dpt:53
FW2MARK udp -- anywhere 192.168.0.1 udp dpt:53
Chain MultiWanLoadBalancer (1 references)
target prot opt source destination
Chain MultiWanPostHandler (1 references)
target prot opt source destination
Chain MultiWanPreHandler (1 references)
target prot opt source destination
FW1MARK all -- anywhere anywhere state NEW
FW2MARK all -- anywhere anywhere state NEW
Chain MultiWanRules (1 references)
target prot opt source destination
root@OpenWrt:/#firewall:
root@OpenWrt:/# cat /etc/config/firewall
config 'defaults'
option 'syn_flood' '1'
option 'input' 'ACCEPT'
option 'output' 'ACCEPT'
option 'forward' 'ACCEPT'
option 'drop_invalid' '1'
config 'zone'
option 'name' 'lan'
option 'input' 'ACCEPT'
option 'output' 'ACCEPT'
option 'forward' 'REJECT'
option 'network' 'lan'
config 'zone'
option 'name' 'wan'
option 'masq' '1'
option 'input' 'ACCEPT'
option 'output' 'ACCEPT'
option 'forward' 'ACCEPT'
option 'mtu_fix' '1'
option 'network' 'wan wan2'
config 'forwarding'
option 'src' 'lan'
option 'dest' 'wan'
config 'forwarding'
option 'src' 'wan'
option 'dest' 'lan'
config 'rule'
option 'src' 'wan'
option 'proto' 'udp'
option 'dest_port' '68'
option 'target' 'ACCEPT'
config 'rule'
option 'src' 'wan'
option 'proto' 'icmp'
option 'icmp_type' 'echo-request'
option 'target' 'ACCEPT'
config 'include'
option 'path' '/etc/firewall.user'
root@OpenWrt:/#multiwan:
root@OpenWrt:/# cat /etc/config/multiwan
config 'multiwan' 'config'
option 'default_route' 'balancer'
config 'interface' 'wan'
option 'weight' '10'
option 'health_interval' '10'
option 'icmp_hosts' 'dns'
option 'timeout' '3'
option 'health_fail_retries' '3'
option 'health_recovery_retries' '5'
option 'failover_to' 'balancer'
option 'dns' 'auto'
config 'interface' 'wan2'
option 'weight' '10'
option 'health_interval' '10'
option 'icmp_hosts' 'dns'
option 'timeout' '3'
option 'health_fail_retries' '3'
option 'health_recovery_retries' '5'
option 'failover_to' 'balancer'
option 'dns' 'auto'
config 'mwanfw'
option 'dst' 'www.whatismyip.com'
option 'wanrule' 'fastbalancer'
root@OpenWrt:/#Id like to share with You result of a day of my researching dual 3G dongle loadbalancing connection.
After having two working 3G modem setup You need to:
1. Set 2 zones in firewall - each for one modem. It seems one zone isnt enough for multiwan.
2. Check if interfaces are configured to have
option 'peerdns' '0'
option 'defaultroute' '0'This is the option which render loadbalancing finally start to work properly on both interfaces
3. set performance loadbalancer. Compatibility mode didnt worked for me.
Heres my configs:
Network:
config 'interface' 'loopback'
option 'ifname' 'lo'
option 'proto' 'static'
option 'ipaddr' '127.0.0.1'
option 'netmask' '255.0.0.0'
config 'interface' 'lan'
option 'ifname' 'eth0.1'
option 'type' 'bridge'
option 'proto' 'static'
option 'ipaddr' '192.168.1.1'
option 'netmask' '255.255.255.0'
config 'interface' 'wan'
option 'proto' '3g'
option 'service' 'umts'
option 'device' '/dev/ttyUSB0'
option 'apn' 'vpn'
option 'pincode' '5165'
option 'username' 'vpn'
option 'password' 'vpn'
option 'maxwait' '20'
option 'peerdns' '0'
option 'defaultroute' '0'
config 'interface' 'wan2'
option 'proto' '3g'
option 'service' 'umts'
option 'device' '/dev/ttyUSB3'
option 'apn' 'erainternet'
option 'pincode' '6093'
option 'username' 'erainternet'
option 'password' 'erainternet'
option 'maxwait' '10'
option 'peerdns' '0'
option 'defaultroute' '0'
config 'switch'
option 'name' 'rtl8366s'
option 'reset' '1'
option 'enable_vlan' '1'
option 'blinkrate' '2'
config 'switch_vlan'
option 'device' 'rtl8366s'
option 'vlan' '1'
option 'ports' '0 1 2 3 5t'
config 'switch_port'
option 'device' 'rtl8366s'
option 'port' '1'
option 'led' '6'
config 'switch_port'
option 'device' 'rtl8366s'
option 'port' '2'
option 'led' '9'
config 'switch_port'
option 'device' 'rtl8366s'
option 'port' '5'
option 'led' '2'Firewall:
config 'defaults'
option 'syn_flood' '1'
option 'input' 'ACCEPT'
option 'output' 'ACCEPT'
option 'forward' 'REJECT'
option 'drop_invalid' '1'
config 'zone'
option 'name' 'lan'
option 'network' 'lan'
option 'input' 'ACCEPT'
option 'output' 'ACCEPT'
option 'forward' 'REJECT'
config 'zone'
option 'name' 'wan'
option 'input' 'REJECT'
option 'output' 'ACCEPT'
option 'forward' 'REJECT'
option 'masq' '1'
option 'mtu_fix' '1'
option 'network' 'wan'
config 'rule'
option 'src' 'wan'
option 'proto' 'udp'
option 'dest_port' '68'
option 'target' 'ACCEPT'
option 'family' 'ipv4'
config 'rule'
option 'src' 'wan'
option 'proto' 'icmp'
option 'icmp_type' 'echo-request'
option 'family' 'ipv4'
option 'target' 'ACCEPT'
config 'rule'
option 'src' 'wan'
option 'proto' 'icmp'
list 'icmp_type' 'echo-request'
list 'icmp_type' 'destination-unreachable'
list 'icmp_type' 'packet-too-big'
list 'icmp_type' 'time-exceeded'
list 'icmp_type' 'bad-header'
list 'icmp_type' 'unknown-header-type'
list 'icmp_type' 'router-solicitation'
list 'icmp_type' 'neighbour-solicitation'
option 'limit' '1000/sec'
option 'family' 'ipv6'
option 'target' 'ACCEPT'
config 'rule'
option 'src' 'wan'
option 'dest' '*'
option 'proto' 'icmp'
list 'icmp_type' 'echo-request'
list 'icmp_type' 'destination-unreachable'
list 'icmp_type' 'packet-too-big'
list 'icmp_type' 'time-exceeded'
list 'icmp_type' 'bad-header'
list 'icmp_type' 'unknown-header-type'
option 'limit' '1000/sec'
option 'family' 'ipv6'
option 'target' 'ACCEPT'
config 'include'
option 'path' '/etc/firewall.user'
config 'forwarding'
option 'dest' 'wan'
option 'src' 'lan'
config 'rule'
option 'target' 'ACCEPT'
config 'zone'
option 'name' 'wan2'
option 'forward' 'REJECT'
option 'output' 'ACCEPT'
option 'network' 'wan2'
option 'input' 'REJECT'
option 'masq' '1'
option 'mtu_fix' '1'
config 'forwarding'
option 'dest' 'wan2'
option 'src' 'lan'Multiwan:
config 'multiwan' 'config'
option 'default_route' 'fastbalancer'
option 'debug' '1'
config 'interface' 'wan'
option 'health_interval' '10'
option 'timeout' '3'
option 'health_fail_retries' '3'
option 'health_recovery_retries' '5'
option 'failover_to' 'fastbalancer'
option 'dns' '8.8.8.8 8.8.4.4'
option 'weight' '5'
option 'icmp_hosts' 'gateway'
config 'interface' 'wan2'
option 'health_interval' '10'
option 'timeout' '3'
option 'health_fail_retries' '3'
option 'health_recovery_retries' '5'
option 'weight' '5'
option 'failover_to' 'fastbalancer'
option 'dns' '208.67.222.222 208.67.220.220'
option 'icmp_hosts' 'dns'
config 'mwanfw'
option 'wanrule' 'fastbalancer'Still I have problems with "Health Monitor" - simply, it dont work at all. At reboot one modem is up automatically but second needs manual start. Anybody have any idea what to do to make it work?
Sorry, posts 301 to 300 are missing from our archive.
Page 12 of 14