Bug#765690: packagename: type_problemheading_here

[westlake <westlake2012@videotron.ca>]

There's a bug in multiple places.

1) netfilter-persistent/systemd fails
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764950

2) Emailed J.Wiltshire, he never responded. He's responsible for the 
netfilter package

3) There is a systemd bug related to the netfilter-persistent package, 
filed over here,
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765683


"linux (3.17-1~exp1) experimental; urgency=medium

  * New upstream release: http://kernelnewbies.org/Linux_3.17

  * armel: Drop ixp4xx image.
  * topconfig: Reenable renamed IP_NF_NAT. (closes #762458)
  * udeb: refix renamed i2c-core.

 -- maximilian attems <maks@debian.org>  Tue, 14 Oct 2014 23:01:39 +0200

linux (3.17~rc5-1~exp1) experimental; urgency=medium

  * New upstream release candidate

  [ Ben Hutchings ]
  * aufs: Update to aufs3.x-rcN-20140908

  [ maximilian attems ]
  * udeb: fix renamed i2ccore.

 -- maximilian attems <maks@debian.org>  Thu, 18 Sep 2014 23:50:00 +0200
"

http://metadata.ftp-master.debian.org/changelogs//main/l/linux/linux_3.17-1~exp1_changelog


I think it's very clear there was indeed a change with nat in this kernel.

This is not a configuration issue, otherwise iptables would be loading 
successfully without crashing with a "NAT" message.

fwiw, iptables relies on the "kernel" for the "NAT" modules, so it 
appears quite clearly what the problem is, and that is this kernel has 
something new with "NAT" causing iptables to fail. Not rocket science.