Re: DHCP client setup for @Home
Read Sven's message below again - dhcpcd - this is not server software.
This is what I use for my cable modem connection. It worked for me before
I even had a clue what I was doing! It automatically is assigned the DNS
servers, etc, so all you need to do is turn it on and it works (even
easier than static IP), unless @home doesn't do "pure" DHCP. Also, just
because DHCP is used, doesn't mean that the IP address assigned to a MAC
address WILL change, just don't assume it will never change, or things
might be very broken when they do.
John
On Wed, 6 Sep 2000, Michael Smith wrote:
> Oh, no, dhcpd is the server software. That won't work at all, unless
> you are on contract with @home to provide this service:^) In fact,
> you might be handing out addresses to @home customers who wonder why
> it doesn't work.
>
> What they don't tell you about @home is that they use static ip
> addresses, they just make you get it with dhcp. If you have the
> information, you can just set it up normally and not dink around with
> all this dhcp junk. I think it's supposed to make it easier on tech
> support if they tell you all the addresses through dhcp. I've been
> running two boxen for about 4 months without a problem--all using
> static IP. If you have the work order that they gave you with the
> other goodies, you can look on it and it will have all the info you
> need, or if you have another working setup, you can look to see what
> the settings are. Then set up a normal network with
> /etc/network/interfaces and resolv.conf.
>
> Sven Burgener wrote:
>
> > On Wed, Sep 06, 2000 at 11:30:13AM -0500, Phil Brutsche wrote:
> > > dhclient (that's the name of the executable in the dhcp-client package) is
> > > the best (imo) dhcp client for unix-type systems. That would explain why
> > > NetBSD, OpenBSD, and FreeBSD use dhclient in their bootup sequence when
> > > you select "automatic interface configuration" (or something like that).
> >
> > How about dhcpcd?
> >
> > **--**--**
> > Package: dhcpcd
> > Priority: optional
> > Section: net
> > Installed-Size: 102
> > Maintainer: Dennis Kelly <dpk@debian.org>
> > Architecture: i386
> > Version: 1:1.3.17pl2-8
> > Replaces: dhcpcd-sv
> > Depends: libc6 (>= 2.1.2)
> > Conflicts: dhcpcd-sv
> > Filename: dists/stable/main/binary-i386/net/dhcpcd_1.3.17pl2-8.deb
> > Size: 37178
> > MD5sum: c843acf777bf739206ccfca1769de412
> > Description: DHCP client for automatically configuring IPv4 networking
> > This package contains both the 0.70 and 1.3.x version of dhcpcd and
> > should work with any Linux kernel.
> > **--**--**
> >
> > Thing is, I am having trouble with getting my cable connection working.
> >
> > I can use "dhcpcd eth0" to get connected. I get an IP address, my
> > default route gets set, and my /etc/resolv.conf is changed.
> > So far so good, all *seems* well.
> >
> > Now, what I can do is ping the default gateway, but not the DHCP server.
> > Also, I cannot resolve DNS names.
> >
> > Can anyone judge to say what *could* be the problem? Thing is exactly
> > the same situation occurs under WinDos. (Them stupid support folks first
> > told me to use WinDos instead of Linux - they don't support Linux!)
> >
> > Anyway, I am waiting for the cable company to respond / fix the problems.
> > My guess is that their network is somewhat fsck'ed.
> >
> > > You weren't doing anything wrong. pump simply doesn't work very well.
> >
> > Has anyone ever had any problems when using dhcpcd instead of dhclient?
> > I never tried dhclient.
> >
> > Thanks
> > Sven
> > --
> > The program required me to install Windows 95 or better ...
> > ... so I installed Linux.
> >
> > --
> > Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
>
>
> --
> Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
>
Reply to: