Bug#765690: packagename: type_problemheading_here

2014-10-17 Thread westlake 

Package: linux-image-3.17-rc5-amd64
Version: 3.17~rc5-1~exp1
Severity: normal

hi, can the following be a kernel problem?
I'll explain a bit, it's got to do with the iptables command..

(fwiw, there's a bug with the lsb-functions, 40-systemd which is instead 
this can be used to test rules.v4

iptables-restore  /etc/iptables/rules.v4
)

output,
iptables-restore v1.4.21: iptables-restore: unable to initialize table 
'nat'


Error occurred at line: 2
Try `iptables-restore -h' or 'iptables-restore --help' for more 
information 


all basic nat modules I can come up with modprobe are loaded, but 
iptables continues to fail, I checked if NAT is compiled 
/boot/config-3.17-rc5-amd64


lsmod |grep nat
act_nat12501  0
nft_chain_nat_ipv4 12552  0
nft_nat12507  0
nf_tables  54396  2 nft_chain_nat_ipv4,nft_nat
nf_nat_ipv412912  1 nft_chain_nat_ipv4
nf_nat_ipv612920  0
nf_nat 18241  4 
nft_chain_nat_ipv4,nft_nat,nf_nat_ipv4,nf_nat_ipv6
nf_conntrack   87476  5 
nf_nat,nf_nat_ipv4,nf_nat_ipv6,nf_conntrack_ipv4,nf_conntrack_ipv6 


so it looks like everything is compiled and loads, but iptables fails 
for v4. fwiw, the ip6tables loads properly for rules.v6..


If I recall the previous kernel in testing(vmlinuz-3.16-2-amd64) can 
have the iptables load ipv4 rules timely without issue



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#765690: packagename: type_problemheading_here

2014-10-17 Thread Ian Campbell 
On Fri, 2014-10-17 at 07:12 -0400, westlake wrote:
 hi, can the following be a kernel problem?

Please can you start to make use of the user support forums (e.g. the
debian-user mailing list) in the first instance rather than filing
things as bugs which are not yet clearly (or even vaguely) identifiable
as such.

Ian.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#765690: packagename: type_problemheading_here

2014-10-17 Thread westlake 

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 m...@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 m...@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.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#765690: packagename: type_problemheading_here

2014-10-17 Thread westlake 

this report is for package maintainers, not clueless idiots.

thank you


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org