From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jarno Rajahalme <jarno@ovn.org>
Cc: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
dev@openvswitch.org
Subject: Re: [PATCH net-next v4 8/8] openvswitch: Interface with NAT.
Date: Thu, 10 Dec 2015 20:10:08 +0100 [thread overview]
Message-ID: <20151210191008.GA20440@salvia> (raw)
In-Reply-To: <1449622870-48944-9-git-send-email-jarno@ovn.org>
On Tue, Dec 08, 2015 at 05:01:10PM -0800, Jarno Rajahalme wrote:
> - /* Call the helper right after nf_conntrack_in() for confirmed
> - * connections, but only when commiting for unconfirmed connections.
> - */
> ct = nf_ct_get(skb, &ctinfo);
> - if (ct && (nf_ct_is_confirmed(ct) ? !cached : info->commit)
> - && ovs_ct_helper(skb, info->family) != NF_ACCEPT) {
> - WARN_ONCE(1, "helper rejected packet");
> - return -EINVAL;
> + if (ct) {
> +#ifdef CONFIG_NF_NAT_NEEDED
> + /* Packets starting a new connection must be NATted before the
> + * helper, so that the helper knows about the NAT. We enforce
> + * this by delaying both NAT and helper calls for unconfirmed
> + * connections until the commiting CT action. For later
> + * packets NAT and Helper may be called in either order.
> + *
> + * NAT will be done only if the CT action has NAT, and only
> + * once per packet (per zone), as guarded by the NAT bits in
> + * the key->ct.state.
> + */
> + if (info->nat && !(key->ct.state & OVS_CS_F_NAT_MASK) &&
> + (nf_ct_is_confirmed(ct) || info->commit) &&
> + ovs_ct_nat(net, key, info, skb, ct, ctinfo) != NF_ACCEPT) {
> + WARN_ONCE(1, "NAT rejected packet");
NAT can drop packets, so this warn_on I don't think you need it.
> + return -EINVAL;
> + }
> +#endif
> + /* Call the helper whenever nf_conntrack_in() was called for
> + * confirmed connections, but only when commiting for
> + * unconfirmed connections.
> + */
> + if ((nf_ct_is_confirmed(ct) ? !cached : info->commit)
> + && ovs_ct_helper(skb, info->family) != NF_ACCEPT) {
> + WARN_ONCE(1, "helper rejected packet");
Same thing may happen with helpers.
next prev parent reply other threads:[~2015-12-10 19:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 1:01 [PATCH net-next v4 0/8] openvswitch: NAT support Jarno Rajahalme
[not found] ` <1449622870-48944-1-git-send-email-jarno-LZ6Gd1LRuIk@public.gmane.org>
2015-12-09 1:01 ` [PATCH net-next v4 1/8] netfilter: Remove IP_CT_NEW_REPLY definition Jarno Rajahalme
2015-12-09 1:01 ` [PATCH net-next v4 2/8] netfilter: Factor out nf_ct_get_info() Jarno Rajahalme
2015-12-10 19:14 ` Pablo Neira Ayuso
2015-12-10 21:51 ` Jarno Rajahalme
2015-12-09 1:01 ` [PATCH net-next v4 3/8] netfilter: Allow calling into nat helper without skb_dst Jarno Rajahalme
2015-12-09 1:01 ` [PATCH net-next v4 4/8] openvswitch: Update the CT state key only after nf_conntrack_in() Jarno Rajahalme
2015-12-09 13:40 ` Sergei Shtylyov
2015-12-09 1:01 ` [PATCH net-next v4 5/8] openvswitch: Find existing conntrack entry after upcall Jarno Rajahalme
2015-12-09 1:01 ` [PATCH net-next v4 6/8] openvswitch: Handle NF_REPEAT in conntrack action Jarno Rajahalme
2015-12-09 1:01 ` [PATCH net-next v4 7/8] openvswitch: Delay conntrack helper call for new connections Jarno Rajahalme
2015-12-09 13:44 ` Sergei Shtylyov
2015-12-09 1:01 ` [PATCH net-next v4 8/8] openvswitch: Interface with NAT Jarno Rajahalme
2015-12-10 19:10 ` Pablo Neira Ayuso [this message]
2015-12-17 0:54 ` Jarno Rajahalme
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=20151210191008.GA20440@salvia \
--to=pablo@netfilter.org \
--cc=dev@openvswitch.org \
--cc=jarno@ovn.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).