Mikkel:
Wait till you hear this. I went back into my kernel configuration, and
took out some other unecessary stuff - IRDA subsystem, ISDN, etc. but
absolutely no changes in either the networking section, or network devices
section. I recompiled, rebooted, and now I can ping 192.168.1.2 and get a
response. I have absolutely no idea which device was causing this, but I
will try to figure it out. Apparently, having something else in the
kernel config as a module (as this is how most of Red Hat's stuff
is) caused it not to work.
Thank you for taking the time to look at the problem.
Now to see if I can get ipchains working :)
- Mike
On Sat, 22 Apr 2000, Mikkel L. Ellertson wrote:
> At 07:03 PM 4/22/00 -0400, you wrote:
> >Mikkel:
> >
> >Is there possibly anything wrong with the kernel? I have 2 ethernet
> >cards, 3Com 10/100 PCI cards. When Red Hat first installed, it set up
> >modules for these two cards as 3c59x. I believe the correct driver for
> >these cards is 3c90x, so in the past, as I did this time, I've gone in to
> >the kernel configuration, made sure I was using what Red hat did by doing
> >a make oldconfig first, and the only thing I changed was I removed all of
> >the other cards as modules, and compiled in:
> >
> > 3c90x/3c980 B/C series "Cyclone/Hurricane/Tornado" support
> >
> >This is exactly what I've done in the past. I recompiled, and the machine
> >comes back up, apparently normal, and I get no error messages. Possibly
> >something has changed with these, or the way the kernel now handles
> >machines with 2 Ethernet cards in them?
> >
> >- Mike
> >
> >
> Mike,
> This one has got me stumped. I am going to have to set up a machine
> with 2 NICs and 6.2 that I can play with. Unless I am overlooking something,
> your setup should be working. I think it is time to take your problem to
> the Linux network list, and let the people that write the code see if they
> can figure it out. ([EMAIL PROTECTED])
> I wish I had saved the message with the ifconfig/ping/ifconfig results.
> Maybe I missed something there... But I thought you were pinging an address
> that the route command results said should go out eth1, but actualy went out
> eth0.
>
> I wish I had an answer for you...
>
> Mikkel
>
> --
> I Haven't Lost My Mind,
> It's Backed Up On Disk Somewhere...
>
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
