I was looking for a tool to send a stream of data with FEC where the
client/receiver can connect even if the stream has yet begun. I haven't
found anything but Udpcast that can do anything similar. I think that
maybe an "streaming" option can be added so the sender sends Hello
packets at the end of a block of slices+FEC so a receiver can hook to
the UDP stream.
What do you think about this? Can this be made modifying Udpcast without
broken it all? Is there another software that I can use?
Jorge Muñoz Castañer
Grupo de Tecnologías de la Información
Departamento de Ingeniería Telemática
Universidad de Vigo
Campus 36310 Vigo SPAIN
This was working and now it has stopped.
Have a UDPcast server running on a HP DL360G5 with 4 NICS. One
connected to an internal infrastructure (eth2) and another connected
to a dedicated switch with the client systems on the same switch (eth3).
When i run the UDPcast send or receive, using the following command:
udp-sender -f /home/base.udpc --interface eth3 --point-to-point --full-
duplex --max-bitrate 600m --nokbd --portbase=9922 --min-receivers 1 --
rexmit-hello-interval 5000 --max-wait 300
I get the following error message:
No suitable network interface found
The following interfaces are available:
Interestingly, an ifconfig show eth3 as a valid network adapter, but
the udp-sender does not see the device. This was working last week,
and nothing has changed on the server
I have tried everything, restarting DHCP, removing the interface and
adding again. Rebooted the server, restarted the network stack
manually. nothing seems to help.
Using SUSE linux 10 as the base server OS.
I'd like to use udp-sender with async and a unicast address instead of
multicast so that unicast at the MAC layer is actually used.
Ive tried using the pointopoint switch, but I get the message "pointopoint
mode set, and 0 participants instead of 1".
Is there a way to do this with udpcast?
I've been using UDP Cast extensively for a while now and I love it, but I
had an issue last week and I want to share it witou you.
The UDP Cast website provides handy ready-made boot images. Apparently,
those images are compiled for i686 and I couldn't make them work on an
older machine because the processor doesn't implement the CMOV operation.
The problem seem to belong to GCC, because it thinks that every i686
processor implements the optional CMOV operation, which is not true.
I solved the problem by compiling my own UDP Cast kernel, but I suggest
that the next UDP Cast ready-made boot images drop the i686 requirement
and stick to i386, for compatibility reasons.
Is this a reasonable request?
Thank you and best regards,
Engenharia Informatica e de Computadores - Instituto Superior Tecnico
I am playing around with the "udpcast image generator" and I need to
store the next-server address in the filesystem for later processing.
I am using kernel-udpcast_2.6.30-rc5_all.deb and
This is what my dhcp.script looks like:
=== snip ===
[ -n "$broadcast" ] && BROADCAST="broadcast $broadcast"
[ -n "$subnet" ] && NETMASK="netmask $subnet"
case "$1" in
/sbin/ifconfig $interface 0.0.0.0
/sbin/ifconfig $interface $ip $BROADCAST $NETMASK
/sbin/echo $siaddr > /etc/server.ip
=== snap ===
This works as expected when generating cd-images.
If I generate a initrd and boot via PXE, the file /etc/server.ip never
I tried to create the file in many places (/tmp, /sbin, etc.) but it
Is there something important that I am missing?
I thought that there is no difference between a cd-image and a plain
initrd (besides syslinux/pxelinux and the kernel being separate).
Additionally FYI, when using the latest kernel and mkimage I get some
I use VirtualBox 2.2 for testing purposes and both cd-image and initrd
crash the VM when trying to write to the filesystem from within
Any help/suggestion is much appreciated.
Thanks in advance.
Does udpcast currently allow using async and pointopoint options together ?
That is, I want to specify the unicast address of the participant manually
from the command line.
I noticed that the same question was raised in last January, 2009, and the
answer was "not -yet- supported":
There's no option to choose the forcedeth module
on the current cast-o-matic web site; is that
intentional? I did find it in the .deb package
containting the 2.6.30 pre-compiled kernel and modules.
I want to use udpcast in unicast (or pointopoint) mode.
However, I do not want udp-sender to determine whether to use unicast or
multicast based on the number of connections coming from the clients since I
want to test udp-sender along with another application on the receiving side
other than udp-receiver (In this framework, there won't be any connections
coming from the clients).
Based on above, I want udp-sender to use the unicast destination IP address
provided by the user from the command line or it may be even hard-coded into
the source code.
I tried to use -m option to specify a unicast address instead of a multicast
address to "trick" udpcast.
But, it did not like that. I guess that it got some kind of negative
feedback from the existing udp-receiver clients, and aborted the transfer
since the clients were expecting a "proper" multicast address after -m
Any ideas to overcome this issue ?