Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Anthony R.  Vallario" <avallari@sirinet.net>
To: lartc@vger.kernel.org
Subject: [LARTC] DSL/CABLE Routing
Date: Tue, 15 Jan 2002 17:44:17 +0000	[thread overview]
Message-ID: <marc-lartc-101111673719457@msgid-missing> (raw)

I have a Mandrake 8.1 linux box that I was using as a firewall/router for my
DSL connection. I recently acquired a cable modem. I would like to use both
simultaneously. I've read documentation on iproute2, iptables, kernel
modules, and some "examples". I'm still having problems though.

Particulars
eth0 - dsl
eth1 - local net
eth2 - cable

distro mandrake 8.1
kernel 2.4.8 or 2.4.13
iptables 1.2.2
iproute2 2.2.4

Would like to do some bandwidth shaping also.
Note: I'm not looking for redundancy on incoming connections, As the only
one I allow is SSH. Only looking to allow more bandwidth for outgoing
traffic.

Any intel would be greatly appreciated.


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/

                 reply	other threads:[~2002-01-15 17:44 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-101111673719457@msgid-missing \
    --to=avallari@sirinet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox