On Tuesday, June 29, 2010 9:14 AM, K. Posern wrote: > Hi, > > I really hope you might give me a hint and/or can refer me to somebody > to help me with the below problem. > > I am having a really weird problem with getting an IP with dhcp. > BUT only at my work place - and it works fine for everybody else there > AND it works fine for me if I MANUALLY run the dhcp-client! > > ... > > And honestly I have no clue anymore :( > And I am beginning to think that this /must/ be a bug somewhere. But I > have even no clue in which of the involded components the problem > could reside (as P.S. to this mail I listed details about all involved > components). > > So here are the 2 ways of invoking the dhcp client I am using: > > /1st/ > I am using netplugd (see /// ABOUT MY MACHINE ///) to start either the > gentoo startup-script /etc/init.d/net.eth0 which then starts the dhcp > client /OR/ a script started by netplugd (both ran as root) to start > the dhcp program. > And this JUST DOES NOT WORK: > > I can see with ps the dhcp client running: > pixel ~ # ps faux|grep -i dhc > root 332 0.0 0.0 4200 616 pts/6 S+ 22:22 0:00 > | \_ grep --colour=auto -i dhc > root 32751 0.0 0.0 1828 308 ? Ss 22:22 0:00 > /sbin/dhcpcd eth0 > > And I see its output in the syslog: > Jun 28 17:27:45 [dhcpcd] eth0: dhcpcd 4.0.15 starting > Jun 28 17:27:45 [dhcpcd] eth0: broadcasting for a lease > Jun 28 17:27:57 [acpid] ACPI Battery Event: 88% > - Last output repeated 2 times - > Jun 28 17:28:15 [dhcpcd] eth0: timed out > > And I can see the dhcp/bootp packets: > I captured the attached network traffic with wireshark. > > There you can see: Repeated dhcp requests > (until the dhcp times out), but no responses! > > /2nd/ > As root I copy and paste the exact command I see in ps above and > voila. > In about 1 second I get my ip! > > Again the syslog: > Jun 28 17:28:54 [dhcpcd] eth0: dhcpcd 4.0.15 starting > Jun 28 17:28:55 [dhcpcd] eth0: broadcasting for a lease > Jun 28 17:28:55 [dhcpcd] eth0: offered 192.168.0.64 from 192.168.0.1 > Jun 28 17:28:55 [dhcpcd] eth0: acknowledged 192.168.0.64 from > 192.168.0.1 Jun 28 17:28:55 [dhcpcd] eth0: checking 192.168.0.64 is > available on attached networks > > In the attached wireshark capture I have two files: one complete > capture and one filtered for bootp. For now I only attached the > filtered one. > In there you will find first the above failure and then the above > success (to the LAST of the dhcp requests, is the one triggered by the > /2nd/ trial all the other requests before belong to the failed /1st/ > trial). I also (tried to) compare the packets (I picked the FIRST > dhcp request (of the failed /1st/ trial) and the dhcp-request of the > successful /2nd/ trial: I only see a different transactionID and > thous two different hashsums, otherwise they seem bit for bit > identical! > > As dhcp clients I already tried these both: dhcpcd and pump (see /// > ABOUT MY MACHINE ///). > --> Identical results. > > I also tried to invoke the dhcp client instead of just: > /sbin/dhcpcd eth0 > within a login shell to avoid any ENVIRONMENT differences: > /bin/sh -l -c '/sbin/dhcpcd eth0' > --> Identical results. > > In the P.S. you will find more details about "ALL THE INVOLVED > COMPONENTS". > > So I honestly don't know what to do anymore. But I would like to > UNDERSTAND WHY it is not working even though it should be working and > even though I see the identical dhcp-request two times on the wire, > but > in only ONE case I get a response in the other I get seemingly nothing > back!? > > Any help/hint is greatly appreciated. > And of course I would be eager to provide you with any more debug > information you could/would need! > > Thanks a lot!!! > > Best, > > Knuth > > > P.S.: ALL THE INVOLVED COMPONENTS: > > ///////////////////////// > /// ABOUT MY MACHINE /// > I am using a TOSHIBA notebook with an INTEL network adapter: > 01:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet > Controller > > Wireless is turned off. > > uname -a: > Linux pixel 2.6.31.3-nogo-pixel #1 SMP PREEMPT Mon Dec 7 01:14:18 EST > 2009 i686 Intel(R) Core(TM)2 CPU U7600 @ 1.20GHz GenuineIntel > GNU/Linux > > Gentoo Linux 32-bit > > The dhcp clients I am using: > [I] net-misc/dhcpcd > Installed versions: 4.0.15(02:33:39 03/12/09)(compat -zeroconf) > > [I] net-misc/pump > Installed versions: 0.8.24-r3(02:41:08 03/12/09) > > The netplug I am using: > [I] sys-apps/netplug > Installed versions: 1.2.9.1(20:57:30 27/09/09) > > When I am using netplugd it seems to work just fine: > If I plug the network cable --> I see in the syslog: > Jun 29 09:49:08 [netplugd] eth0: state INNING pid 2174 exited status 0 > Then my netplug script gets run with ACTION == "in" > > Or when I unplug the network cable --> I see in the syslog: > Jun 29 10:59:42 [netplugd] eth0: state OUTING pid 5805 exited status 0 > Then my netplug script gets run with ACTION == "out" > > > ///////////////////// > /// CISCO ROUTER /// > Catalyst 2950 series [WS-G2950-24] IOS VERSION: 12.1(9)EA1 > > > ///////////////////////////////////////// > /// PF-SENSE FIREWALL (+dhcp-daemon) /// > 1.2-RELEASE > FreeBSD 6.2-RELEASE-p11 i386
Recently there have been other reports of dhcpcd not always able to get DHCP addresses with a number of vendors' adapters/drivers (an issue with carrier detection). Perhaps pump is having a similar issue. Have you tried dhclient? What are the other people at your work place successfully using (distro, kernel, DHCP client, NIC/LOM, driver and driver version)? One thing that comes to mind is there have been a number of changes in the e1000e driver (and possibly other vendors' drivers) with respect to how it reports link (carrier detection) to userland tools. Would you be willing to try the lastest out-of-tree e1000e driver at http://e1000.sourceforge.net? Thanks, Bruce. ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ E1000-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
