From: Nguyen Dinh Nam <64vn@cardvn.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Multiple Links
Date: Thu, 14 Apr 2005 14:13:16 +0000 [thread overview]
Message-ID: <1113487996.10416.1.camel@nam> (raw)
In-Reply-To: <marc-lartc-106387078916999@msgid-missing>
You may want to read my tutorial
http://routeskeeper.sourceforge.net/Routeskeeper/MultihomingWithLinux.html
And feel free to ask your questions
On Thu, 2005-04-14 at 15:58 +0200, Paulo Andre wrote:
> I have two ISP links that I am trying to firewall through a Linux
> Server, I have been following
> http://lartc.org/howto/lartc.rpdb.multiple-links.html
> and I can not seem to get it working.
>
> Do you have to NAT the incoming packets for this to work correctly?
>
> _______________________________________________
> 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
prev parent reply other threads:[~2005-04-14 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 7:48 [LARTC] Multiple Links hare ram
2003-09-22 7:59 ` Matthieu Turpault
2005-04-14 13:58 ` Paulo Andre
2005-04-14 14:13 ` Nguyen Dinh Nam [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=1113487996.10416.1.camel@nam \
--to=64vn@cardvn.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;
as well as URLs for NNTP newsgroup(s).