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

    Unable to assign interfaces

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    3 Posts 2 Posters 3.1k 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.
    • D
      dacree
      last edited by

      Greetings,

      I am unable to assign interfaces during installation on any of my NICs
      ra0  Realtek 8111E
      em0 Intel(R) PRO/1000 Network
      em1 Intel(R) PRO/1000 Network

      installation output is similar for all network interfaces.

      em0: <intel(r) 1000="" pro="" network="" connection="" 6.9.6="">port 0xd040-8xd07f mem 0xfe4a0 000-8xfebffff, 0xfe400000-0xfe49ffff irq 18 at device 0.0 on pci14
      em0: Setup of Shared code failed
      device_attach: em0 attach returned 6</intel(r)>

      Setting up the interfaces manually returns the following.

      Warning: array_key_exists(): The second argument should be either an array or an object in /etc/inc/config.inc on line 1357
      Invalid Interfce name 'em0'

      Using auto detection returns the following

      Warning: Invalid argument supplied for foreach() in /etc/inc/config.inc on line 1527
      no link-up detected.

      system info
      Intel Core i3-2100 Sandy Bridge
      BIOSTAR H67MU3 with on board Realtek 8111E
      2 x Intel Pro 1000 PCI

      Please help.

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

        Update:  The same issue comes up with pfSense 2.0 RC1 for the em0 and em1 interfaces. ra0 can be assigned to the WAN now. I still cant assign IP's to the other 2 NICs

        1 Reply Last reply Reply Quote 0
        • H
          HillBoy
          last edited by

          Try using one of the newer snapshot images. I just experienced similar weirdness with the February 2.0 RC-1 build. I switched to the April 29th build and everything worked like a charm.

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