32-bit ulogd running on 64-bit kernel writes garbage to syslogemu

Bug #1048974 reported by Roman Fiedler
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ulogd (Ubuntu)
New
Undecided
Unassigned

Bug Description

After upgrading the kernel from 32 to 64 bit WITHOUT upgrading the system to 64 bit, everything worked fine except that the ulogd (1.24-3ubuntu1) messages written to syslogemu were complete garbage, e.g.

Jan 1 00:00:00 localhost 0 0 20 0 1 < IN= [unprintable bytes]
R OUT= [unprintable bytes] MAC=50:54:2d:49:4e:46:4f:00:00:00:00:00:00:00:00:00:00:00:00:0e:00:50:56:9c:3c:a6:00:50:56:9c:00:a2:08:00:34:35:37:36:36:31:32:20:34:32:38:37:38:35:39:38:34:30:20:34:32:38:37:38:35:38:31:30:34:20:34:31:35:31:32 SRC=32.48.32.48 DST=32.49.55.32 LEN=13112 TOS=10 PREC=0x20 TTL=57 ID=12340 MF FRAG:5940 PROTO=53

(I guess, this was a TCP4 SYN)

All other iptables tools seem to work correctly, e.g. iptables-save shows correct interface names, rules and also the ruleset works as expected. From that I would expect, that the error should reside in the netlink handover of captured packets to ulogd or the ulogd handling of those messages.

* I asked about problem on netfilter-devel (upstream), but no replies so far: http://marc.info/?l=netfilter-devel&m=134725936925109&w=2

* Not clear, if 32-bit ulogd can really work on 64-bit kernel

System info:

# lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04

# dpkg --print-architecture
i386

# apt-cache policy ulogd
ulogd:
  Installed: 1.24-3ubuntu1
  Candidate: 1.24-3ubuntu1
  Version table:
 *** 1.24-3ubuntu1 0
        500 http://ubuntu-proxy-ehealth.d03.arc.local/ubuntu/ natty/universe i386 Packages
        100 /var/lib/dpkg/status

# cat /proc/version
Linux version 3.3.2-vs2.3.3.2 (root@v3ls1202) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu4) ) #1 SMP Tue Apr 17 16:37:51 UTC 2012

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.