Hello all,
Udpcast 20211207 is released.
The most important changes are:
- --max-bitrate now works with bitrates greater than 2**31
- Use newest busybox (1.33.2) and kernel (5.10.83)
- Lots of compiler warnings and variable type issues have been resolved
Regards,
Alain
Dear sir,
I would like to start by thanking you for your work on udpcast as it has
been very useful for a lot of people and companies.
I am reaching out in order to get some insight on how to use udpcast
(sender & receiver) directly in C code without executing it from a bash
call.
To be clear, I would like to know if there is some kind of documentation on
how to use these programs in C as functions that I could call.
So far, every program that I have seen uses udp-sender and udp-receiver by
a bash call inside a C or python code. This does not suit me because it
slows significantly the speed of the program.
Thanks a lot
I am trying to push data through a one-way pipe in an automated way
using udp-sender and udp-receiver. I have a working example, but can't
get the --nokbd option to work on the sending side.
Working Sender:
yes | ~/udp-sender --async --fec 8x6/64 --max-bitrate 500M -f
tmp_send_tarball.tar
Receiver Command:
~/udp-receiver --pipe ~/rx_hook.sh --nokbd
But notice I have to pipe the "yes" command into udp-sender to trigger
the start from udp-sender. When instead I use --nokbd on the receiver,
it hangs waiting for something after the control message. True to the
documentation, it doesn't ask nor accept input, but it seems to fall
into a default of "don't send" rather than a default of "send
immediately" as I would expect.
$ ~/udp-sender --async --fec 8x6/64 --max-bitrate 500M -f
.tmp_send_tarball.tar --nokbd
stripes=8 redund=6 stripesize=64
Udp-sender 20200328
Using mcast address 234.14.136.217
UDP sender for .tmp_send_tarball.tar at 10.14.136.217 on eno3
Broadcasting control to 10.14.143.255
<hangs here...>
Am I missing something?
Respectfully,
Luke
William
Please ensure you are using UDP/IGMP.
Brent
Hi, (I hope this list is still active)
I am a newbie. I am testing multicast support on three computers connected
through a gigabit switch. When only the server, ran as (rand.bin is a 1Gb
file)
udp-sender --interface eth1 --file rand.bin
and ONE client
udp-receiver --file rand.bin
are connected, the bandwidth is around 937.32 Mbps, which is very good. But
with two or more clients if consistently drops to 11 Mbps
I would expect to bandwidth to decrease as 1/N, where N is the number of
clients.
What am I missing?
I am using a dumb switch.
Thanks
--
Best regards / Cordialmente,
William-Fernando Oquendo
--------------------------
Este correo puede carecer de tildes o e?es debido al teclado.
THIS MESSAGE IS FOR THE USE OF THE INTENDED RECIPIENT(S) ONLY AND MAY CONTAIN INFORMATION THAT IS PRIVILEGED, PROPRIETARY, CONFIDENTIAL, AND/OR EXEMPT FROM DISCLOSURE UNDER ANY RELEVANT PRIVACY LEGISLATION. No rights to any privilege have been waived. If you are not the intended recipient, you are hereby notified that any review, re-transmission, dissemination, distribution, copying, conversion to hard copy, taking of action in reliance on or other use of this communication is strictly prohibited. If you are not the intended recipient and have received this message in error, please notify me by return e-mail and delete or destroy all copies of this message.
Hi, (I hope this list is still active)
I am a newbie. I am testing multicast support on three computers connected
through a gigabit switch. When only the server, ran as (rand.bin is a 1Gb
file)
udp-sender --interface eth1 --file rand.bin
and ONE client
udp-receiver --file rand.bin
are connected, the bandwidth is around 937.32 Mbps, which is very good. But
with two or more clients if consistently drops to 11 Mbps
I would expect to bandwidth to decrease as 1/N, where N is the number of
clients.
What am I missing?
I am using a dumb switch.
Thanks
--
Best regards / Cordialmente,
William-Fernando Oquendo
--------------------------
Este correo puede carecer de tildes o eñes debido al teclado.
Hi ALL
I am a IT teacher in Taiwan. I use Udpcast Windows version + WinPE to maintain our PC & NB for a lon time.
Udpcast is a very useful tool and helpful, thanks for all your works.
We now encounter an upgrade to 86-x64.
Can anyone help to compile Udpcast Windows 86-x64 version?
Sincerely
MS. Yang.
嘉義縣教育網路中心
05-2304464
Hello all,
Udpcast 20200328 is released.
The most important changes are:
- Use newest busybox (1.31.1) and kernel (5.0.21)
- Udp-sender now returns a non-zero exit status if a timeout expires at
start
- Fix compiler warnings and various typoes
- Fixes for Mingw
- Fix issues in assembly in fec.c
Unfortunately, due to bigger sizes produced by today's kernels, and due
to lack of usage, I dropped floppy support. Similarly, Etherboot support
has been dropped. Indeed PXE is the recommended net boot solution today.
Regards,
Alain
Dear developpers,
we are academic researchers working in automated program analysis.
We are currently interested in checking compliance of inline asm chunks
as found in C programs.
While benchmarking our tool and technique, we found 2 significant compliance
issues in UDPCAST. We report them to you, as well as adequate patches
with explanations.
* All these bugs are related to compliance between the block of asm and its
surrounding "contract" (in gcc-style notation). They are akin to undefined or
implementation-defined behaviours in C: they currently do not manifest
themselves in your program, but at some point in time with compiler
optimizations becoming more and more aggressive or changes in undocumented
compiler choices regarding asm chunks, they can suddenly trigger a
(hard-to-find) bug.
* The typical problems come from the compiler missing dataflow information
and performing undue optimizations on this wrong basis, or the compiler
allocating an already used register. Actually, we demonstrate "in lab" problems
with all these categories of bugs in case of inlining
(especially with LTO enabler) or code refactoring.
* Some of those issues may seems benign or irrealistic but it cost nothing
to patch so, why not do it?
We would be very interested to hear your opinion on these matters.
Are you interested in such errors and patches?
Also, besides the patches, we are currently working on a code analyzer
prototype designed to check asm compliance and to propose patches when the
chunk is not compliant. This is still work in progress and we are finalizing it.
The errors and patches I reported to you came from my prototype.
In case such a prototype would be made available, would you consider using it?
Best regards
Frédéric Recoules
hey, I have a doubt about UDPCast
Actually a few questions...
When have u made the last atualization in the software?
You still do it?
Can I use it for clone modern machines (2010-201X)?
Please answer as soon as possible, thank you
