MultiWAN: WAN1(Static +PPTP) and WAN2 (DHCP). Gateway at WAN2 didn`t come alive.

[krylou]

MultiWAN: WAN1(Static +PPTP) alias GW_OPT2 and WAN2 (DHCP)  . Gateway at WAN2 always down once Monitor IP ping fails. It will never get up even if WAN2 Monitor IP is ailve.
Workaround: go to System -Gateways -> edit WAN2 Gateway and without changes click save. I suppose that triggers apinger to gather info about Gateways and in serveral seconds BOTH WAN1 and WAN2 treated as alive and all is working great till next fail at WAN2.

Pfsense:2.0.2 stable release.
LAN nic - Intel
WAN1 nic - Intel
WAN2 nic - Realtek

Allow default gateway switching - selected and default GW not selected at Gateways tab.

GW IP: WAN2 dynamic (always getting 192.168.2.2 with WAN2 IP 192.168.2.10). WAN1 ( getting dynamically during PPTP initiation, usually 81.25.33.1), so I have different IPs for Gateways.
Monitor GW IP`s: WAN1 8.8.8.8, WAN2 8.8.4.4.
See more info at screenshots.

…........12 hours passed after WAN2 was really down.. Real status of WAN2 Gateway was alive in several minutes after fail, but pfsense still treating it as down..

GW_OPT2 - is WAN1
ADSL2GW - is WAN2

var/log/system.log

...............
Mar 24 20:57:51 pfsense apinger: ALARM: GW_OPT2(8.8.8.8)  *** delay ***
Mar 24 20:58:01 pfsense check_reload_status: Reloading filter
Mar 24 20:58:03 pfsense php: : MONITOR: ADSL2GW is down, removing from routing group
Mar 24 20:58:03 pfsense php: : MONITOR: ADSL2GW is down, removing from routing group
Mar 24 20:58:03 pfsense php: : MONITOR: ADSL2GW is down, removing from routing group
Mar 24 20:58:05 pfsense apinger: alarm canceled: GW_OPT2(8.8.8.8)  *** delay ***
Mar 24 20:58:15 pfsense check_reload_status: Reloading filter
Mar 24 20:58:18 pfsense php: : MONITOR: ADSL2GW is down, removing from routing group
Mar 24 20:58:18 pfsense php: : MONITOR: ADSL2GW is down, removing from routing group
Mar 24 20:58:18 pfsense php: : MONITOR: ADSL2GW is down, removing from routing group
Mar 24 21:00:36 pfsense check_reload_status: Syncing firewall
Mar 24 21:00:38 pfsense php: /system_gateways.php: ROUTING: setting default route to 10.10.20.1
Mar 24 21:00:38 pfsense check_reload_status: Reloading filter
Mar 24 21:00:38 pfsense php: /system_gateways.php: Removing static route for monitor 8.8.8.8 and adding a new route through 81.25.33.1
Mar 24 21:00:38 pfsense php: /system_gateways.php: Removing static route for monitor 8.8.4.4 and adding a new route through 192.168.2.2
Mar 24 21:00:38 pfsense apinger: Exiting on signal 15.
Mar 24 21:00:39 pfsense apinger: Starting Alarm Pinger, apinger(39121)
Mar 24 21:00:40 pfsense php: : Gateways status could not be determined, considering all as up/active.
Mar 24 21:00:40 pfsense php: : Gateways status could not be determined, considering all as up/active.
Mar 24 21:00:40 pfsense php: : Gateways status could not be determined, considering all as up/active.
...................

Around 21.00 i did applied workaround.

Any ideas how to fix this?









[krylou]

The same issue at Pfsense 2.0.3 stable release.
LAN - static ip
WAN - static ip
WAN2 - statis ip

WAN and WAN2 has internet access through different providers.