Re: dh-client setup problems
Well, folks, I'm still having no success here. Here's an excerpt from my syslog files:
Mar 10 15:24:38 lambic dhclient-2.2.x: send_packet: Network is down
Mar 10 15:24:53 lambic dhclient-2.2.x: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
Mar 10 15:24:53 lambic dhclient-2.2.x: send_packet: Network is down
Mar 10 15:25:07 lambic dhclient-2.2.x: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
Mar 10 15:25:07 lambic dhclient-2.2.x: send_packet: Network is down
Mar 10 15:25:18 lambic dhclient-2.2.x: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 2
Mar 10 15:25:18 lambic dhclient-2.2.x: send_packet: Network is down
Mar 10 15:25:20 lambic dhclient-2.2.x: No DHCPOFFERS received.
Mar 10 15:25:20 lambic dhclient-2.2.x: No working leases in persistent database.
Mar 10 15:25:20 lambic dhclient-2.2.x: execve (/etc/dhclient-script, ...): No such file or directory
Mar 10 15:25:20 lambic dhclient-2.2.x: exiting.
Mar 10 15:25:20 lambic dhclient-2.2.x: Sleeping.
As far as I know, roadrunner in NYC requires no host name - the modem validates the mac address of the ethernet card. It works fine when I boot to NT..., so I'm pretty confident the network is good, but I'm really at a loss right now...
Thoughts?
- Stephen Nosal
NY, NY
On Wed, Feb 27, 2002 at 06:13:15PM +0100, Bjorn Erik Gravingen wrote:
> On Tuesday 26 February 2002 20:16, dman wrote:
> > On Sat, Feb 23, 2002 at 05:32:53PM -0600, hanasaki wrote:
> >
> > | What are the pro/con of dhcp-client vs pump?
> >
> > pump is made by RH (IIRC), dh-client is made by ISC (same group who
> > makes dhcpd and bind). I've heard complaints in the past of pump not
> > working. Anyways, I figure that the folks who make dhcpd must know
> > something about DHCP, and why not use their client if I'm using their
> > server?
> >
>
> I've tried both, and have had problems with both. I have a dual boot
> set-up and booting linux after a windows session I sometimes fail
> to get an IP-address. My ISP is running a MS server of some kind
> and using the "--win-client-ident" option in pump solved all my troubles.
> (well, for DHCP that is ;-))
>
> Unfortunately, I didn't find a way to set this option using the if-up
> package, so I replaced it with a script.
>
> Regards,
>
> Bj?rn Erik Gravingen
>
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>
Reply to: