From: "David" <maniacdavid@cableone.net>
To: lartc@vger.kernel.org
Subject: [LARTC] RE: Contents of LARTC digest, Vol 1 #282 - 4 msgs
Date: Mon, 01 Oct 2001 11:25:24 +0000 [thread overview]
Message-ID: <marc-lartc-100193571907382@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 1418 bytes --]
As far as I know, the cable modems each share the same bandwidth. They
would also share the same subnet, so if one link goes down, wouldn't
they both be down? I can't see using more than 1 modem for each coaxial
line.
Chris.
David wrote:
> Here is the setup I have. I have 3 network cards in my linux machine.
> 1 network card (eth0) goes to my internet network (192.168.0.0).
> Network Card 2 (eth1) and Network Card 3(eth2) go to the internet via
> 2 cable modems whose address is determined by dhcp. I can get either
> cable modem to work alone but I can't get them to work together. I
> would really like to be able to combine the 2 into 1 and have it
> detect a bad link as well in case i have to unplug 1 cable modem.
>
>
>
> Thanks!
>
> David
> maniacdavid@cableone.net
>
>
>
I am using 2 different cable modems because there are 2 different people
paying of them. The way our cable system is set up is that 2 separate cable
modems combined together ($50 each) will be faster than the cable company's
$100 package. And yes, they would both go down at the same time. But for
future reference, it would be nice if I could have it detect when 1 goes
down (like unplugging it) because later I will be combining a DSL and a
cable. Im trying to get this teql thing (tc qdisc,etc.) to work but now that
Im reading about it seems like I would have to access to both sides.
Thanks
David
maniacdavid@cableone.net
reply other threads:[~2001-10-01 11:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-lartc-100193571907382@msgid-missing \
--to=maniacdavid@cableone.net \
--cc=lartc@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.