Problem with gateway's monitoring



  • Hello, i see several of this in System Logs:

    Oct 23 15:35:30 check_reload_status: Reloading filter
    Oct 23 15:35:30 check_reload_status: Reloading filter
    Oct 23 15:35:20 apinger: alarm canceled: IFEGW(xxx.xxx.xxx.xxx) *** down ***
    Oct 23 15:35:20 apinger: alarm canceled: DFGW(xxx.xxx.xxx.xxx) *** down ***
    Oct 23 15:35:20 apinger: ALARM: IFEGW(xxx.xxx.xxx.xxx) *** down ***
    Oct 23 15:35:20 apinger: ALARM: DFGW(xxx.xxx.xxx.xxx) *** down ***

    The two nics are on different physical network and different switch. I have also another two interface withoust this problem.
    I have also installed OpenNMS and it send me several email where detect the HTTP interface of pfsense is not responding.
    I supposed problem with my nics, but in the log i can't see an entry that say the NIC is down…
    In what log's file i can check if pfsense set interfaces to down?
    Thanks



  • I'm experiencing the same logfile pattern

    Mar 10 05:17:24	check_reload_status: Reloading filter
    Mar 10 05:17:25	apinger: alarm canceled: NLVPN(IPADDRESS) *** NLVPNdown ***
    Mar 10 05:17:31	apinger: ALARM: NLVPN(IPADDRESS) *** NLVPNdown ***
    Mar 10 05:17:33	apinger: alarm canceled: NLVPN(IPADDRESS) *** NLVPNdown ***
    Mar 10 05:17:34	apinger: alarm canceled: NLVPN(IPADDRESS) *** delay ***
    Mar 10 05:17:35	check_reload_status: Reloading filter
    Mar 10 05:17:41	apinger: ALARM: NLVPN(IPADDRESS) *** NLVPNdown ***
    Mar 10 05:17:43	apinger: alarm canceled: NLVPN(IPADDRESS) *** NLVPNdown ***
    

    and so forth, but with a nice "feature" coming with it: 100% CPU Load. I see that the above mentioned Gateway shows high pings (4.000 ms up to 20.000 ms). I'm on 2.0.2-RELEASE  (i386) built on Fri Dec 7 16:30:14 EST 2012.



  • would you happen to have the same monitor ip on both wan connections ?



  • Edit: Oh, I'm sorry, you mean Monitor IP. No, all different on all interfaces (2 WAN, 2 VPN). But both VPNs have the same gateway IP.


Log in to reply