Udpcast June 2008

udpcast@udpcast.linux.lu

4 discussions

throttle output of udp-cast
by David Crider 23 Sep '08

23 Sep '08

Is it possible to do dynamically throttled UPDcast transmission? We need to throttle the data flow to a Logic Innovations IP encapsulator (with LI's documentation attached with their permission). The udpcast mutlticast address is considered a single route to the IPE. The IPE sends out flow-control messages (described in document) that shows how many bytes are available for traffic for each route every 100 milliseconds in a multicastand comes from a user specified multicast of its own. Attached is the LI document, again with the manufactures permission. Also, you can contact Theo Aukerman, taukerman(a)logici.com for any additional info. I'm asking these questions because IF this is possible, then this would be an almost complete framework for an open source Data-casting network, and can be used for over the air data-broadcasting from any DTV transmitter or any other system with null packets. I currently work as an engineer for a TV station that does data transmission, but would like to move to an open source model.

2 1

Sender's timeout for waiting for receivers
by Dmitry Popov 23 Sep '08

23 Sep '08

Hi everyone, Please confirm my guess (or explain how to implement it). I need a "sender-timeout", a period of time while sender waits for receivers to connect, and if none are connected - sender exits without transmission. The only way to implement this is shell/perl/... script, which starts udp-sender with --min-receivers option and monitors its stderr. If no "Starting transfer" is found during specified period of time - it kills udp-sender process. Regards, Dmitry

2 1

Request - include netcat
by brian＠polibyte.com 23 Sep '08

23 Sep '08

Hi, It would be nice if netcat were included in the CD and PXE images. Busybox has a version, so adding it shouldn't take much. All the best, Brian

2 1

incorrect documentation of --nosync flag?
by George Coulouris, MSD 11 Sep '08

11 Sep '08

http://udpcast.linux.lu/cmd.html states that --nosync is the default when writing to a file or a pipe, but this does not appear to be the case; I verified with strace that udp-receiver open()s its output file with O_SYNC unless you specify --nosync.

2 1

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Udpcast June 2008