Tjyylli

Did arcade monitors have same pixel aspect ratio as TV sets?

How do I color the graph in datavisualization?

Delivering sarcasm

Store Credit Card Information in Password Manager?

Start making guitar arrangements

Is it better practice to read straight from sheet music rather than memorize it?

What was this official D&D 3.5e Lovecraft-flavored rulebook?

Which one is correct as adjective “protruding” or “protruded”?

Loading commands from file

What prevents the use of a multi-segment ILS for non-straight approaches?

Open a doc from terminal, but not by its name

How much character growth crosses the line into breaking the character

What does chmod -u do?

The screen of my macbook suddenly broken down how can I do to recover

Why is it that I can sometimes guess the next note?

What does routing an IP address mean?

Electoral considerations aside, what are potential benefits, for the US, of policy changes proposed by the tweet recognizing Golan annexation?

How to bake one texture for one mesh with multiple textures blender 2.8

Is it improper etiquette to ask your opponent what his/her rating is before the game?

Drawing ramified coverings with tikz

Non-trope happy ending?

Does an advisor owe his/her student anything? Will an advisor keep a PhD student only out of pity?

Is there a name for this algorithm to calculate the concentration of a mixture of two solutions containing the same solute?

How could a planet have erratic days?

Multiple applications using same multicast group on the same Windows host

in wireshark how to know if packet was send to vpn or to internet?UDP packet and firewallRecord multicast stream on multi-homed Linux hostudp client sending ICMP “port unreachable” when receiveing messages from the servernetstat -o timer value “probe”Is it possible to process millions of datagrams per second with Windows?ethernet interface on Linux drops packetsMulticast in LAN not received by all hostsRouters block multicast request once node joins the same groupMultiple VLANs with SAME ip (Ubuntu/Mint)

0

I am a software engineer designing a distributed software, in which the startup procedure utilizes IP multicasting to discover its peers. The software itself is distributed as different executable modules and as such, it sometimes make sense to run several executable modules on the same host. This is where my issues begin, as it seems to me that Windows is not good at managing several processes subscribing to a single multicast group.

My aim is to freely be able to choose on which hosts I start which executables, and these will discover all its peers (be it on the same host or on other hosts) without any predefined knowledge.

So far, troubleshooting indicates that the issue is how Windows handles the scenario of multiple processes subscribing to the same multicast groups, because:

1. If the same process is used for sending and receiving multicast datagrams on the same machine, it works as expected. The process can be split into several threads without any issue.




2. If I run different processes for sending and receiving, the receiving process receives nothing, despite the group join-message and all datagrams shows up in Wireshark.




3. The scenario described in 2 works if I prior to listening also use the same socket to send a packet to the multicast group which I have joined. Then the latter receives multicast datagrams for an unspecified amount of time, upon which then solely stops receiving datagrams (it keeps waiting for datagrams to come). The datagrams are confirmed being sent to/from the network using Wireshark.




4. My latest findings indicate that if I periodically send a multicast message to the group which I subscribe to, I receive datagrams sent to this multicast group, also from other processes on the same host.

IP multicast does, to the best of my understanding, only define communication between hosts, while it is the responsibility of the OS to redirect incoming packets to the appropriate application. As packets seem to always show up in Wireshark, even if an application is not receiving them, it seems that Windows fails in handling incoming packages, or at least deliver them to appropriate applications.

I appreaciate if anyone could either confirm or reject my reasoning as well as to point me in the right direction on how to solve this problem. The goal is to be able for several applications on the same host to join a single multicast group channel and also receive messages without require to also send "junk" to the multicast group in order for them to receive data (the workaround described as point number 4).

I am using Java for implementation and can, if requested, post a MWE here. However, I fear that it may shift focus from the scenario to programming, which is not the concern here (from what I can deduce).

windows-10 ip udp sockets multicast

share

asked 5 mins ago

Christoffer CalåsChristoffer Calås

31

add a comment | 

0

I am a software engineer designing a distributed software, in which the startup procedure utilizes IP multicasting to discover its peers. The software itself is distributed as different executable modules and as such, it sometimes make sense to run several executable modules on the same host. This is where my issues begin, as it seems to me that Windows is not good at managing several processes subscribing to a single multicast group.

My aim is to freely be able to choose on which hosts I start which executables, and these will discover all its peers (be it on the same host or on other hosts) without any predefined knowledge.

So far, troubleshooting indicates that the issue is how Windows handles the scenario of multiple processes subscribing to the same multicast groups, because:

1. If the same process is used for sending and receiving multicast datagrams on the same machine, it works as expected. The process can be split into several threads without any issue.




2. If I run different processes for sending and receiving, the receiving process receives nothing, despite the group join-message and all datagrams shows up in Wireshark.




3. The scenario described in 2 works if I prior to listening also use the same socket to send a packet to the multicast group which I have joined. Then the latter receives multicast datagrams for an unspecified amount of time, upon which then solely stops receiving datagrams (it keeps waiting for datagrams to come). The datagrams are confirmed being sent to/from the network using Wireshark.




4. My latest findings indicate that if I periodically send a multicast message to the group which I subscribe to, I receive datagrams sent to this multicast group, also from other processes on the same host.

IP multicast does, to the best of my understanding, only define communication between hosts, while it is the responsibility of the OS to redirect incoming packets to the appropriate application. As packets seem to always show up in Wireshark, even if an application is not receiving them, it seems that Windows fails in handling incoming packages, or at least deliver them to appropriate applications.

I appreaciate if anyone could either confirm or reject my reasoning as well as to point me in the right direction on how to solve this problem. The goal is to be able for several applications on the same host to join a single multicast group channel and also receive messages without require to also send "junk" to the multicast group in order for them to receive data (the workaround described as point number 4).

I am using Java for implementation and can, if requested, post a MWE here. However, I fear that it may shift focus from the scenario to programming, which is not the concern here (from what I can deduce).

windows-10 ip udp sockets multicast

share

asked 5 mins ago

Christoffer CalåsChristoffer Calås

31

add a comment | 

I am a software engineer designing a distributed software, in which the startup procedure utilizes IP multicasting to discover its peers. The software itself is distributed as different executable modules and as such, it sometimes make sense to run several executable modules on the same host. This is where my issues begin, as it seems to me that Windows is not good at managing several processes subscribing to a single multicast group.

My aim is to freely be able to choose on which hosts I start which executables, and these will discover all its peers (be it on the same host or on other hosts) without any predefined knowledge.

So far, troubleshooting indicates that the issue is how Windows handles the scenario of multiple processes subscribing to the same multicast groups, because:

1. If the same process is used for sending and receiving multicast datagrams on the same machine, it works as expected. The process can be split into several threads without any issue.




2. If I run different processes for sending and receiving, the receiving process receives nothing, despite the group join-message and all datagrams shows up in Wireshark.




3. The scenario described in 2 works if I prior to listening also use the same socket to send a packet to the multicast group which I have joined. Then the latter receives multicast datagrams for an unspecified amount of time, upon which then solely stops receiving datagrams (it keeps waiting for datagrams to come). The datagrams are confirmed being sent to/from the network using Wireshark.




4. My latest findings indicate that if I periodically send a multicast message to the group which I subscribe to, I receive datagrams sent to this multicast group, also from other processes on the same host.

IP multicast does, to the best of my understanding, only define communication between hosts, while it is the responsibility of the OS to redirect incoming packets to the appropriate application. As packets seem to always show up in Wireshark, even if an application is not receiving them, it seems that Windows fails in handling incoming packages, or at least deliver them to appropriate applications.

I appreaciate if anyone could either confirm or reject my reasoning as well as to point me in the right direction on how to solve this problem. The goal is to be able for several applications on the same host to join a single multicast group channel and also receive messages without require to also send "junk" to the multicast group in order for them to receive data (the workaround described as point number 4).

I am using Java for implementation and can, if requested, post a MWE here. However, I fear that it may shift focus from the scenario to programming, which is not the concern here (from what I can deduce).

windows-10 ip udp sockets multicast

share

asked 5 mins ago

Christoffer CalåsChristoffer Calås

31

share

asked 5 mins ago

Christoffer CalåsChristoffer Calås

31

share

asked 5 mins ago

Christoffer CalåsChristoffer Calås

31

asked 5 mins ago

Christoffer CalåsChristoffer Calås

31

asked 5 mins ago

Christoffer CalåsChristoffer Calås

31