If you want me to be able to look into it I would need something like a tcpdump or ethereal dump of the traffic at the ethernet level. The dhcp client definitely has some design limitations, but I'd like to know what is going on, especially if it is something the router is requiring that it doesn't do correctly. -Tom
On 15 Jan 2003, Christian E. [ISO-8859-1] J�rgensen wrote: > Date: 15 Jan 2003 14:04:46 +0100 > From: "Christian E. [ISO-8859-1] J�rgensen" <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: [tomsrtbt] DHCP woes > > Hello all, > > I don't know if this is a bug or a design limitation of the DHCP client > in tomsrtbt (version 2.0.103) but anyway: When I boot either my ThinkPad > 560X or my stationary box with tomsrtbt, I get something like this: > > Looking for DHCPOFFER... > > ERROR > timeout > > SIOCADDRT: Invalid argument > > I've tried to increase the timeout value in "dhcpcd--.lua" to 30 > seconds, but this has no effect[1]. I've also tried putting "sleep 30" > after the "/etc/rc.pcmcia start" line in "rc.custom", but this also has > no effect[1]. > > The NIC in my stationary box is RealTek 8029-based (PCI), the one in my > laptop is Tulip-based (CardBus) and needs the "tulip_cb.o" and > "cb_enabler.o" modules from the add-ons directory to work. > > I can configure the ethernet devices manually with the ifconfig/route > combo. Also, the "fully-featured" DHCP clients in RH Linux and Windows > 2000 (which ordinarily inhabit the two machines) configure the > interfaces correctly. > > I wonder whether my DHCP server is to blame (a SpeedStream 2601 router). > Any ideas? > > > Best regards, > CJ > > > [1] ... other than increasing boot time, of course. :-) >
