The 2.0.32 and 2.0.34 kernels have worked flawlessly with the network from
day one.  The reason that I would like to use the 2.1.x kernel is that it is
more efficient with SMP systems, but, of course, if I can't get an IP
address, it doesn't seem much use!

Here's what I've done today:

Recompiled a fairly basic kernel with no sound, no real bells and whistles,
basically just something designed to get the computer on the Internet.
Unfortunately, I got the same results.

It seem that the problem lies with the way that dhcpcd interfaces with the
network drivers that the 2.1.106 kernel uses.  I'm going to try the system
with a 3COM 3C595 card and see if I get any better results.  If that doesn't
work, I think that I've got a tulip card laying around somewhere.

Of course, I don't really have any complaints with using the 2.0.34
kernel...it gets the job done, but you know how it is when there's something
newer out there...

Drew Dunn
[log in to unmask]
Check out the BurbCam!
http://adsl24.bois.uswest.net/drew/hood.html


>   I run kernel 2.0.33 on a home network using ip forwarding and
> ip masquerading successfully.  I'm waiting for ASDL to be implemented in
> my area.  That being said....
>
>   You're running an experimental kernel, drop back to 2.0.33 or 34 and see
> what happens.  There's an article in the Linux Journal June, 1998 dealing
> with xSDL.  Maybe that will help.  Sorry I can't be of more help.