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

    Traffic Graphs weird behaviour

    Scheduled Pinned Locked Moved WireGuard
    5 Posts 3 Posters 773 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.
    • G
      Griffo
      last edited by

      When I view the WG0 interface with the traffic graphs, I see weird behaviour.
      The graph itself does not show any traffic. Hovering over various places shows 0/0.

      However if I go into Status -> Graphs, the numerical value next to the graph is correct.

      https://imgur.com/a/tFBC2ey

      Is this the same for other people?

      P 1 Reply Last reply Reply Quote 1
      • P
        pooperman @Griffo
        last edited by

        I've come across this issue as well. Still happening in 2.5.0.a.20210125.2350

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

          Bug has been opened: https://redmine.pfsense.org/issues/11315

          Also seeing that here.

          Steve

          P 1 Reply Last reply Reply Quote 0
          • P
            pooperman @stephenw10
            last edited by

            Updated by Jim Pingle 8 days ago:

            • Status changed from New to Duplicate
            • Target version deleted (2.5.0)

            Already being tracked internally (NG 5522)

            Does this mean we're unlikely to see this particular issue resolved in time for the 2.5.0 release? I really hope this is just an internal organization (perhaps related to another issue) and not the beginning of moving away from issue tracking in the open (to feed pfSense Plus).

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

              It's because in this particular case we had been testing Wireguard internally before it was announced on CE. The bug was noted there and a report opened.

              Steve

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