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

    Netgate SG-1100 connection dropping hourly

    Scheduled Pinned Locked Moved
    Official Netgate® Hardware
    3
    4
    702
    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.
    • J
      jcdillin
      last edited by

      Hello!

      Trying to nail down an issue on a new install with a Netgate SG-1100.

      We had a standard comcast technicolor modem and recently switched over to an ARRIS SB8200 and an Netgate SG-1100. The system is working well with great speeds. But the issue is the internet is dropping out at almost exactly an hour. It only drops out for a short period but then comes back. It wasn't doing this with the stock Comcast modem. I checked in the SB8200 event logs and it's staying stable with no dropouts.

      This is what is in the log of the Netgate, i've changed the WAN cable running from the Netgate to the Arris but it's doing the same thing. Anything else I can check?

      I've changed the public IP's to x for security sake.

      May 19 10:05:47	dpinger	34229	WAN_DHCP x.x.x.x: Alarm latency 0us stddev 0us loss 100%
May 19 10:05:57	dpinger	12421	send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr x.x.x.x bind_addr x.x.x.x identifier "WAN_DHCP "
May 19 10:05:57	dpinger	12776	send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr fe80::dead:beef:80:1%mvneta0.4090 bind_addr fe80::xxxx:xxxx:fe1d:1e17%mvneta0.4090 identifier "WAN_DHCP6 "
May 19 10:05:57	dpinger	22076	send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr x.x.x.x bind_addr x.x.x.x identifier "WAN_DHCP "
May 19 10:05:57	dpinger	22951	send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr fe80::dead:beef:80:1%mvneta0.4090 bind_addr fe80::xxxx:xxxx:fe1d:1e17%mvneta0.4090 identifier "WAN_DHCP6 "
May 19 10:05:59	dpinger	41393	send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr x.x.x.x bind_addr x.x.x.x identifier "WAN_DHCP "
May 19 10:06:00	dpinger	53405	send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr fe80::dead:beef:80:1%mvneta0.4090 bind_addr fe80::xxxx:xxxx:fe1d:1e17%mvneta0.4090 identifier "WAN_DHCP6 "
May 19 10:06:01	dpinger	41393	WAN_DHCP x.x.x.x: Alarm latency 0us stddev 0us loss 100%
May 19 11:11:10	dpinger	30283	send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr fe80::dead:beef:1:1%mvneta0.4090 bind_addr fe80::xxxx:xxxx:fe1d:1e17%mvneta0.4090 identifier "WAN_DHCP6 "
May 19 11:11:12	dpinger	34635	send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr x.x.x.x bind_addr x.x.x.x identifier "WAN_DHCP "
May 19 11:11:13	dpinger	35007	send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr fe80::dead:beef:1:1%mvneta0.4090 bind_addr fe80::xxxx:xxxx:fe1d:1e17%mvneta0.4090 identifier "WAN_DHCP6 "
May 19 11:11:14	dpinger	34635	WAN_DHCP x.x.x.x: Alarm latency 0us stddev 0us loss 100%
May 19 11:11:23	dpinger	13670	send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr x.x.x.x bind_addr x.x.x.x identifier "WAN_DHCP "
May 19 11:11:23	dpinger	14275	send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr fe80::dead:beef:6:1%mvneta0.4090 bind_addr fe80::xxxx:xxxx:fe1d:1e17%mvneta0.4090 identifier "WAN_DHCP6 "
May 19 11:11:23	dpinger	22868	send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr x.x.x.x bind_addr x.x.x.x identifier "WAN_DHCP "
May 19 11:11:23	dpinger	23903	send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr fe80::dead:beef:6:1%mvneta0.4090 bind_addr fe80::xxxx:xxxx:fe1d:1e17%mvneta0.4090 identifier "WAN_DHCP6 "
May 19 11:11:25	dpinger	41099	send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr x.x.x.x bind_addr x.x.x.x identifier "WAN_DHCP "
May 19 11:11:26	dpinger	41419	send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr fe80::dead:beef:6:1%mvneta0.4090 bind_addr fe80::xxxx:xxxx:fe1d:1e17%mvneta0.4090 identifier "WAN_DHCP6 "
May 19 11:11:27	dpinger	41099	WAN_DHCP x.x.x.x: Alarm latency 0us stddev 0us loss 100%
      S 1 Reply Last reply Reply Quote 0
      • S
        SteveITS Rebel Alliance @jcdillin
        last edited by

        @jcdillin Do you have a lot of rules? There is the patch
        Disable pf counter data preservation to temporarily work around latency when reloading large rulesets (Redmine #12827).

        If you change the gateway monitoring IP does it still happen? Or disable gateway monitoring?

        Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
        When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
        Upvote 👍 helpful posts!

        J 1 Reply Last reply Reply Quote 0
        • J
          jcdillin @SteveITS
          last edited by

          @steveits

          Only the default rules, nothing extra yet.

          I haven't tried the gateway monitoring, i'll take a look a that. Thanks!

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Hitting 100% packet loss like that is unlikely to be just latency reloading the rules.
            Is that the system or gateway log? Is there anything else in the system log at that time?

            It looks more like, say, the modem rebooting. Does it have an uptime you can check?

            Steve

            1 Reply Last reply Reply Quote 0
            • First post
              Last post