All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kristian Evensen <kristian.evensen@gmail.com>
To: Florian Westphal <fw@strlen.de>
Cc: Netfilter Development Mailing list
	<netfilter-devel@vger.kernel.org>,
	Network Development <netdev@vger.kernel.org>
Subject: Re: Silently dropped UDP packets on kernel 4.14
Date: Wed, 2 May 2018 00:42:52 +0200	[thread overview]
Message-ID: <CAKfDRXhkXvF==6LQFOG3Rf4dH4QVVUxR=1cXZoM2FPQksGdxwg@mail.gmail.com> (raw)
In-Reply-To: <20180501222406.fy5rph2t4dzndhu2@breakpoint.cc>

Hi,

Thanks for your quick and detailed reply!

On Wed, May 2, 2018 at 12:24 AM, Florian Westphal <fw@strlen.de> wrote:
> I'm not sure what the best way to solve this is, we either need
> to insert earlier in nfqueue case, or do conflict resolution in nfqueue
> case (and perhaps also nat undo? not sure).

My knowledge of the conntrack/nat subsystem is not that great, and I
don't know the implications of what I am about to suggest. However,
considering that the two packets represent the same flow, wouldn't it
be possible to apply the existing nat-mapping to the second packet,
and then let the second packet pass?

BR,
Kristian

  reply	other threads:[~2018-05-01 22:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01 18:50 Silently dropped UDP packets on kernel 4.14 Kristian Evensen
2018-05-01 18:58 ` Kristian Evensen
2018-05-01 22:24   ` Florian Westphal
2018-05-01 22:42     ` Kristian Evensen [this message]
2018-05-02 23:54       ` Kristian Evensen
2018-05-03  5:03         ` Florian Westphal
2018-05-03  9:06           ` Kristian Evensen
2018-05-03  9:42           ` Michal Kubecek
2018-05-03 11:19             ` Kristian Evensen

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='CAKfDRXhkXvF==6LQFOG3Rf4dH4QVVUxR=1cXZoM2FPQksGdxwg@mail.gmail.com' \
    --to=kristian.evensen@gmail.com \
    --cc=fw@strlen.de \
    --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 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.