Your message dated Thu, 28 Jan 2016 13:58:42 +0100
with message-id
<caoksjbin2zvjjv8kuwxe03b1knmujzztnhkyyscm94-h0ei...@mail.gmail.com>
and subject line shorewall: Incorrect kernel messages marking
has caused the Debian Bug report #681229,
regarding shorewall: Incorrect kernel messages marking
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
681229: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681229
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: shorewall
Version: 4.5.5.3-1
Severity: normal
Dear Maintainer,
Shorewall logging causes incorrect prefix to show in syslog:
Jul 11 09:09:34 webhost kernel: [89535.830300] --log-prefixIN=eth0 OUT=
MAC=00:0c:29:f7:0c:4b:00:1a:64:20:3c:12:08:00 SRC=199.253.60.146 etc.
as oppose to correct message:
Jul 11 09:18:31 prophit kernel: [8087718.916833]
Shorewall:net2fw:DROP:IN=eth0 OUT=
MAC=70:71:bc:e3:22:85:00:1b:d5:ff:28:de:08:00 SRC=220.3.184.164 etc.
It started after upgrade to shorewall 4.5.5.1, no change in 4.5.5.3.
Shorewall 4.4.27.3 does not show this behaviour.
Probably just a silly typo somewhere... :)
Regards,
David Priban
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages shorewall depends on:
ii bc 1.06.95-2+b1
ii debconf [debconf-2.0] 1.5.44
ii iproute 20120521-3
ii iptables 1.4.14-2
ii perl-modules 5.14.2-12
ii shorewall-core 4.5.5.3-1
shorewall recommends no packages.
Versions of packages shorewall suggests:
ii linux-image-3.0.0-1-amd64 [linux-image] 3.0.0-3
ii linux-image-3.2.0-2-amd64 [linux-image] 3.2.20-1
ii linux-image-3.2.0-3-amd64 [linux-image] 3.2.21-3
ii make 3.81-8.2
pn shorewall-doc <none>
-- Configuration Files:
/etc/default/shorewall changed:
startup=1
OPTIONS=""
STARTOPTIONS=""
RESTARTOPTIONS=""
INITLOG=/dev/null
SAFESTOP=0
-- debconf information:
shorewall/dont_restart:
shorewall/major_release:
shorewall/invalid_config:
--- End Message ---
--- Begin Message ---
Control: fixed -1 1.6.0-2
Hi,
iptables includes a fix for this since years.
I think we can close the bug.
thanks, best regards.
--
Arturo Borrero González
--- End Message ---
