From: Pablo Neira Ayuso <pablo@netfilter.org>
To: wenxu@ucloud.cn
Cc: fw@strlen.de, netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH nf-next] netfilter: bridge: Fix non-untagged fragment packet
Date: Thu, 20 Jun 2019 12:48:04 +0200 [thread overview]
Message-ID: <20190620104804.cbbodvw2llnt6qcl@salvia> (raw)
In-Reply-To: <1560954907-20071-1-git-send-email-wenxu@ucloud.cn>
On Wed, Jun 19, 2019 at 10:35:07PM +0800, wenxu@ucloud.cn wrote:
[...]
> So if the first fragment packet don't contain vlan tag, all of the
> remain should not contain vlan tag..
If I understand correctly, the problem is this:
* First fragment comes with no vlan tag.
* Second fragment comes with vlan tag.
If you have a vlan setup, you have to use ct zone to map the vlan id
to the corresponding ct zone.
nf_ct_br_defrag4() calls:
err = ip_defrag(state->net, skb,
IP_DEFRAG_CONNTRACK_BRIDGE_IN + zone_id);
if ct zones are used, first fragment will go to defrag queue
IP_DEFRAG_CONNTRACK_BRIDGE_IN + 0, while second fragment will go to
IP_DEFRAG_CONNTRACK_BRIDGE_IN + zone_id.
So they will go to different defrag queues.
> Fixes: 3c171f496ef5 ("netfilter: bridge: add connection tracking system")
> Signed-off-by: wenxu <wenxu@ucloud.cn>
> ---
> net/bridge/netfilter/nf_conntrack_bridge.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/net/bridge/netfilter/nf_conntrack_bridge.c b/net/bridge/netfilter/nf_conntrack_bridge.c
> index b675cd7..4f5444d 100644
> --- a/net/bridge/netfilter/nf_conntrack_bridge.c
> +++ b/net/bridge/netfilter/nf_conntrack_bridge.c
> @@ -331,6 +331,8 @@ static int nf_ct_bridge_frag_restore(struct sk_buff *skb,
> }
> if (data->vlan_present)
> __vlan_hwaccel_put_tag(skb, data->vlan_proto, data->vlan_tci);
> + else if (skb_vlan_tag_present(skb))
> + __vlan_hwaccel_clear_tag(skb);
>
> skb_copy_to_linear_data_offset(skb, -ETH_HLEN, data->mac, ETH_HLEN);
> skb_reset_mac_header(skb);
> --
> 1.8.3.1
>
next prev parent reply other threads:[~2019-06-20 10:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 14:35 [PATCH nf-next] netfilter: bridge: Fix non-untagged fragment packet wenxu
2019-06-20 10:48 ` Pablo Neira Ayuso [this message]
2019-06-20 11:39 ` wenxu
2019-06-20 17:05 ` Florian Westphal
2019-06-21 15:08 ` Pablo Neira Ayuso
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=20190620104804.cbbodvw2llnt6qcl@salvia \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=wenxu@ucloud.cn \
/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