Sorry to reply to my own mail, but hey, I finally got my cable
connection working and I'm willing to share what I've learnt. ;-)
The problems I experienced were with the method my cable provider uses
to get their clients authenticated / initialized / connected.
This is what happens:
o
On Sat, 9 Sep 2000, S.Salman Ahmed wrote:
I just tried installing Potato using the latest boot floppies (compact
set) and had the same result - pump failed to get configuration info
using DHCP. I ended up statically configuring the ethernet card in my
system using the same values as
A long time ago, in a galaxy far, far way, someone said...
So, does this mean that if I try and install potato on my home system
using the boot floppies (to avoid having to burn 1 or more CDs) and I
select the DHCP net configuration option for doing a network/internet
install that the
I used the boot floppies, and it worked with my cable modem. I guess I
didn't know it was using pump, it just worked by magic. I went ahead and
installed dhcpcd when I was done.
BTW, make sure you get root.bin, resc.bin, plus all three driver floppies
BEFORE you start the installation and blow
I'm on @home as well, and pump just failed badly for me. However, dhcpcd
worked out of the box, so to say:
dhcpcd -h XXX did the job right then.
Andrei
--
First there was Explorer...
Then came Expedition.
This summer
A long time ago, in a galaxy far, far way, someone said...
I was able to figure out the problem myself. For some reason, I was
unable to get Pump to work with the [EMAIL PROTECTED] DHCP servers. I then
remembered that there was another DHCP client, dhcp-client, which I have
used earlier on
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
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
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
Yeah, there's that, but from all the inquiring I have done, that address is
pretty much
unchanging. The problem I've found with @home, at least in Eugene, OR, is that
they use
alot of mystique to describe what they do, like it's magic or something, when
all they
really do is pass packets and
On Wed, Sep 06, 2000 at 01:53:19PM -0500, John Reinke wrote:
Read Sven's message below again - dhcpcd - this is not server software.
Yup, note the 'c' in dhcpcd. Stands for client. And the binary behaves
like a daemon in the way that it disconnects from the terminal and keeps
running the way
11 matches
Mail list logo
