From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Yegor Yefremov <yegorslists@googlemail.com>,
Mugunthan V N <mugunthanvnm@ti.com>
Cc: 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: Tue, 29 Mar 2016 14:05:16 +0300 [thread overview]
Message-ID: <56FA616C.9080502@ti.com> (raw)
In-Reply-To: <CAGm1_ksxRPCAqx4n5gbsARSYeF116BT7r8cC6=1QYnEsYRxpVw@mail.gmail.com>
On 03/29/2016 08:21 AM, Yegor Yefremov wrote:
> Hi Mugunthan,
>
> On Tue, Mar 29, 2016 at 6:00 AM, Mugunthan V N <mugunthanvnm@ti.com> wrote:
>> Hi Yegor
>>
>> On Wednesday 16 March 2016 08:35 PM, Yegor Yefremov wrote:
>>> I have an am335x based board using CPSW in Dual EMAC mode. Without
>>> VLAN IDs I can receive and send multicast packets [1]. When I create
>>> VLAN ID:
>>>
>>> ip link add link eth1 name eth1.100 type vlan id 100
>>> ip addr add 192.168.100.2/24 brd 192.168.100.255 dev eth1.100
>>> route add -net 224.0.0.0 netmask 224.0.0.0 eth1.100
>>>
>>> I can successfully send multicast packets, but not receive them. On
>>> the other side of the Ethernet cable I've used Pandaboard. Pandaboard
>>> could both receive and send multicast packets via VLAN.
>>
>> Are you trying multicast tx/rx on eth1 or eth1.100?
>
> I'm trying multicast tx/rx on eth1.100.
>
> eth1 has no problems.
>
it'd be nice if will be able to post here output fom commands:
# switch-config -d [git://git.ti.com/switch-config/switch-config.git v4.1]
# ifconfig -a
# tcpdump -e -f -Q in -i eth0
# tcpdump -e -f -Q in -i eth0.100
--
regards,
-grygorii
next prev parent reply other threads:[~2016-03-29 11:05 UTC|newest]
Thread overview: 17+ 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 5:21 ` Yegor Yefremov
2016-03-29 11:05 ` Grygorii Strashko [this message]
2016-03-29 12:35 ` Yegor Yefremov
2016-03-29 12:44 ` Grygorii Strashko
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 19:47 ` Peter Korsgaard
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:16 ` Yegor Yefremov
2016-04-01 12:09 ` Grygorii Strashko
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=56FA616C.9080502@ti.com \
--to=grygorii.strashko@ti.com \
--cc=drivshin@allworx.com \
--cc=linux-omap@vger.kernel.org \
--cc=ml@markusgrimm.de \
--cc=mugunthanvnm@ti.com \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox