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

    Ping spikes on LAN

    Scheduled Pinned Locked Moved General pfSense Questions
    2 Posts 1 Posters 368 Views
    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.
    • D
      Dredex
      last edited by Dredex

      Hi, I have ping spikes every few minutes on the LAN side and I do not know why. There is little traffic on the LAN side, CPU is ~1-2% usage, I have disable all offloading features, disabled/enabled PowerD. Sometimes it spikes after 1-2 hours once or twice. Tried to play some games on Geforce Now and every time it spikes the game freezes, sometimes its unplayable. On clients with 10Gb/s connections we can max our WAN's and there are no spikes, ping is <1ms. If we ping our WAN addresses from outside there are no spikes.

      Supermicro X11SSL-F
      CPU: E3-1230 v6
      RAM: 4GB (17% usage)
      Storage: SSD Kingston 120GB (6% usage)
      WAN: 2 x 1Gb/s - I210-AT (Load Balance 1Gb/s)
      LAN: Intel X520-DA2 with 4 vlans
      Switch DLink DGS-1510-52

      PfSense 2.4.4 P3
      Packages

      • acme
      • haproxy
      • iperf
      • ntopng
      • mailreport
      • nmap
      • openvpn-client-export
      • zabbix-agent44

      192.168.100.1 is the LAN interface

      Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
      Reply from 192.168.100.1: bytes=32 time=1620ms TTL=64
      Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
      Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
      Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
      Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
      Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
      Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
      Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
      Reply from 192.168.100.1: bytes=32 time=756ms TTL=64
      Reply from 192.168.100.1: bytes=32 time=602ms TTL=64
      Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
      Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
      Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
      Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
      Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
      Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
      Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
      Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
      Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
      Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
      Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
      Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
      Reply from 192.168.100.1: bytes=32 time=1485ms TTL=64
      Reply from 192.168.100.1: bytes=32 time<1ms TTL=64
      Reply from 192.168.100.1: bytes=32 time<1ms TTL=64

      d83d10ae-e0ca-4fbf-a8a9-67968e964635-image.png

      1 Reply Last reply Reply Quote 0
      • D
        Dredex
        last edited by

        The problem is fixed after removing ntopng.
        No more spikes.

        Thank you

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