From: <administrator@netwlan.net>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Two uplinks,
Date: Wed, 08 Nov 2006 13:13:03 +0000 [thread overview]
Message-ID: <000701c70337$9f51c7d0$641497c1@sysadmin> (raw)
You can accomplish this in two ways:
1. Put two routers on the place of this one and solve two internal networks
to see each other trough two routers with static route.
2. if two outgoing connections are to ISPs then solution can be with one
router but with BGP so two networks can go out with both ISP
3 There is third solution also called source routing but this is not a
stable solution and can get you in major trouble.
-----Original Message-----
From: lartc-bounces@mailman.ds9a.nl [mailto:lartc-bounces@mailman.ds9a.nl]
On Behalf Of John Douglass
Sent: Monday, November 06, 2006 10:05 PM
To: lartc@mailman.ds9a.nl
Subject: [LARTC] Two uplinks, two networks and policy routing help requested
I am hoping that someone with more experience and knowledge than I can
assist me in finding a solution ;)
We have a RedHat AS4 box with 5 interfaces. Two interfaces serve two
different networks and two interfaces connect to two different uplinks.
The fifth interface is our management interface.
Since a picture is worth a thousand words I attempted to come up with a
diagram:
http://studpup74.googlepages.com/networkproblem
(I did not want to post this image to the list :)
If anyone with this experience has a few moments to assist us, I would
be very grateful. Let me know if you need additional information.
- John Douglass, Georgia Tech
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2006-11-08 13:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 13:13 administrator [this message]
2006-11-09 14:56 ` [LARTC] Two uplinks, the sew
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='000701c70337$9f51c7d0$641497c1@sysadmin' \
--to=administrator@netwlan.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.