From: Isamp <isamp@terra.com.br>
To: lartc@vger.kernel.org
Subject: [LARTC] FreeSWAN and IPROUTE2
Date: Tue, 20 Aug 2002 19:14:33 +0000 [thread overview]
Message-ID: <marc-lartc-102987076727238@msgid-missing> (raw)
Hi People !!!
I'm a newbie in this list and in this concepts.
Please, I need help to learn more about routing tools on Linux and its interaction with FreeSWAN and IPTables.
I just read the "Fun with iproute2 and FreeS/WAN" (www.quintilion.com/moat/ipsec+routing/iproute2.html,
very, very, very good text) document but, I need more !!!
On my project, I'm tinking in a lot of linux boxes with 2 or more uplinks, like this:
Frame Relay uplink
/------------------------------\
/ \
| +---------+/ \+---------+ |
+----+Linux Box|---==============================---|Linux Box|----+
| +---------+\ IPSEC with /+---------+ |
\ FreeS/WAN /
\ /
\ /
\----------+POTS+----------/
Dial on Demand
On my tests, when the tunnel is downed, the routing table is updated but, if the tunnel broke,
the kernel routing table persists with routes added by freeSWAN.
I'm thinking to use OSPF (Zebra or BIRD): on this protocol we have the 'helo' packets to determine
the current state of links but, ipsec interface is not a multicast interface !
Reading "Linux Advanced Routing & Traffic Control HOWTO" (http://lartc.org/howto/,
very good document too), in chapter 5.3 we can read
"GRE is a tunneling protocol that was originally developed by Cisco, and it can do
a few more things than IP-in-IP tunneling. For example, you can also transport
multicast traffic and IPv6 through a GRE tunnel.".
So, What I use ? Ipsec tunnels from FreeS/WAN or GRE Tunnels ? Both ? How ?
The traffic over GRE Tunnel are encripted ? How ?
I'm tinking to use the OSPF protocol (Zebra) do make a load balance between FrameRelay and
ipsec interfaces but, in same HOWTO ("Fun...") I see the new possibilitie with iproute2.
What is better ?
Someone have interest in this solution ? Someone can help me ?
Tanks in Advance .
Isamp
ps.: sorry for my poor english !!!
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2002-08-20 19:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-102987076727238@msgid-missing \
--to=isamp@terra.com.br \
--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.