All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartek Krajnik <bartek@bicom.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Suggestions welcome
Date: Thu, 20 Feb 2003 21:37:43 +0000	[thread overview]
Message-ID: <marc-lartc-104577712416366@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104575924914624@msgid-missing>

[-- Attachment #1: Type: text/plain, Size: 2509 bytes --]

On 20-02-2003 at 08:39:32AM -0800, Jeff Nye wrote:
JN> I have a network laid out as follows.
JN> 
JN> The Network
JN> 
JN> 
JN> ---------- Eth0 - INTERNET x.x.x.x
JN>  LINUX   |
JN> Router1  | Eth2 - LAN   172.16.1.x
JN>          |
JN> ---------- Eth1 -Bridge 1a  192.168.1.1
JN>     |
JN>     |
JN> ---------- Eth0 - Bridge 1b  192.168.1.2
JN>  LINUX   |
JN> Router2  | Eth2 - LAN   172.16.2.x
JN>          |
JN> ---------- Eth1 -Bridge 2a 192.168.2.1
JN>     |
JN>     |
JN> ---------- Eth0 - Bridge 2b  192.168.2.2
JN>  LINUX   |
JN> Router3  | Eth2 - LAN1   172.16.3.x
JN>          | Eth3 - LAN2   172.16.4.x
JN>          | Eth4 - LAN3   172.16.5.x
JN>          |
JN> ---------- Eth1 -Bridge 3a 192.168.3.1
JN>     |
JN>     |
JN> ---------- Eth0 - Bridge 3b  192.168.3.2
JN>  LINUX   |
JN> Router4  | Eth1 - INTERNET 2   x.x.x.x
JN>          |
JN> ---------- Eth2 - Bridge 4a  192.168.4.1
JN>     |
JN>     |
JN> ---------- Eth0 - Bridge 4b  192.168.4.2
JN>  LINUX   |
JN> Router5  | Eth1 - LAN   172.16.2.x
JN>          |
JN> ---------- 
JN> 
JN> Currently I do no real routing and use mainly IPTABLES to set rules for forwarding.  This
JN> worked great until I got a second source, Now I set up virtual interfaces for each person
JN> I want to go out INTERNET 2 or eth1 on router 4.  
JN> 
JN> I want to use a routing protocol that will allow these routers to speak to each other.  I
JN> wanted to get feedback on where I could find some GOOD documentation on OSPF or RIPv2.

http://lartc.org/lartc.pdf
Chapter 17
or http://www.zebra.org

Only about OSPF, BGP and protocols: http://www.cisco.com or rfc's :)

JN> 
JN> There are large amounts of computers on each LAN and I want the router to determine which
JN> line is the best to send the packet out.  I would also like the ability to tell it only

spray, mgen

JN> send certain types of clients out one pipe.  Does anyone have suggestions for this.  I

man iptables /MARK

JN> would like to keep it a little more low maintenance then my firewall scripts I already
JN> have.  By the way I have swizeet HTB limiting scripts I hope to contribute to the list.
JN> 
JN> Thanks,
JN> 

Rgds,
  Bartek.
--
GPG-key-ID:  0x948DE45D -- visit http://www.keyserver.net
Fingerprint: 95E9 8E2D 1801 7864 2244  6EAA 03E5 764D 948D E45D

The great baby you see there is not yet out of his swaddling-clouts.
                                                           Shakespeare, Hamlet.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2003-02-20 21:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20 16:39 [LARTC] Suggestions welcome Jeff Nye
2003-02-20 21:37 ` Bartek Krajnik [this message]

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-104577712416366@msgid-missing \
    --to=bartek@bicom.pl \
    --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.