Subject: RE: Double Net cards? problem#1 solved
From: Barry Sparenborg (sparenborgb@hadadycorp.com)
Date: Mon Apr 02 2001 - 08:15:31 MDT
I'm sure you could. You would probably have to subnet your network. That
way you would have 2 separate networks.
Barry
-----Original Message-----
From: Vanja Bucic [SMTP:vanjab@UDel.Edu]
Sent: Monday, April 02, 2001 9:14 AM
To: yellowdog-general@lists.yellowdoglinux.com
Subject: Re: Double Net cards? problem#1 solved
I suspected that I would have to do that. I compiled kernels before,
no
trouble, it is just that I hate that process. You need to do it each
time you try out a new kernel, new YDog update, etc. I wish
YellowDog
would compile less things into the kernel and make more modules.
Thanks, I'll try that.
The setup I have now is that I have built-in eth0, and Farallon
FastEther 10/100 TX working in tandem. The in traffic goes through
eth0,
and out traffic goes through eth2 (Farallon). I had problems with
the
built-in network card, and I heard it is a queue corruption
triggered by
packet collisions. So I made the built-in network card an in-only
card - Farallon takes care of the rest.
So far so good.
Question (again):
Is there a way to set up two network cards ON THE SAME NETWORK so
they
act as a two different, distinct, computers? Whatever comes into
eth0
comes out from eth0, whatever comes into eth1 comes out from eth1 -
completely independent operation.
Thanks.
On Monday, April 2, 2001, at 09:23 , Barry Sparenborg wrote:
> Here is what worked for me under the same situation:
>
> Created a new kernel with no support for the dec (D21143) chip no
other
> card
> either. That stopped it from picking it up at boot time. Then
setup
> the
> tulip card as you did (modprobe tulip)and put it into a boot
script.
> Now I
> only get eth0 (built in interface) and eth1 (farallon 10/100 card)
and
> they
> both work.
>
> barry
>
This archive was generated by hypermail 2a24 : Mon Apr 02 2001 - 08:26:32 MDT