Re: [dts] Idem with Multicast Packets Feature

[Daniel Kirichok <dkirichok@iol.unh.edu>]

[-- Attachment #1: Type: text/plain, Size: 1755 bytes --]

Hi all,

I wanted to send a follow up question regarding the development of the Idem
for Multicast Packets feature. Based on the plan we have so far, it
involves having one port be designated to send the packet, and two ports be
designated to receive the packet. In order to send out one packet for the
two ports to receive, it looks like this would require for all three ports
to be on the same network and a 1-2 pairing configuration would be needed
on the server. Is this the right approach for developing this feature?
Would an alternate approach be better to avoid server reconfiguration such
as sending out a multicast packet from each of the ports (two total packets
sent out) and see if they each receive what was sent?

Thanks,
Dan

On Fri, Jul 10, 2020 at 1:27 PM Daniel Kirichok <dkirichok@iol.unh.edu>
wrote:

> Hi all,
>
> The Idem with Multicast Packets test will first create three groups of
> port combinations. The first group will have both ports be capable of
> receiving a packet. The second group will have one port be open to receive
> a packet and one be closed. The third group will have both ports be closed.
> Each of the ports will be pinged to ensure that they are reachable.
> Afterwards, a packet will be generated and sent to each of these groups,
> and it will ensure that the correct behavior of a failed or successful
> delivery occurs on each port.
>
> Let me know if there are any comments or questions.
>
> Thanks,
> Dan
>
> --
>
> Dan Kirichok
>
> UNH InterOperability Laboratory
>
> 21 Madbury Rd, Suite 100, Durham, NH 03824
>
> dkirichok@iol.unh.edu
>
> www.iol.unh.edu
>
>
>
>

-- 

Dan Kirichok

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

dkirichok@iol.unh.edu

www.iol.unh.edu

[-- Attachment #2: Type: text/html, Size: 6021 bytes --]