I dunno about @home, but the stock dhcp client, pump works fine here
with San Diego roadrunner. I use to have problems with dhcpcd fetching a
new ip after my isp kills my connection for random reasons (and it does
this alot). If you have an ethernet device set up, pump -i eth0 works
* Michael P. Soulier (firstname.lastname@example.org) wrote:
> On Fri, Feb 02, 2001 at 08:32:18PM -0500, James Di Toro wrote:
> > Has anyone sucessfully gotten the dhcp to work for the ethernet connection
> > to the cable modem. In my area I have a static IP based on my hostname so
> > I'm ok.
> > I tried adding the dhcp connect w/ passing the hostname to my
> > /etc/network/interfaces file, but the client just hung up. Anyone else
> > have luck in this front?
> I'm using dhcpcd with rogers@home on my gateway/firewall. The -I argument
> lets me use my client id as is required. Works fine for the most part, except
> for the occasional time when rogers' crappy dhcp servers don't respond.
> Michael P. Soulier <email@example.com>
> "...the word HACK is used as a verb to indicate a massive amount
> of nerd-like effort." -Harley Hahn, A Student's Guide to UNIX
> PGP Public Key: http://126.96.36.199/email.phtml
- From: James Di Toro <firstname.lastname@example.org>
- Re: debian@home
- From: "Michael P. Soulier" <email@example.com>