UDP Multicast traffic not delivered to the other drone

[Yordan Sutanto]

Hi Srivats & Team,

I'm using Ostinato in my VIRL topology below:

Ping between drones was working.

ICMP Multicast traffic was successfully delivered to the other drone. And below were the settings:

a. Protocol Selection:

- L1: Mac

- VLAN: Untagged

- L2: Ethernet II

- L3: IPv4

- L4: ICMP

- L5: None

- Payload: Pattern

b. Protocol Data:

. Media Access Protocol

- Destination Address: 01-00-5E-0A-18-05 (the multicast destination MAC address)

- Source Address: fa:16:3e:54:a9:5b (drone 1’s eth1 MAC address)

. Internet Protocol ver 4

- Source: 192.168.0.4

- Destination: 238.10.24.5

c. Stream Control:

- Number of Packets: 1000

- Packets/Sec: 10

- After this stream: Goto Next Stream

- click OK, then click Apply.

However, if we change the above parameters to UDP 20480, then the multicast traffic could not be delivered to the other node.

a. Protocol Selection:

- L1: Mac

- VLAN: Untagged

- L2: Ethernet II

- L3: IPv4

- L4: UDP

- L5: None

- Payload: Pattern

b. Protocol Data:

. Media Access Protocol

- Destination Address: 01-00-5E-0A-18-05 (the multicast destination MAC address)

- Source Address: fa:16:3e:54:a9:5b (drone 1’s eth1 MAC address)

. Internet Protocol ver 4

- Source: 192.168.0.4

- Destination: 238.10.24.5

. UDP Destination Port: 20480

c. Stream Control:

- Number of Packets: 1000

- Packets/Sec: 10

- After this stream: Goto Next Stream

- click OK, then click Apply.

Could you please advise what the recommended setting is for generating UDP Multicast Traffic between drones?

Note: I'm using version 0.8.

Thanks.

Best regards,

Yordan

[Srivats P]

Yordan,

If the source UDP port is set to 0, can you try a non-zero value?

Do you know which IOS router is dropping the packet? Is there a counter on that router that could give us a hint about the drop?

Srivats

Founder, Ostinato

--
Get Ostinato News and Updates on Twitter - Follow @ostinato (http://twitter.com/ostinato)
---
You received this message because you are subscribed to the Google Groups "ostinato" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ostinato+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ostinato/CAB6gD_QpvgHt744fZ-XnS3cqwa6a79X0TaKuV3Xw4t2M0x-Njg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

http://ostinato.org/
@ostinato

[Yordan Sutanto]

Hi Srivats,

The 3 IOS nodes in the middle are all Layer 2 switches. I have tried disabling IGMP Snooping, and now the number of frames sent by drone 1 matches the number of frames received by drone 2.

With IGMP Snooping on, I have tried below parameters as well, but still no luck.

a. Multicast Sender:

Double click the Gear Option and select below options

a. Protocol Selection:

- L1: Mac

- VLAN: Untagged

- L2: Ethernet II

- L3: IPv4

- L4: UDP

- L5: None

- Payload: Pattern

b. Protocol Data:

. Media Access Protocol

- Destination Address: 01-00-5E-0A-18-05 (the multicast destination MAC address)

- Source Address: fa:16:3e:69:4b:b7 (drone 1’s eth1 MAC address)

. Internet Protocol ver 4

- Source: 192.168.0.1

- Destination: 238.10.24.5

. User Datagram Protocol

- Override Source Port: 20480

- Override Destination Port: 20480

c. Stream Control:

- Number of Packets: 100

- Packets/Sec: 10

- After this stream: Stop

  (What this means is when we run this stream, it will attempt to send 10 multicast IP packets encapsulated in multicast Ethernet Frames each second for a period of 10 seconds and then it shall stop.)

- click OK, then click Apply.

  - click the port, Select 'Resolve Device Neighbors'

  - click on start packet capture (optional)

  - clear stat

  - click start Tx

  - click stop packet capture

  - click view packet capture

---

b. Multicast Receiver:

Double click the Gear Option and select below options

a. Protocol Selection:

- L1: Mac

- VLAN: Untagged

- L2: Ethernet II

- L3: IPv4

- L4: IGMP

- L5: None

- Payload: Pattern

b. Protocol Data:

. Media Access Protocol

- Destination Address: 01:00:5e:00:00:02 (the multicast destination MAC address of 224.0.0.2)

- Source Address: fa:16:3e:30:87:fa (drone 2’s eth1 MAC address)

. Internet Protocol ver 4

- Source: 192.168.0.2

- Destination: 224.0.0.2

. Internet Group Management Protocol

- Message Type: 22 IGMPv2 Report

- Group Address: 238.10.24.5

c. Stream Control:

- Number of Packets: 1

- Packets/Sec: 0.1

- After this stream: Goto First

  (What this means is when we run this stream, it will attempt to send 1 IGMP Join every 10 seconds continuously.)

- click OK, then click Apply.

  - click the port, 

  - then click 'start packet capture' (optional)

  - clear statistics

  - click 'Resolve Device Neighbors'

  - click start Tx

  - click stop packet capture

  - click view packet capture

------

Do you have a proven-to-be-working cisco L2 switches (in virl) configurations and ostinato-drones settings that will always work in UDP multicast traffic scenario?

Thanks.

Best regards,

Yordan

[Carlos G Mendioroz]

Jumping in the midle of something, but if disabling IGMP snooping fixes
the issue, I would say the problem is not with the frame generator, or
is it ?

Yordan Sutanto @ 17/05/2019 16:10 -0300 dixit:

> <mailto:ostinato+u...@googlegroups.com>.

> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ostinato/CAB6gD_QpvgHt744fZ-XnS3cqwa6a79X0TaKuV3Xw4t2M0x-Njg%40mail.gmail.com

> <https://groups.google.com/d/msgid/ostinato/CAB6gD_QpvgHt744fZ-XnS3cqwa6a79X0TaKuV3Xw4t2M0x-Njg%40mail.gmail.com?utm_medium=email&utm_source=footer>.

> For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> http://ostinato.org/
> @ostinato
>

> --
> Get Ostinato News and Updates on Twitter - Follow @ostinato
> (http://twitter.com/ostinato)
> ---
> You received this message because you are subscribed to the Google
> Groups "ostinato" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to ostinato+u...@googlegroups.com

> <mailto:ostinato+u...@googlegroups.com>.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/ostinato/CAB6gD_SsY3jBSwAEuPGCMAKW8oAKX5q-Cv-VkzghP4%3DyrV%2BOTw%40mail.gmail.com
> <https://groups.google.com/d/msgid/ostinato/CAB6gD_SsY3jBSwAEuPGCMAKW8oAKX5q-Cv-VkzghP4%3DyrV%2BOTw%40mail.gmail.com?utm_medium=email&utm_source=footer>.

> For more options, visit https://groups.google.com/d/optout.

--

Carlos G Mendioroz <tr...@huapi.ba.ar> LW7 EQI Argentina

[Carlos G Mendioroz]

The drone is not a mcast aware app, so it does not send igmp messages
unless you craft them. And as you say, that would have to come from the
client side.

The sending side has no means to impost reports to make its mcast frames
reach everywhere. And switches with IGMP snoopint do filter mcast for
ports not joined, as you are aware of.

My point is that no config on the sender side can change that.
Am I missing something ?

-Carlos

Yordan Sutanto @ 17/05/2019 16:23 -0300 dixit:
> Hi Carlos,
>
> I might be wrong. But there's still a chance that the receiving drone
> did not send the correct IGMP signal that told the switch to send
> multicast traffic to it. Disabling IGMP means enabling broadcast. All
> devices in the VLAN (regardless if they're asking for the multicast
> traffic or not) will get the multicast traffic sent by the sending
> drone. For example, without the receiving drone configured to send
> IGMPv2 Report message, it will get it. This is not a good scenario.
> Hence my question above.
> Thanks.
>
> Best regards,
> Yordan

> > <mailto:psta...@gmail.com <mailto:psta...@gmail.com>>> wrote:
> >
> >     Yordan,
> >
> >     If the source UDP port is set to 0, can you try a non-zero value?
> >
> >     Do you know which IOS router is dropping the packet? Is there a
> >     counter on that router that could give us a hint about the drop?
> >
> >     Srivats
> >     Founder, Ostinato
> >
> >     On Fri, May 17, 2019 at 12:48 AM Yordan Sutanto
> <yord...@gmail.com <mailto:yord...@gmail.com>

> <mailto:ostinato%2Bunsu...@googlegroups.com>
> >         <mailto:ostinato+u...@googlegroups.com
> <mailto:ostinato%2Bunsu...@googlegroups.com>>.

> >         To view this discussion on the web visit
> >       
>  https://groups.google.com/d/msgid/ostinato/CAB6gD_QpvgHt744fZ-XnS3cqwa6a79X0TaKuV3Xw4t2M0x-Njg%40mail.gmail.com
> >       
>  <https://groups.google.com/d/msgid/ostinato/CAB6gD_QpvgHt744fZ-XnS3cqwa6a79X0TaKuV3Xw4t2M0x-Njg%40mail.gmail.com?utm_medium=email&utm_source=footer>.
> >         For more options, visit https://groups.google.com/d/optout.
> >
> >
> >
> >     --
> >     http://ostinato.org/
> >     @ostinato
> >
> > --
> > Get Ostinato News and Updates on Twitter - Follow @ostinato
> > (http://twitter.com/ostinato)
> > ---
> > You received this message because you are subscribed to the Google
> > Groups "ostinato" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> > an email to ostinato+u...@googlegroups.com

> <mailto:ostinato%2Bunsu...@googlegroups.com>
> > <mailto:ostinato+u...@googlegroups.com
> <mailto:ostinato%2Bunsu...@googlegroups.com>>.

> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/ostinato/CAB6gD_SsY3jBSwAEuPGCMAKW8oAKX5q-Cv-VkzghP4%3DyrV%2BOTw%40mail.gmail.com
> >
> <https://groups.google.com/d/msgid/ostinato/CAB6gD_SsY3jBSwAEuPGCMAKW8oAKX5q-Cv-VkzghP4%3DyrV%2BOTw%40mail.gmail.com?utm_medium=email&utm_source=footer>.
> > For more options, visit https://groups.google.com/d/optout.
>
> --

> Carlos G Mendioroz  <tr...@huapi.ba.ar <mailto:tr...@huapi.ba.ar>> 
> LW7 EQI  Argentina

[Srivats P]

Yordan,

As Carlos said the problem is not with the UDP multicast data stream since it is received at the destination without IGMP snooping enabled.

The problem I believe is with the IGMPv2 report. Looking at a valid IGMP capture https://www.cloudshark.org/captures/009000d278f5, you are missing the following -

* IP Destination Address should be same as the Group address

* IP Router Alert option

Please try that and let me know.

You could also import a valid IGMP packet from a pcap file like the one linked above directly into Ostinato

Srivats

Founder, Ostinato

To unsubscribe from this group and stop receiving emails from it, send an email to ostinato+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ostinato/ae5c6fcf-e988-6159-974d-db28844d3fd9%40huapi.ba.ar.

For more options, visit https://groups.google.com/d/optout.

--

http://ostinato.org/
@ostinato

[Carlos G Mendioroz]

I don't know the snooping code of your switches, but RFC 2236 indicates
that reports go to the group, not to all routers:

9. Message destinations

This information is provided elsewhere in the document, but is
summarized here for convenience.

Message Type Destination Group
------------ -----------------
General Query ALL-SYSTEMS (224.0.0.1)
Group-Specific Query The group being queried
Membership Report The group being reported
Leave Message ALL-ROUTERS (224.0.0.2)

That may be your issue.
-Carlos

Yordan Sutanto @ 20/05/2019 13:34 -0300 dixit:
> Hi Srivats & Carlos,
>
> I really appreciate your feedback. Thanks.
> I have seen this link https://www.cloudshark.org/captures/009000d278f5,
> and have tried to craft the IGMP packets on the client (received) drone,
> and also craft the UDP Multicast packets on the sender drone.
> The settings are on the 01-multicast.ossn packet.
> The sender drone IP is 192.168.0.1, and the receiver drone IP is
> 192.168.0.2.
> The multicast group we're using is 239.255.255.250.
> The UDP source & destination port is 20480.
>
> Below is the ostinato setting on both drones:
> 1. Multicast Sender:

>
> Double click the Gear Option and select below options
> a. Protocol Selection:
> - L1: Mac
> - VLAN: Untagged
> - L2: Ethernet II
> - L3: IPv4
> - L4: UDP
> - L5: None
> - Payload: Pattern
> b. Protocol Data:
> . Media Access Protocol

> - Destination Address: 01-00-5E-7f-ff-fa (the multicast destination MAC
> address)
> - Source Address: fa:16:3e:d7:fe:ef (drone 1’s eth1 MAC address)

> . Internet Protocol ver 4
> - Source: 192.168.0.1

> - Destination: 239.255.255.250

> . User Datagram Protocol
> - Override Source Port: 20480
> - Override Destination Port: 20480
> c. Stream Control:
> - Number of Packets: 100
> - Packets/Sec: 10
> - After this stream: Stop
>   (What this means is when we run this stream, it will attempt to send
> 10 multicast IP packets encapsulated in multicast Ethernet Frames each
> second for a period of 10 seconds and then it shall stop.)
> - click OK, then click Apply.
>

> 2. Multicast Receiver:

>
> Double click the Gear Option and select below options
> a. Protocol Selection:
> - L1: Mac
> - VLAN: Untagged
> - L2: Ethernet II
> - L3: IPv4
> - L4: IGMP
> - L5: None

> - Payload: None

> b. Protocol Data:
> . Media Access Protocol
> - Destination Address: 01:00:5e:00:00:02 (the multicast destination MAC
> address of 224.0.0.2)

> - Source Address: fa:16:3e:62:26:55 (drone 2’s eth1 MAC address)

> . Internet Protocol ver 4
> - Source: 192.168.0.2
> - Destination: 224.0.0.2
> . Internet Group Management Protocol
> - Message Type: 22 IGMPv2 Report

> - Group Address: 239.255.255.250

> c. Stream Control:
> - Number of Packets: 1
> - Packets/Sec: 0.1
> - After this stream: Goto First
>   (What this means is when we run this stream, it will attempt to send 1
> IGMP Join every 10 seconds continuously.)
> - click OK, then click Apply.
>
>

> I don't see Router Alert option in the ostinato drone's IGMP setting /
> in this URL:https://www.cloudshark.org/captures/009000d278f5. Please
> guide me where I can find this setting.
> I don't intend to have any router in the topology since both multicast
> sender and receiver are in the same broadcast domain (same subnet, same
> VLAN).
> They're only separated by 3x Layer 2 managed switches.
> I believe the problem is with the receiving drone's IGMP setting.
> I wonder if you have a golden configuration to test multicast traffic
> using ostinato (I believe no configuration required on the switches,
> since by default IGMP is enabled for all VLANs).
> We just need to ensure that the receiving drone is sending the correct
> signal to the connected switch that it wants to receive multicast traffic.
> Do we need any multicast router (PIM router) on the setup for this scenario?
>
> Please kindly advise.
> Thanks.

> >     <mailto:ostinato%2Bunsu...@googlegroups.com
> <mailto:ostinato%252Buns...@googlegroups.com>>
> >     >         <mailto:ostinato+u...@googlegroups.com
> <mailto:ostinato%2Bunsu...@googlegroups.com>
> >     <mailto:ostinato%2Bunsu...@googlegroups.com
> <mailto:ostinato%252Buns...@googlegroups.com>>>.

> >     >         To view this discussion on the web visit
> >     >       
> >   
>   https://groups.google.com/d/msgid/ostinato/CAB6gD_QpvgHt744fZ-XnS3cqwa6a79X0TaKuV3Xw4t2M0x-Njg%40mail.gmail.com
> >     >       
> >   
>   <https://groups.google.com/d/msgid/ostinato/CAB6gD_QpvgHt744fZ-XnS3cqwa6a79X0TaKuV3Xw4t2M0x-Njg%40mail.gmail.com?utm_medium=email&utm_source=footer>.
> >     >         For more options, visit
> https://groups.google.com/d/optout.
> >     >
> >     >
> >     >
> >     >     --
> >     >     http://ostinato.org/
> >     >     @ostinato
> >     >
> >     > --
> >     > Get Ostinato News and Updates on Twitter - Follow @ostinato
> >     > (http://twitter.com/ostinato)
> >     > ---
> >     > You received this message because you are subscribed to
> the Google
> >     > Groups "ostinato" group.
> >     > To unsubscribe from this group and stop receiving emails
> from it, send
> >     > an email to ostinato+u...@googlegroups.com
> <mailto:ostinato%2Bunsu...@googlegroups.com>

> >     <mailto:ostinato%2Bunsu...@googlegroups.com
> <mailto:ostinato%252Buns...@googlegroups.com>>
> >     > <mailto:ostinato+u...@googlegroups.com
> <mailto:ostinato%2Bunsu...@googlegroups.com>
> >     <mailto:ostinato%2Bunsu...@googlegroups.com
> <mailto:ostinato%252Buns...@googlegroups.com>>>.

> >     > To view this discussion on the web visit
> >     >
> >   
>  https://groups.google.com/d/msgid/ostinato/CAB6gD_SsY3jBSwAEuPGCMAKW8oAKX5q-Cv-VkzghP4%3DyrV%2BOTw%40mail.gmail.com
> >     >
> >   
>  <https://groups.google.com/d/msgid/ostinato/CAB6gD_SsY3jBSwAEuPGCMAKW8oAKX5q-Cv-VkzghP4%3DyrV%2BOTw%40mail.gmail.com?utm_medium=email&utm_source=footer>.
> >     > For more options, visit https://groups.google.com/d/optout.
> >
> >     --
> >     Carlos G Mendioroz  <tr...@huapi.ba.ar

> <mailto:tr...@huapi.ba.ar> <mailto:tr...@huapi.ba.ar

> <mailto:tr...@huapi.ba.ar>>> 
> >     LW7 EQI  Argentina
> >
>
> --
> Carlos G Mendioroz  <tr...@huapi.ba.ar
> <mailto:tr...@huapi.ba.ar>>  LW7 EQI  Argentina
>
> --

> Get Ostinato News and Updates on Twitter - Follow @ostinato
> (http://twitter.com/ostinato)
> ---
> You received this message because you are subscribed to the
> Google Groups "ostinato" group.
> To unsubscribe from this group and stop receiving emails from
> it, send an email to ostinato+u...@googlegroups.com

> <mailto:ostinato%2Bunsu...@googlegroups.com>.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/ostinato/ae5c6fcf-e988-6159-974d-db28844d3fd9%40huapi.ba.ar.
> For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> http://ostinato.org/
> @ostinato
>

[Yordan Sutanto]

Hi Srivats & Carlos,

I really appreciate your feedback. Thanks.

I have seen this link https://www.cloudshark.org/captures/009000d278f5, and have tried to craft the IGMP packets on the client (received) drone, and also craft the UDP Multicast packets on the sender drone.

The settings are on the 01-multicast.ossn packet.

The sender drone IP is 192.168.0.1, and the receiver drone IP is 192.168.0.2.

The multicast group we're using is 239.255.255.250.

The UDP source & destination port is 20480.

Below is the ostinato setting on both drones:

1. Multicast Sender:

Double click the Gear Option and select below options
a. Protocol Selection:
- L1: Mac
- VLAN: Untagged
- L2: Ethernet II
- L3: IPv4
- L4: UDP
- L5: None
- Payload: Pattern
b. Protocol Data:
. Media Access Protocol

- Destination Address: 01-00-5E-7f-ff-fa (the multicast destination MAC address)
- Source Address: fa:16:3e:d7:fe:ef (drone 1’s eth1 MAC address)

. Internet Protocol ver 4
- Source: 192.168.0.1

- Destination: 239.255.255.250

. User Datagram Protocol
- Override Source Port: 20480
- Override Destination Port: 20480
c. Stream Control:
- Number of Packets: 100
- Packets/Sec: 10
- After this stream: Stop
  (What this means is when we run this stream, it will attempt to send 10 multicast IP packets encapsulated in multicast Ethernet Frames each second for a period of 10 seconds and then it shall stop.)
- click OK, then click Apply.

2. Multicast Receiver:

Double click the Gear Option and select below options
a. Protocol Selection:
- L1: Mac
- VLAN: Untagged
- L2: Ethernet II
- L3: IPv4
- L4: IGMP
- L5: None

- Payload: None

b. Protocol Data:
. Media Access Protocol
- Destination Address: 01:00:5e:00:00:02 (the multicast destination MAC address of 224.0.0.2)

- Source Address: fa:16:3e:62:26:55 (drone 2’s eth1 MAC address)

. Internet Protocol ver 4
- Source: 192.168.0.2
- Destination: 224.0.0.2
. Internet Group Management Protocol
- Message Type: 22 IGMPv2 Report

- Group Address: 239.255.255.250

c. Stream Control:
- Number of Packets: 1
- Packets/Sec: 0.1
- After this stream: Goto First
  (What this means is when we run this stream, it will attempt to send 1 IGMP Join every 10 seconds continuously.)
- click OK, then click Apply.

I don't see Router Alert option in the ostinato drone's IGMP setting / in this URL:https://www.cloudshark.org/captures/009000d278f5. Please guide me where I can find this setting.

I don't intend to have any router in the topology since both multicast sender and receiver are in the same broadcast domain (same subnet, same VLAN).

They're only separated by 3x Layer 2 managed switches.

I believe the problem is with the receiving drone's IGMP setting.

I wonder if you have a golden configuration to test multicast traffic using ostinato (I believe no configuration required on the switches, since by default IGMP is enabled for all VLANs).

We just need to ensure that the receiving drone is sending the correct signal to the connected switch that it wants to receive multicast traffic.

Do we need any multicast router (PIM router) on the setup for this scenario?

Please kindly advise.

Thanks.

[Carlos G Mendioroz]

Yordan Sutanto @ 20/05/2019 17:14 -0300 dixit:
> Hi Carlos,
>
> Thanks for your feedback.
> Membership Report & Leave Messages are sent from the client to the
> router using 224.0.0.2.
> General Query Messages are sent from the router to the client using
> 224.0.0.1.
> So I guess our understanding is correct.

That's not what I said, so I don't follow what "our" understanding
refers to.

The RFC for IGMPv2 says that reports go to the group, in your case,
to 239.255.255.250 if memory serves. Not to all routers (224.0.0.2).

[Carlos G Mendioroz]

Yordan Sutanto @ 20/05/2019 17:27 -0300 dixit:
> Hi Carlos,
>
> I have done what you said.

I don't see that's the case :)

> In the receiver drone > Protocol Data tab, below were the settings:
> 1. Media Access Protocol

> - Destination Address: 01:00:5e:00:00:02 (the multicast destination MAC
> address of 224.0.0.2)

> - Source Address: fa:16:3e:12:1d:9c (drone 2’s eth1 MAC address)
>
> 2. Internet Protocol ver 4
> - Source: 192.168.0.4
> - Destination: *224.0.0.2*
>
> 3. Internet Group Management Protocol

> - Message Type: 22 IGMPv2 Report

> - Group Address: *239.255.255.250*
> *
> *
> Is the above setting correct?
> I was following this URL's
> guide: http://www.thingnetwork.io/multicast-testing-with-ostinato/
> I can change the Destination from 224.0.0.2 to 239.255.255.250 if you
> think it's better.

That's what the RFC says. It's not my call.

> Please kindly advise.
> Thanks.

Try using the group as the report destination. That may in turn get the
snooping code to recognize the client...

-Carlos

> *
> *
> Best regards,
> Yordan

> Carlos G Mendioroz  <tr...@huapi.ba.ar <mailto:tr...@huapi.ba.ar>> 
> LW7 EQI  Argentina
>

[Yordan Sutanto]

Hi Carlos,

Thanks for your feedback.

Membership Report & Leave Messages are sent from the client to the router using 224.0.0.2.

General Query Messages are sent from the router to the client using 224.0.0.1.

So I guess our understanding is correct.

For the sake of testing, I have even tested using a different topology:

IPv4:

IPv6:

I have also attached the VIRL router & switches configuration for both IPv4 & IPv6 scenario.

I was trying to send UDP multicast packets from drone-1 to drone-4 in all scenarios, this time.

drone-4 never got the UDP multicast traffic.

Best regards,

Yordan

[Yordan Sutanto]

Hi Carlos,

I have done what you said.

In the receiver drone > Protocol Data tab, below were the settings:

1. Media Access Protocol

- Destination Address: 01:00:5e:00:00:02 (the multicast destination MAC address of 224.0.0.2)

- Source Address: fa:16:3e:12:1d:9c (drone 2’s eth1 MAC address)

2. Internet Protocol ver 4
- Source: 192.168.0.4
- Destination: 224.0.0.2

3. Internet Group Management Protocol

- Message Type: 22 IGMPv2 Report
- Group Address: 239.255.255.250

Is the above setting correct?

I was following this URL's guide: http://www.thingnetwork.io/multicast-testing-with-ostinato/

I can change the Destination from 224.0.0.2 to 239.255.255.250 if you think it's better.

Please kindly advise.
Thanks.

Best regards,

Yordan

[Yordan Sutanto]

Hi Carlos & Srivats,

Thank you! Like you said, it's now working!

Below are the working settings:

IPv4 UDP Multicast Test

1. Multicast Sender:

Double click the Gear Option and select below options
a. Protocol Selection:
- L1: Mac
- VLAN: Untagged
- L2: Ethernet II
- L3: IPv4
- L4: UDP
- L5: None
- Payload: Pattern
b. Protocol Data:

. Media Access Protocol

- Destination Address: 01-00-5E-7f-ff-fa (the multicast destination MAC address)

- Source Address: fa:16:3e:69:be:05 (drone 1’s eth1 MAC address)

. Internet Protocol ver 4

- Source: 192.168.1.2

- Destination: 239.255.255.250
. User Datagram Protocol
- Override Source Port: 20480
- Override Destination Port: 20480
c. Stream Control:
- Number of Packets: 100
- Packets/Sec: 10
- After this stream: Stop
  (What this means is when we run this stream, it will attempt to send 10 multicast IP packets encapsulated in multicast Ethernet Frames each second for a period of 10 seconds and then it shall stop.)
- click OK, then click Apply.

-----------------

2. Multicast Receiver:

Double click the Gear Option and select below options
a. Protocol Selection:
- L1: Mac
- VLAN: Untagged
- L2: Ethernet II
- L3: IPv4
- L4: IGMP
- L5: None
- Payload: None
b. Protocol Data:

. Media Access Protocol
- Destination Address: 01-00-5E-7f-ff-fa (the multicast destination MAC address of 239.255.255.250)
- Source Address: fa:16:3e:af:6c:4b (drone 2’s eth1 MAC address)

. Internet Protocol ver 4

- Source: 192.168.0.2
- Destination: 239.255.255.250

. Internet Group Management Protocol
- Message Type: 22 IGMPv2 Report

- Group Address: 239.255.255.250
c. Stream Control:
- Number of Packets: 1
- Packets/Sec: 0.1
- After this stream: Goto First
  (What this means is when we run this stream, it will attempt to send 1 IGMP Join every 10 seconds continuously.)
- click OK, then click Apply.

Muchas Gracias!

Best regards,

Yordan

[Yordan Sutanto]

Hi Carlos, Srivats,

I wonder if you also have a proven working Ostinato sender & receiver setting for sending & receiving IPv6 UDP Multicast traffic.

I have tested the IPv6 topology above using below settings, but the receiver couldn't get the IPv6 UDP Multicast frames.

!R1:

ipv6 unicast-routing
ipv6 multicast-routing
int gi0/1
 descr to SW1
 ipv6 add 2001:db8:cafe:2::1/64
 ipv6 address fe80::1 link-local
 ipv6 pim
 no shut
 
int gi0/2
 descr to Drone-1 (sender)
 ipv6 add 2001:db8:cafe:1::1/64
 ipv6 address fe80::1 link-local
 ipv6 pim
 no shut

-------

!SW1:

vtp mode transparent
vlan 111
 name iot
 exit

int gi0/1
 descr to R1
 switchport mode access
 switchport access vlan 111
 spanning-tree portfast
 no shut

int gi0/2
 descr to SW2
 switchport trunk encapsulation dot1q
 switchport mode trunk
 no shut

int gi0/3
 descr to Drone-2 (Receiver)
 switchport mode access
 switchport access vlan 111
 spanning-tree portfast
 no shut

int gi1/0
 descr to Drone-3 (Receiver)
 switchport mode access
 switchport access vlan 111
 spanning-tree portfast
 no shut

-----------

!SW2:

vtp mode transparent
vlan 111
 name iot
 exit

int gi0/1
 descr to SW1
 switchport trunk encapsulation dot1q
 switchport mode trunk
 no shut

int gi0/2
 descr to Drone-4 (Receiver)
 switchport mode access
 switchport access vlan 111
 spanning-tree portfast
 no shut

int gi0/3
 descr to Drone-5 (Receiver)
 switchport mode access
 switchport access vlan 111
 spanning-tree portfast
 no shut

----------------

IPv6 UDP Multicast Test

1. Multicast Sender:

Double click the Gear Option and select below options
a. Protocol Selection:

- Frame Length: 66

- L1: Mac
- VLAN: Untagged
- L2: Ethernet II

- L3: IPv6

- L4: UDP
- L5: None
- Payload: Pattern
b. Protocol Data:
. Media Access Protocol

- Destination Address: 33-33-ff-aa-aa-aa (the multicast destination MAC address)
- Source Address: fa:16:3e:a7:d3:03 (drone 1’s eth1 MAC address)
. Internet Protocol ver 6
- Source: 2001:db8:cafe:1:f816:3eff:fea7:d303
- Destination: ff3e:40:2001:db8:cafe:1:aaaa:aaaa

. User Datagram Protocol
- Override Source Port: 20480
- Override Destination Port: 20480
c. Stream Control:
- Number of Packets: 100
- Packets/Sec: 10
- After this stream: Stop
  (What this means is when we run this stream, it will attempt to send 10 multicast IP packets encapsulated in multicast Ethernet Frames each second for a period of 10 seconds and then it shall stop.)
- click OK, then click Apply.

-------------------

2. Multicast Receiver:

Double click the Gear Option and select below options
a. Protocol Selection:

- Frame Length: 82

- L1: Mac
- VLAN: Untagged
- L2: Ethernet II

- L3: IPv6
- L4: MLD

- L5: None
- Payload: None
b. Protocol Data:
. Media Access Protocol

- Destination Address: 33-33-ff-aa-aa-aa (the multicast destination MAC address of ff3e:40:2001:db8:cafe:1:aaaa:aaaa)
- Source Address: fa:16:3e:93:55:be (drone 2’s eth1 MAC address)
. Internet Protocol ver 6
- Source: 2001:db8:cafe:2:f816:3eff:fe93:55be
- Destination: ff3e:40:2001:db8:cafe:1:aaaa:aaaa

. Internet Group Management Protocol

- Message Type: 131 - MLDv1 Report
- Group Address: ff3e:40:2001:db8:cafe:1:aaaa:aaaa

c. Stream Control:
- Number of Packets: 1
- Packets/Sec: 0.1
- After this stream: Goto First
  (What this means is when we run this stream, it will attempt to send 1 IGMP Join every 10 seconds continuously.)
- click OK, then click Apply.

----------------

Please kindly advise.

Thanks.

Best regards,

Yordan

[Srivats P]

Yordan,

Did you try without enabling MLD Snooping on the switches to verify if the problem is with with the multicast data stream or the MLD join packet?

Srivats

Founder, Ostinato

--

http://ostinato.org/
@ostinato

[Srivats P]

+ ostinato

Yordan,

Sorry, missed this email.

Were you able to get MLD snooping to work?

Srivats

Founder, Ostinato

On Wed, May 22, 2019 at 10:57 PM Yordan Sutanto <yord...@gmail.com> wrote:

Hi Srivats,

Thanks for your feedback. 

I just tested this again, but this time without any router between the sender & receiver. 

So, across IOSvL2 switches, ostinato sender could broadcast UDP multicast traffic to ostinato receivers (even without the ostinato receivers sending MLDv1 Report ). This means there's no problem with the multicast data stream. There could be a problem in on the MLD Join though.

I wonder if you have the correct wireshark packet capture for MLDv1. I couldn't find it here: https://wiki.wireshark.org/SampleCaptures.

I wonder if my receiver ostinato drone's setting below is already correct.

2. Multicast Receiver:

Double click the Gear Option and select below options
a. Protocol Selection:
- Frame Length: 82
- L1: Mac
- VLAN: Untagged
- L2: Ethernet II
- L3: IPv6
- L4: MLD
- L5: None
- Payload: None
b. Protocol Data:
. Media Access Protocol
- Destination Address: 33-33-ff-aa-aa-aa (the multicast destination MAC address of ff3e:40:2001:db8:cafe:1:aaaa:aaaa)

- Source Address: fa:16:3e:78:6a:5b (drone 2’s eth1 MAC address)

. Internet Protocol ver 6

- Source: 2001:db8:cafe:2:f816:3eff:fe78:6a5b

- Destination: ff3e:40:2001:db8:cafe:1:aaaa:aaaa

. Multicast Listener Discovery

- Message Type: 131 - MLDv1 Report
- Group Address: ff3e:40:2001:db8:cafe:1:aaaa:aaaa
c. Stream Control:
- Number of Packets: 1
- Packets/Sec: 0.1
- After this stream: Goto First
  (What this means is when we run this stream, it will attempt to send 1 IGMP Join every 10 seconds continuously.)
- click OK, then click Apply.

Best regards,

Yordan

--

http://ostinato.org/
@ostinato