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

    Seems a bit slow…

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 4 Posters 1.9k 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.
    • L
      leaded
      last edited by

      Hi there. I just set up 1.2.3 on a P4 with 1 GB RAM. Speedtest.net shows that things are as they were before when the AirPort Extreme was doing the routing. But when I'm logged into another server with SSH, my typing seems very laggy. Ping times are around 22ms to Google. What sorts of things should I be checking for in my pfSense config to see if I've done something wrong?

      Edit: The only package I have installed is rate, which adds ip-specific graphs next to the SVG traffic graph. I don't think it does any logging.

      Edit2: I just tried disabling various services and nothing seems to affect these erratic ping times:

      $ ping google.com
      PING google.com (66.249.80.104): 56 data bytes
      ...snip...
      64 bytes from 66.249.80.104: icmp_seq=49 ttl=52 time=18.253 ms
      64 bytes from 66.249.80.104: icmp_seq=50 ttl=52 time=44.471 ms
      64 bytes from 66.249.80.104: icmp_seq=51 ttl=52 time=21.529 ms
      64 bytes from 66.249.80.104: icmp_seq=52 ttl=52 time=297.910 ms
      64 bytes from 66.249.80.104: icmp_seq=53 ttl=52 time=215.403 ms
      64 bytes from 66.249.80.104: icmp_seq=54 ttl=52 time=144.693 ms
      64 bytes from 66.249.80.104: icmp_seq=55 ttl=52 time=127.212 ms
      64 bytes from 66.249.80.104: icmp_seq=56 ttl=52 time=26.703 ms
      64 bytes from 66.249.80.104: icmp_seq=57 ttl=52 time=25.651 ms
      64 bytes from 66.249.80.104: icmp_seq=58 ttl=52 time=47.692 ms
      64 bytes from 66.249.80.104: icmp_seq=59 ttl=52 time=40.967 ms
      Request timeout for icmp_seq 60
      64 bytes from 66.249.80.104: icmp_seq=60 ttl=52 time=1008.037 ms
      64 bytes from 66.249.80.104: icmp_seq=61 ttl=52 time=32.788 ms
      64 bytes from 66.249.80.104: icmp_seq=62 ttl=52 time=607.531 ms
      64 bytes from 66.249.80.104: icmp_seq=63 ttl=52 time=226.991 ms
      64 bytes from 66.249.80.104: icmp_seq=64 ttl=52 time=141.886 ms
      64 bytes from 66.249.80.104: icmp_seq=65 ttl=52 time=33.528 ms
      64 bytes from 66.249.80.104: icmp_seq=66 ttl=52 time=110.377 ms
      
      
      1 Reply Last reply Reply Quote 0
      • C
        clarknova
        last edited by

        Your latency is certainly erratic, although your post doesn't suggest throughput to be a problem. A number of things could cause erratic latency. First off, do you see this same pattern when you remove pfsense from the network, i.e., through the airport or another router, or by direct connection to the internet? Do you have other traffic passing on the link while experiencing the problem? If your up or down pipe is running at capacity you will see this type of thing. Check your rrd graphs if you're not sure, or your real-time graph while testing.

        db

        1 Reply Last reply Reply Quote 0
        • ?
          Guest
          last edited by

          May I suggest www.pingtest.net

          1 Reply Last reply Reply Quote 0
          • T
            tommyboy180
            last edited by

            leaded,
            I think if you follow clarknova's advice you may be able to narrow your issue down to a single point.

            Also a suggestion is to reset the modem when you change firewalls or even install a new os on the same firewall hardware.

            -Tom Schaefer
            SuperMicro 1U 2X Intel pro/1000 Dual Core Intel 2.2 Ghz - 2 Gig RAM

            Please support pfBlocker | File Browser | Strikeback

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