RTL8111C (StarTech1000SPEXD2)



  • Hi all

    Just building my first pfsense machine today. Ive got an intel NIC (i350t4) on the way but in the short term im using the StarTech1000 which is based on the RealTechL111C chip.

    Its listed as a 2 x Gigabit NIC but when im in pfsense its showing the LAN interface as 100BaseTX whereas the onboard intel interface for wan is 1000BaseT.

    Ive pinched the StarTech nic from a tower server i had laying around so i know it works at 1GB as ive used it before.

    Any ideas?


  • Netgate Administrator

    8111 should be a Gigabit NIC, though it's not one I'd ever recommend using.  ;)

    Do you mean it's just not connecting at 1Gbps or that it is not showing 1G even available?

    Try running at the command line:

    ifconfig -m
    

    What media types are listed?

    Steve



  • On the dashboard its showing this on the interfaces.

    WAN autoselect n/a
    LAN 100baseTX <full-duplex>192.168.0.199

    ifconfig results are below for the ST. States supported media is capable of 1000Base…..there is an option in pfsense to manually select the type but there is a warning on that option. The cable plugged into that port is coming from a small poe switch so unless the poe is causing an issue somehow.

    re0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
            options=82099 <rxcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic,linkstate>capabilities=183999 <rxcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,tso4,wol_ucast,wol_mcast,wol_magic,linkstate,netmap>ether 00:e0:4c:68:d7:83
            hwaddr 00:e0:4c:68:d7:83
            inet6 fe80::2e0:4cff:fe68:d783%re0 prefixlen 64 scopeid 0x1
            inet 192.168.0.199 netmask 0xffffff00 broadcast 192.168.0.255
            nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect (100baseTX <full-duplex>)
            status: active
            supported media:
                    media autoselect mediaopt flowcontrol
                    media autoselect
                    media 1000baseT mediaopt full-duplex,flowcontrol,master
                    media 1000baseT mediaopt full-duplex,flowcontrol
                    media 1000baseT mediaopt full-duplex,master
                    media 1000baseT mediaopt full-duplex
                    media 1000baseT mediaopt master
                    media 1000baseT
                    media 100baseTX mediaopt full-duplex,flowcontrol
                    media 100baseTX mediaopt full-duplex
                    media 100baseTX
                    media 10baseT/UTP mediaopt full-duplex,flowcontrol
                    media 10baseT/UTP mediaopt full-duplex
                    media 10baseT/UTP
                    media none
    re1: flags=8802 <broadcast,simplex,multicast>metric 0 mtu 1500
            options=82099 <rxcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic,linkstate>capabilities=183999 <rxcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,tso4,wol_ucast,wol_mcast,wol_magic,linkstate,netmap>ether 00:e0:4c:68:dc:1a
            hwaddr 00:e0:4c:68:dc:1a
            nd6 options=21 <performnud,auto_linklocal>media: Ethernet autoselect (10baseT/UTP <half-duplex>)
            status: no carrier
            supported media:
                    media autoselect mediaopt flowcontrol
                    media autoselect
                    media 1000baseT mediaopt full-duplex,flowcontrol,master
                    media 1000baseT mediaopt full-duplex,flowcontrol
                    media 1000baseT mediaopt full-duplex,master
                    media 1000baseT mediaopt full-duplex
                    media 1000baseT mediaopt master
                    media 1000baseT
                    media 100baseTX mediaopt full-duplex,flowcontrol
                    media 100baseTX mediaopt full-duplex
                    media 100baseTX
                    media 10baseT/UTP mediaopt full-duplex,flowcontrol
                    media 10baseT/UTP mediaopt full-duplex
                    media 10baseT/UTP
                    media none</half-duplex></performnud,auto_linklocal></rxcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,tso4,wol_ucast,wol_mcast,wol_magic,linkstate,netmap></rxcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic,linkstate></broadcast,simplex,multicast></full-duplex></performnud,auto_linklocal></rxcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,tso4,wol_ucast,wol_mcast,wol_magic,linkstate,netmap></rxcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,wol_magic,linkstate></up,broadcast,running,simplex,multicast></full-duplex>


  • Netgate Administrator

    Ok, so it's negotiating 100Mb-FD with whatever you have connected to it for some reason. It looks capable of 1G if connected to the right thing.

    Try switching cables if the connected device is definitely 1G. Try connecting a different device.

    Steve



  • Weird. Changed cable and connected directly to my current routers LAN port and its now picked 1000BaseT FD.

    There arent any 100BaseT bottle necks on that network. ive got a Cisco switch thats 100mb but not hooked up to this network. Only assumption is the TPLink poe switch is at fault. Il have a play round with the ports, but anyway for now its working :)


  • Netgate Administrator

    I have a laptop with a Realtek 8111 NIC in it that inexplicably won't negotiate a connection at all with one particular switch I have. I gave up trying to solve it.  ::)

    Steve



  • It may have been prior to getting pfsense running my home network has been a bit of a mess. Lots of un-managed little switches connected to each other around the house. Think i may rip it out and start again yet but this is what ive got so far :)

    Next plan is to shrink pfsense from the lenovo desktop up top into something rack mounted.

    My i350 arrives tomorrow, i guess simple as drop it in and boot up to recognize or will i need to rebuild pfsense for that?



  • Netgate Administrator

    You can just add it and reboot. The interfaces will use a different driver (igb) so will be named differently. The boot will stop at the assign interfaces screen at the console because the re interfaces will no longer present.
    As long as you're ready for that you can just re-assign your interfaces to the new NIC names and continue.

    Steve