What is happening is your gateway is ignoring/dropping the icmp probes used by pfSense to verify your gateway is up.

You need to adjust these variables under system>>>routing>>>gateways>>>Edit next to your gateway.

Down
This defines the down time for the alarm to fire, in seconds.

Frequency Probe
This defines the frequency in seconds that an icmp probe will be sent. Default is 1 second.

Maybe change the frequency probe to 10 seconds and dead time to 2 minutes. If you have a dual wan, you obviously will want to try and keep your dead time lower.

Another solution is to find a monitor ip that doesn't drop pings.

If you have a single wan, you could disable gateway monitoring as well. The only advantage to using it on single wan is it flushes firewall states in the case of outage.

-Jonathon

On 9/21/2012 7:47 AM, [email protected] wrote:
On 21.09.2012 02:56, Vick Khera wrote:
On Tue, Sep 18, 2012 at 5:11 PM, [email protected] <mailto:[email protected]> <[email protected] <mailto:[email protected]>> wrote:

    Hi,

    Once in a while we got such errors:

     apinger:     : WANGW(x.x.x.1)  *** WANGWdown ***
     apinger: ALARM: WANGW(x.x.x.1)  *** WANGWdown ***
     apinger: alarm canceled: WANGW(x.x.x.1)  *** WANGWdown ***


What were the timestamps on those? And did pfsense actually mark your WAN GW as down?
Here is the log:
04:07:59 pfs1 apinger:     : WANGW(x.x.x.1)  *** WANGWdown ***
04:08:09 pfs1 check_reload_status: Reloading filter
04:13:17 pfs1 apinger: alarm canceled: WANGW(x.x.x.1)  *** WANGWdown ***
04:13:27 pfs1 check_reload_status: Reloading filter
04:15:38 pfs1 apinger: ALARM: WANGW(x.x.x.1)  *** WANGWdown ***
04:15:48 pfs1 check_reload_status: Reloading filter
04:16:38 pfs1 apinger: alarm canceled: WANGW(x.x.x.1)  *** WANGWdown ***
04:16:48 pfs1 check_reload_status: Reloading filter

Single random pings fail from time to time, as do all packets that get sent over the wires.
No, interface is down, and no packets can be send over via that pfsense instance. I switch traffic manually to a spare pfsense, and can see that apinger has marked WANGW down. Providers told they haven't had any outages. I'm not sure if this is pfsense misconfiguration.

Thanks.



_______________________________________________
List mailing list
[email protected]
http://lists.pfsense.org/mailman/listinfo/list

_______________________________________________
List mailing list
[email protected]
http://lists.pfsense.org/mailman/listinfo/list

Reply via email to