From: Mugunthan V N <mugunthanvnm@ti.com>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: Yegor Yefremov <yegorslists@googlemail.com>,
Grygorii Strashko <grygorii.strashko@ti.com>,
netdev <netdev@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
drivshin@allworx.com, ml@markusgrimm.de
Subject: Re: am335x: no multicast reception over VLAN
Date: Thu, 31 Mar 2016 12:07:15 +0530 [thread overview]
Message-ID: <56FCC59B.70209@ti.com> (raw)
In-Reply-To: <878u0z9297.fsf@dell.be.48ers.dk>
On Thursday 31 March 2016 01:17 AM, Peter Korsgaard wrote:
>>>>>> "Mugunthan" == Mugunthan V N <mugunthanvnm@ti.com> writes:
>
> Hi,
>
> > You had received these packets as tcpdump will enable promiscuous mode
> > so that you receive all the packets from the wire.
>
> FYI, you can use the -p option to tcpdump to not put the interface into
> promiscuous mode.
>
Thanks for the information Peter Korsgaard.
Yegor, can you provide tcpdump using -p as well in Grygorii commands.
Regards
Mugunthan V N
WARNING: multiple messages have this Message-ID (diff)
From: Mugunthan V N <mugunthanvnm@ti.com>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: Yegor Yefremov <yegorslists@googlemail.com>,
Grygorii Strashko <grygorii.strashko@ti.com>,
netdev <netdev@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
<drivshin@allworx.com>, <ml@markusgrimm.de>
Subject: Re: am335x: no multicast reception over VLAN
Date: Thu, 31 Mar 2016 12:07:15 +0530 [thread overview]
Message-ID: <56FCC59B.70209@ti.com> (raw)
In-Reply-To: <878u0z9297.fsf@dell.be.48ers.dk>
On Thursday 31 March 2016 01:17 AM, Peter Korsgaard wrote:
>>>>>> "Mugunthan" == Mugunthan V N <mugunthanvnm@ti.com> writes:
>
> Hi,
>
> > You had received these packets as tcpdump will enable promiscuous mode
> > so that you receive all the packets from the wire.
>
> FYI, you can use the -p option to tcpdump to not put the interface into
> promiscuous mode.
>
Thanks for the information Peter Korsgaard.
Yegor, can you provide tcpdump using -p as well in Grygorii commands.
Regards
Mugunthan V N
next prev parent reply other threads:[~2016-03-31 6:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 15:05 am335x: no multicast reception over VLAN Yegor Yefremov
2016-03-29 4:00 ` Mugunthan V N
2016-03-29 4:00 ` Mugunthan V N
2016-03-29 5:21 ` Yegor Yefremov
2016-03-29 11:05 ` Grygorii Strashko
2016-03-29 11:05 ` Grygorii Strashko
2016-03-29 12:35 ` Yegor Yefremov
2016-03-29 12:44 ` Grygorii Strashko
2016-03-29 12:44 ` Grygorii Strashko
2016-03-30 5:33 ` Mugunthan V N
2016-03-30 5:33 ` Mugunthan V N
2016-03-30 8:35 ` Yegor Yefremov
2016-03-30 16:52 ` Mugunthan V N
2016-03-30 16:52 ` Mugunthan V N
2016-03-30 19:47 ` Peter Korsgaard
2016-03-30 19:47 ` Peter Korsgaard
2016-03-31 6:37 ` Mugunthan V N [this message]
2016-03-31 6:37 ` Mugunthan V N
2016-03-31 7:52 ` Yegor Yefremov
2016-03-31 10:02 ` Mugunthan V N
2016-03-31 10:02 ` Mugunthan V N
2016-03-31 10:16 ` Yegor Yefremov
2016-04-01 12:09 ` Grygorii Strashko
2016-04-01 12:09 ` Grygorii Strashko
2016-04-05 6:11 ` Mugunthan V N
2016-04-05 6:11 ` Mugunthan V N
2016-04-05 6:22 ` Yegor Yefremov
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=56FCC59B.70209@ti.com \
--to=mugunthanvnm@ti.com \
--cc=drivshin@allworx.com \
--cc=grygorii.strashko@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=ml@markusgrimm.de \
--cc=netdev@vger.kernel.org \
--cc=peter@korsgaard.com \
--cc=yegorslists@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.