All of lore.kernel.org
 help / color / mirror / Atom feed
From: Les Mikesell <les@futuresource.com>
To: "primero@hdr-roma.it" <primero@fastwebnet.it>
Cc: netfilter@lists.netfilter.org
Subject: Re: GRE over IPSec?
Date: Thu, 06 Jan 2005 11:59:42 -0600	[thread overview]
Message-ID: <1105034382.14796.26.camel@moola.futuresource.com> (raw)
In-Reply-To: <41DD7B1C.404@hdr-roma.it>

On Thu, 2005-01-06 at 11:53, primero@hdr-roma.it wrote:

> >This may be off-topic for this list but perhaps someone could at least
> >point me to a better source...  When doing IPSec tunnels between Cisco
> >routers it works nicely to first make a GRE tunnel which gives you
> >a fairly normal interface that can run routing protocols, etc., then
> >use 'crypto map' to push the GRE packets through IPSec encryption.
> >
> >Are there any examples available that would match this setup with
> >Linux on one end, Cisco on the other?  A Linux<->Cisco GRE is easy
> >enough and zebra/quagga should run rip or ospf over that, but then
> >I'd like to pass the GRE packets though IPSec before sending.
> >
> >  
> >
> would not be better to have a GRE Tunnel Secured with ipsec?
> i mean creating the normale tunnel
> 
> interface tunnel 1
> etc ....
> 
> then apply the crypto map to make a transport ipsec point 2 point 
> connecttion beetween the REAL interface ip address of both end of the 
> tunnel matching GRE packets.
> 
> This way you'll have a logical interface Tunnel on both routers with an 
> IPSEC encryption for all GRE packets beetween this 2 interfaces.

I thought that was what I said... Regardless, what I want is the
Linux-side setup to match.  On the Ciscos, the GRE is configured
to work without IPSec, then the IPSec tunnel is established and
an access list blocks unencrypted GRE packets. 

-- 
  Les Mikesell
    les@futuresource.com




      reply	other threads:[~2005-01-06 17:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-06 16:51 GRE over IPSec? Les Mikesell
2005-01-06 17:53 ` primero@hdr-roma.it
2005-01-06 17:59   ` Les Mikesell [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=1105034382.14796.26.camel@moola.futuresource.com \
    --to=les@futuresource.com \
    --cc=netfilter@lists.netfilter.org \
    --cc=primero@fastwebnet.it \
    /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.