Multiwan internet dropps and doesnt always recover

[grandrivers]

having issues with multiwan dropping and not recovering wan is pppoe and opt1 is dhcp generally requires at a restart of apinger

2.2-BETA (amd64)
built on Mon Dec 01 14:00:17 CST 2014
FreeBSD 10.1-RELEASE

this is a full install on bare metal

[cmb]

Nothing to go on there. What doesn't recover? Define "drops", which WAN drops and what does "drop" mean? ISP failure, or?

[grandrivers]

yes isp failure which happens a lot very lot, and isp  upstream supplier failure  more and more as they plugged there connection
cmts had power flash today dropping all modems my modem came back but had to reset apinger to make it realize it came back after waiting five minutes

my windstream dsl pppoe handled by pfsense changes ip's frequently maybe every other day to daily and it has been getting stuck at pending has been getting stuck at pending on boot up

and some where in the mix i get a mail storm like ~60 messages in 3-4 min

at surface looks like it related to the other 2 problems ive been seeing all related to apinger in some way

https://forum.pfsense.org/index.php?topic=84410.0

https://forum.pfsense.org/index.php?topic=84337.0

updated to
2.2-BETA (amd64)
built on Tue Dec 02 17:19:37 CST 2014
FreeBSD 10.1-RELEASE

seems better too early to tell

[grandrivers]

if you ever need a couple of unreliable internet connection into one box for testing anything I have a couple of flaky ones

[grandrivers]

gateway status doesnt agree with log

SystemFirewallDHCPPortal AuthIPsecPPPVPNLoad BalancerOpenVPNNTPSettings
GeneralGatewaysRoutingResolverWireless
Last 1000 system log entries
Dec 2 23:24:10 apinger: Polling, timeout: 0.806s
Dec 2 23:24:09 apinger: Polling, timeout: 0.129s
Dec 2 23:24:09 apinger: (avg. loss: 0.0%)
Dec 2 23:24:09 apinger: (avg: 0.000ms)
Dec 2 23:24:09 apinger: #10002 from DSL_DHCP(8.8.4.4) delay: 61.549ms/62.321ms/-0.193ms received = 10001
Dec 2 23:24:09 apinger: Polling, timeout: 0.153s
Dec 2 23:24:09 apinger: (avg. loss: 0.0%)
Dec 2 23:24:09 apinger: (avg: 38.685ms)
Dec 2 23:24:09 apinger: #10002 from CABLEMODEM_DHCP(8.8.8.8) delay: 38.159ms/40.090ms/386.848ms received = 9982
Dec 2 23:24:09 apinger: Polling, timeout: 0.191s
Dec 2 23:24:09 apinger: Recently lost packets: 0
Dec 2 23:24:09 apinger: Sending ping #10002 to DSL_DHCP (8.8.4.4)
Dec 2 23:24:09 apinger: Recently lost packets: 0
Dec 2 23:24:09 apinger: Sending ping #10002 to CABLEMODEM_DHCP (8.8.8.8)
Dec 2 23:24:08 apinger: Polling, timeout: 0.938s
Dec 2 23:24:08 apinger: (avg. loss: 0.0%)
Dec 2 23:24:08 apinger: (avg: 0.058ms)
Dec 2 23:24:08 apinger: #10001 from DSL_DHCP(8.8.4.4) delay: 60.886ms/62.106ms/0.579ms received = 10000
Dec 2 23:24:08 apinger: Polling, timeout: 0.961s
Dec 2 23:24:08 apinger: (avg. loss: 0.0%)
Dec 2 23:24:08 apinger: (avg: 38.878ms)
Dec 2 23:24:08 apinger: #10001 from CABLEMODEM_DHCP(8.8.8.8) delay: 38.241ms/38.477ms/388.779ms received = 9981
Dec 2 23:24:08 apinger: Polling, timeout: 0.999s
Dec 2 23:24:08 apinger: Recently los


[grandrivers]

Dec 2 23:32:53 apinger: Polling, timeout: 0.937s
Dec 2 23:32:53 apinger: (avg. loss: 0.0%)
Dec 2 23:32:53 apinger: (avg: 0.547ms)
Dec 2 23:32:53 apinger: #10523 from DSL_DHCP(8.8.4.4) delay: 62.484ms/62.379ms/5.475ms received = 10522


[hmh]

Hi!

I having this problem on 2.1.5 too

To resolve this increase Probe Interval on all gateways
I set value to 10 sec
No problems after that