I was studying the UDPCast source code for some experimental purposes. I have the following question.
1. The whole data to be transfered into is divided into slices which again contains a series of blocks to transfer. Can we consider the whole data to be transfered as a single slice ( By setting appropriate parameters in code) and what kind of performance issues we can expect if we do a change of this kind at code level.
Thanks in advance,
Do you Yahoo!?
Y! Messenger - Communicate in real time. Download now.
The option of ipappend 1 in the default file and retransmission
of HELLOs in udp-sender (--rexmit-hello-interval) has been
valuable to getting udpcast working with the Dell notebooks
we have with Broadcom 5700 series ethernet.
Today, with a slightly newer broadcom chipset appearing in
the most recent shipment, we noticed that udp-receiver was
intermittantly not showing the "hit any button to start transfer"
message. With some trial and error I found that if I
watched the tail of /var/log/message on the receiver (server)
and waited for the messages on TX and RX flow control to
complete before running udp-receiver, it would always initiate
a good connection. If I had started the udp-receiver
prior to the TX/RX flow control appearing in the message log
(in which case there was no "hit any key" message),
I could ^C the receiver, run it again and it would signify
the ready state with 100% success.
In conclusion, we have a workaround of starting udp-receiver
after a few seconds past the client PXE machine booting and
showing the udp-sender status ready (but not yet "hit any key...").
Another solution would be if udp-receiver also supported
--rexmit-hello-interval. It isn't a flaw in the udpcast system
but a kludge for a network device that is proving itself to be
sluggish in initialization in general.
I downloaded your CD image and it worked fine until I used it on a pc with a
USB keyboard. These PCs are in the lab I am trying the program on. Do I need
to compile my own image using my own kernal? I am using debian 3.1 and cannot
find the required files as specified by the -k switch.
Please, let me know what I need to do.
Thank you for your reply. Here is the output I get:
cc -Wall -Wshadow -DBB_FEATURE_UDPCAST_FEC -D_FILE_OFFSET_BITS=64 -DUSE_SYSLOG -DNO_BB -c -o socklib.o socklib.c
socklib.c: In function 'udpc_getSendBuf':
socklib.c:280: warning: pointer targets in passing argument 5 of 'getsockopt' differ in signedness
socklib.c: In function 'udpc_getRcvBuf':
socklib.c:293: warning: pointer targets in passing argument 5 of 'getsockopt' differ in signedness
socklib.c: In function 'udpc_setTtl':
socklib.c:323: error: 'SOL_IP' undeclared (first use in this function)
socklib.c:323: error: (Each undeclared identifier is reported only once
socklib.c:323: error: for each function it appears in.)
socklib.c: In function 'mcastOp':
socklib.c:368: error: 'SOL_IP' undeclared (first use in this function)
make: *** [socklib.o] Error 1
Thank you for your help,
>>> D Teed <dteed(a)artistic.ca> 09/14/05 9:18 PM >>>
I suggest posting the actual error you got when you
tried to make the udpcast binaries. It could be
an ordinary dependancy or lib you don't have. Usually
the last 6 to 10 lines from a make error tell the tale
of what went wrong.
I've built udpcast on Sun with Linux, so I don't think
there is anything x86 centric about it.
On Wed, 14 Sep 2005, Jeff Michels wrote:
> I've been using UDPCast for about a year now and it has saved our school
> district from the cost of a commercial imaging program. I has also
> saved me many hours. For that I am grateful.
> Our district just purchased two Apple Servers. Currently I am using a
> 500 Mhz PIII box running Debian as our main image server. It has been
> extermely reliable and UDPCast works great however disk I / O and
> processing limitations are showing.
> I would like to compile UDPCast for OSX. I have a Powerbook with 10.4
> and the 2.1 Developer tools installed. I have tried to compile but was
> unsucessful. I have very limited coding skills so here is the
> information I need:
> 1. What do I need to do to get UDPCast to compile on OSX. If a total
> rewrite is needed, I will to lobby for a new(er) x86 box.
> 2. If anyone has done this I would like to read your experience.
> Thank you in advance for your help.
> Jeff Michels
> School District of Beloit
> Technology Support Specialist
> Udpcast mailing list
I use udpcast with several computers. After duplicating one hard disk to the
others, i would like that the computers that received the data reboot
automatically. But i don't know how to do this because udpcast don't allow
us to do that with it's options.
I'm waiting for your advice
MSN Messenger : personnalisez votre messagerie instantanée !
I tried for three times to copy a 8GB Partition over a 100 MBit network
using the prebuild cd images.
The transfer always stopped after exactly 3,238,596,608 bytes and the
following error message was shown:
What's going on here?
Thanks in advance,
EDV-Serviceteam Werthmann & Hierweck GbR
Dear UDPCAST users,
We are using Udpcast for our deployment installation up to now.
We have bought some DELL GX620 which contains a motherboard named FOXCONN LS
36 and only one sata drive.
We tried to make an image of this computer with Udpcast but the SATA drivers
needed for it are not available.
We don't have any other PC with sata controller.
Do you know this problem ?
Can you help us ?
Thanks a lot for all suggestions...
European School Luxembourg
23, Boulevard Konrad Adenauer
Can someone give me a simple working example of what's required on 2 linux
boxes and the network switch in order to send files. 1 box is the sender
and the other the receiver. I've never done anything with multicast
I'm trying this in a sandbox. I've got a Symbol ES 3000 PWR switch and
have IGMP snooping turned on. Both linux boxen connected to the switch.
I've been reading the help on the website but still cannot seem to send a
THe basic operation does not work :
./udp-sender --file udp-sender
Using mcast address 188.8.131.52
UDP sender for udp-sender at 184.108.40.206 on eth0
Broadcasting control to 255.152.135.47
[waits here til I hit enter, then]
Starting transfer: 00000019
But on the other end udp-reciever is still just waiting :
udp-receiver --file udp-sender
UDP receiver for udp-sender at 220.127.116.11 on eth1
Nothing. When hit enter, still nothing. When I ctrl-C the udp-sender
file is there but size zero. Oh, I'm just trying to get it to send
itself as an example
I also try lots of the different tuning options including --nokbd,
--broadcast and more, and still cannot get anything to transfer.
Any idea what I'm doing wrong?
The Beer Site