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

    Marvell switch (XG-7100) no communication with Realtek R8169 NIC

    Official Netgate® Hardware
    2
    7
    316
    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.
    • E
      erasedhammer
      last edited by

      I have my XG-7100 setup with a vlan on a couple of ports. I have a small SBC (single board computer) with a Realtek R8169 NIC plugged into eth6.

      I have pretty much ruled out the realtek device being the problem. They work on every other switch (cisco) or router (tplink) I plug it into. I've tried several different cables of varying lengths and even got another identical realtek nic and it doesn't work either. The realtek device has both the correct firmware and driver installed (debian 10)

      Eth6 is tagged with vlan130, and set to default (autoselect). The LEDs on the xg7100 side is green and activity LED is blinking. The LED on the realtek side is Amber and activity LED is also blinking. The LED is also Amber when plugged in and WORKING on other switches/routers.

      All the pcaps I've done show traffic (on the same subnet) is just timing out. There is no firewall on the realtek device.

      Is there any more granular troubleshooting I can do on the marvell switch?

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

        @erasedhammer said in Marvell switch (XG-7100) no communication with Realtek R8169 NIC:

        Eth6 is tagged with vlan130

        Is the SBC expecting dot1q tagged traffic?

        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
        • E
          erasedhammer
          last edited by

          I don't fully understand marvell switch configurations, but I would believe eth6 is acting as an access port for my vlan, which means the traffic is only getting tagged inbound, not outbound to the device?

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

            It is just like any other switch. The VLAN is tagged or untagged.

            If you wan an "Access port" on VLAN 130 you need to:

            Create VLAN 130 in pfSense on lagg0
            Assign lagg0.130 to an interface
            Enable it and number it
            Add DHCP servers, firewall rules, etc

            In the switch chip you need to create VLAN 130 and TAG it to ports 9 and 10 and set port 6 UNTAGGED.

            Then set the PVID on port 6 to 130.

            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
            • E
              erasedhammer
              last edited by

              Okay, then how I have it configured it is definitely an access port. I have other devices on vlan130 that work fine (but they are Intel nics)

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

                Not tracking any incompatibilities with realtek NICs connecting to the 7100 switch ports.

                Drop to a shell and post the output of etherswitchcfg

                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
                • E
                  erasedhammer
                  last edited by

                  Well theres my problem...
                  I was caught up in configuring the port itself I forgot to add the port to the vlan group!

                  Communication is now working.

                  As always, thank you for the help!

                  port6:
                  pvid: 130
                  state=8<FORWARDING>
                  flags=0<>
                  media: Ethernet autoselect (1000baseT <full-duplex>)
                  status: active
                  laggroup0:
                  members 9,10
                  vlangroup1:
                  vlan: 130
                  members 7,8,9t,10t

                  1 Reply Last reply Reply Quote 1
                  • First post
                    Last post