Message-ID: <BAY143-W2353DFECB11A239842C4C3B99B0@phx.gbl>
Date:	Mon, 16 Mar 2009 22:31:43 +0100
From:	Pelle Svensson <pelle2004@...mail.com>
To:	<jesse.brandeburg@...el.com>
CC:	<netdev@...r.kernel.org>, <e1000-devel@...ts.sourceforge.net>
Subject: RE: Intel 82567LM e1000e DHCP problem/question




----------------------------------------
> Date: Mon, 16 Mar 2009 11:38:49 -0700
> From: jesse.brandeburg@...el.com
> To: pelle2004@...mail.com
> CC: netdev@...r.kernel.org; e1000-devel@...ts.sourceforge.net
> Subject: Re: Intel 82567LM e1000e DHCP problem/question
>
> good idea to include e1000-devel@...ts.sourceforge.net on these kinds of
> requests.
>
>
> On Sun, 15 Mar 2009, Pelle Svensson wrote:
>> Is there any functionality inside the driver for DHCP request.
>> I see in the source that there is some kind of DHCP filter f the tx stream.
>> Can the drive issue DHCP request inside it self when the Cable is unplugged/plugged.
>
> short answer, the driver no, but the management firmware, maybe.
>
>> I'm tracing a DHCP fault.
>
> what kind of fault? Is the server faulting?

Yes the DHCP server cause the fault in a short answer.
In the long answer it depends on several things. 
By the 2 kinds of request made by the client to the server,
it issued new IP adresses for each of the type of request rather frequently.
This ends up, after a while, with almost an idential faults as this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=473658

>
>> When the net is brought down, ifdown eth0, the dhclient is killed.
>> Then when I unplugged/plugged the cable I get a DHCP request even that
>> dhclient is down.
>>
>> Also the Wireshark format of the DHCP request are different.
>> Correct request includes from dhclient has:
>>> Option: (t=12,l=5) Host Name = "pc005"
>> Incorrect requests when dhclient is killed does not have above.
>
> you apparently have the Intel AMT firmware (ME aka Management Engine)
> enabled in your BIOS, you can try to configure it by hitting CTRL-P during
> post (pre-boot) or at the prompt where it says to hit CTRL-P to enter
> system management setup.
>
> The ME (management engine) firmware is trying to acquire its own dhcp
> address and will do so if the driver is either not loaded or not up.
>
> Once the driver is loaded the firmware may still try to acquire a second
> dhcp address for the ME, depending on your configuration. This whole
> setup works a lot like IPMI, but generally the ME is not configurable via
> IPMI interfaces.
>
> Hope this helps,
> Jes

Your assumption about the Intel AMT seems right!

Log Tracking DHCP Request when plugged net cable in:

- Power on and load Fedora -> No DHCP Request from BIOS until Desktop up
- ifdown eth0 -> DHCP Request
- Restart Fedora -> DHCP Request during the hole Shutdown process
- Enter BIOS menu -> DHCP Request
- Boot up Fedora -> DHCP Request from BIOS until Desktop up

ifdown eth0 trigged the plugged net cable DHCP Request

I tried to hit Ctrl-P frequently during the boot process but it newer display any


management setup. I'm running Fedora 10 on Lenovo T500 bios 1.20 (6FET50WW).





Only AMT stuff I can find for Lenovo is related to Vista or XP, But that seems to


for the OS not the BIOS. Can I load the Windows stuff and turn the AMT DHCP

stuff off? I do have dual boot for XP on this PC.



/Thanks
Pelle





_________________________________________________________________
Dela foton på ett smidigt sätt med Windows Live™ Photos.
http://www.microsoft.com/windows/windowslive/products/photos.aspx--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists