Intel Pro/1000 Nic - no communication with network

From: Wang (wang_at_sdf.lonestar.org)
Date: 12/29/04

  • Next message: Steven Stremciuc: "Re: Intel Pro/1000 Nic - no communication with network" 
    Date: Wed, 29 Dec 2004 07:37:53 +0000 (UTC)
To: freebsd-net@freebsd.org

    Hi all,

    I am trying to get FreeBSD installed and running on a new rack server
    (asus ap140r-e1). The rack has a Intel Pro/1000 Nic (Intelr 82541GI
    Gigabit Controller).

    I have tried both freebsd 4.10 and 5.3 - and after installation both
    detect the network card and ifconfig shows it. I provided the ip manually
    via rc.conf lines:

         defaultrouter="10.0.0.2"

         hostname="blah.testbox.com"

         ifconfig_em0="inet 10.0.0.9 netmask 255.0.0.0"

    These lines are definately correct because I use them on another freebsd
    5.3 box on my network without any problems (dhcp also works on the other
    5.3 box).

    Ifconfig shows for em0:

         em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500

         options=3<RXCSUM,TXCSUM>

         inet 10.0.0.9 netmask 0xff000000 broadcast 10.255.255.255

         ether 00:11:2F:0F:80:f4

         media: Ethernet autoselect

         status: no carrier

    I have tried both dhcp (my preference here) and hardcoding the ip/gateway
    details - but neither work. DHCP can not be obtained, and if i manually
    give ifconfig the ip/gateway etc...i just do not seem to get any
    connectivity out of the card, I can't ping any other boxes on the
    network...only pinging the boxes own 10.0.0.9 ip works.

    I went to the intel web site and downloaded the driver they have on there
    for freebsd, but it seems the same as what freebsd already has built into
    the kernel (I tried the intel driver regardless, but the result is the
    same...no network communication).

    I decided to verify that the card/cable/network itself is ok - so I ran
    the Knoppix Linux Live cd on the rack....it dectected the nic perfectly
    and got dhcp immediately! So I know for sure the problem is something to
    do with freebsd and its setup.

    I really have no clue where to turn with this problem, and I don't want to
    have to ditch bsd in favour of linux for this rack - please can anyone
    help? I really need this all complete tomorrow

    Thank you in advance,

    daveuk
    _______________________________________________
    freebsd-net@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-net
    To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"

  • Next message: Steven Stremciuc: "Re: Intel Pro/1000 Nic - no communication with network"

    Relevant Pages

    • Re: NIC wont DHCP or configure
      ... It won't DHCP. ... Configuring it using ifconfig doesn't permit any connection. ... > My FreeBSD kernel is generic, and both the following lines are uncommented: ... try a different network switch / hub. ...
      (freebsd-questions)
    • Re: iwi discarding oversized packets while mtu=1500 for src/dst
      ... Today I wanted to go back to using FreeBSD on my laptop, ... device = 'PRO/Wireless 2200BG Network Connection' ... of how the device is setup (e.g. ifconfig cmds) and current ...
      (freebsd-net)
    • Re: Problem regarding dhcp and FreeBSD 4.10 on a laptop
      ... When I've had a problem like this it's usually my firewall. ... can you ssh in to the BSD box from inside the network? ... This is my first FreeBSD installation, ... +no problem using dhcp to obtain their IP addresses. ...
      (freebsd-questions)
    • Re: SuSE 9.2 + Asus A4712DLH
      ... but IP is there from ifconfig to "network ... I suspect longer time delay in DHCP configuration, ... Repeat this with "network restart". ... before it can send first real packet on line, ...
      (alt.os.linux.suse)
    • Re: Problem regarding dhcp and FreeBSD 4.10 on a laptop
      ... The laptop still can't connect to the internet, ... Problem regarding dhcp and FreeBSD 4.10 on a laptop ... both of which have no problem using dhcp to obtain their IP ... >> unable to get past the network. ...
      (freebsd-questions)