Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    [ASK]DONE! Pfsense aku drop/lost connection setiap 2-3 minit =(

    Indonesian
    2
    4
    2.4k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      syedadi
      last edited by

      Sejak smnggu lalu, pfsens aku selalu lost connection…..kejadian ini selalu berlaku selepasa di on dalam masa 1 jam...bila dah resrart connection akan bertahan dalam masa 1 jam, selepas itu akan ada lost connection dgn interval 2-3 minit skali...tengok log system aku dibawah ini...

      Aug 24 14:13:00 check_reload_status: Reloading filter
      Aug 24 14:12:50 apinger: ALARM: TM(218.111.XX.X) *** loss ***
      Aug 24 14:12:07 check_reload_status: Reloading filter
      Aug 24 14:11:57 apinger: alarm canceled: TM(218.111.XX.X) *** loss ***
      Aug 24 14:10:35 check_reload_status: Reloading filter
      Aug 24 14:10:25 apinger: ALARM: TM(218.111.XX.X) *** loss ***
      Aug 24 14:07:15 check_reload_status: Reloading filter
      Aug 24 14:07:05 apinger: alarm canceled: TM(218.111.XX.X) *** loss ***
      Aug 24 14:06:11 check_reload_status: Reloading filter
      Aug 24 14:06:01 apinger: ALARM: TM(218.111.XX.X) *** loss ***
      Aug 24 14:04:59 check_reload_status: Reloading filter
      Aug 24 14:04:58 check_reload_status: Reloading filter
      Aug 24 14:04:49 apinger: alarm canceled: TM(218.111.XX.X) *** down ***
      Aug 24 14:04:48 apinger: ALARM: TM(218.111.XX.X) *** down ***
      Aug 24 14:04:48 check_reload_status: Reloading filter
      Aug 24 14:04:38 apinger: alarm canceled: TM(218.111.XX.X) *** down ***
      Aug 24 14:04:38 check_reload_status: Reloading filter
      Aug 24 14:04:28 apinger: ALARM: TM(218.111.XX.X) *** down ***
      Aug 24 14:04:16 bandwidthd: DNS timeout for 192.168.0.160: This problem reduces graphing performance
      Aug 24 14:04:16 bandwidthd: DNS timeout for 192.168.0.160: This problem reduces graphing performance
      Aug 24 14:04:00 check_reload_status: Reloading filter
      Aug 24 14:03:58 check_reload_status: Reloading filter
      Aug 24 14:03:56 bandwidthd: DNS timeout for 192.168.0.160: This problem reduces graphing performance
      Aug 24 14:03:56 bandwidthd: DNS timeout for 192.168.0.160: This problem reduces graphing performance
      Aug 24 14:03:54 bandwidthd: DNS timeout for 192.168.0.160: This problem reduces graphing performance
      Aug 24 14:03:54 bandwidthd: DNS timeout for 192.168.0.160: This problem reduces graphing performance
      Aug 24 14:03:50 apinger: alarm canceled: TM(218.111.XX.X) *** down ***
      Aug 24 14:03:48 apinger: ALARM: TM(218.111.XX.X) *** down ***
      Aug 24 14:03:44 check_reload_status: Reloading filter
      Aug 24 14:03:34 apinger: alarm canceled: TM(218.111.XX.X) *** loss ***
      Aug 24 14:02:47 check_reload_status: Reloading filter
      Aug 24 14:02:37 apinger: ALARM: TM(218.111.XX.X) *** loss ***
      Aug 24 13:59:02 check_reload_status: Reloading filter
      Aug 24 13:58:52 apinger: alarm canceled: TM(218.111.XX.X) *** loss ***
      Aug 24 13:58:24 check_reload_status: Reloading filter
      Aug 24 13:58:14 apinger: ALARM: TM(218.111.XX.X) *** loss ***
      Aug 24 13:57:24 bandwidthd: Previouse graphing run not complete… Skipping current run
      Aug 24 13:57:22 bandwidthd: Previouse graphing run not complete... Skipping current run
      Aug 24 13:57:13 check_reload_status: Reloading filter
      Aug 24 13:57:13 check_reload_status: Reloading filter
      Aug 24 13:57:11 check_reload_status: Reloading filter
      Aug 24 13:57:03 apinger: alarm canceled: TM(218.111.XX.X) *** loss ***
      Aug 24 13:57:03 apinger: alarm canceled: TM(218.111.XX.X) *** down ***
      Aug 24 13:57:01 apinger: ALARM: TM(218.111.XX.X) *** down ***
      Aug 24 13:55:50 check_reload_status: Reloading filter
      Aug 24 13:55:41 php: : Config sync not being done because of missing sync IP (normal on secondary systems).
      Aug 24 13:55:40 apinger: ALARM: TM(218.111.XX.X) *** loss ***
      Aug 24 13:55:39 check_reload_status: Syncing firewall
      Aug 24 13:54:45 check_reload_status: Reloading filter
      Aug 24 13:54:35 apinger: alarm canceled: TM(218.111.XX.X) *** loss ***
      Aug 24 13:54:00 check_reload_status: Reloading filter
      Aug 24 13:53:50 apinger: ALARM: TM(218.111.XX.X) *** loss ***
      Aug 24 13:53:37 check_reload_status: Reloading filter
      Aug 24 13:53:27 apinger: alarm canceled: TM(218.111.XX.X) *** loss ***
      Aug 24 13:53:24 kernel: pid 37454 (imspector), uid 0: exited on signal 11 (core dumped)
      Aug 24 13:53:24 imspector: SSL get peer certificate error: error:00000000:lib(0):func(0):reason(0)
      Aug 24 13:53:24 imspector: SSL get peer certificate error: error:00000000:lib(0):func(0):reason(0)
      Aug 24 13:53:24 imspector: SSL new error: error:140BA0C3:lib(20):func(186):reason(195)
      Aug 24 13:53:24 imspector: SSL new error: error:140BA0C3:lib(20):func(186):reason(195)
      Aug 24 13:52:25 check_reload_status: Reloading filter
      Aug 24 13:52:15 apinger: ALARM: TM(218.111.XX.X) *** loss ***
      Aug 24 13:49:57 check_reload_status: Reloading filter
      Aug 24 13:49:47 apinger: alarm canceled: TM(218.111.XX.X) *** loss ***
      Aug 24 13:48:35 check_reload_status: Reloading filter
      Aug 24 13:48:25 apinger: ALARM: TM(218.111.XX.X) *** loss ***
      Aug 24 13:46:55 check_reload_status: Reloading filter
      Aug 24 13:46:45 apinger: alarm canceled: TM(218.111.XX.X) *** loss ***
      Aug 24 13:46:45 check_reload_status: Reloading filter
      Aug 24 13:46:35 apinger: ALARM: TM(218.111.XX.X) *** loss ***
      Aug 24 13:45:34 check_reload_status: Reloading filter
      Aug 24 13:45:24 apinger: alarm canceled: TM(218.111.XX.X) *** down ***
      Aug 24 13:45:17 check_reload_status: Reloading filter
      Aug 24 13:45:07 apinger: ALARM: TM(218.111.XX.X) *** down ***
      Aug 24 13:45:07 check_reload_status: Reloading filter
      Aug 24 13:44:57 apinger: alarm canceled: TM(218.111.XX.X) *** down ***
      Aug 24 13:44:25 check_reload_status: Reloading filter
      Aug 24 13:44:15 apinger: ALARM: TM(218.111.XX.X) *** down ***
      Aug 24 13:36:45 check_reload_status: Reloading filter
      Aug 24 13:36:35 apinger: alarm canceled: TM(218.111.XX.X) *** loss ***
      Aug 24 13:36:31 check_reload_status: Reloading filter
      Aug 24 13:36:21 apinger: ALARM: TM(218.111.XX.X) *** loss ***
      Aug 24 13:35:20 check_reload_status: Reloading filter
      Aug 24 13:35:19 check_reload_status: Reloading filter
      Aug 24 13:35:10 apinger: alarm canceled: TM(218.111.XX.X) *** loss ***
      Aug 24 13:35:10 apinger: alarm canceled: TM(218.111.XX.X) *** down ***
      Aug 24 13:35:09 apinger: ALARM: TM(218.111.XX.X) *** down ***
      Aug 24 13:34:36 check_reload_status: Reloading filter
      Aug 24 13:34:26 apinger: ALARM: TM(218.111.XX.X) *** loss ***
      Aug 24 13:30:08 kernel: pid 31929 (imspector), uid 0: exited on signal 11 (core dumped)
      Aug 24 13:30:08 imspector: SSL get peer certificate error: error:00000000:lib(0):func(0):reason(0)
      Aug 24 13:30:08 imspector: SSL get peer certificate error: error:00000000:lib(0):func(0):reason(0)
      Aug 24 13:30:08 imspector: SSL new error: error:140BA0C3:lib(20):func(186):reason(195)
      Aug 24 13:30:08 imspector: SSL new error: error:140BA0C3:lib(20):func(186):reason(195)
      Aug 24 13:29:52 check_reload_status: Reloading filter
      Aug 24 13:29:42 apinger: alarm canceled: TM(218.111.XX.X) *** loss ***
      Aug 24 13:29:16 check_reload_status: Reloading filter
      Aug 24 13:29:06 apinger: ALARM: TM(218.111.XX.X) *** loss ***
      Aug 24 13:28:05 check_reload_status: Reloading filter
      Aug 24 13:28:04 check_reload_status: Reloading filter
      Aug 24 13:27:55 apinger: alarm canceled: TM(218.111.XX.X) *** down ***
      Aug 24 13:27:54 apinger: ALARM: TM(218.111.XX.X) *** down ***
      Aug 24 13:26:19 php: : Config sync not being done because of missing sync IP (normal on secondary systems).
      Aug 24 13:26:17 check_reload_status: Syncing firewall
      Aug 24 13:25:28 check_reload_status: Reloading filter
      Aug 24 13:25:18 apinger: alarm canceled: TM(218.111.XX.X) *** loss ***
      Aug 24 13:24:41 check_reload_status: Reloading filter
      Aug 24 13:24:31 apinger: ALARM: TM(218.111.XX.X) *** loss ***
      Aug 24 13:15:31 check_reload_status: Reloading filter
      Aug 24 13:15:31 check_reload_status: Reloading filter
      Aug 24 13:15:26 check_reload_status: Reloading filter
      Aug 24 13:15:21 apinger: alarm canceled: TM(218.111.XX.X) *** loss ***
      Aug 24 13:15:21 apinger: alarm canceled: TM(218.111.XX.X) *** down ***
      Aug 24 13:15:16 apinger: ALARM: TM(218.111.XX.X) *** down ***
      Aug 24 13:14:35 check_reload_status: Reloading filter
      Aug 24 13:14:25 apinger: ALARM: TM(218.111.XX.X) *** loss ***

      1 Reply Last reply Reply Quote 0
      • U
        ujangs
        last edited by

        http://www.facebook.com/groups/194694837234318/

        1 Reply Last reply Reply Quote 0
        • S
          syedadi
          last edited by

          @ujangs:

          http://www.facebook.com/groups/194694837234318/

          OM, aku engak punya FB….ada cara lain mau access?

          1 Reply Last reply Reply Quote 0
          • S
            syedadi
            last edited by

            Aku jugak pakai Untangle bersama2 pfsense ini…adakah UT + PfSense = problems? aku sudah unplug UT dari network, dan skarang semua network masih bertahan tiada putus selama 1 jam…. =(

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.