From: Vincent Jaussaud <tatooin@kelkoo.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] LARTC / Multipath routing: Thanks & feedbacks :)
Date: Tue, 29 Apr 2003 09:33:11 +0000 [thread overview]
Message-ID: <marc-lartc-105160888820667@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105153009810072@msgid-missing>
On Mon, 2003-04-28 at 16:51, Nuno Miguel Pais Fernandes wrote:
> One thing you could do is: make a tutorial showing problems and
> solutions you've found in implementing such a system and put it in the
> ML.
I will. I'll post an url to the list once it's done. (Might takes some
times, though.)
Regards,
Vincent.
>
> Thanks
> Nuno Fernandes
>
>
>
> On Mon, 2003-04-28 at 12:40, Vincent Jaussaud wrote:
> > Hello,
> >
> > A while ago I bothered some people in this list regarding issues with
> > multipath routing and advanced routing in general. The main goal was to
> > setup a complex networks where all servers would be available through
> > both link. Each server was public, and thus had 2 public IP addresses.
> > This setup included VPN setup with fail-over, firewalls with gateway as
> > routing key & alternatives routes setup, NAT for internal private
> > networks, DMZs available over both links,etc... The whole thing was
> > about setting up full redundancy for every server.
> >
> > There was a lot of problems building the whole thing up, but in the end,
> > everything worked perfectly. I mean it.
> >
> > I currently have more than 30 Linux servers reachable through 2
> > dedicated lines, over 2 ISP, using 2 public distinct netblocks. Each
> > server is linux-based, and does outgoing load-balancing in equalize
> > mode. Incoming traffic load-balancing is done using standard round-robin
> > DNS. Everything got filtered by firewalls. I have VPN fail-over setup
> > using alternatives routes & dead gateway detection.
> >
> > For all of these, I would like to thanks you.
> > Thank you for giving this wonderful toolkit to the Internet Community.
> > Thank you for your time answering our questions, and finally for you
> > help & assistance. I wouldn't have been able to build the whole thing up
> > without you. Thank you also, for keeping my users off my back. :)
> >
> > I never doubted Linux was the best OS in the world. But now, I have a
> > proof.
> >
> > I would especially like to thanks Julian Anastasov (your patches works
> > just perfectly !), Arthur van Leeuwen and Dawid Kuroczko.
> >
> > Thanks again.
> > Yours,
> > Vincent Jaussaud.
> >
> > --
> > ########################################################
> > Kelkoo Security Manager / Networks & Systems Architect
> > JID: portsentry@jabber.kelkoo.net
> > Office: +(33)04 7629 7163 / Mobile: +(33)06 806 409 62
> > ########################################################
> > Kelkoo.com --- GNU/Linux Powered.
--
Vincent Jaussaud
Kelkoo.com Security Manager
email: tatooin@kelkoo.com
"The UNIX philosophy is to design small tools that do one thing, and do
it well."
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-04-29 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 11:40 [LARTC] LARTC / Multipath routing: Thanks & feedbacks :) Vincent Jaussaud
2003-04-28 14:51 ` Nuno Miguel Pais Fernandes
2003-04-29 9:33 ` Vincent Jaussaud [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-105160888820667@msgid-missing \
--to=tatooin@kelkoo.com \
--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.