[98375] in RedHat Linux List
Re: DHCP Problems - "The Saga Continues"
daemon@ATHENA.MIT.EDU (William Stearns)
Sun Nov 8 19:03:45 1998
Date: Sun, 8 Nov 1998 19:04:50 -0500 (EST)
From: William Stearns <wstearns@pobox.com>
To: redhat-list@redhat.com
cc: Steve Ettorre <sme@nycap.rr.com>
In-Reply-To: <3645B0CA.A7D06B85@nycap.rr.com>
Resent-From: redhat-list@redhat.com
Reply-To: redhat-list@redhat.com
Good evening, Steve,
On Sun, 8 Nov 1998, Steve Ettorre wrote:
> > I am hooking up a second computer to the Time Warner roadrunner cable
> > modem network in Albany, NY. The first computer has been running
> > smoothly using RH v4.2 with dhcp at boot time. I am running v5.1 on
> > the new computer. At boot the ethernet card is detected properly and
> > dhcp fires. However, it is consistently fails. As additional
I don't have answers to all of your questions, but though that a
few small pieces of insight might help.
You refer to hooking up a _second_ computer to the Cable modem
network. With a small hub [*1], this is physically no problem. However,
I wasted a day troubleshooting a similar setup where I had my laptop
hooked up _solely_ as a monitoring machine.
The problem is that the Roadrunner box I was using latches on to
the mac address of the first Ethernet device it sees when it is turned on.
It absolutely refuses to talk to any other Ethernet card until the box is
turned off and on again. If you have two Ethernet devices connected, one
will get access and the other won't; it's random as to which will get it
on a given RoadRunner power cycle.
In short, when they say hook up one machine to the RoadRunner with
a standard Ethernet cable, they mean it - unless you want to spend a day
troubleshooting what appears to be a flaky box too... :-)
Secondly, the RoadRunner network I was on required the user to log
into the network with Kerberos authentication. That can be done in one of
two ways. You can run a client _on_ the Linux computer - someone has
written one - or you can run it on one of the machines on your Lan. The
login process works surprisingly well _through_ IP masquerading. [*2]
See the Cable modem howto for more info.
If you've got the Linux box physically hooked up correctly but
haven't logged in, traceroute will show packets going partway out to the
Internet, but you won't be able to get all the way.
The good news is that the Linux box connected to the RoadRunner
can have a second Ethernet card connected to your internal lan. The Linux
box can use IP masquerading to allow everyone out. Run squid as a cache;
do your ISP a favor.
There are a number of other issues with the RoadRunner network;
for example, it's pretty difficult to run servers visible from the outside
world and IP tunneling becomes closer to an art form. On the other hand,
I must admit that I don't believe I have _ever_ seen faster download
speeds - and I used to run an ISP!
I really must apologize as I haven't directly addressed even one
of your questions. I hope that one of these ideas is one you haven't
tried already...
Best of luck,
- Bill
[*1] and a crossover cable or regular Ethernet on a crossover port to the
RoadRunner...
[*2] Use the latest Windows 95 client from:
ftp://ftp1.optonline.net/pub/Agent/dist/Win95
or the Linux software from:
ftp://ftp.vortech.net/pub/rrlinux/
I've had no luck getting the Mac login software to work through IP
masquerading... no idea why.
---------------------------------------------------------------------------
Unix _is_ user friendly. It's just very selective about who its friends
are. And sometimes even best friends have fights.
William Stearns (wstearns@pobox.com)
Mason, buildkernel, and named2hosts are at: http://www.pobox.com/~wstearns
---------------------------------------------------------------------------
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com http://archive.redhat.com
To unsubscribe: mail redhat-list-request@redhat.com with
"unsubscribe" as the Subject.
