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

    Lan out speed double Wan in speed per Traffic Graph

    Scheduled Pinned Locked Moved General pfSense Questions
    19 Posts 7 Posters 4.9k Views 1 Watching
    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.
    • M Offline
      MindfulCoyote
      last edited by

      More and more interesting. The fact that the throughput graph is balanced indicates that the traffic is probably not being generated by the router. Here are some simple steps to take to isolate the mystery traffic. (You might need a console for these.)

      From the console, run "systat -ifstat" (This should match with your WAN/LAN Traffic Graphs BTW. If not, another important discrepancy.)

      1. Unplug the WAN interface from the router. Does the mystery traffic persist, or stop?
          If it stops, the mystery traffic is definitely related to WAN traffic despite what the graphs appear to indicate. I would try step 3 below with the WAN plugged in to see if a client is also involved.

      2. If it continues, then leaving the WAN unplugged, unplug the router LAN interface. Does the mystery traffic persist, or stop?
          If it continued even with the LAN interface unplugged, try running tcpdump from the console to see what it shows.

      3. If it stops, plug the router LAN interface back in and unplug everything else from the LAN switch except the router. This keeps keeps the interface up, but traffic should be zero. Does the mystery traffic persist, or stop?
          Again, if it persists, try running tcpdump from the console to see what it shows. There should be virtually no traffic as only the only devices involved are the router and the switch.
          If it stops, try plugging in the other connections one by one to see which device is "triggering" the mystery traffic.

      Err

      –
      Erreu Gedmon

      Firewalls are hard...
      but the book makes it easier: https://portal.pfsense.org/book/

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

        I would have this down as a glitch in the LAN graph and not much else. It's happened before and was fixed but I can't find anything on redmine now. Doesn't explain the actual reduced throughput though.

        https://forum.pfsense.org/index.php?topic=77744.0
        https://forum.pfsense.org/index.php?topic=75607.msg412605#msg412605

        Steve

        1 Reply Last reply Reply Quote 0
        • H Offline
          Harvy66
          last edited by

          @stephenw10:

          I would have this down as a glitch in the LAN graph and not much else. It's happened before and was fixed but I can't find anything on redmine now. Doesn't explain the actual reduced throughput though.

          https://forum.pfsense.org/index.php?topic=77744.0
          https://forum.pfsense.org/index.php?topic=75607.msg412605#msg412605

          Steve

          Like what he said, I current have the issue of the Traffic Graph many times being incorrect. The shape of the graph is correct, but many times is 2x or 1/2 the correct value, even though it shows the correct value right next to the graph. So some times it shows 20mb when it's really 10mb, and other times it shows 5mb when it's really 10mb. For me at least, it's not consistent. RRD seems to be correct.

          1 Reply Last reply Reply Quote 0
          • M Offline
            markn62
            last edited by

            Despite warnings not to use RealTek adapters with PfSense I had one vacant on the MB.  So I switched LAN1 from EM0 to RL0 and the 2x graph problem went away.  What does that say about Intel adapters?  Not sure we solved this but a work-around is in place.  The Intel is the 2-port commercial model and the other port does not exhibit bad behavior.  Perhaps they share few components between ports on the adapter board.

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

              It's almost certainly nothing to do with the NIC hardware or driver. For instance if you had started out using the Realtek NIC and switched to the Intel I imagine the problem would also have gone away. It will be some bug in the code that sends the data to rrdtool.

              Steve

              1 Reply Last reply Reply Quote 0
              • M Offline
                markn62
                last edited by

                Boy did I miss the adapter names, IGB1 and RE0.  I switched back to Intel IGB1 and the 2x problem resumes.  Sure it's not the NIC hardware or driver?

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

                  Nope, not sure.  ;)
                  There are many people using Intel NICs without issue though. Try something basic. Go tot eh Status: Interfaces: page and note the values for in/out packets(data) for WAN and LAN. Pass some LAN-WAN traffic. Now check the values again, they should have incremented by the same amount.

                  Steve

                  1 Reply Last reply Reply Quote 0
                  • C Offline
                    Cino
                    last edited by

                    I know this is an old topic but were you able to fix this?

                    I'm noticing the same behavior on my box (2.1.5 i386) today… WAN is correct, LAN is double.

                    running systat -ifstat, I see the LAN traffic is double also.. All Intel NICs

                    Checked vnstat and same deal... looks like its been like this for a while and I've just haven't noticed. Normally I only look at the WAN interface. RRD graphs look correct tho

                    1 Reply Last reply Reply Quote 0
                    • DerelictD Offline
                      Derelict LAYER 8 Netgate
                      last edited by

                      Isn't this a bug in FreeBSD?

                      https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=182828

                      Chattanooga, Tennessee, USA
                      A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                      DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                      Do Not Chat For Help! NO_WAN_EGRESS(TM)

                      1 Reply Last reply Reply Quote 0
                      • C Offline
                        Cino
                        last edited by

                        Interesting… Would this apply to em# interfaces also? If its a bug with FreeBSD then I guess I'll have to wait until I move to 2.2.

                        1 Reply Last reply Reply Quote 0
                        • C Offline
                          Cino
                          last edited by

                          Found the pfSense bug reports. They are for VLANs but I believe the issue is related

                          https://redmine.pfsense.org/issues/3314
                          https://redmine.pfsense.org/issues/3264

                          1 Reply Last reply Reply Quote 0
                          • M Offline
                            MarcoP
                            last edited by MarcoP

                            Hi Folks,

                            FYI bug is back and reported as https://redmine.pfsense.org/issues/10812

                            Cheers

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