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

    Unable to connect to network in 2.1.4 - 2nd intel nic 2 names?

    Hardware
    2
    3
    688
    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.
    • R
      robpal
      last edited by

      I am having trouble getting my networks and adaptors configured in Pfsense 2.1.4

      I have an onboard intel and a pci intel nic and these work under pfsense 1.2.3

      i cant get them working in pfsense 2.1.4

      when pfsense 2.1.4 is loading valid interfaces are: (below is shortened but has main info in)

      em0 intel pro/1000 nw crlr 7.3.0
      usbus00 (up) intel 82001i ich9 usb controller
      this usbus naming goes on up to
      usbus70 (up)
      then
      em1 mac (up) intel pro/1000legacy network connection 1.0.6

      when i auto-configure to detect networks the link is detected as em0 and em1

      the interfaces are then assigned
      WAN em0
      LAN usbus0

      I cannot then connect any devices on the lan, they just refresh as though there trying to get an ip address and fail - even if i set a manual address in the correct range they wont connect

      I know the hardware all works so this seems to be a software/driver issue

      i can get screenshots for more detailed info but think this naming discrepancy may be the reason i'm having trouble.

      Any help would be appreciated

      many thanks

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

        LAN set as usbus0 is never going to work. Try manually re-assigning LAN as em1.

        Steve

        1 Reply Last reply Reply Quote 0
        • R
          robpal
          last edited by

          Yep I needed to manually assign the interfaces
          Issue resolved many thanks ;)

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