From: Patrick McHardy <kaber@trash.net>
To: Marco Berizzi <pupilla@hotmail.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: ipsec with 2.6.16-rc3-git6
Date: Fri, 17 Feb 2006 11:15:30 +0100 [thread overview]
Message-ID: <43F5A242.9040809@trash.net> (raw)
In-Reply-To: <BAY103-F81B8A00B6663452743916B2F80@phx.gbl>
Marco Berizzi wrote:
>
>> > IN=eth0 OUT= MAC=00:90:27:74:66:4c:00:0c:ce:93:65:ce:08:00
>> > SRC=venezia-gateway DST=firenze-gateway LEN=112 TOS=0x00 PREC=0x00
>> > TTL=53 ID=45921 PROTO=ESP SPI=0x583f3ff9
>> > IN=eth0 OUT= MAC=00:90:27:74:66:4c:00:0c:ce:93:65:ce:08:00
>> > SRC=venezia-gateway DST=firenze-gateway LEN=80 TOS=0x00 PREC=0x00
>> TTL=53
>> > ID=45921 PROTO=4
>>
>> Thats odd, these packets should be caught by your ESP rule, so I guess
>> they must be dropped by another rule. Please post your full ruleset with
>> iptables -vxnL.
>
>
> Me again. Aha! Found!!! ;-))
>
> iptables -I INPUT -s venice-gateway --protocol 4 -j ACCEPT
>
> did the trick.
I also just noticed the second line contains IPCOMP not ESP, which is
strange because ESP is used in transport mode, so the ESP and IPCOMP
decapsulation should happen without any netfilter hooks in between.
src 172.16.0.0/23 dst 172.23.0.0/23
dir in priority 2377
tmpl src venezia-gateway dst firenze-gateway
proto comp reqid 16406 mode tunnel
level use
tmpl src 0.0.0.0 dst 0.0.0.0
proto esp reqid 16405 mode transport
next prev parent reply other threads:[~2006-02-17 10:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-16 15:28 ipsec with 2.6.16-rc3-git6 Marco Berizzi
2006-02-16 20:29 ` Patrick McHardy
2006-02-17 8:33 ` Marco Berizzi
2006-02-17 8:53 ` Patrick McHardy
2006-02-17 8:58 ` Marco Berizzi
2006-02-17 9:09 ` Patrick McHardy
2006-02-17 9:26 ` Marco Berizzi
2006-02-17 9:29 ` Patrick McHardy
2006-02-17 9:57 ` Marco Berizzi
2006-02-17 10:07 ` Marco Berizzi
2006-02-17 10:11 ` Marco Berizzi
2006-02-17 10:15 ` Patrick McHardy [this message]
2006-02-17 10:35 ` Marco Berizzi
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=43F5A242.9040809@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=pupilla@hotmail.com \
/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.