From: Antonio Quartulli <antonio@meshcoding.com>
To: Vlad Yasevich <vyasevich@gmail.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Antonio Quartulli <antonio@open-mesh.com>,
"David S. Miller" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH net] bridge: clean the nf_bridge status when forwarding the skb
Date: Mon, 21 Oct 2013 17:06:39 +0200 [thread overview]
Message-ID: <20131021150639.GC1544@neomailbox.net> (raw)
In-Reply-To: <526541A0.4000504@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]
On Mon, Oct 21, 2013 at 11:00:48AM -0400, Vlad Yasevich wrote:
> >>
> >> Looking at other encapsulators (PPP, iptunnel, VXLAN), they do
> >> nf_reset() on input. Would that be appropriate for batman as well?
> >
> > I thought that too.
> >
> > But at this point, wouldn't it be better to do a reset here and remove the other
> > resets from any other encapsulation module?
> >
> > Maybe this operation is supposed to not happen if no encapsulation is involved?
>
> This is exactly right. The reset happens much later if there is no
> encapsulation. However, if there is an encapsuation that changes the
> hader values that are used to filter, then nf_reset has to happen.
> That is why nf_reset happens input to the encapsulation layer instead
> of always on output from bridge.
I see.
Then I think that this patch can be dropped.
I will provide another patch to batman-adv so that it can reset the nf state
before extracting the payload packet.
Thanks a lot for your feedback!
Regards,
--
Antonio Quartulli
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-10-21 15:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 22:51 [PATCH net] bridge: clean the nf_bridge status when forwarding the skb Antonio Quartulli
2013-10-17 11:28 ` Pablo Neira Ayuso
2013-10-17 11:37 ` Antonio Quartulli
2013-10-18 11:10 ` Pablo Neira Ayuso
2013-10-18 11:35 ` Antonio Quartulli
2013-10-18 14:32 ` Vlad Yasevich
2013-10-18 14:46 ` Antonio Quartulli
2013-10-18 15:33 ` Vlad Yasevich
2013-10-18 15:41 ` Antonio Quartulli
2013-10-21 15:00 ` Vlad Yasevich
2013-10-21 15:06 ` Antonio Quartulli [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=20131021150639.GC1544@neomailbox.net \
--to=antonio@meshcoding.com \
--cc=antonio@open-mesh.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=stephen@networkplumber.org \
--cc=vyasevich@gmail.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.