Suggestions welcome
I have a network laid out as follows.
The Network
---------- Eth0 - INTERNET x.x.x.x
LINUX |
Router1 | Eth2 - LAN 172.16.1.x
|
---------- Eth1 -Bridge 1a 192.168.1.1
|
|
---------- Eth0 - Bridge 1b 192.168.1.2
LINUX |
Router2 | Eth2 - LAN 172.16.2.x
|
---------- Eth1 -Bridge 2a 192.168.2.1
|
|
---------- Eth0 - Bridge 2b 192.168.2.2
LINUX |
Router3 | Eth2 - LAN1 172.16.3.x
| Eth3 - LAN2 172.16.4.x
| Eth4 - LAN3 172.16.5.x
|
---------- Eth1 -Bridge 3a 192.168.3.1
|
|
---------- Eth0 - Bridge 3b 192.168.3.2
LINUX |
Router4 | Eth1 - INTERNET 2 x.x.x.x
|
---------- Eth2 - Bridge 4a 192.168.4.1
|
|
---------- Eth0 - Bridge 4b 192.168.4.2
LINUX |
Router5 | Eth1 - LAN 172.16.2.x
|----------
Currently I do no real routing and use mainly IPTABLES to set rules for forwarding. This worked great until I got a second source, Now I set up virtual interfaces for each person I want to go out INTERNET 2 or eth1 on router 4.
I want to use a routing protocol that will allow these routers to speak to each other. I wanted to get feedback on where I could find some GOOD documentation on OSPF or RIPv2.
There are large amounts of computers on each LAN and I want the router to determine which line is the best to send the packet out. I would also like the ability to tell it only send certain types of clients out one pipe. Does anyone have suggestions for this. I would like to keep it a little more low maintenance then my firewall scripts I already have. By the way I have swizeet HTB limiting scripts I hope to contribute to the list.
Thanks,
==/* Jeff Nye */
/* 801-728-1755 */
__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
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.