Re: am335x: no multicast reception over VLAN
Grygorii, Mugunthan, On Tue, Apr 5, 2016 at 8:11 AM, Mugunthan V Nwrote: > On Friday 01 April 2016 05:39 PM, Grygorii Strashko wrote: >> On 03/31/2016 10:52 AM, Yegor Yefremov wrote: >>> On Thu, Mar 31, 2016 at 8:37 AM, Mugunthan V N wrote: On Thursday 31 March 2016 01:17 AM, Peter Korsgaard wrote: >> "Mugunthan" == Mugunthan V N 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. >>> >>> Before VLAN configuration: >>> >>> # switch-config -d >>> cpsw hw version 1.12 (0) >>> 0 : type: vlan , vid = 1, untag_force = 0x3, reg_mcast = 0x3, >>> unreg_mcast = 0x0, member_list = 0x3 >>> 1 : type: mcast, vid = 1, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, >>> no super, port_mask = 0x3 >>> 2 : type: ucast, vid = 1, addr = 74:6a:8f:00:16:12, ucast_type = >>> persistant, port_num = 0x0, Secure >>> 3 : type: vlan , vid = 0, untag_force = 0x7, reg_mcast = 0x0, >>> unreg_mcast = 0x0, member_list = 0x7 >>> 4 : type: mcast, vid = 1, addr = 01:00:5e:00:00:01, mcast_state = f, >>> no super, port_mask = 0x3 >>> 5 : type: vlan , vid = 2, untag_force = 0x5, reg_mcast = 0x5, >>> unreg_mcast = 0x0, member_list = 0x5 >>> 6 : type: mcast, vid = 2, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, >>> no super, port_mask = 0x5 >>> 7 : type: ucast, vid = 2, addr = 74:6a:8f:00:16:13, ucast_type = >>> persistant, port_num = 0x0, Secure >>> 8 : type: mcast, vid = 2, addr = 01:00:5e:00:00:01, mcast_state = f, >>> no super, port_mask = 0x5 >>> >>> After VLAN configuration: >>> >>> # switch-config -d >>> cpsw hw version 1.12 (0) >>> 0 : type: vlan , vid = 1, untag_force = 0x3, reg_mcast = 0x3, >>> unreg_mcast = 0x0, member_list = 0x3 >>> 1 : type: mcast, vid = 1, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, >>> no super, port_mask = 0x3 >>> 2 : type: ucast, vid = 1, addr = 74:6a:8f:00:16:12, ucast_type = >>> persistant, port_num = 0x0, Secure >>> 3 : type: vlan , vid = 0, untag_force = 0x7, reg_mcast = 0x0, >>> unreg_mcast = 0x0, member_list = 0x7 >>> 4 : type: mcast, vid = 1, addr = 01:00:5e:00:00:01, mcast_state = f, >>> no super, port_mask = 0x3 >>> 5 : type: vlan , vid = 2, untag_force = 0x5, reg_mcast = 0x5, >>> unreg_mcast = 0x0, member_list = 0x5 >>> 6 : type: mcast, vid = 2, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, >>> no super, port_mask = 0x5 >>> 7 : type: ucast, vid = 2, addr = 74:6a:8f:00:16:13, ucast_type = >>> persistant, port_num = 0x0, Secure >>> 8 : type: mcast, vid = 2, addr = 01:00:5e:00:00:01, mcast_state = f, >>> no super, port_mask = 0x5 >>> 9 : type: vlan , vid = 100, untag_force = 0x0, reg_mcast = 0x5, >>> unreg_mcast = 0x0, member_list = 0x5 >>> 10 : type: ucast, vid = 100, addr = 74:6a:8f:00:16:13, ucast_type = >>> persistant, port_num = 0x0 >>> 11 : type: mcast, vid = 100, addr = ff:ff:ff:ff:ff:ff, mcast_state = >>> f, no super, port_mask = 0x5 >>> 12 : type: mcast, vid = 2, addr = 01:80:c2:00:00:21, mcast_state = f, >>> no super, port_mask = 0x5 >>> >>> During mulitcast receive: >>> >>> # switch-config -d >>> cpsw hw version 1.12 (0) >>> 0 : type: vlan , vid = 1, untag_force = 0x3, reg_mcast = 0x3, unreg_mcast >>> = 0x0, member_list = 0x3 >>> 1 : type: mcast, vid = 1, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, no >>> super, port_mask = 0x3 >>> 2 : type: ucast, vid = 1, addr = 74:6a:8f:00:16:12, ucast_type = >>> persistant, port_num = 0x0, Secure >>> 3 : type: vlan , vid = 0, untag_force = 0x7, reg_mcast = 0x0, unreg_mcast >>> = 0x0, member_list = 0x7 >> >> unreg_mcast = 0x0 means unregistered multicast packets will be dropped >> >>> 4 : type: mcast, vid = 1, addr = 01:00:5e:00:00:01, mcast_state = f, no >>> super, port_mask = 0x3 >>> 5 : type: vlan , vid = 2, untag_force = 0x5, reg_mcast = 0x5, unreg_mcast >>> = 0x0, member_list = 0x5 >> >> unreg_mcast = 0x0 >> >>> 6 : type: mcast, vid = 2, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, no >>> super, port_mask = 0x5 >>> 7 : type: ucast, vid = 2, addr = 74:6a:8f:00:16:13, ucast_type = >>> persistant, port_num = 0x0, Secure >>> 8 : type: mcast, vid = 2, addr = 01:00:5e:00:00:01, mcast_state = f, no >>> super, port_mask = 0x5 >>> 9 : type: vlan , vid = 100, untag_force = 0x0, reg_mcast = 0x5, >>> unreg_mcast = 0x0, member_list = 0x5 >> >> unreg_mcast = 0x0 >> >>> 10 : type: ucast, vid = 100, addr = 74:6a:8f:00:16:13, ucast_type = >>> persistant, port_num = 0x0 >>> 11 : type: mcast, vid = 100, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, no >>> super, port_mask = 0x5 >>> 12 : type: mcast, vid = 2, addr = 01:80:c2:00:00:21, mcast_state = f, no >>> super,
Re: am335x: no multicast reception over VLAN
On Friday 01 April 2016 05:39 PM, Grygorii Strashko wrote: > On 03/31/2016 10:52 AM, Yegor Yefremov wrote: >> On Thu, Mar 31, 2016 at 8:37 AM, Mugunthan V Nwrote: >>> On Thursday 31 March 2016 01:17 AM, Peter Korsgaard wrote: > "Mugunthan" == Mugunthan V N 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. >> >> Before VLAN configuration: >> >> # switch-config -d >> cpsw hw version 1.12 (0) >> 0 : type: vlan , vid = 1, untag_force = 0x3, reg_mcast = 0x3, >> unreg_mcast = 0x0, member_list = 0x3 >> 1 : type: mcast, vid = 1, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, >> no super, port_mask = 0x3 >> 2 : type: ucast, vid = 1, addr = 74:6a:8f:00:16:12, ucast_type = >> persistant, port_num = 0x0, Secure >> 3 : type: vlan , vid = 0, untag_force = 0x7, reg_mcast = 0x0, >> unreg_mcast = 0x0, member_list = 0x7 >> 4 : type: mcast, vid = 1, addr = 01:00:5e:00:00:01, mcast_state = f, >> no super, port_mask = 0x3 >> 5 : type: vlan , vid = 2, untag_force = 0x5, reg_mcast = 0x5, >> unreg_mcast = 0x0, member_list = 0x5 >> 6 : type: mcast, vid = 2, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, >> no super, port_mask = 0x5 >> 7 : type: ucast, vid = 2, addr = 74:6a:8f:00:16:13, ucast_type = >> persistant, port_num = 0x0, Secure >> 8 : type: mcast, vid = 2, addr = 01:00:5e:00:00:01, mcast_state = f, >> no super, port_mask = 0x5 >> >> After VLAN configuration: >> >> # switch-config -d >> cpsw hw version 1.12 (0) >> 0 : type: vlan , vid = 1, untag_force = 0x3, reg_mcast = 0x3, >> unreg_mcast = 0x0, member_list = 0x3 >> 1 : type: mcast, vid = 1, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, >> no super, port_mask = 0x3 >> 2 : type: ucast, vid = 1, addr = 74:6a:8f:00:16:12, ucast_type = >> persistant, port_num = 0x0, Secure >> 3 : type: vlan , vid = 0, untag_force = 0x7, reg_mcast = 0x0, >> unreg_mcast = 0x0, member_list = 0x7 >> 4 : type: mcast, vid = 1, addr = 01:00:5e:00:00:01, mcast_state = f, >> no super, port_mask = 0x3 >> 5 : type: vlan , vid = 2, untag_force = 0x5, reg_mcast = 0x5, >> unreg_mcast = 0x0, member_list = 0x5 >> 6 : type: mcast, vid = 2, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, >> no super, port_mask = 0x5 >> 7 : type: ucast, vid = 2, addr = 74:6a:8f:00:16:13, ucast_type = >> persistant, port_num = 0x0, Secure >> 8 : type: mcast, vid = 2, addr = 01:00:5e:00:00:01, mcast_state = f, >> no super, port_mask = 0x5 >> 9 : type: vlan , vid = 100, untag_force = 0x0, reg_mcast = 0x5, >> unreg_mcast = 0x0, member_list = 0x5 >> 10 : type: ucast, vid = 100, addr = 74:6a:8f:00:16:13, ucast_type = >> persistant, port_num = 0x0 >> 11 : type: mcast, vid = 100, addr = ff:ff:ff:ff:ff:ff, mcast_state = >> f, no super, port_mask = 0x5 >> 12 : type: mcast, vid = 2, addr = 01:80:c2:00:00:21, mcast_state = f, >> no super, port_mask = 0x5 >> >> During mulitcast receive: >> >> # switch-config -d >> cpsw hw version 1.12 (0) >> 0 : type: vlan , vid = 1, untag_force = 0x3, reg_mcast = 0x3, unreg_mcast >> = 0x0, member_list = 0x3 >> 1 : type: mcast, vid = 1, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, no >> super, port_mask = 0x3 >> 2 : type: ucast, vid = 1, addr = 74:6a:8f:00:16:12, ucast_type = >> persistant, port_num = 0x0, Secure >> 3 : type: vlan , vid = 0, untag_force = 0x7, reg_mcast = 0x0, unreg_mcast >> = 0x0, member_list = 0x7 > > unreg_mcast = 0x0 means unregistered multicast packets will be dropped > >> 4 : type: mcast, vid = 1, addr = 01:00:5e:00:00:01, mcast_state = f, no >> super, port_mask = 0x3 >> 5 : type: vlan , vid = 2, untag_force = 0x5, reg_mcast = 0x5, unreg_mcast >> = 0x0, member_list = 0x5 > > unreg_mcast = 0x0 > >> 6 : type: mcast, vid = 2, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, no >> super, port_mask = 0x5 >> 7 : type: ucast, vid = 2, addr = 74:6a:8f:00:16:13, ucast_type = >> persistant, port_num = 0x0, Secure >> 8 : type: mcast, vid = 2, addr = 01:00:5e:00:00:01, mcast_state = f, no >> super, port_mask = 0x5 >> 9 : type: vlan , vid = 100, untag_force = 0x0, reg_mcast = 0x5, >> unreg_mcast = 0x0, member_list = 0x5 > > unreg_mcast = 0x0 > >> 10 : type: ucast, vid = 100, addr = 74:6a:8f:00:16:13, ucast_type = >> persistant, port_num = 0x0 >> 11 : type: mcast, vid = 100, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, no >> super, port_mask = 0x5 >> 12 : type: mcast, vid = 2, addr = 01:80:c2:00:00:21, mcast_state = f, no >> super, port_mask = 0x5 >> 13 : type: mcast, vid = 2, addr = 01:00:5e:03:1d:47, mcast_state = f, no >> super, port_mask = 0x5 > > This is requested mcast address, but it's registered for vid=2 (propagated > through
Re: am335x: no multicast reception over VLAN
On 03/31/2016 10:52 AM, Yegor Yefremov wrote: > On Thu, Mar 31, 2016 at 8:37 AM, Mugunthan V Nwrote: >> On Thursday 31 March 2016 01:17 AM, Peter Korsgaard wrote: "Mugunthan" == Mugunthan V N 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. > > Before VLAN configuration: > > # switch-config -d > cpsw hw version 1.12 (0) > 0 : type: vlan , vid = 1, untag_force = 0x3, reg_mcast = 0x3, > unreg_mcast = 0x0, member_list = 0x3 > 1 : type: mcast, vid = 1, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, > no super, port_mask = 0x3 > 2 : type: ucast, vid = 1, addr = 74:6a:8f:00:16:12, ucast_type = > persistant, port_num = 0x0, Secure > 3 : type: vlan , vid = 0, untag_force = 0x7, reg_mcast = 0x0, > unreg_mcast = 0x0, member_list = 0x7 > 4 : type: mcast, vid = 1, addr = 01:00:5e:00:00:01, mcast_state = f, > no super, port_mask = 0x3 > 5 : type: vlan , vid = 2, untag_force = 0x5, reg_mcast = 0x5, > unreg_mcast = 0x0, member_list = 0x5 > 6 : type: mcast, vid = 2, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, > no super, port_mask = 0x5 > 7 : type: ucast, vid = 2, addr = 74:6a:8f:00:16:13, ucast_type = > persistant, port_num = 0x0, Secure > 8 : type: mcast, vid = 2, addr = 01:00:5e:00:00:01, mcast_state = f, > no super, port_mask = 0x5 > > After VLAN configuration: > > # switch-config -d > cpsw hw version 1.12 (0) > 0 : type: vlan , vid = 1, untag_force = 0x3, reg_mcast = 0x3, > unreg_mcast = 0x0, member_list = 0x3 > 1 : type: mcast, vid = 1, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, > no super, port_mask = 0x3 > 2 : type: ucast, vid = 1, addr = 74:6a:8f:00:16:12, ucast_type = > persistant, port_num = 0x0, Secure > 3 : type: vlan , vid = 0, untag_force = 0x7, reg_mcast = 0x0, > unreg_mcast = 0x0, member_list = 0x7 > 4 : type: mcast, vid = 1, addr = 01:00:5e:00:00:01, mcast_state = f, > no super, port_mask = 0x3 > 5 : type: vlan , vid = 2, untag_force = 0x5, reg_mcast = 0x5, > unreg_mcast = 0x0, member_list = 0x5 > 6 : type: mcast, vid = 2, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, > no super, port_mask = 0x5 > 7 : type: ucast, vid = 2, addr = 74:6a:8f:00:16:13, ucast_type = > persistant, port_num = 0x0, Secure > 8 : type: mcast, vid = 2, addr = 01:00:5e:00:00:01, mcast_state = f, > no super, port_mask = 0x5 > 9 : type: vlan , vid = 100, untag_force = 0x0, reg_mcast = 0x5, > unreg_mcast = 0x0, member_list = 0x5 > 10 : type: ucast, vid = 100, addr = 74:6a:8f:00:16:13, ucast_type = > persistant, port_num = 0x0 > 11 : type: mcast, vid = 100, addr = ff:ff:ff:ff:ff:ff, mcast_state = > f, no super, port_mask = 0x5 > 12 : type: mcast, vid = 2, addr = 01:80:c2:00:00:21, mcast_state = f, > no super, port_mask = 0x5 > > During mulitcast receive: > > # switch-config -d > cpsw hw version 1.12 (0) > 0 : type: vlan , vid = 1, untag_force = 0x3, reg_mcast = 0x3, unreg_mcast = > 0x0, member_list = 0x3 > 1 : type: mcast, vid = 1, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, no > super, port_mask = 0x3 > 2 : type: ucast, vid = 1, addr = 74:6a:8f:00:16:12, ucast_type = > persistant, port_num = 0x0, Secure > 3 : type: vlan , vid = 0, untag_force = 0x7, reg_mcast = 0x0, unreg_mcast = > 0x0, member_list = 0x7 unreg_mcast = 0x0 means unregistered multicast packets will be dropped > 4 : type: mcast, vid = 1, addr = 01:00:5e:00:00:01, mcast_state = f, no > super, port_mask = 0x3 > 5 : type: vlan , vid = 2, untag_force = 0x5, reg_mcast = 0x5, unreg_mcast = > 0x0, member_list = 0x5 unreg_mcast = 0x0 > 6 : type: mcast, vid = 2, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, no > super, port_mask = 0x5 > 7 : type: ucast, vid = 2, addr = 74:6a:8f:00:16:13, ucast_type = > persistant, port_num = 0x0, Secure > 8 : type: mcast, vid = 2, addr = 01:00:5e:00:00:01, mcast_state = f, no > super, port_mask = 0x5 > 9 : type: vlan , vid = 100, untag_force = 0x0, reg_mcast = 0x5, unreg_mcast > = 0x0, member_list = 0x5 unreg_mcast = 0x0 > 10 : type: ucast, vid = 100, addr = 74:6a:8f:00:16:13, ucast_type = > persistant, port_num = 0x0 > 11 : type: mcast, vid = 100, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, no > super, port_mask = 0x5 > 12 : type: mcast, vid = 2, addr = 01:80:c2:00:00:21, mcast_state = f, no > super, port_mask = 0x5 > 13 : type: mcast, vid = 2, addr = 01:00:5e:03:1d:47, mcast_state = f, no > super, port_mask = 0x5 This is requested mcast address, but it's registered for vid=2 (propagated through .ndo_set_rx_mode()) > 14 : type: ucast, vid = 100, addr = 66:22:04:bc:90:26, ucast_type = > untouched , port_num = 0x2 [...] > > Both tcpdumps with -p option showed no packets.
Re: am335x: no multicast reception over VLAN
On Thu, Mar 31, 2016 at 12:02 PM, Mugunthan V Nwrote: > On Thursday 31 March 2016 01:22 PM, Yegor Yefremov wrote: >> On Thu, Mar 31, 2016 at 8:37 AM, Mugunthan V N wrote: >>> On Thursday 31 March 2016 01:17 AM, Peter Korsgaard wrote: > "Mugunthan" == Mugunthan V N 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. >> >> Before VLAN configuration: >> >> # switch-config -d >> cpsw hw version 1.12 (0) >> 0 : type: vlan , vid = 1, untag_force = 0x3, reg_mcast = 0x3, >> unreg_mcast = 0x0, member_list = 0x3 >> 1 : type: mcast, vid = 1, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, >> no super, port_mask = 0x3 >> 2 : type: ucast, vid = 1, addr = 74:6a:8f:00:16:12, ucast_type = >> persistant, port_num = 0x0, Secure >> 3 : type: vlan , vid = 0, untag_force = 0x7, reg_mcast = 0x0, >> unreg_mcast = 0x0, member_list = 0x7 >> 4 : type: mcast, vid = 1, addr = 01:00:5e:00:00:01, mcast_state = f, >> no super, port_mask = 0x3 >> 5 : type: vlan , vid = 2, untag_force = 0x5, reg_mcast = 0x5, >> unreg_mcast = 0x0, member_list = 0x5 >> 6 : type: mcast, vid = 2, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, >> no super, port_mask = 0x5 >> 7 : type: ucast, vid = 2, addr = 74:6a:8f:00:16:13, ucast_type = >> persistant, port_num = 0x0, Secure >> 8 : type: mcast, vid = 2, addr = 01:00:5e:00:00:01, mcast_state = f, >> no super, port_mask = 0x5 >> >> After VLAN configuration: >> >> # switch-config -d >> cpsw hw version 1.12 (0) >> 0 : type: vlan , vid = 1, untag_force = 0x3, reg_mcast = 0x3, >> unreg_mcast = 0x0, member_list = 0x3 >> 1 : type: mcast, vid = 1, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, >> no super, port_mask = 0x3 >> 2 : type: ucast, vid = 1, addr = 74:6a:8f:00:16:12, ucast_type = >> persistant, port_num = 0x0, Secure >> 3 : type: vlan , vid = 0, untag_force = 0x7, reg_mcast = 0x0, >> unreg_mcast = 0x0, member_list = 0x7 >> 4 : type: mcast, vid = 1, addr = 01:00:5e:00:00:01, mcast_state = f, >> no super, port_mask = 0x3 >> 5 : type: vlan , vid = 2, untag_force = 0x5, reg_mcast = 0x5, >> unreg_mcast = 0x0, member_list = 0x5 >> 6 : type: mcast, vid = 2, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, >> no super, port_mask = 0x5 >> 7 : type: ucast, vid = 2, addr = 74:6a:8f:00:16:13, ucast_type = >> persistant, port_num = 0x0, Secure >> 8 : type: mcast, vid = 2, addr = 01:00:5e:00:00:01, mcast_state = f, >> no super, port_mask = 0x5 >> 9 : type: vlan , vid = 100, untag_force = 0x0, reg_mcast = 0x5, >> unreg_mcast = 0x0, member_list = 0x5 >> 10 : type: ucast, vid = 100, addr = 74:6a:8f:00:16:13, ucast_type = >> persistant, port_num = 0x0 >> 11 : type: mcast, vid = 100, addr = ff:ff:ff:ff:ff:ff, mcast_state = >> f, no super, port_mask = 0x5 >> 12 : type: mcast, vid = 2, addr = 01:80:c2:00:00:21, mcast_state = f, >> no super, port_mask = 0x5 >> >> During mulitcast receive: >> >> # switch-config -d >> cpsw hw version 1.12 (0) >> 0 : type: vlan , vid = 1, untag_force = 0x3, reg_mcast = 0x3, >> unreg_mcast = 0x0, member_list = 0x3 >> 1 : type: mcast, vid = 1, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, >> no super, port_mask = 0x3 >> 2 : type: ucast, vid = 1, addr = 74:6a:8f:00:16:12, ucast_type = >> persistant, port_num = 0x0, Secure >> 3 : type: vlan , vid = 0, untag_force = 0x7, reg_mcast = 0x0, >> unreg_mcast = 0x0, member_list = 0x7 >> 4 : type: mcast, vid = 1, addr = 01:00:5e:00:00:01, mcast_state = f, >> no super, port_mask = 0x3 >> 5 : type: vlan , vid = 2, untag_force = 0x5, reg_mcast = 0x5, >> unreg_mcast = 0x0, member_list = 0x5 >> 6 : type: mcast, vid = 2, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, >> no super, port_mask = 0x5 >> 7 : type: ucast, vid = 2, addr = 74:6a:8f:00:16:13, ucast_type = >> persistant, port_num = 0x0, Secure >> 8 : type: mcast, vid = 2, addr = 01:00:5e:00:00:01, mcast_state = f, >> no super, port_mask = 0x5 >> 9 : type: vlan , vid = 100, untag_force = 0x0, reg_mcast = 0x5, >> unreg_mcast = 0x0, member_list = 0x5 >> 10 : type: ucast, vid = 100, addr = 74:6a:8f:00:16:13, ucast_type = >> persistant, port_num = 0x0 >> 11 : type: mcast, vid = 100, addr = ff:ff:ff:ff:ff:ff, mcast_state = >> f, no super, port_mask = 0x5 >> 12 : type: mcast, vid = 2, addr = 01:80:c2:00:00:21, mcast_state = f, >> no super, port_mask = 0x5 >> 13 : type: mcast, vid = 2, addr = 01:00:5e:03:1d:47, mcast_state = f, >> no super, port_mask = 0x5 >> 14 : type: ucast, vid = 100, addr = 66:22:04:bc:90:26, ucast_type = >> untouched , port_num = 0x2 > > I could see multicast address 01:00:5e:03:1d:47 is added to ALE table at > index 13, but it is added
Re: am335x: no multicast reception over VLAN
On Thursday 31 March 2016 01:22 PM, Yegor Yefremov wrote: > On Thu, Mar 31, 2016 at 8:37 AM, Mugunthan V Nwrote: >> On Thursday 31 March 2016 01:17 AM, Peter Korsgaard wrote: "Mugunthan" == Mugunthan V N 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. > > Before VLAN configuration: > > # switch-config -d > cpsw hw version 1.12 (0) > 0 : type: vlan , vid = 1, untag_force = 0x3, reg_mcast = 0x3, > unreg_mcast = 0x0, member_list = 0x3 > 1 : type: mcast, vid = 1, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, > no super, port_mask = 0x3 > 2 : type: ucast, vid = 1, addr = 74:6a:8f:00:16:12, ucast_type = > persistant, port_num = 0x0, Secure > 3 : type: vlan , vid = 0, untag_force = 0x7, reg_mcast = 0x0, > unreg_mcast = 0x0, member_list = 0x7 > 4 : type: mcast, vid = 1, addr = 01:00:5e:00:00:01, mcast_state = f, > no super, port_mask = 0x3 > 5 : type: vlan , vid = 2, untag_force = 0x5, reg_mcast = 0x5, > unreg_mcast = 0x0, member_list = 0x5 > 6 : type: mcast, vid = 2, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, > no super, port_mask = 0x5 > 7 : type: ucast, vid = 2, addr = 74:6a:8f:00:16:13, ucast_type = > persistant, port_num = 0x0, Secure > 8 : type: mcast, vid = 2, addr = 01:00:5e:00:00:01, mcast_state = f, > no super, port_mask = 0x5 > > After VLAN configuration: > > # switch-config -d > cpsw hw version 1.12 (0) > 0 : type: vlan , vid = 1, untag_force = 0x3, reg_mcast = 0x3, > unreg_mcast = 0x0, member_list = 0x3 > 1 : type: mcast, vid = 1, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, > no super, port_mask = 0x3 > 2 : type: ucast, vid = 1, addr = 74:6a:8f:00:16:12, ucast_type = > persistant, port_num = 0x0, Secure > 3 : type: vlan , vid = 0, untag_force = 0x7, reg_mcast = 0x0, > unreg_mcast = 0x0, member_list = 0x7 > 4 : type: mcast, vid = 1, addr = 01:00:5e:00:00:01, mcast_state = f, > no super, port_mask = 0x3 > 5 : type: vlan , vid = 2, untag_force = 0x5, reg_mcast = 0x5, > unreg_mcast = 0x0, member_list = 0x5 > 6 : type: mcast, vid = 2, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, > no super, port_mask = 0x5 > 7 : type: ucast, vid = 2, addr = 74:6a:8f:00:16:13, ucast_type = > persistant, port_num = 0x0, Secure > 8 : type: mcast, vid = 2, addr = 01:00:5e:00:00:01, mcast_state = f, > no super, port_mask = 0x5 > 9 : type: vlan , vid = 100, untag_force = 0x0, reg_mcast = 0x5, > unreg_mcast = 0x0, member_list = 0x5 > 10 : type: ucast, vid = 100, addr = 74:6a:8f:00:16:13, ucast_type = > persistant, port_num = 0x0 > 11 : type: mcast, vid = 100, addr = ff:ff:ff:ff:ff:ff, mcast_state = > f, no super, port_mask = 0x5 > 12 : type: mcast, vid = 2, addr = 01:80:c2:00:00:21, mcast_state = f, > no super, port_mask = 0x5 > > During mulitcast receive: > > # switch-config -d > cpsw hw version 1.12 (0) > 0 : type: vlan , vid = 1, untag_force = 0x3, reg_mcast = 0x3, > unreg_mcast = 0x0, member_list = 0x3 > 1 : type: mcast, vid = 1, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, > no super, port_mask = 0x3 > 2 : type: ucast, vid = 1, addr = 74:6a:8f:00:16:12, ucast_type = > persistant, port_num = 0x0, Secure > 3 : type: vlan , vid = 0, untag_force = 0x7, reg_mcast = 0x0, > unreg_mcast = 0x0, member_list = 0x7 > 4 : type: mcast, vid = 1, addr = 01:00:5e:00:00:01, mcast_state = f, > no super, port_mask = 0x3 > 5 : type: vlan , vid = 2, untag_force = 0x5, reg_mcast = 0x5, > unreg_mcast = 0x0, member_list = 0x5 > 6 : type: mcast, vid = 2, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, > no super, port_mask = 0x5 > 7 : type: ucast, vid = 2, addr = 74:6a:8f:00:16:13, ucast_type = > persistant, port_num = 0x0, Secure > 8 : type: mcast, vid = 2, addr = 01:00:5e:00:00:01, mcast_state = f, > no super, port_mask = 0x5 > 9 : type: vlan , vid = 100, untag_force = 0x0, reg_mcast = 0x5, > unreg_mcast = 0x0, member_list = 0x5 > 10 : type: ucast, vid = 100, addr = 74:6a:8f:00:16:13, ucast_type = > persistant, port_num = 0x0 > 11 : type: mcast, vid = 100, addr = ff:ff:ff:ff:ff:ff, mcast_state = > f, no super, port_mask = 0x5 > 12 : type: mcast, vid = 2, addr = 01:80:c2:00:00:21, mcast_state = f, > no super, port_mask = 0x5 > 13 : type: mcast, vid = 2, addr = 01:00:5e:03:1d:47, mcast_state = f, > no super, port_mask = 0x5 > 14 : type: ucast, vid = 100, addr = 66:22:04:bc:90:26, ucast_type = > untouched , port_num = 0x2 I could see multicast address 01:00:5e:03:1d:47 is added to ALE table at index 13, but it is added for VLAN id 2 ie eth1, did you ran the test for eth1 or eth1.100? Regards Mugunthan V N
Re: am335x: no multicast reception over VLAN
On Thu, Mar 31, 2016 at 8:37 AM, Mugunthan V Nwrote: > On Thursday 31 March 2016 01:17 AM, Peter Korsgaard wrote: >>> "Mugunthan" == Mugunthan V N 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. Before VLAN configuration: # switch-config -d cpsw hw version 1.12 (0) 0 : type: vlan , vid = 1, untag_force = 0x3, reg_mcast = 0x3, unreg_mcast = 0x0, member_list = 0x3 1 : type: mcast, vid = 1, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, no super, port_mask = 0x3 2 : type: ucast, vid = 1, addr = 74:6a:8f:00:16:12, ucast_type = persistant, port_num = 0x0, Secure 3 : type: vlan , vid = 0, untag_force = 0x7, reg_mcast = 0x0, unreg_mcast = 0x0, member_list = 0x7 4 : type: mcast, vid = 1, addr = 01:00:5e:00:00:01, mcast_state = f, no super, port_mask = 0x3 5 : type: vlan , vid = 2, untag_force = 0x5, reg_mcast = 0x5, unreg_mcast = 0x0, member_list = 0x5 6 : type: mcast, vid = 2, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, no super, port_mask = 0x5 7 : type: ucast, vid = 2, addr = 74:6a:8f:00:16:13, ucast_type = persistant, port_num = 0x0, Secure 8 : type: mcast, vid = 2, addr = 01:00:5e:00:00:01, mcast_state = f, no super, port_mask = 0x5 After VLAN configuration: # switch-config -d cpsw hw version 1.12 (0) 0 : type: vlan , vid = 1, untag_force = 0x3, reg_mcast = 0x3, unreg_mcast = 0x0, member_list = 0x3 1 : type: mcast, vid = 1, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, no super, port_mask = 0x3 2 : type: ucast, vid = 1, addr = 74:6a:8f:00:16:12, ucast_type = persistant, port_num = 0x0, Secure 3 : type: vlan , vid = 0, untag_force = 0x7, reg_mcast = 0x0, unreg_mcast = 0x0, member_list = 0x7 4 : type: mcast, vid = 1, addr = 01:00:5e:00:00:01, mcast_state = f, no super, port_mask = 0x3 5 : type: vlan , vid = 2, untag_force = 0x5, reg_mcast = 0x5, unreg_mcast = 0x0, member_list = 0x5 6 : type: mcast, vid = 2, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, no super, port_mask = 0x5 7 : type: ucast, vid = 2, addr = 74:6a:8f:00:16:13, ucast_type = persistant, port_num = 0x0, Secure 8 : type: mcast, vid = 2, addr = 01:00:5e:00:00:01, mcast_state = f, no super, port_mask = 0x5 9 : type: vlan , vid = 100, untag_force = 0x0, reg_mcast = 0x5, unreg_mcast = 0x0, member_list = 0x5 10 : type: ucast, vid = 100, addr = 74:6a:8f:00:16:13, ucast_type = persistant, port_num = 0x0 11 : type: mcast, vid = 100, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, no super, port_mask = 0x5 12 : type: mcast, vid = 2, addr = 01:80:c2:00:00:21, mcast_state = f, no super, port_mask = 0x5 During mulitcast receive: # switch-config -d cpsw hw version 1.12 (0) 0 : type: vlan , vid = 1, untag_force = 0x3, reg_mcast = 0x3, unreg_mcast = 0x0, member_list = 0x3 1 : type: mcast, vid = 1, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, no super, port_mask = 0x3 2 : type: ucast, vid = 1, addr = 74:6a:8f:00:16:12, ucast_type = persistant, port_num = 0x0, Secure 3 : type: vlan , vid = 0, untag_force = 0x7, reg_mcast = 0x0, unreg_mcast = 0x0, member_list = 0x7 4 : type: mcast, vid = 1, addr = 01:00:5e:00:00:01, mcast_state = f, no super, port_mask = 0x3 5 : type: vlan , vid = 2, untag_force = 0x5, reg_mcast = 0x5, unreg_mcast = 0x0, member_list = 0x5 6 : type: mcast, vid = 2, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, no super, port_mask = 0x5 7 : type: ucast, vid = 2, addr = 74:6a:8f:00:16:13, ucast_type = persistant, port_num = 0x0, Secure 8 : type: mcast, vid = 2, addr = 01:00:5e:00:00:01, mcast_state = f, no super, port_mask = 0x5 9 : type: vlan , vid = 100, untag_force = 0x0, reg_mcast = 0x5, unreg_mcast = 0x0, member_list = 0x5 10 : type: ucast, vid = 100, addr = 74:6a:8f:00:16:13, ucast_type = persistant, port_num = 0x0 11 : type: mcast, vid = 100, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, no super, port_mask = 0x5 12 : type: mcast, vid = 2, addr = 01:80:c2:00:00:21, mcast_state = f, no super, port_mask = 0x5 13 : type: mcast, vid = 2, addr = 01:00:5e:03:1d:47, mcast_state = f, no super, port_mask = 0x5 14 : type: ucast, vid = 100, addr = 66:22:04:bc:90:26, ucast_type = untouched , port_num = 0x2 After multicast receive use case: # switch-config -d cpsw hw version 1.12 (0) 0 : type: vlan , vid = 1, untag_force = 0x3, reg_mcast = 0x3, unreg_mcast = 0x0, member_list = 0x3 1 : type: mcast, vid = 1, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, no super, port_mask = 0x3 2 : type: ucast, vid = 1, addr = 74:6a:8f:00:16:12, ucast_type = persistant, port_num = 0x0, Secure 3 : type: vlan , vid = 0, untag_force = 0x7, reg_mcast = 0x0, unreg_mcast = 0x0, member_list = 0x7 4 : type: mcast, vid = 1, addr = 01:00:5e:00:00:01,
Re: am335x: no multicast reception over VLAN
On Thursday 31 March 2016 01:17 AM, Peter Korsgaard wrote: >> "Mugunthan" == Mugunthan V Nwrites: > > 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
Re: am335x: no multicast reception over VLAN
> "Mugunthan" == Mugunthan V Nwrites: 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. -- Bye, Peter Korsgaard
Re: am335x: no multicast reception over VLAN
On Wednesday 30 March 2016 02:05 PM, Yegor Yefremov wrote: > On Wed, Mar 30, 2016 at 7:33 AM, Mugunthan V Nwrote: >> On Tuesday 29 March 2016 06:14 PM, Grygorii Strashko wrote: >>> On 03/29/2016 03:35 PM, Yegor Yefremov wrote: On Tue, Mar 29, 2016 at 1:05 PM, Grygorii Strashko wrote: > On 03/29/2016 08:21 AM, Yegor Yefremov wrote: >> Hi Mugunthan, >> >> On Tue, Mar 29, 2016 at 6:00 AM, Mugunthan V N >> 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 Which kernel/branch do you want me to test? git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git and ti-rt-linux-4.1.y? So far I was using vanilla kernel. >>> >>> Your branch (but better 4.5 kernels (or 4.4)). >>> Just when you've done with configuration run cmds 1&2, >>> and when you run your use-case - run cmds 2&3 on receiver side (grap ~5-10 >>> packets). >>> then stop test and run cmd 1 again. >>> >>> After all could you provide your console output here, pls. >>> >>> >> >> To use command 1, you need TI kernel [1] as it won't build with vanilla >> kernel. >> >> [1]: git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git ti-linux-4.1.y > > # uname -a > Linux buildroot 4.1.18 #1 SMP Wed Mar 30 09:48:37 CEST 2016 armv7l GNU/Linux > > # switch-config -d > cpsw hw version 1.12 (0) > 0 : type: vlan , vid = 1, untag_force = 0x3, reg_mcast = 0x3, > unreg_mcast = 0x1, member_list = 0x3 > > 1 : type: mcast, vid = 1, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, > no super, port_mask = 0x3 > 2 : type: ucast, vid = 1, addr = 74:6a:8f:00:16:12, ucast_type = > persistant, port_num = 0x0, Secure > 3 : type: vlan , vid = 0, untag_force = 0x7, reg_mcast = 0x0, > unreg_mcast = 0x1, member_list = 0x7 > 4 : type: mcast, vid = 1, addr = 01:00:5e:00:00:01, mcast_state = f, > no super, port_mask = 0x3 > 5 : type: vlan , vid = 2, untag_force = 0x5, reg_mcast = 0x5, > unreg_mcast = 0x1, member_list = 0x5 > 6 : type: mcast, vid = 2, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, > no super, port_mask = 0x5 > 7 : type: ucast, vid = 2, addr = 74:6a:8f:00:16:13, ucast_type = > persistant, port_num = 0x0, Secure > 8 : type: mcast, vid = 2, addr = 01:00:5e:00:00:01, mcast_state = f, > no super, port_mask = 0x5 > 9 : type: vlan , vid = 100, untag_force = 0x0, reg_mcast = 0x5, > unreg_mcast = 0x1, member_list = 0x5 > 10 : type: ucast, vid = 100, addr = 74:6a:8f:00:16:13, ucast_type = > persistant, port_num = 0x0 > 11 : type: mcast, vid = 100, addr = ff:ff:ff:ff:ff:ff, mcast_state = > f, no super, port_mask = 0x5 > 12 : type: mcast, vid = 2, addr = 01:80:c2:00:00:21, mcast_state = f, > no super, port_mask = 0x5 > 13 : type: mcast, vid = 2, addr = 01:00:5e:03:1d:47, mcast_state = f, > no super, port_mask = 0x5 I don't see multicast entry added to ALE table for 01:00:5e:03:1d:47, can you run the receive command in background/another terminal and get the dump when receiving on eth1 and eth1.100 as well and don't enable tcpdump as it will put the switch in promiscuous mode. > > # ifconfig -a > can0 Link encap:UNSPEC HWaddr > 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 > NOARP MTU:16 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:10 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > Interrupt:165 > > eth0 Link encap:Ethernet HWaddr 74:6A:8F:00:16:12 > inet addr:192.168.254.254 Bcast:0.0.0.0 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > Interrupt:175 >
Re: am335x: no multicast reception over VLAN
On Wed, Mar 30, 2016 at 7:33 AM, Mugunthan V Nwrote: > On Tuesday 29 March 2016 06:14 PM, Grygorii Strashko wrote: >> On 03/29/2016 03:35 PM, Yegor Yefremov wrote: >>> On Tue, Mar 29, 2016 at 1:05 PM, Grygorii Strashko >>> wrote: On 03/29/2016 08:21 AM, Yegor Yefremov wrote: > Hi Mugunthan, > > On Tue, Mar 29, 2016 at 6:00 AM, Mugunthan V N > 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 >>> >>> Which kernel/branch do you want me to test? >>> >>> git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git and ti-rt-linux-4.1.y? >>> >>> So far I was using vanilla kernel. >> >> Your branch (but better 4.5 kernels (or 4.4)). >> Just when you've done with configuration run cmds 1&2, >> and when you run your use-case - run cmds 2&3 on receiver side (grap ~5-10 >> packets). >> then stop test and run cmd 1 again. >> >> After all could you provide your console output here, pls. >> >> > > To use command 1, you need TI kernel [1] as it won't build with vanilla > kernel. > > [1]: git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git ti-linux-4.1.y # uname -a Linux buildroot 4.1.18 #1 SMP Wed Mar 30 09:48:37 CEST 2016 armv7l GNU/Linux # switch-config -d cpsw hw version 1.12 (0) 0 : type: vlan , vid = 1, untag_force = 0x3, reg_mcast = 0x3, unreg_mcast = 0x1, member_list = 0x3 1 : type: mcast, vid = 1, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, no super, port_mask = 0x3 2 : type: ucast, vid = 1, addr = 74:6a:8f:00:16:12, ucast_type = persistant, port_num = 0x0, Secure 3 : type: vlan , vid = 0, untag_force = 0x7, reg_mcast = 0x0, unreg_mcast = 0x1, member_list = 0x7 4 : type: mcast, vid = 1, addr = 01:00:5e:00:00:01, mcast_state = f, no super, port_mask = 0x3 5 : type: vlan , vid = 2, untag_force = 0x5, reg_mcast = 0x5, unreg_mcast = 0x1, member_list = 0x5 6 : type: mcast, vid = 2, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, no super, port_mask = 0x5 7 : type: ucast, vid = 2, addr = 74:6a:8f:00:16:13, ucast_type = persistant, port_num = 0x0, Secure 8 : type: mcast, vid = 2, addr = 01:00:5e:00:00:01, mcast_state = f, no super, port_mask = 0x5 9 : type: vlan , vid = 100, untag_force = 0x0, reg_mcast = 0x5, unreg_mcast = 0x1, member_list = 0x5 10 : type: ucast, vid = 100, addr = 74:6a:8f:00:16:13, ucast_type = persistant, port_num = 0x0 11 : type: mcast, vid = 100, addr = ff:ff:ff:ff:ff:ff, mcast_state = f, no super, port_mask = 0x5 12 : type: mcast, vid = 2, addr = 01:80:c2:00:00:21, mcast_state = f, no super, port_mask = 0x5 13 : type: mcast, vid = 2, addr = 01:00:5e:03:1d:47, mcast_state = f, no super, port_mask = 0x5 # ifconfig -a can0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 NOARP MTU:16 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:10 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:165 eth0 Link encap:Ethernet HWaddr 74:6A:8F:00:16:12 inet addr:192.168.254.254 Bcast:0.0.0.0 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:175 eth1 Link encap:Ethernet HWaddr 74:6A:8F:00:16:13 inet addr:192.168.1.233 Bcast:0.0.0.0 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:245 errors:0 dropped:0 overruns:0 frame:0 TX packets:123 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:40995 (40.0 KiB) TX bytes:14086 (13.7 KiB) eth1.100 Link encap:Ethernet HWaddr 74:6A:8F:00:16:13 inet
Re: am335x: no multicast reception over VLAN
On Tuesday 29 March 2016 06:14 PM, Grygorii Strashko wrote: > On 03/29/2016 03:35 PM, Yegor Yefremov wrote: >> On Tue, Mar 29, 2016 at 1:05 PM, Grygorii Strashko >>wrote: >>> On 03/29/2016 08:21 AM, Yegor Yefremov wrote: Hi Mugunthan, On Tue, Mar 29, 2016 at 6:00 AM, Mugunthan V N 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 >> >> Which kernel/branch do you want me to test? >> >> git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git and ti-rt-linux-4.1.y? >> >> So far I was using vanilla kernel. > > Your branch (but better 4.5 kernels (or 4.4)). > Just when you've done with configuration run cmds 1&2, > and when you run your use-case - run cmds 2&3 on receiver side (grap ~5-10 > packets). > then stop test and run cmd 1 again. > > After all could you provide your console output here, pls. > > To use command 1, you need TI kernel [1] as it won't build with vanilla kernel. [1]: git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git ti-linux-4.1.y Regards Mugunthan V N
Re: am335x: no multicast reception over VLAN
On 03/29/2016 03:35 PM, Yegor Yefremov wrote: > On Tue, Mar 29, 2016 at 1:05 PM, Grygorii Strashko >wrote: >> On 03/29/2016 08:21 AM, Yegor Yefremov wrote: >>> Hi Mugunthan, >>> >>> On Tue, Mar 29, 2016 at 6:00 AM, Mugunthan V N 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 > > Which kernel/branch do you want me to test? > > git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git and ti-rt-linux-4.1.y? > > So far I was using vanilla kernel. Your branch (but better 4.5 kernels (or 4.4)). Just when you've done with configuration run cmds 1&2, and when you run your use-case - run cmds 2&3 on receiver side (grap ~5-10 packets). then stop test and run cmd 1 again. After all could you provide your console output here, pls. -- regards, -grygorii
Re: am335x: no multicast reception over VLAN
On Tue, Mar 29, 2016 at 1:05 PM, Grygorii Strashkowrote: > On 03/29/2016 08:21 AM, Yegor Yefremov wrote: >> Hi Mugunthan, >> >> On Tue, Mar 29, 2016 at 6:00 AM, Mugunthan V N 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 Which kernel/branch do you want me to test? git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git and ti-rt-linux-4.1.y? So far I was using vanilla kernel. Yegor
Re: am335x: no multicast reception over VLAN
On 03/29/2016 08:21 AM, Yegor Yefremov wrote: > Hi Mugunthan, > > On Tue, Mar 29, 2016 at 6:00 AM, Mugunthan V Nwrote: >> 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
Re: am335x: no multicast reception over VLAN
Hi Mugunthan, On Tue, Mar 29, 2016 at 6:00 AM, Mugunthan V Nwrote: > 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. Yegor >> This setup was tested with both 3.18.21 and 4.5 kernels. >> >> Any idea? >> >> [1] https://pymotw.com/2/socket/multicast.html >> > > -- > Regards > Mugunthan V N >
Re: am335x: no multicast reception over VLAN
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? > > This setup was tested with both 3.18.21 and 4.5 kernels. > > Any idea? > > [1] https://pymotw.com/2/socket/multicast.html > -- Regards Mugunthan V N
am335x: no multicast reception over VLAN
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. This setup was tested with both 3.18.21 and 4.5 kernels. Any idea? [1] https://pymotw.com/2/socket/multicast.html Regards, Yegor