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

    Realtek 8111

    Hardware
    2
    9
    2.3k
    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.
    • C
      cain
      last edited by

      So after countless hours trying to get my router to work, it turned out that the PCI Adapter that I bought is supposedly "incompatible" with pfSense.

      I'm not entirely sure what this means, as the adapter is registered and showing. Can someone help me out here?

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

        What version of pfSense?  This is for 2.2.4:

        https://www.freebsd.org/releases/10.1R/hardware.html

        In says The re(4) driver supports RealTek RTL8139C+, RTL8169, RTL816xS, RTL811xS, RTL8168, RTL810xE and RTL8111 based Fast Ethernet and Gigabit Ethernet adapters including:

        So you should be good I figure.

        You must be doing something wrong.  When you install it does it show up as an available NIC to select?  You sure you have your NICs identified properly (which is which?)

        From my system.  Not exactly sure which chipset it really is:

        [2.2.4-RELEASE][pfSense]/root: grep re0 /var/log/dmesg.boot
        re0: <realtek 8111="" 8168="" b="" c="" cp="" d="" dp="" e="" f="" g="" pcie="" gigabit="" ethernet="">port 0xd800-0xd8ff mem 0xfdfff000-0xfdffffff,0xfdff8000-0xfdffbfff irq 19 at device 0.0 on pci2
        re0: Using 1 MSI-X message
        re0: Chip rev. 0x28000000
        re0: MAC rev. 0x00100000
        miibus0: <mii bus="">on re0
        re0: Ethernet address: 00:30:18:ad:7e:4f</mii></realtek>

        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
          cain
          last edited by

          @Derelict:

          What version of pfSense?  This is for 2.2.4:

          https://www.freebsd.org/releases/10.1R/hardware.html

          In says The re(4) driver supports RealTek RTL8139C+, RTL8169, RTL816xS, RTL811xS, RTL8168, RTL810xE and RTL8111 based Fast Ethernet and Gigabit Ethernet adapters including:

          So you should be good I figure.

          You must be doing something wrong.  When you install it does it show up as an available NIC to select?  You sure you have your NICs identified properly (which is which?)

          From my system.  Not exactly sure which chipset it really is:

          [2.2.4-RELEASE][pfSense]/root: grep re0 /var/log/dmesg.boot
          re0: <realtek 8111="" 8168="" b="" c="" cp="" d="" dp="" e="" f="" g="" pcie="" gigabit="" ethernet="">port 0xd800-0xd8ff mem 0xfdfff000-0xfdffffff,0xfdff8000-0xfdffbfff irq 19 at device 0.0 on pci2
          re0: Using 1 MSI-X message
          re0: Chip rev. 0x28000000
          re0: MAC rev. 0x00100000
          miibus0: <mii bus="">on re0
          re0: Ethernet address: 00:30:18:ad:7e:4f</mii></realtek>

          Hi,

          Sorry for the late reply I've been trying other options.

          Running on pfSense 2.2.4.
          Yeah when I install it it shows it up as a functioning adapter and everything, it's just not letting anything go through it and yes they are identified properly. (alc0 is my Motherboard Eth, re0 is my Realtek Eth).

          I think that there is something definitely wrong because whenever I plug my alc0 into my router via LAN, it works fine. But whenever I plug my re0 into my router via LAN, I can't get access to it.

          Setting it up so re0 is WAN plugged into my router, the DHCP-side of it won't retrieve an IP address from the router so there's something not right and it's really bugging me.

          Also,
          when plugged in via alc0, it shows the Device Name as "pfSense" on the router.
          When plugged in via re0, it shows the Device Name as "–" which means that one wasn't sent out (re0 being the Realtek)

          The only thing which looks weird is the MAC address of the adapter, which is 00:00:00:00:00:03

          1 Reply Last reply Reply Quote 0
          • C
            cain
            last edited by

            Dump from root:

            [2.2.4-RELEASE][root@pfSense.localdomain]/etc: grep re0 /var/log/dmesg.boot
            re0: <realtek 8111="" 8168="" b="" c="" cp="" d="" dp="" e="" f="" g="" pcie="" gigabit="" ethernet="">port 0xe800-0xe8ff mem 0xfdfff000-0xfdffffff,0xfdff8000-0xfdffbfff irq 16 at device 0.0 on pci2
            re0: Using 1 MSI-X message
            re0: Chip rev. 0x2c800000
            re0: MAC rev. 0x00100000
            miibus0: <mii bus="">on re0
            re0: Ethernet address: 00:00:00:00:00:03</mii></realtek> 
            
            1 Reply Last reply Reply Quote 0
            • DerelictD
              Derelict LAYER 8 Netgate
              last edited by

              The only thing which looks weird is the MAC address of the adapter, which is 00:00:00:00:00:03

              Definitely invalid.

              Guess Realtek drivers still suck.

              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
                cain
                last edited by

                @Derelict:

                The only thing which looks weird is the MAC address of the adapter, which is 00:00:00:00:00:03

                Definitely invalid.

                Guess Realtek drivers still suck.

                It makes no sense though because mine and your's adapters are the exact same.

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

                  There's a reason my realtek NIC is relegated to use as my backup DSL WAN.  Sorry.  I have nothing else.

                  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
                    cain
                    last edited by

                    @Derelict:

                    There's a reason my realtek NIC is relegated to use as my backup DSL WAN.  Sorry.  I have nothing else.

                    I managed to get it working myself.

                    I was able to assign it a MAC Address randomly using ifconfig and set the card to Promiscuous. Upon boot the Promiscuous setting reset so I made a script on boot that turned it back on. All up and running now!

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

                      Whatever floats your boat.  I'd buy a new NIC.

                      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
                      • First post
                        Last post
                      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.