Hi Alain,
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,
Sai
---------------------------------
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.
--Donald Teed
Hi all,
I don't know if this should be applied to the source tree, but perhaps
some people will find this patch useful (I know we do).
We wanted some additional logging from udpcast to debug our casting
sessions, because it seems that the only thing logged to its logfile is
messages like this:
"Doubling slice size to 1024"
We also prefer syslog in stead of the separate file for logging
So I wrote this little patch.
It logs more information (very usefull for udpcast's running in the
background on a image server) and it logs it to syslog.
Information being logged:
* New connections
* Why a cast starts (is min clients reached or max wait passed, etc)
* Transfer start (+ what file,pipe,port,if,participants)
* Transfer complete
* Disconnects
See attached .patch
Kind regards,
--
Ramon Bastiaans
SARA - Academic Computing Services
Kruislaan 415
1098 SJ Amsterdam
Hi!
I'am using udpcast to transfert disk Images from a server to several clients.
The server box has one Network card and several virtual interfaces (eth0, eth0:0, eth0:1...).
When I try to send a file to one client through one of the virtual interface(eth0:x) everything goes well.
But when the client number increases (more than one) I get an error saying:
Rogue packet received <eth0 IP address>:9001 expecting <eth0:x IP address>:9001
The command line used on the server is :
udp-sender --file <filename> --interface eth0:x
On the client:
udp-receiver --file <filename>
It seems that only the eth0 interface can be used bay udpcast. It works perfectly with this one.
How can I get udpcast to work with my virtual interfaces
Sorry for my bad English!
Thank you for your help.
regards
Alex
hello group
i work for a school system and have been using UDPCast for a couple of years
now with great results. but we just got in the new dell gx280 pcs. they have
sata hard drivers and a broadcom gigabit ethernet card. i can not get the boot
disk nor the cd to use either device. is there anyone who has add these
devices to the /dev/ on the floppy or cd image?
(John Allison )
First let me thank you for udpcast, it has been a valuable tool for my
school district. And now to what I'm here for, we have gotten a new batch
of computers from Gateway with Marvell nic cards not supported with the
current version of udpcast. I have attempted to build a custom iso with
these new drivers following the instructions on the website. I used the
2.4.26 kernel sources and the rpm's from the site. I can't get the
computers to boot to determine if the new drivers work. I'm sure I've just
overlooked some small detail but I haven't been able to determine what.
I downloaded the linux driver from the Marvell site; installed in 2.4.26
src tree and built kernel according to instructions on the site.
I created the iso with the following command:
./makeImage -k
/usr/local/lx/2.4.26-udpcast/linux-2.4.26/arch/i386/boot/bzImage -c
udpcast1.iso --fullbox
the resulting iso is then burned to cd and when booted gives the following
error:
Please append a correct "root=" boot option.
kernel panic not able to mount root
Thanks,
Michael
--
Michael Williams Haywood County Schools
Technology Director Instructional Technology
http://www.haywood.k12.nc.us (828) 627-8314
Hello Michael,
I also work for a school district and have found udp-cast to be a great
tool.
I believe the problem you are having is similar to a problem I faced
recently. Our district uses PXE boot servers but I got the same error you
did. Here's what you can try:
Open ISOLINUX.CFG on the CD and see if it looks like this:
default linux
label linux
kernel LINUX
append root=/dev/ram0 initrd=INITRD
Your default, label, and kernel lines may be different but make sure the
root=/dev/ram0 option is there. I have never made custom UDP-Cast CDs. I
do not know how you would make these changes when making the image.
Hopefully someone else will be able to step in and help.
Jeff Michels
The School District of Beloit
Technology Services
-----Original Message-----
From: udpcast-bounces(a)udpcast.linux.lu
[mailto:udpcast-bounces@udpcast.linux.lu] On Behalf Of
udpcast-request(a)udpcast.linux.lu
Sent: Saturday, January 29, 2005 5:00 AM
To: udpcast(a)udpcast.linux.lu
Subject: Udpcast Digest, Vol 19, Issue 1
Send Udpcast mailing list submissions to
udpcast(a)udpcast.linux.lu
To subscribe or unsubscribe via the World Wide Web, visit
http://udpcast.linux.lu/mailman/listinfo/udpcast
or, via email, send a message with subject or body 'help' to
udpcast-request(a)udpcast.linux.lu
You can reach the person managing the list at
udpcast-owner(a)udpcast.linux.lu
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Udpcast digest..."
Today's Topics:
1. Custom iso (Michael Williams)
----------------------------------------------------------------------
Message: 1
Date: Fri, 28 Jan 2005 10:54:58 -0500 (EST)
From: "Michael Williams" <mwilliams(a)haywood.k12.nc.us>
Subject: [Udpcast] Custom iso
To: udpcast(a)udpcast.linux.lu
Message-ID: <36958.68.115.172.62.1106927698.squirrel(a)68.115.172.62>
Content-Type: text/plain;charset=iso-8859-1
First let me thank you for udpcast, it has been a valuable tool for my
school district. And now to what I'm here for, we have gotten a new batch
of computers from Gateway with Marvell nic cards not supported with the
current version of udpcast. I have attempted to build a custom iso with
these new drivers following the instructions on the website. I used the
2.4.26 kernel sources and the rpm's from the site. I can't get the
computers to boot to determine if the new drivers work. I'm sure I've just
overlooked some small detail but I haven't been able to determine what.
I downloaded the linux driver from the Marvell site; installed in 2.4.26
src tree and built kernel according to instructions on the site.
I created the iso with the following command:
./makeImage -k
/usr/local/lx/2.4.26-udpcast/linux-2.4.26/arch/i386/boot/bzImage -c
udpcast1.iso --fullbox
the resulting iso is then burned to cd and when booted gives the following
error:
Please append a correct "root=" boot option.
kernel panic not able to mount root
Thanks,
Michael
--
Michael Williams Haywood County Schools
Technology Director Instructional Technology
http://www.haywood.k12.nc.us (828) 627-8314
------------------------------
_______________________________________________
Udpcast mailing list
Udpcast(a)udpcast.linux.lu
http://udpcast.linux.lu/mailman/listinfo/udpcast
End of Udpcast Digest, Vol 19, Issue 1
**************************************
