From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] iproute2 and freeswan
Date: Thu, 16 Jan 2003 15:13:33 +0000 [thread overview]
Message-ID: <marc-lartc-104273026323730@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104272473515627@msgid-missing>
Hello Tomas,
Fortunately for you, this has been adequately documented! Please visit
the following site for the overview of "why".
http://www.quintillion.com/moat/ipsec+routing/ipsec+routing.html
Once you have read that, there's a more detailed (HOWTO-like) description
here:
http://www.quintillion.com/moat/ipsec+routing/iproute2.html
And here's the "main page" with links to other related documentation which
may answer some of your more general questions.
http://www.quintillion.com/fdis/moat/index.html
-Martin
: hello, anyone using freeswan and iproute2 with policy routing? freeswan
: creates routes for VPN destination networks and puts them in the main
: table, or for you that use the route command, the only table.
:
: anyway, this is causing me troubles since i want to keep the main table
: free from the VPN networks, i want them in a special table and use that
: table in conjunction with ip rule.
:
: a clue anyone?
:
: regards,
:
: tomas bonnedahl
: _______________________________________________
: LARTC mailing list / LARTC@mailman.ds9a.nl
: http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
:
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-01-16 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 13:44 [LARTC] iproute2 and freeswan Tomas Bonnedahl
2003-01-16 15:13 ` Martin A. Brown [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-104273026323730@msgid-missing \
--to=mabrown-lartc@securepipe.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox