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

    Assistance with jetway daugherboard; dmesg looks okay but interface not showing?

    Scheduled Pinned Locked Moved 1.2.1-RC Snapshot Feedback and Problems-RETIRED
    3 Posts 2 Posters 2.6k 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.
    • A
      adrianhensler
      last edited by

      Hi,

      Hoping someone can point me in the right direction here.  From dmesg:

      rlphy0: <rtl8201l 10="" 100="" media="" interface="">PHY 9 on miibus0
      rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

      From /var/log/system.log:

      rlphy0: <rtl8201l 10="" 100="" media="" interface="">PHY 9 on miibus0
      rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

      Shouldn't that interface be showing?  I don't see it with ifconfig or in the interface tab in pfSense.  Am I reading that correctly? I don't see any errors related to that interface in the logs.

      Any direction welcome.</rtl8201l></rtl8201l>

      1 Reply Last reply Reply Quote 0
      • D
        David_W
        last edited by

        That's the phy, not the network controller - phys will never appear as interfaces.

        Do you have a Realtek controller that goes with that phy? It's unusual, but not impossible, for the phy to be detected but not the controller. I'd expect a rl or re interface to go with the rlphy.

        dmesg and system.log will always be the same, by the way - there's no need to post both.

        1 Reply Last reply Reply Quote 0
        • A
          adrianhensler
          last edited by

          Hi,
          Thanks for the help- either the daughterboard wasn't installed with correct contact with all the pins (the led's on the back lit when a cable was plugged in) or it was an IRQ conflict with the Dlink NIC I had installed. or possibly something else….

          In any case; it is working correctly now.

          User error in this case, I think.  That's what I get for trying to do this stuff half asleep.

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