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

    Ping Spikes Internal and External (Solved)

    Official Netgate® Hardware
    2
    5
    470
    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.
    • G
      GuloGuloDesu
      last edited by GuloGuloDesu

      I am running an SG-3100 with 2.4-5 (RELEASE).

      When I am ping anything on the netgate or through the netgate I get random high ping responses.

      64 bytes from 8.8.8.8: icmp_seq=327 ttl=53 time=6.50 ms
64 bytes from 8.8.8.8: icmp_seq=328 ttl=53 time=115 ms
64 bytes from 8.8.8.8: icmp_seq=329 ttl=53 time=8.14 ms
64 bytes from 8.8.8.8: icmp_seq=330 ttl=53 time=12.2 ms
64 bytes from 8.8.8.8: icmp_seq=331 ttl=53 time=5.87 ms
64 bytes from 8.8.8.8: icmp_seq=332 ttl=53 time=322 ms
64 bytes from 8.8.8.8: icmp_seq=333 ttl=53 time=6.21 ms
64 bytes from 8.8.8.8: icmp_seq=334 ttl=53 time=8.55 ms
64 bytes from 8.8.8.8: icmp_seq=335 ttl=53 time=672 ms
64 bytes from 8.8.8.8: icmp_seq=336 ttl=53 time=13.6 ms
64 bytes from 8.8.8.8: icmp_seq=337 ttl=53 time=8.53 ms
64 bytes from 8.8.8.8: icmp_seq=338 ttl=53 time=6.55 ms
64 bytes from 8.8.8.8: icmp_seq=339 ttl=53 time=7.21 ms
64 bytes from 8.8.8.8: icmp_seq=340 ttl=53 time=572 ms
64 bytes from 8.8.8.8: icmp_seq=341 ttl=53 time=7.08 ms
64 bytes from 8.8.8.8: icmp_seq=342 ttl=53 time=517 ms
64 bytes from 8.8.8.8: icmp_seq=343 ttl=53 time=6.100 ms
64 bytes from 8.8.8.8: icmp_seq=344 ttl=53 time=7.51 ms
^C
--- 8.8.8.8 ping statistics ---
344 packets transmitted, 344 received, 0% packet loss, time 729ms
rtt min/avg/max/mdev = 5.776/112.354/729.299/189.658 ms

      Also, if I ping the LAN port on the netgate, I have the exact same problem

      64 bytes from 172.23.45.253: icmp_seq=12 ttl=64 time=640 ms
64 bytes from 172.23.45.253: icmp_seq=13 ttl=64 time=0.342 ms
64 bytes from 172.23.45.253: icmp_seq=14 ttl=64 time=0.273 ms
64 bytes from 172.23.45.253: icmp_seq=15 ttl=64 time=0.332 ms
64 bytes from 172.23.45.253: icmp_seq=16 ttl=64 time=607 ms
64 bytes from 172.23.45.253: icmp_seq=17 ttl=64 time=0.360 ms
64 bytes from 172.23.45.253: icmp_seq=18 ttl=64 time=687 ms
64 bytes from 172.23.45.253: icmp_seq=19 ttl=64 time=27.7 ms
64 bytes from 172.23.45.253: icmp_seq=20 ttl=64 time=0.356 ms
64 bytes from 172.23.45.253: icmp_seq=21 ttl=64 time=0.314 ms
64 bytes from 172.23.45.253: icmp_seq=22 ttl=64 time=608 ms
64 bytes from 172.23.45.253: icmp_seq=23 ttl=64 time=0.323 ms
64 bytes from 172.23.45.253: icmp_seq=24 ttl=64 time=0.300 ms
64 bytes from 172.23.45.253: icmp_seq=25 ttl=64 time=91.4 ms
64 bytes from 172.23.45.253: icmp_seq=26 ttl=64 time=0.344 ms
64 bytes from 172.23.45.253: icmp_seq=27 ttl=64 time=0.328 ms
64 bytes from 172.23.45.253: icmp_seq=28 ttl=64 time=0.293 ms
64 bytes from 172.23.45.253: icmp_seq=29 ttl=64 time=36.5 ms
^C
--- 172.23.45.253 ping statistics ---
29 packets transmitted, 29 received, 0% packet loss, time 402ms
rtt min/avg/max/mdev = 0.273/145.266/686.638/252.549 ms

      I have tried the following:

      • Swapping network cables

      • Power cycling

      • Rebooting (multiple times)

      • Test pings to other devices on my network (All normal ping times)

      • Connecting straight to my Internet Modem (All websites have normal pings when bypassing netgate)

      • Disabled all 3 Hardware Offloading options

      I am running a pretty bare bones configuration, I only have the IPSEC and VPN wizard packages installed. I only have a couple of firewall rules (most are default), and my netgate is my DHCP server as well.

      I did notice that I am between 60% - 80% CPU usage all of the time, and that is even with light to no web traffic. I have 2 computers, and 2 laptops, and 2 cell phones that are connected through the netgate. Powering off any number of those devices does not impact the CPU usage.

      I'm not sure what else to try, but I plan to continue to Google and troubleshoot the issue on my own. Any advice would be greatly appreciated.

      Edit:
      Solved by disabling DHCP6 on WAN interface which dropped CPU usage.

      1 Reply Last reply Reply Quote 0
      • G
        GuloGuloDesu
        last edited by

        Alright, after digging through the status -> system logs -> system -> general and I found that there were a ton of events referencing DHCP6 on the WAN interface.

        I set DHCP6 to none on the WAN interface and my CPU load when to 9% and all of my ping latency went away.

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

          Nice catch. Do you actually have IPv6 available on your WAN?

          Steve

          1 Reply Last reply Reply Quote 0
          • G
            GuloGuloDesu
            last edited by

            Nope. Looking at my Internet modem, I do not even have an option to enable IPv6 on it.

            Double checking my PFsense, I don't have IPv6 enabled on any interface now.

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

              Hmm, I imagine then it just removed the IPv6 bogons table which would otherwise be loaded causing pfctl to spike.

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