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.
<<attachment: slava.vcf>>
_______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
