[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#655314: marked as done (linux-image-3.1.0-1-amd64: ICMPv6 debugging message)

Your message dated Fri, 31 May 2013 18:04:35 +0200
with message-id <20130531160435.GA5794@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #655314,
regarding linux-image-3.1.0-1-amd64: ICMPv6 debugging message
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 owner@bugs.debian.org
immediately.)


-- 
655314: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655314
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-2.6
Version: 3.1.6-1
Severity: normal
Tags: ipv6

I'm running a Teredo relay/server using miredo-server and the
system logs are being filled with this message:

Jan 10 09:24:33 6to4 kernel: [93060.760149] icmpv6_send: no reply to icmp error
Jan 10 09:24:42 6to4 kernel: [93069.812879] icmpv6_send: no reply to icmp error

This message is generated when the kernel feels it should send
an ICMP error for a packet that itself was an ICMP error. RFC
says that you don't send errors for errors, so it's dropped, but
the developers have decided to put a debugging message in
that if-branch.

Normally that debugging message should never be displayed,
because under normal server conditions it should never occur.
However, due to the way Teredo works, this can and will happen
quite often. Would it be possible to remove or comment out
this particular debuggin message, because on normal servers
it has no value and on Teredo servers ... well ... it has no
value either but it fills the logs.

Or if it can't be removed, it should be possible to turn it
on and off using some sysctl.

-- Package-specific info:
** Kernel log: boot messages should be attached


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-image-3.1.0-1-amd64 depends on:
ii  debconf [debconf-2.0]                   1.5.41
ii  initramfs-tools [linux-initramfs-tool]  0.99
ii  linux-base                              3.4
ii  module-init-tools                       3.16-1

Versions of packages linux-image-3.1.0-1-amd64 recommends:
ii  firmware-linux-free  3

Versions of packages linux-image-3.1.0-1-amd64 suggests:
pn  grub-pc        1.99-14
pn  linux-doc-3.1  <none>

Versions of packages linux-image-3.1.0-1-amd64 is related to:
pn  firmware-bnx2           <none>
pn  firmware-bnx2x          <none>
pn  firmware-ipw2x00        <none>
pn  firmware-ivtv           <none>
pn  firmware-iwlwifi        <none>
pn  firmware-linux          <none>
pn  firmware-linux-nonfree  0.34
pn  firmware-qlogic         <none>
pn  firmware-ralink         <none>
pn  xen-hypervisor          <none>

-- debconf information excluded

--- End Message ---
--- Begin Message --- 
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.0 / Wheezy with a severity
less than important.

We don't have the ressources to reproduce the complete backlog of all older kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by sending
a mail to control@bugs.debian.org with the following three commands included in the
mail:

reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks

Cheers,
        Moritz

--- End Message ---
Reply to: