Udpcast April 2005

udpcast@udpcast.linux.lu

3 participants
4 discussions

UDPCast source code issues...
by Saikrishna Dasari 25 Apr '06

25 Apr '06

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.

3 2

Buggy tg3 ethernet
by Donald Teed 04 Apr '06

04 Apr '06

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

2 1

Fw: Re: [Udpcast] Udpcast and Vlans
by Matteo Balduzzi 29 Apr '05

29 Apr '05

Sorry, i replied directly to Alain... reposting to the list: Begin forwarded message: Date: Fri, 29 Apr 2005 14:49:36 +0200 From: Matteo Balduzzi <matteo.balduzzi(a)polimi.it> To: Alain Knaff <alain(a)knaff.lu> Subject: Re: [Udpcast] Udpcast and Vlans On Fri, 29 Apr 2005 13:41:10 +0200 Alain Knaff <alain(a)knaff.lu> wrote: > On Friday 29 April 2005 10:15, Matteo Balduzzi wrote: > > Hi everybody, i'm using udpcast successfully since last year to > > deploy windows partitions in our university. > > The classrooms i manage are in different vlans, so now i store the > > partition images on many server inside every single vlan. > > > > What i'd like to do now is to have a single server with vlan support > > on its nic to do all the job. Well this seems not to work :-( > > I mean: i can start the udpcast session, i see the clients > > connetting, > > i start sending data (which arrives to the clients) but it > > seems that the replies get lost somewhere... i get for every single > > client a "Timeout notAnswered ... notReady". > > > > The net guys here say that the net is correctly configured... > > Finally: i'm doing something wrong? Does udpcast work on vlans (oh, > > i'm using version 2005-02-26)? Experiences? > > > > Ciao, Matteo > > Could you run a "tcpdump -ni <vlanIf> port 9000 or port 9001" on the > vlan interface on the sender, and tell me whether you see any reply > received from the clients? > > Regards, > > Alain > Attached is an extract of a "tcpdump -ni eth0.735 port 9000", where 10.160.66.248 is the sender and 10.160.66.45 10.160.66.95 are the receivers. It seems good to me... or not? Matteo -- Matteo Balduzzi Area Sistemi Informatici POLITECNICO DI MILANO Via La Masa, 34 - 20156 Milano Tel: 02-2399-8091 Fax: 02-2399-8088

1 0

Udpcast and Vlans
by Matteo Balduzzi 29 Apr '05

29 Apr '05

Hi everybody, i'm using udpcast successfully since last year to deploy windows partitions in our university. The classrooms i manage are in different vlans, so now i store the partition images on many server inside every single vlan. What i'd like to do now is to have a single server with vlan support on its nic to do all the job. Well this seems not to work :-( I mean: i can start the udpcast session, i see the clients connetting, i start sending data (which arrives to the clients) but it seems that the replies get lost somewhere... i get for every single client a "Timeout notAnswered ... notReady". The net guys here say that the net is correctly configured... Finally: i'm doing something wrong? Does udpcast work on vlans (oh, i'm using version 2005-02-26)? Experiences? Ciao, Matteo -- Matteo Balduzzi Area Sistemi Informatici POLITECNICO DI MILANO Via La Masa, 34 - 20156 Milano

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Udpcast April 2005