All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ramin Dousti <ramin@cannon.eng.us.uu.net>
To: Ian Hunter <ihunter@hunterweb.net>
Cc: netfilter@lists.netfilter.org
Subject: Re: Argh!  I'm kicking myself
Date: Fri, 19 Dec 2003 17:06:26 -0500	[thread overview]
Message-ID: <20031219220626.GF17702@cannon.eng.us.uu.net> (raw)
In-Reply-To: <015b01c3c670$99b77600$3dc2a70a@melita.com>

On Fri, Dec 19, 2003 at 03:42:21PM -0500, Ian Hunter wrote:

> For days now I've been trying to figure out how to recompile my Redhat
> 2.4.20-24.9 kernel to allow masquerading IPSec ESP traffic.  I ran the

"allow masquerading IPSec ESP traffic" ?? Or just allow forwarding the
IPsec traffic?

> much-vaunted "grep -i masq /proc/ksyms" and to my chagrin got nothing back,
> but on a lark decided I'd try "iptables -A FORWARD -t nat -i ppp0 -p esp -j
> ACCEPT" just to see if it would fly and it did.  Of course.  And now you're
> all laughing at me.
> 
> Where is this documented, that gre, esp, ah, and the like are acceptable
> protocols?  The docs mention icmp, tcp, and udp only.

Which doc?

> 
> Is there such a document, or have I discovered a particular cover of the
> netfilter doc-hole?

man iptables:

...
       -p, --protocol [!] protocol
              The protocol of the rule or of the packet to check.  The  speci-
              fied protocol can be one of tcp, udp, icmp, or all, or it can be
              a numeric value, representing one of these protocols or  a  dif-
              ferent  one.   A  protocol  name  from  /etc/protocols  is  also
              allowed.  A "!" argument before the protocol inverts  the  test.
              The  number  zero is equivalent to all.  Protocol all will match
              with all protocols and is taken as default when this  option  is
              omitted.
...

Ramin

> Ian
> 


      parent reply	other threads:[~2003-12-19 22:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-19 20:42 Argh! I'm kicking myself Ian Hunter
2003-12-19 20:59 ` Aldo S. Lagana
2003-12-19 21:33 ` pheusion
2003-12-19 21:39 ` pheusion
2003-12-19 22:06 ` Ramin Dousti [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=20031219220626.GF17702@cannon.eng.us.uu.net \
    --to=ramin@cannon.eng.us.uu.net \
    --cc=ihunter@hunterweb.net \
    --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 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.