From: "Mike Calvo" <mike@radiowebcaster.com>
To: <speakup@braille.uwo.ca>
Subject: Re: Multiple Network Cards
Date: Fri, 11 May 2001 13:25:10 -0400 [thread overview]
Message-ID: <029901c0da3f$554d54a0$82d9f2d8@mikey> (raw)
In-Reply-To: <Pine.LNX.4.10.10105111007550.3168-100000@lnx1.holmesgrown.com>
I am using the same configuration but for something different and it works
fine. Redhat figures out all that stuff if it is a card.
----- Original Message -----
From: "Steve Holmes" <steve@holmesgrown.com>
To: "speakup e-mail list" <speakup@braille.uwo.ca>
Sent: Friday, May 11, 2001 1:13 PM
Subject: Multiple Network Cards
> I know, this is more generic than speakup, but I'm wanting to hook up two
> network cards to one of my linux boxes. Using one to connect to a
> broadband modem and the other for my inside local area network.
>
> I don't invision real problems configuring the two separate interfaces
> (eth0 and eth1) but do wonder about putting two similar network cards on
> the same bus. I'm thinking about IRQ conflicts, I/O base addresses and
> all that good stuff. This is not a plug and pray setup, but the cards are
> "jumperless" where I would configure them from a provided DOS utility.
>
> Have any of you brains out there done this? how did it go for you? Will
> there really be any problems configuring separate cards in the same
> machine like this? I would think this would be a trivial matter for any
> machine that works as a gateway or router.
>
> Thanks for any help.
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
Steve Holmes
` Terry D. Cudney
` Mike Calvo [this message]
` Stephen Dawes
` Steve Holmes
` Shaun Oliver
` Gregory Nowak
` Kirk Wood
` Raul A. Gallegos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='029901c0da3f$554d54a0$82d9f2d8@mikey' \
--to=mike@radiowebcaster.com \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).