netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tom Marshall <tmarshall@real.com>
To: netdev@oss.sgi.com
Subject: icmpv6_send filling the logs
Date: Thu, 20 May 2004 09:01:59 -0700	[thread overview]
Message-ID: <20040520160158.GA785@real.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3034 bytes --]

I have a Linux bridge machine with a 2.6.6 kernel.  It's a simple setup: two
ethernet cards (both using the eepro100 driver) acting as a bridge to my
office.  Here's the relevant ifconfig output:

    br0       Link encap:Ethernet  HWaddr 00:02:B3:16:D3:16  
              inet addr:172.23.22.199  Bcast:172.23.255.255  Mask:255.255.0.0
              inet6 addr: feed:4d56::202:b3ff:fe16:d316/64 Scope:Site
              inet6 addr: fe80::202:b3ff:fe16:d316/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

    eth0      Link encap:Ethernet  HWaddr 00:D0:B7:74:76:CE  
              inet6 addr: fe80::2d0:b7ff:fe74:76ce/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

    eth1      Link encap:Ethernet  HWaddr 00:02:B3:16:D3:16  
              inet6 addr: fe80::202:b3ff:fe16:d316/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

I've manually assigned the site address to br0.  I am running radvd 0.7.2 on
the machine.  Its configuration looks like this:

    interface br0 {
            AdvSendAdvert on;
    #       UnicastOnly on;
            prefix feed:4d56::/64 {
                    AdvOnLink on;
                    AdvAutonomous on;
            };
    };   

Occasionally the machine will get into a state where this message fills the
logs (thank goodness for the ratelimit):

    hashi kernel: icmpv6_send: no reply to icmp error

It looks like this traffic may be related to the error:

    08:14:49.389415 fe80::202:b3ff:fe16:d316 > ff02::1:ffb4:fdbb: icmp6: neighbor sol: who has fe80::20c:76ff:feb4:fdbb
    08:14:49.389455 fe80::20c:76ff:feb4:fdbb > fe80::202:b3ff:fe16:d316: icmp6: neighbor adv: tgt is fe80::20c:76ff:feb4:fdbb
    08:14:49.389486 fe80::202:b3ff:fe16:d316 > ff02::1:ff16:d316: icmp6: neighbor sol: who has fe80::202:b3ff:fe16:d316
    08:14:50.389265 fe80::202:b3ff:fe16:d316 > ff02::1:ffb4:fdbb: icmp6: neighbor sol: who has fe80::20c:76ff:feb4:fdbb
    08:14:50.389306 fe80::20c:76ff:feb4:fdbb > fe80::202:b3ff:fe16:d316: icmp6: neighbor adv: tgt is fe80::20c:76ff:feb4:fdbb
    08:14:50.389341 fe80::202:b3ff:fe16:d316 > ff02::1:ff16:d316: icmp6: neighbor sol: who has fe80::202:b3ff:fe16:d316

Note in the third and sixth lines the bridge is requesting its own address.
fe80::20c:76ff:feb4:fdbb belongs to another one of my machines, also running
Linux 2.6.6.  There's very little IPv6 traffic on this LAN (mostly my own
ssh sessions), though there are quite a few machines with various OS's that
have IPv6 enabled.  I can provide packet dumps if they are needed.

I've temporarily worked around this problem with the following command:

    # ip6tables -A OUTPUT -p icmpv6 -s fe80::/16 -j DROP

This works out okay for me because I always use the site local addresses,
but obviously it isn't an ideal solution...

-- 
The universe is ruled by letting things take their course.  It cannot be
ruled by interfering.
        -- Chinese proverb

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2004-05-20 16:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040520160158.GA785@real.com \
    --to=tmarshall@real.com \
    --cc=netdev@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).