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

    Negate 6100 - unstable LAN interface

    Scheduled Pinned Locked Moved Official Netgate® Hardware
    16 Posts 5 Posters 1.6k Views 6 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.
    • H Offline
      hac76 @stephenw10
      last edited by

      @stephenw10
      My computer is connected with a USB3 gigabit ethernet adapter to the LAN1 port of the 6100.

      I already tested with another CAT5E brand new cable and checked another ethernet adapter with still these interface resets.

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

        I set up my LAN interface to default again an restarted the 6100.

        Is there any tools/logs to troubleshoot link negotiation errors ?

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

          When I saw this it was cycling at ~5s, the system logs will show the timing.

          What happens when you set the speed to 'Default'? Does it link at all?

          One thing you can try is setting both ends the 1G fixed but that shouldn't be required for Gigabit Ethernet.

          Steve

          H 1 Reply Last reply Reply Quote 0
          • H Offline
            hac76 @stephenw10
            last edited by

            @stephenw10

            With "default" parameter I can access the web admin but sometimes the interface resets.

            I put an unmanaged cisco smb gigabit switch between the netgate and my computer, it looks promising.

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

              Hmm, almost certainly a negotiation issue then.

              1 Reply Last reply Reply Quote 0
              • GertjanG Online
                Gertjan @hac76
                last edited by Gertjan

                @hac76

                Test with this :
                Take a 100Mbit or better 1Gbit ordinary switch.
                Hook up pfSense port LAN1 to the a port on the Switch.
                Hook up the Ethernet cable coming from your USB dongle to the same switch.
                I bet the issue is gone.
                And if it persists, it's on the "USB dongle side" of the switch port, not the pfSense port.

                Because, look closely to the USB electrical contacts. The traffic has to go over these 4 contacts. Not some xx kbit/sec, but at least 100 Mbits/sec (GBits is even possible ?)
                and
                The needed power also goes over the same contacts. Knowing that Ethernet type device doesn't use "one or two millli amps" but a lot more ... If the USB dongle even vibrates a bit, power to the USB NIC goes flat.
                The entire Ethernet links goes down, and up again.

                IMHO : USB Ethernet dongles are usable at best as an extreme "no other options left" Ethernet connection solution. Even a wifi USB dongle is better ( the connection still breaks, but you won't see it any more so it "doesn't happen" ;) )

                No "help me" PM's please. Use the forum, the community will thank you.
                Edit : and where are the logs ??

                H 1 Reply Last reply Reply Quote 0
                • H Offline
                  hac76 @Gertjan
                  last edited by

                  As I said I tried this configuration with a switch and can now confirm the issue is gone !

                  The 6100 is now installed, thanks for your help @Gertjan @stephenw10

                  1 Reply Last reply Reply Quote 1
                  • J Offline
                    jkline @stephenw10
                    last edited by

                    @stephenw10 said in Negate 6100 - unstable LAN interface:

                    I have seen something similar to that once before, it was a link negotiation issue. It only did it when I had the interface link speed specifically set to 'autoselect' rather than default. Is it possible you have set that?

                    Steve

                    When setting up my 6100, I had this issue when I chose AutoSelect. I changed it back to Default and the issue went away.

                    1 Reply Last reply Reply Quote 0
                    • Z Offline
                      zesta
                      last edited by

                      I appear to have had this problem as well.

                      For my 6100, if you do a full reboot, everything is stable for a long time, but if the link goes down (switch reboot, or unplug/replug cable), the LAN port would go into an endless cycle of up/down.

                      I discovered that the LAN port was set to "autoselect" which must be the default, as I did not set that at all. When set to "default" it seems to be working now (for now).

                      My questions are:

                      1. is this a hardware issue or a software bug?
                      2. what is the difference between "default" and "autoselect" (and why the difference?)
                      3. how is this not a widely known issue? TAC had no clue when I contacted them right after I got the unit.

                      thanks,
                      -Randy

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

                        Setting 'autoselect' specifically sets the NIC to auto negotiate speed and duplex. Setting 'default' doesn't set anything so the NIC remains set at it's power on values. That usually is 'autoselect' but may be slightly different for some of the sub settings.

                        After booting when you set 'default' it may not change what was previously set. So for example if you have set 100Mbps and want to then connect at 1G you may need to set autoselect first then default.

                        Does the link remain stable with the NIC set as 'Default'?

                        Steve

                        Z 1 Reply Last reply Reply Quote 0
                        • Z Offline
                          zesta @stephenw10
                          last edited by

                          @stephenw10

                          After setting it to "default" (which oddly, seems not to be the default), it does seem to be stable.

                          I have tested this on a 2.5G and 10G port on the LAN side and both seem to function just fine in terms of link. Getting the unit to properly re-assign IPv6 addressing on the LAN side is a different story, but a release/renew on the WAN fixes that.

                          I am still a bit confused as to why there would be a difference. All 1G and 10G should be set to auto-negotiate, should they not? Is there any documentation as to exactly what "default" does at the interface level?

                          thanks,
                          -Randy

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

                            Setting 'autoselect' there runs 'ifconfig media autoselect' against the NIC which may also set/unset some other registers in the NIC. Setting 'default' does not.

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