Netdev List
 help / color / mirror / Atom feed
From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Patrick McHardy <kaber@trash.net>,
	Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
	"David S. Miller" <davem@davemloft.net>,
	netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: kernel BUG at net/netfilter/nf_nat_core.c:395
Date: Wed, 10 Feb 2016 19:34:40 +0200	[thread overview]
Message-ID: <3938975.V1JGlkzPkU@spock> (raw)

Hi.

With 4.4.1 I've got BUG_ON() triggered in net/netfilter/nf_nat_core.c:395, 
nf_nat_setup_info(), today on my home router.

Here is full trace got via netconsole: [1]

I perform LAN NATting using nftables like this:

===
table ip nat {
        chain prerouting {
                type nat hook prerouting priority -150;
        }
 
        chain postrouting {
                type nat hook postrouting priority -150;
 
                oifname enp2s0 ip saddr 172.17.28.0/24 counter snat 1.2.3.4
                oifname enp2s0 ip saddr 172.17.29.0/24 counter snat 1.2.3.4
                oifname enp2s0 ip saddr 172.17.31.0/24 counter snat 1.2.3.4
                oifname enp2s0 ip saddr 172.17.35.0/24 counter snat 1.2.3.4
                oifname enp2s0 ip saddr 172.17.37.0/24 counter snat 1.2.3.4
                oifname tun0 ip saddr 172.17.28.0/24 counter masquerade
                oifname tun0 ip saddr 172.17.29.0/24 counter masquerade
                oifname tinc0 ip saddr 172.17.28.0/24 counter masquerade
                oifname tinc0 ip saddr 172.17.29.0/24 counter masquerade
        }
}
===

Traffic filtering is done via nftables as well.

Ideas? What could I do to debug the issue better?

[1] https://gist.github.com/bbb3712f40a7753537fe

                 reply	other threads:[~2016-02-10 17:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3938975.V1JGlkzPkU@spock \
    --to=oleksandr@natalenko.name \
    --cc=coreteam@netfilter.org \
    --cc=davem@davemloft.net \
    --cc=kaber@trash.net \
    --cc=kadlec@blackhole.kfki.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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