Modify

Opened 4 years ago

Last modified 2 years ago

#14173 new defect

icmp6_send: no reply to icmp error

Reported by: daniel.petre@… Owned by: developers
Priority: normal Milestone: Chaos Calmer 15.05
Component: kernel Version: Trunk
Keywords: Cc:

Description

Since 3.10.12 i get some lines (not so many, not so few) in dmesg:

"icmp6_send: no reply to icmp error"

the error seems to come from net/ipv6/icmp.c - is_ineligible()

my connection is pppoe with native ipv6 over it (dhcpv6).

Attachments (0)

Change History (4)

comment:1 Changed 4 years ago by yousong

Same here. Not "not so many". Kernel log was all filled with it.

The log item comes from http://lxr.free-electrons.com/source/net/ipv6/icmp.c#L144. It's a debug info output.

...
[693472.880000] icmp6_send: no reply to icmp error
[693472.880000] icmp6_send: no reply to icmp error
[693472.880000] icmp6_send: no reply to icmp error
[693472.880000] icmp6_send: no reply to icmp error
[693600.110000] icmp6_send: no reply to icmp error
[693618.500000] icmp6_send: no reply to icmp error
[693786.660000] icmp6_send: no reply to icmp error
[694415.890000] icmp6_send: no reply to icmp error
[694700.910000] icmp6_send: no reply to icmp error
[694937.410000] icmp6_send: no reply to icmp error
[694937.410000] icmp6_send: no reply to icmp error
[695232.040000] icmp6_send: no reply to icmp error
[695232.040000] icmp6_send: no reply to icmp error
[695232.040000] icmp6_send: no reply to icmp error
[695232.040000] icmp6_send: no reply to icmp error
[695232.040000] icmp6_send: no reply to icmp error
[695232.040000] icmp6_send: no reply to icmp error
[695404.850000] icmp6_send: no reply to icmp error
[695407.870000] icmp6_send: no reply to icmp error
[695407.870000] icmp6_send: no reply to icmp error
[695422.810000] icmp6_send: no reply to icmp error
[695422.810000] icmp6_send: no reply to icmp error
[695422.810000] icmp6_send: no reply to icmp error
[695422.810000] icmp6_send: no reply to icmp error
[695422.810000] icmp6_send: no reply to icmp error
[695510.980000] icmp6_send: no reply to icmp error
[696218.600000] icmp6_send: no reply to icmp error
[696413.240000] icmp6_send: no reply to icmp error
[696413.240000] icmp6_send: no reply to icmp error

comment:2 Changed 3 years ago by Alex106060

Same here running r42611. My log is messed up with tons of these messages.
Since you mentioned these are debug messages I tried to change loglevel of logd, but without success.

root@gw2:~# cat /etc/config/system
config system
        option cronloglevel '8'
        option klogconloglevel '1'
        option conloglevel '1'

Also with conloglevel=1 and klogconloglevel=1 the messages
"kern.debug kernel: [653338.227410] icmp6_send: no reply to icmp error"
are still there.

What can be done to get rid of these messages?

comment:3 Changed 3 years ago by christian@…

In my setup with native IPv6, with an openwrt as a member in the network (not the gateway) with an ip6tables rule:

ip6tables -A INPUT -j REJECT

every received multicast packet is triggering this message.

Solved by using

ip6tables -A INPUT -j DROP

comment:4 Changed 2 years ago by xavier@…

From the discussion outlined here [1]:

OK, this is a pure Linux kernel issue. I had a look at the sources of the kernel and in file net/ipv6/icmp.c are the following lines:
        /*
         *      Never answer to a ICMP packet.
         */

        if (is_ineligible(skb)) {
                if (net_ratelimit())
                        printk(KERN_DEBUG "icmpv6_send: no reply to icmp error\n");
                return;
        }
The function is_ineligible() itself carries the comment:
 * We do not reply, if:
 *      - it was icmp error message.
 *      - it is truncated, so that it is known, that protocol is ICMPV6
 *        (i.e. in the middle of some exthdr)
I would suggest: * either exclude kernel debug messages from beeing logged in /etc/syslogd.conf or * comment out the if and printk, but keep the return, then recompile your kernel. Maybe future versions of the 2.4 line remove that message. But it's a debug message (highest level of verbosity) so if you don't like it, remove it from the code or reconfigure your syslog-daemon. Hope that helps, good luck!

Comment out the code that prints the debug message and recompile the kernel to avoid these annoying lines.

[1] https://www.sixxs.net/forum/?msg=general-142198

Add Comment

Modify Ticket

Action
as new .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.