Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to do some multicast big file copies over to remote clients on the other side of a satellite link. The idea is to minimize the amount of traffic going up to the satellite.

I tried using uftp without luck. The problem is that, even though we can reach clients via multicast from our central Hub, they aren't able to respond to a multicast address (it's not supported by the return link). As uftp needs to respond to a multicast address in order to report any missing packets I'm out of luck.

So does anyone have any recommendations or alternatives I can use to do the trasfers? Any tip or pointer would be appreciated.

share|improve this question

A UFTP client sends packets unicast back to the server's IP address. The fact that the incoming packets are sent to a multicast address shouldn't change that. If you can't send unicast from the clients back to the server, perhaps you can set up routes on the client side so that the return traffic takes a route other than satellite.

If there's no way at all for the receivers to talk to the sender, you'll need something that supports FEC like NORM. Of course, in a situation like this you can't know conclusively that the files arrived successfully.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.