I'm not sure how best to approach my problem. I have a service with runs on a remote machine with receives and process UDP packets. I want the service to be able to re-send these packets to anyone that happens to want them (could be no-one, will typically be one machine, but may be more)
I figured UDP Multicasting would be ideal - the service can send to the multicast group and it doesn't matter how many receivers have registered, or even if there are none.
However, I want to be able to access this over the internet and from what I gather this is nigh-on impossible with UDP Multicasting. Is there another method I might use to achieve this?
If relevant, both my client and service are written in C#.
You cannot multicast on the public Internet, but you can multicast across the public Internet to another site by using a tunnel that supports multicast. Multicast routing is very different from unicast routing, and all the routers in the path of the multicast packets need to have multicast routing configured.
Multicast needs to use multicast routers. Internet is not especially provided with this type of routers. Moreover for the provider of video stream service he cannot charge the user because the configuration of the multicast-group is done in the routers, and he has no control of those routers in the Internet.
Multicast uses UDP (User Datagram Protocol) for “broadcasting” a stream over a closed IP network such as a LAN (Local Area Network) or an IP Service provider's own network. Multicast streaming of live TV is commonly referred to as IPTV, whereas OTT is unicast over the internet.
Use UDP functions to communicate with other computers through a unicast, broadcast, or multicast. Communication with a single other client is called a unicast.
In general this is not possible since multicast packets aren't routed.
There are some techniques to work around this (DVMRP, MOSPF and others) but they all require that you can configure all the routers between your server and the clients (or create a tunnel). There are backbone networks (Abilene, Mbone) with multicast support, but those are of most interest for universities and such. The normal consumer's internet does not have multicast.
Unfortunately you need point-to-point communication. But you are in good company, internet, radio and TV all do point-to-point, transmitting the same data numerous times. Quite a waste of bandwidth.
The preferred method is to use overlay multicast, i.e. use TCP links between peers and implement multicast semantics above that.
Many IPv4 routers do not support multicast or have it disabled, IPv6 is mandated to support multicast and broadcast semantics have been removed.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With