Your message dated Tue, 29 Apr 2025 16:10:08 -0600
with message-id
<CAA0dE=VwUj7k=73puwpcp+irpmu2civrgkejmu5xu7ijyhg...@mail.gmail.com>
and subject line Re: Bug#1099651: syslog filled with joold debug despite being
disabled
has caused the Debian Bug report #1099651,
regarding syslog filled with joold debug despite being disabled
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.)
--
1099651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1099651
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: jool
Version: 4.1.9-1
Severity: normal
Hi,
We've got a jool instance defined as:
# jool -i demo global display
manually-enabled: true
pool6: 2001:db8::/64
lowest-ipv6-mtu: 1280
logging-debug: false
zeroize-traffic-class: false
override-tos: false
tos: 0
mtu-plateaus: 65535,32000,17914,8166,4352,2002,1492,1006,508,296,68
address-dependent-filtering: false
drop-externally-initiated-tcp: false
drop-icmpv6-info: false
source-icmpv6-errors-better: true
f-args: 11 (0b1011): SrcAddr:1 SrcPort:0 DstAddr:1 DstPort:1
handle-rst-during-fin-rcv: false
tcp-est-timeout: 2:00:00 (HH:MM:SS)
tcp-trans-timeout: 0:05:00 (HH:MM:SS)
udp-timeout: 0:02:00 (HH:MM:SS)
icmp-timeout: 0:00:30 (HH:MM:SS)
logging-bib: true
logging-session: true
maximum-simultaneous-opens: 100
ss-enabled: true
ss-flush-asap: true
ss-flush-deadline: 2000
ss-capacity: 512
ss-max-payload: 1452
#
And the setup works just fine for forwarding.
Yet in /var/log/syslog we find tons of:
...
2025-03-06T12:49:53.339324+01:00 fw1 joold: Received a packet from kernelspace.
2025-03-06T12:49:53.339455+01:00 fw1 joold: Sending 140 bytes to the network...
2025-03-06T12:49:53.339480+01:00 fw1 joold: Sent 140 bytes to the network.
2025-03-06T12:49:53.343011+01:00 fw1 joold: Received a packet from kernelspace.
2025-03-06T12:49:53.343050+01:00 fw1 joold: Sending 140 bytes to the network...
2025-03-06T12:49:53.343070+01:00 fw1 joold: Sent 140 bytes to the network.
2025-03-06T12:49:53.354028+01:00 fw1 joold: Received a packet from kernelspace.
2025-03-06T12:49:53.354063+01:00 fw1 joold: Sending 140 bytes to the network...
2025-03-06T12:49:53.354083+01:00 fw1 joold: Sent 140 bytes to the network.
2025-03-06T12:49:53.988336+01:00 fw1 joold: Received a packet from kernelspace.
2025-03-06T12:49:53.988444+01:00 fw1 joold: Sending 140 bytes to the network...
2025-03-06T12:49:53.988476+01:00 fw1 joold: Sent 140 bytes to the network.
2025-03-06T12:49:53.992093+01:00 fw1 joold: Received a packet from kernelspace.
2025-03-06T12:49:53.992127+01:00 fw1 joold: Sending 140 bytes to the network...
...
Despite the logging-debug being set to false.
As it seems we already have all debug set to disabled, but still the
loglines are being printed.
Please explain how to stop them.
Best regards,
Kilian
-- System Information:
Debian Release: 12.9
APT prefers stable-security
APT policy: (990, 'stable-security'), (990, 'stable'), (800, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-31-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Version: 4.1.14-1
Fixed upstream; package 4.1.14-1 already contains the fix.
(I forgot to close this in the changelog.)
On Thu, Mar 6, 2025 at 5:57 AM Kilian Krause <[email protected]> wrote:
>
> Source: jool
> Version: 4.1.9-1
> Severity: normal
>
> Hi,
>
> We've got a jool instance defined as:
> # jool -i demo global display
> manually-enabled: true
> pool6: 2001:db8::/64
> lowest-ipv6-mtu: 1280
> logging-debug: false
> zeroize-traffic-class: false
> override-tos: false
> tos: 0
> mtu-plateaus: 65535,32000,17914,8166,4352,2002,1492,1006,508,296,68
> address-dependent-filtering: false
> drop-externally-initiated-tcp: false
> drop-icmpv6-info: false
> source-icmpv6-errors-better: true
> f-args: 11 (0b1011): SrcAddr:1 SrcPort:0 DstAddr:1 DstPort:1
> handle-rst-during-fin-rcv: false
> tcp-est-timeout: 2:00:00 (HH:MM:SS)
> tcp-trans-timeout: 0:05:00 (HH:MM:SS)
> udp-timeout: 0:02:00 (HH:MM:SS)
> icmp-timeout: 0:00:30 (HH:MM:SS)
> logging-bib: true
> logging-session: true
> maximum-simultaneous-opens: 100
> ss-enabled: true
> ss-flush-asap: true
> ss-flush-deadline: 2000
> ss-capacity: 512
> ss-max-payload: 1452
> #
>
> And the setup works just fine for forwarding.
>
> Yet in /var/log/syslog we find tons of:
> ...
> 2025-03-06T12:49:53.339324+01:00 fw1 joold: Received a packet from
> kernelspace.
> 2025-03-06T12:49:53.339455+01:00 fw1 joold: Sending 140 bytes to the
> network...
> 2025-03-06T12:49:53.339480+01:00 fw1 joold: Sent 140 bytes to the network.
> 2025-03-06T12:49:53.343011+01:00 fw1 joold: Received a packet from
> kernelspace.
> 2025-03-06T12:49:53.343050+01:00 fw1 joold: Sending 140 bytes to the
> network...
> 2025-03-06T12:49:53.343070+01:00 fw1 joold: Sent 140 bytes to the network.
> 2025-03-06T12:49:53.354028+01:00 fw1 joold: Received a packet from
> kernelspace.
> 2025-03-06T12:49:53.354063+01:00 fw1 joold: Sending 140 bytes to the
> network...
> 2025-03-06T12:49:53.354083+01:00 fw1 joold: Sent 140 bytes to the network.
> 2025-03-06T12:49:53.988336+01:00 fw1 joold: Received a packet from
> kernelspace.
> 2025-03-06T12:49:53.988444+01:00 fw1 joold: Sending 140 bytes to the
> network...
> 2025-03-06T12:49:53.988476+01:00 fw1 joold: Sent 140 bytes to the network.
> 2025-03-06T12:49:53.992093+01:00 fw1 joold: Received a packet from
> kernelspace.
> 2025-03-06T12:49:53.992127+01:00 fw1 joold: Sending 140 bytes to the
> network...
> ...
>
> Despite the logging-debug being set to false.
>
> As it seems we already have all debug set to disabled, but still the
> loglines are being printed.
>
> Please explain how to stop them.
>
> Best regards,
> Kilian
>
> -- System Information:
> Debian Release: 12.9
> APT prefers stable-security
> APT policy: (990, 'stable-security'), (990, 'stable'), (800, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 6.1.0-31-amd64 (SMP w/8 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
> TAINT_UNSIGNED_MODULE
> Locale: LANG=en_US.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
--- End Message ---
