Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Ted Phelps <phelps@gnusto.com>
To: netfilter@lists.netfilter.org
Subject: Re: GRE Packet in IPSec not Inbound?
Date: Fri, 05 Jan 2007 02:10:36 -0600	[thread overview]
Message-ID: <17305.1167984636@laika.gnusto.com> (raw)
In-Reply-To: Your message of Thu, 04 Jan 2007 23:54:53 MST.  <00ea01c73096$671bc7d0$35535770$@com>


"Joshua Perry" writes:
> Ok so the problem I have is that in the interface chain for the interface
> that is connected to the internet Shorewall puts a policy match filter "--m
> policy --dir in --pol none" When the ESP packets come in it matches that
> policy because it is inbound.  The GRE packet that gets excised from the ESP
> begins again at INPUT but that packet does not match that rule for some
> reason.  At first I wasn't sure if this was by design or not so I manually
> put in a jump rule without the policy match which worked good.

The IPsec packet matches the vpn1_in policy because it matches this rule:

    1   152 ACCEPT     esp  --  *      *       67.42.31.242    0.0.0.0/0

It's not surprisng that the packet no longer matches this once the ESP
wrapper is stripped away.  If you want to accept the packet because it
matched this rule when it first came in (which I assume is what you
want) then you need to mark it as having arrived on a secure interface.

Have a look at the LARTC HOWTO:

    http://tldp.org/HOWTO/Adv-Routing-HOWTO/lartc.netfilter.html

Cheers,
-Ted


  reply	other threads:[~2007-01-05  8:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-05  6:54 GRE Packet in IPSec not Inbound? Joshua Perry
2007-01-05  8:10 ` Ted Phelps [this message]
2007-01-05  8:42   ` Joshua Perry
2007-01-05 11:29     ` Ted Phelps

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=17305.1167984636@laika.gnusto.com \
    --to=phelps@gnusto.com \
    --cc=netfilter@lists.netfilter.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