netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 93731] New: GARP packet is not sent for interface up
Date: Tue, 24 Feb 2015 14:21:56 -0800	[thread overview]
Message-ID: <20150224142156.5cd1ea91@urahara> (raw)



Begin forwarded message:

Date: Tue, 24 Feb 2015 08:07:40 +0000
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "shemminger@linux-foundation.org" <shemminger@linux-foundation.org>
Subject: [Bug 93731] New: GARP packet is not sent for interface up


https://bugzilla.kernel.org/show_bug.cgi?id=93731

            Bug ID: 93731
           Summary: GARP packet is not sent for interface up
           Product: Networking
           Version: 2.5
    Kernel Version: 3.10
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: IPV4
          Assignee: shemminger@linux-foundation.org
          Reporter: aniyas15@gmail.com
        Regression: No

Hi All,

I am working custom platform based on x86_64 running 3.10 kernel,
Recently I found an issue related to GARP. It seems like  no GARP
packets are being sent out when an Interface is made up. But I also
noticed that only when I use "arping" tool only then it sends out any
GARP packet.

I also try setting the net variable "arp_notify" then I see the
arp_send() function is being called after that I am unable to track
further.

Could you please help me, what could be issue, Is it a valid
expectation that during interface up the linux kernel should send out
GARP packet? If so, am I missing any kernel configuration related to
it?

Thanks in Advance.

Regards,
A.Mydeen.

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2015-02-24 22:21 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=20150224142156.5cd1ea91@urahara \
    --to=stephen@networkplumber.org \
    --cc=netdev@vger.kernel.org \
    /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).