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

    Getting Errors Out on WAN

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 2 Posters 605 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.
    • ARAMP1A
      ARAMP1
      last edited by ARAMP1

      My modem (Arris SB8200) firmware was recently updated to allow link aggregation, so I created a LACP on the WAN side. The first thing I noticed was either 6 or 7 Errors Out immediately upon startup of pfSense and approximately 300 errors a day. I can go back to one port in and everything is fine, but before I do, I was just wondering if there is anything I can do to troubleshoot to correct these to make this work?

      0_1551646465116_Errors 1.jpg

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

        Switch out the cables is the first thing to try.

        So you see any interface 'events' in the system log? Does the modem give any useful data?

        Steve

        1 Reply Last reply Reply Quote 1
        • ARAMP1A
          ARAMP1
          last edited by

          Yeah, I've tried several sets of cables.

          No corrected or uncorrectable errors. I've had nothing in the Events for the past couple days, but just checked and found a

          "Dynamic Range Window violation" RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW

          That might have something to do with it.

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

            Hmm, that seems more like something on the cable side.

            You could try setting at the command line:
            sysctl net.link.lagg.lacp.debug=1

            That will give you a lot more LACP logs on the pfSense side which might show something.

            Steve

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