[Bug 590] iptables unknown target data

[bugzilla-daemon at bugzilla.netfilter.org]

http://bugzilla.netfilter.org/show_bug.cgi?id=590





------- Comment #1 from idallen at idallen.ca  2009-04-07 14:16 -------
Maybe this isn't your fault.  I got the "official" sources for iptables
for Ubuntu 8.04, compiled iptables, and got the same errors.

# apt-get source iptables
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Need to get 759kB of source archives.
Get:1 http://ca.archive.ubuntu.com hardy/main iptables 1.3.8.0debian1-1ubuntu2
(dsc) [757B]
Get:2 http://ca.archive.ubuntu.com hardy/main iptables 1.3.8.0debian1-1ubuntu2
(tar) [744kB]
Get:3 http://ca.archive.ubuntu.com hardy/main iptables 1.3.8.0debian1-1ubuntu2
(diff) [14.1kB]
Fetched 759kB in 3s (194kB/s)    
dpkg-source: extracting iptables in iptables-1.3.8.0debian1
dpkg-source: unpacking iptables_1.3.8.0debian1.orig.tar.gz
dpkg-source: applying ./iptables_1.3.8.0debian1-1ubuntu2.diff.gz

# cd iptables ; make clean ; make
[...]

# ./iptables -L -t mangle 
[...]
Chain ianmark (0 references)
target     prot opt source               destination         
CONNMARK   all  --  anywhere             anywhere            [12 bytes of
unknown target data] 
RETURN     all  --  anywhere             anywhere            UNKNOWN match
`mark' [4 bytes of unknown target data] 
LOG        all  --  anywhere             anywhere            [32 bytes of
unknown target data] 
RETURN     udp  --  anywhere             anywhere            UNKNOWN match
`udp' [4 bytes of unknown target data] 
RETURN     tcp  --  anywhere             anywhere            UNKNOWN match
`tcp' [4 bytes of unknown target data] 
RETURN     all  --  anywhere             192.168.0.0/16      [4 bytes of
unknown target data] 
RETURN     all  --  anywhere             172.16.0.0/12       [4 bytes of
unknown target data] 
RETURN     all  --  anywhere             10.0.0.0/8          [4 bytes of
unknown target data] 

How did I screw things up at my end?  I know I downloaded the openvz
kernel at one point, though uname suggests I'm not running it at the
moment (assuming that uname would show).  Perhaps that affected some
#include offsets somewhere?

Linux idallen.ca 2.6.24-23-generic #1 SMP Mon Jan 26 00:13:11 UTC 2009 i686
GNU/Linux

kernel-related files in /boot:
-rw-r--r-- 1 root root  905809 Jan 25 23:30 System.map-2.6.24-23-generic
-rw-r--r-- 1 root root  951363 Jan 25 23:51 System.map-2.6.24-23-openvz
-rw-r--r-- 1 root root  422838 Jan 25 23:30 abi-2.6.24-23-generic
-rw-r--r-- 1 root root   80051 Jan 25 23:30 config-2.6.24-23-generic
-rw-r--r-- 1 root root   90360 Jan 25 23:51 config-2.6.24-23-openvz
-rw-r--r-- 1 root root 7498495 Feb 11 01:29 initrd.img-2.6.24-23-generic
-rw-r--r-- 1 root root 7511690 Feb 17 16:18 initrd.img-2.6.24-23-openvz
-rw-r--r-- 1 root root 1922904 Jan 25 23:30 vmlinuz-2.6.24-23-generic
-rw-r--r-- 1 root root 1964312 Jan 25 23:51 vmlinuz-2.6.24-23-openvz

grub boot entry (default 0 should have booted the openvz kernel...):

title           Ubuntu 8.04.2, kernel 2.6.24-23-openvz
root            (hd6,0)
kernel          /vmlinuz-2.6.24-23-openvz
root=UUID=47ee9584-070d-4c4a-b2f9-1d1c896b2873 ro xforcevesa
initrd          /initrd.img-2.6.24-23-openvz

title           Ubuntu 8.04.2, kernel 2.6.24-23-openvz (recovery mode)
root            (hd6,0)
kernel          /vmlinuz-2.6.24-23-openvz
root=UUID=47ee9584-070d-4c4a-b2f9-1d1c896b2873 ro single
initrd          /initrd.img-2.6.24-23-openvz

title           Ubuntu 8.04.2, kernel 2.6.24-23-generic
root            (hd6,0)
kernel          /vmlinuz-2.6.24-23-generic
root=UUID=47ee9584-070d-4c4a-b2f9-1d1c896b2873 ro xforcevesa
initrd          /initrd.img-2.6.24-23-generic

title           Ubuntu 8.04.2, kernel 2.6.24-23-generic (recovery mode)
root            (hd6,0)
kernel          /vmlinuz-2.6.24-23-generic
root=UUID=47ee9584-070d-4c4a-b2f9-1d1c896b2873 ro single
initrd          /initrd.img-2.6.24-23-generic


-- 
Configure bugmail: http://bugzilla.netfilter.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.