From alain at knaff.lu Thu Sep 11 20:03:24 2008 From: alain at knaff.lu (Alain Knaff) Date: Thu, 11 Sep 2008 20:03:24 +0200 Subject: [Udpcast] incorrect documentation of --nosync flag? In-Reply-To: References: Message-ID: <48C95D6C.7050703@knaff.lu> George Coulouris, MSD wrote: Hello George, how's life? Sorry for the slow response, I've been somewhat busy lately. > http://udpcast.linux.lu/cmd.html states that --nosync is the default > when writing to a file or a pipe, but this does not appear to be the > case; I verified with strace that udp-receiver open()s its output > file with O_SYNC unless you specify --nosync. I just checked, the current version (20071228) on http://udpcast.linux.lu does not exhibit the problem. However, I noticed that for some weird reason (K)ubuntu, even 8.04 includes a very old version 20040531-1 which does indeed have the problem that you describe. Regards, Alain From stephane.boireau at free.fr Wed Sep 17 15:50:23 2008 From: stephane.boireau at free.fr (Stephane Boireau) Date: Wed, 17 Sep 2008 15:50:23 +0200 Subject: [Udpcast] Giving options through boot cmdline and udpcparam Message-ID: <200809171550.24033.stephane.boireau@free.fr> Hi, ====================== I already sent this message, but I get troubles using the other email... ====================== I don't succeed in giving two options through apend boot cmdline. Here is my cmdline: label u1auto kernel vmlu26 append initrd=udprd root=01:00 persoparams=oui lang=FR kbmap=FR dhcp=yes compr=lzop port=9002 umode=snd disk=/dev/hda1 auto_reboot=always enableDiskmodule=yes diskmodule=AUTO netmodule=AUTO udpcparam=--max-wait=300--min-receivers=2 A script is launched using predialog. It writes the /udpcfg.txt file. With the above cmdline, I get: udpsender -p lzop --file /dev/hda1 -P 9002 -i eth0 --max-wait=300--min-receiver=2 instead of udpsender -p lzop --file /dev/hda1 -P 9002 -i eth0 --max-wait=300 --min-receiver=2 And it doesn't work. =========================== I've tried: label u1auto kernel vmlu26 append initrd=udprd root=01:00 persoparams=oui lang=FR kbmap=FR dhcp=yes compr=lzop port=9002 umode=snd disk=/dev/hda1 auto_reboot=always enableDiskmodule=yes diskmodule=AUTO netmodule=AUTO udpcparam=--max-wait=300|--min-receivers=2 And my predialog script does: udpcparam=`echo "$udpcparam" | sed -e "s/|/ /g"` echo "udpcparam=$udpcparam" >> /udpcfg.txt But it doesn't work. /udpcfg.txt contains ... umode=snd udpcparam=--max-wait=300 --min-receivers=2 And I get Udp-sender 2007-12-28 --min-receivers=2: not found Using mcast address 232.168.52.210 Compressed UDP sender for /dev/hda1 at 192.168.52.210 on eth0 Broadcasting control to 192.168.52.255 and it fails. How could I get both options working? I did those tests using 2.6.23 kernel and udpcast-mkimage-20080107-1.i586, udpcast-20070602-1.i586 I'll try again using udpcast-20071228-1.i586 udpcast-mkimage-20080911-1.i586 kernel-udpcast-2.6.26.3-1.i586 Regards. -- Stephane From frod at aitelecom.net Thu Sep 18 18:39:32 2008 From: frod at aitelecom.net (Fernando Rodriguez) Date: Thu, 18 Sep 2008 11:39:32 -0500 Subject: [Udpcast] Hello all Message-ID: <68A08BE3-29AD-414D-8DAF-6186D3CD6788@aitelecom.net> This is my first post on the list Fernando Rodriguez frod at aitelecom.net From frod at aitelecom.net Thu Sep 18 19:39:55 2008 From: frod at aitelecom.net (Fernando Rodriguez) Date: Thu, 18 Sep 2008 12:39:55 -0500 Subject: [Udpcast] Scheduling interface Message-ID: Hello, Is there any gui or scheduling interface for udpcast that can be used via web Thanks Fernando Rodriguez frod at aitelecom.net From frod at aitelecom.net Thu Sep 18 20:41:59 2008 From: frod at aitelecom.net (Fernando Rodriguez) Date: Thu, 18 Sep 2008 13:41:59 -0500 Subject: [Udpcast] Content system Message-ID: <20E345AA-62FF-495D-858A-56C1FBFBEBAF@aitelecom.net> Hello, i want to know if udpcast will be able to transmit different files to different multicast addresses at the same time. Also if it is plausible to make a web interface to handle scheduling of the files that are going to be sent over udpcast, so remote recievers are able to get the files they where requested, this will be like on demand content delivery. to do this all clocks from the remote sides have to be in sync with the master content node, and the remote content node or client should be able to parse a file to see the content that udpcast will transmit. Also i need to know what is the best fec algorithm for one way satellite comunicacion. Fernando Rodriguez frod at aitelecom.net From alain at knaff.lu Thu Sep 18 22:16:55 2008 From: alain at knaff.lu (Alain Knaff) Date: Thu, 18 Sep 2008 22:16:55 +0200 Subject: [Udpcast] Content system In-Reply-To: <20E345AA-62FF-495D-858A-56C1FBFBEBAF@aitelecom.net> References: <20E345AA-62FF-495D-858A-56C1FBFBEBAF@aitelecom.net> Message-ID: <48D2B737.9000907@knaff.lu> Fernando Rodriguez wrote: > Hello, i want to know if udpcast will be able to transmit different > files to different multicast addresses at the same time. Yes, you can start several instances of udpcast simultaneously. You only need to make sure that each instance uses a different port base (-P parameter). > Also if it is plausible to make a web interface to handle scheduling > of the files that are going to be sent over udpcast, so remote > recievers are able to get the files they where requested, this will be > like on demand content delivery. You could make a cgi script that would start udpcast in the background as requested. > to do this all clocks from the remote sides have to be in sync with > the master content node, and the remote content node or client should > be able to parse a file to see the content that udpcast will transmit. You could have one udpcast responsible for transmitting the announcement, which would be saved to a file on the receiver, to be parsed by the GUI frontend. Then, the actual content would be transmitted by separate instances, either on-demand, or continuously as a carousel. > Also i need to know what is the best fec algorithm for one way > satellite comunicacion. It all depends on the quality of the link, and the power of your receivers. You want to play with the 3 parameters stripes x redundancy / stripesize . A higher ratio redundancy / stripesize can protect against higher loss rates. However, it also makes the transmission larger. Larger number of stripes protects against clustered losses (so, if your link is likely to lose many packets in a row, use a high number of stripes). However, a higher number of stripes leads to higher memory requirements. A bigger stripesize also helps against clustered losses, at the cost of memory and computation time. You need to play a little bit with the parameters to find the best fit for your transmission link and receiver hardware. The way it works is that each stripe is an independant FEC group. Each stripe is made up of stripesize (n) data packets plus a number of redundancy packets (k). As long as at least n packets are received (i.e. less than k packets lost), no matter whether they are original data packets, or redundancy packets, everything in the FEC group (stripe) can be reconstructed. During transmission, s stripes (FEC groups) are active simultaneously, a packet of each being transmitted in a round-robin fashion (i.e. first a packet of stripe 1, then one stripe 2, etc. until the last stripe is reached, after which the second packet of stripe 1 will be transmitted). This interleaving is meant to protect against clustered losses, so that if for instance 10 packets in a row are lost, they won't all fall within the same FEC group. > > Fernando Rodriguez > frod at aitelecom.net Alain From frod at aitelecom.net Thu Sep 18 23:06:09 2008 From: frod at aitelecom.net (Fernando Rodriguez) Date: Thu, 18 Sep 2008 16:06:09 -0500 Subject: [Udpcast] Content system In-Reply-To: <48D2B737.9000907@knaff.lu> References: <20E345AA-62FF-495D-858A-56C1FBFBEBAF@aitelecom.net> <48D2B737.9000907@knaff.lu> Message-ID: <2B3B7A70-C309-4B5A-8FC7-5A77EEA92229@aitelecom.net> Alain, I also wanted to know because on your satellite example you set the interface to dvb0 i have some cards dvb cards and lnb. Im going to get a php programer to make the scheduling. Thanks On Sep 18, 2008, at 3:16 PM, Alain Knaff wrote: > Fernando Rodriguez wrote: >> Hello, i want to know if udpcast will be able to transmit different >> files to different multicast addresses at the same time. > > Yes, you can start several instances of udpcast simultaneously. You > only > need to make sure that each instance uses a different port base (-P > parameter). > >> Also if it is plausible to make a web interface to handle scheduling >> of the files that are going to be sent over udpcast, so remote >> recievers are able to get the files they where requested, this will >> be >> like on demand content delivery. > > You could make a cgi script that would start udpcast in the background > as requested. > >> to do this all clocks from the remote sides have to be in sync with >> the master content node, and the remote content node or client should >> be able to parse a file to see the content that udpcast will >> transmit. > > You could have one udpcast responsible for transmitting the > announcement, which would be saved to a file on the receiver, to be > parsed by the GUI frontend. Then, the actual content would be > transmitted by separate instances, either on-demand, or continuously > as > a carousel. > >> Also i need to know what is the best fec algorithm for one way >> satellite comunicacion. > > It all depends on the quality of the link, and the power of your > receivers. You want to play with the 3 parameters stripes x > redundancy > / stripesize . > > A higher ratio redundancy / stripesize can protect against higher loss > rates. However, it also makes the transmission larger. > > Larger number of stripes protects against clustered losses (so, if > your > link is likely to lose many packets in a row, use a high number of > stripes). However, a higher number of stripes leads to higher memory > requirements. > > A bigger stripesize also helps against clustered losses, at the cost > of > memory and computation time. > > You need to play a little bit with the parameters to find the best fit > for your transmission link and receiver hardware. > > The way it works is that each stripe is an independant FEC group. Each > stripe is made up of stripesize (n) data packets plus a number of > redundancy packets (k). As long as at least n packets are received > (i.e. > less than k packets lost), no matter whether they are original data > packets, or redundancy packets, everything in the FEC group (stripe) > can > be reconstructed. > > During transmission, s stripes (FEC groups) are active > simultaneously, a > packet of each being transmitted in a round-robin fashion (i.e. > first a > packet of stripe 1, then one stripe 2, etc. until the last stripe is > reached, after which the second packet of stripe 1 will be > transmitted). > This interleaving is meant to protect against clustered losses, so > that > if for instance 10 packets in a row are lost, they won't all fall > within > the same FEC group. > >> >> Fernando Rodriguez >> frod at aitelecom.net > > Alain Fernando Rodriguez frod at aitelecom.net From skotay at byuh.edu Fri Sep 19 23:48:29 2008 From: skotay at byuh.edu (Scott Mikolyski) Date: Fri, 19 Sep 2008 11:48:29 -1000 Subject: [Udpcast] kernel-udpcast-2.6.26.3-1.i586 not detecting nic Message-ID: <48D41E2D.4040203@byuh.edu> Hi, I'm working with a pxe server to get workstations to boot from the network. I'm using the cast-o-matic boot image. Everything works up until I get and error message "ifconfig: SIOCSIFADDR: No such device" Dropping to a shell, I type ifconfig and get nothing. I think I should be getting some nic information. So it looks like to me that the network driver is not getting loaded. I've selected different modules in cast-o-matic. But I feel that it has something to do with this version of the kernel. Last month I had this setup working perfectly. Since then, I've lost my pxe server and need to recreate it. Is it possible that this recent change broke something? Please help. Thank you. From alain at knaff.lu Sat Sep 20 00:00:25 2008 From: alain at knaff.lu (Alain Knaff) Date: Sat, 20 Sep 2008 00:00:25 +0200 Subject: [Udpcast] kernel-udpcast-2.6.26.3-1.i586 not detecting nic In-Reply-To: <48D41E2D.4040203@byuh.edu> References: <48D41E2D.4040203@byuh.edu> Message-ID: <48D420F9.9040707@knaff.lu> Scott Mikolyski wrote: > Hi, > > I'm working with a pxe server to get workstations to boot from the > network. I'm using the cast-o-matic boot image. > > Everything works up until I get and error message "ifconfig: > SIOCSIFADDR: No such device" > > Dropping to a shell, I type ifconfig and get nothing. I think I should > be getting some nic information. > > So it looks like to me that the network driver is not getting loaded. > I've selected different modules in cast-o-matic. But I feel that it has > something to do with this version of the kernel. > > Last month I had this setup working perfectly. Since then, I've lost my > pxe server and need to recreate it. Is it possible that this recent > change broke something? > > Please help. Thank you. Could you tell me which NIC it is (name of module which worked in old kernel), so that I can investigate? Or, lacking that, the output of lspci Thx, Alain From scott at mikolyski.net Sat Sep 20 04:18:10 2008 From: scott at mikolyski.net (Scott Mikolyski) Date: Fri, 19 Sep 2008 16:18:10 -1000 Subject: [Udpcast] kernel-udpcast-2.6.26.3-1.i586 not detecting nic In-Reply-To: <48D42C78.3030706@mikolyski.net> References: <48D41E2D.4040203@byuh.edu> <48D420F9.9040707@knaff.lu> <48D42C78.3030706@mikolyski.net> Message-ID: <48D45D62.80407@mikolyski.net> I have some more information on the error. Instead of using a pre-configured cast-o-matic initrd, I walked through the boot process and at the step where the tg3 driver was loaded I received a kernel message, part of it looks like this. PCI: Setting latency timer of device ... BUG: Unable to handle kernel NULL pointer dereference at 0000001c IP: [] *pde: 0002 [#1] Modules linked in: tg3(+) ... I don't know if it will but I hope this helps. Scott Mikolyski wrote: > Alain Knaff wrote: >> Scott Mikolyski wrote: >>> Hi, >>> >>> I'm working with a pxe server to get workstations to boot from the >>> network. I'm using the cast-o-matic boot image. >>> >>> Everything works up until I get and error message "ifconfig: >>> SIOCSIFADDR: No such device" >>> >>> Dropping to a shell, I type ifconfig and get nothing. I think I >>> should be getting some nic information. >>> >>> So it looks like to me that the network driver is not getting loaded. >>> I've selected different modules in cast-o-matic. But I feel that it >>> has something to do with this version of the kernel. >>> >>> Last month I had this setup working perfectly. Since then, I've lost >>> my pxe server and need to recreate it. Is it possible that this >>> recent change broke something? >>> >>> Please help. Thank you. >> >> Could you tell me which NIC it is (name of module which worked in old >> kernel), so that I can investigate? Or, lacking that, the output of lspci > > It's a Broadcom NetXtreme BCM5751. > >> >> Thx, >> >> Alain >> >> _______________________________________________ >> Udpcast mailing list >> Udpcast at udpcast.linux.lu >> https://lll.lgl.lu/mailman/listinfo/udpcast > From alain at knaff.lu Sat Sep 20 08:50:09 2008 From: alain at knaff.lu (Alain Knaff) Date: Sat, 20 Sep 2008 08:50:09 +0200 Subject: [Udpcast] Giving options through boot cmdline and udpcparam In-Reply-To: <200809171550.24033.stephane.boireau@free.fr> References: <200809171550.24033.stephane.boireau@free.fr> Message-ID: <48D49D21.4000407@knaff.lu> Stephane Boireau wrote: > Hi, > > ====================== > I already sent this message, but I get troubles using the other email... > ====================== > > I don't succeed in giving two options through apend boot cmdline. > Here is my cmdline: > > label u1auto > kernel vmlu26 > append initrd=udprd root=01:00 persoparams=oui lang=FR kbmap=FR dhcp=yes > compr=lzop port=9002 umode=snd disk=/dev/hda1 auto_reboot=always > enableDiskmodule=yes diskmodule=AUTO netmodule=AUTO > udpcparam=--max-wait=300--min-receivers=2 > > A script is launched using predialog. > It writes the /udpcfg.txt file. > > With the above cmdline, I get: > > udpsender -p lzop --file /dev/hda1 -P 9002 -i > eth0 --max-wait=300--min-receiver=2 Yes, that's what you typed... see above. > > instead of > > udpsender -p lzop --file /dev/hda1 -P 9002 -i > eth0 --max-wait=300 --min-receiver=2 > > And it doesn't work. Makes sense. > =========================== > > I've tried: > > label u1auto > kernel vmlu26 > append initrd=udprd root=01:00 persoparams=oui lang=FR kbmap=FR dhcp=yes > compr=lzop port=9002 umode=snd disk=/dev/hda1 auto_reboot=always > enableDiskmodule=yes diskmodule=AUTO netmodule=AUTO > udpcparam=--max-wait=300|--min-receivers=2 ^ You need a space there. Try putting the parameter between quotes to avoid it being interpreted as two parameters: udpcparam="--max-wait=300 --min-receivers=2" > And my predialog script does: > > udpcparam=`echo "$udpcparam" | sed -e "s/|/ /g"` > echo "udpcparam=$udpcparam" >> /udpcfg.txt Why don't you put this directly into udpcfg.txt? > But it doesn't work. > /udpcfg.txt contains > ... > umode=snd > udpcparam=--max-wait=300 --min-receivers=2 correct (no need for quotes here, as the different parameters are line-separated) > And I get > > Udp-sender 2007-12-28 > --min-receivers=2: not found > Using mcast address 232.168.52.210 > Compressed UDP sender for /dev/hda1 at 192.168.52.210 on eth0 > Broadcasting control to 192.168.52.255 > > and it fails. Works for me (just tried it out by editing the SYSLINUX.CFG on a floppy image) > How could I get both options working? > > > I did those tests using 2.6.23 kernel and udpcast-mkimage-20080107-1.i586, > udpcast-20070602-1.i586 > I'll try again using > udpcast-20071228-1.i586 > udpcast-mkimage-20080911-1.i586 > kernel-udpcast-2.6.26.3-1.i586 > > > Regards. > -- > Stephane Regards, Alain From stephane.boireau at free.fr Sun Sep 21 19:35:20 2008 From: stephane.boireau at free.fr (Stephane Boireau) Date: Sun, 21 Sep 2008 19:35:20 +0200 Subject: [Udpcast] Giving options through boot cmdline and udpcparam In-Reply-To: <48D49D21.4000407@knaff.lu> References: <200809171550.24033.stephane.boireau@free.fr> <48D49D21.4000407@knaff.lu> Message-ID: <200809211935.21801.stephane.boireau@free.fr> Hi, Le samedi 20 septembre 2008 08:50, vous avez écrit : > Stephane Boireau wrote: > > ====================== > > I already sent this message, but I get troubles using the other email... > > ====================== > > > > I don't succeed in giving two options through apend boot cmdline. > > Here is my cmdline: > > > > label u1auto > > kernel vmlu26 > > append initrd=udprd root=01:00 persoparams=oui lang=FR kbmap=FR > > dhcp=yes compr=lzop port=9002 umode=snd disk=/dev/hda1 auto_reboot=always > > enableDiskmodule=yes diskmodule=AUTO netmodule=AUTO > > udpcparam=--max-wait=300--min-receivers=2 > > > > A script is launched using predialog. > > It writes the /udpcfg.txt file. > > > > With the above cmdline, I get: > > > > udpsender -p lzop --file /dev/hda1 -P 9002 -i > > eth0 --max-wait=300--min-receiver=2 > > Yes, that's what you typed... see above. I know. But udpcparam=--max-wait=300 --min-receiver=2 doesn't work in boot cmdline. > > instead of > > > > udpsender -p lzop --file /dev/hda1 -P 9002 -i > > eth0 --max-wait=300 --min-receiver=2 > > > > And it doesn't work. > > Makes sense. > > > =========================== > > > > I've tried: > > > > label u1auto > > kernel vmlu26 > > append initrd=udprd root=01:00 persoparams=oui lang=FR kbmap=FR > > dhcp=yes compr=lzop port=9002 umode=snd disk=/dev/hda1 auto_reboot=always > > enableDiskmodule=yes diskmodule=AUTO netmodule=AUTO > > udpcparam=--max-wait=300|--min-receivers=2 > > ^ > You need a space there. Try putting the parameter between quotes to > avoid it being interpreted as two parameters: > udpcparam="--max-wait=300 --min-receivers=2" I'll try... > > And my predialog script does: > > > > udpcparam=`echo "$udpcparam" | sed -e "s/|/ /g"` > > echo "udpcparam=$udpcparam" >> /udpcfg.txt > > Why don't you put this directly into udpcfg.txt? I can't. The boot cmdline is put in /tftpboot/pxelinux.cfg/01-ADDRESS_MAC PHP web interface is used to build 01-ADDRESS_MAC the way I wan't to clone this or this. It's a part of sambaedu3 project. I use udpcast in se3-clonage package. > > But it doesn't work. > > /udpcfg.txt contains > > ... > > umode=snd > > udpcparam=--max-wait=300 --min-receivers=2 > > correct (no need for quotes here, as the different parameters are > line-separated) > > > And I get > > > > Udp-sender 2007-12-28 > > --min-receivers=2: not found > > Using mcast address 232.168.52.210 > > Compressed UDP sender for /dev/hda1 at 192.168.52.210 on eth0 > > Broadcasting control to 192.168.52.255 > > > > and it fails. > > Works for me (just tried it out by editing the SYSLINUX.CFG on a floppy > image) Argh? You're right. It's OK if I put: udpcparam="--max-wait=300 --min-receivers=2" in 01-ADDRESS_MAC Regards. -- Stephane Boireau. PS: Here is my udpcfg_txt.sh scripts launched in predialog script: ======================================== #!/bin/sh # Script de recuperation de parametres de l'isolinux.cfg # pour renseigner le fichier udpcfg.txt avant lancement de udpc_dialog # L'objectif est d'eviter le stockage de 3 initrd pour le mode standard, # le mode preselectionne en emission # et le mode preselectionne en reception. # Auteur: Stephane Boireau # Derniere modification: 15/09/2008 #Couleurs COLTITRE='\033[1;35m' # Rose COLPARTIE='\033[1;34m' # Bleu COLTXT='\033[0;37m' # Gris COLCHOIX='\033[1;33m' # Jaune COLDEFAUT='\033[0;33m' # Brun-jaune COLSAISIE='\033[1;32m' # Vert COLCMD='\033[1;37m' # Blanc COLERREUR='\033[1;31m' # Rouge COLINFO='\033[0;36m' # Cyan echo -e "$COLTITRE" echo "********************" echo "* Preconfiguration *" echo "********************" echo -e "$COLTXT" echo "Recuperation des parametres d'isolinux..." echo -e "$COLCMD" # On devrait recuperer des choses comme: # initrd=linux/udpcast/udprd root=01:00 # Et eventuellement en plus les autres parametres ajoutes à 'append'. cat /proc/cmdline sleep 1 sh /proc/cmdline if [ "$persoparams" = "oui" ]; then echo -e "$COLTXT" echo "Regeneration de l'udpcfg.txt" #echo -e "$COLCMD" echo "auto=yes" > /udpcfg.txt if [ "$lang" = "" ]; then echo "lang=FR" >> /udpcfg.txt else echo "lang=$lang" >> /udpcfg.txt fi if [ "$kbmap" = "" ]; then echo "kbmap=FR" >> /udpcfg.txt else echo "kbmap=$kbmap" >> /udpcfg.txt fi if [ "$netmodule" = "" ]; then echo "Pas de module reseau predefini." else echo "netmodule=$netmodule" >> /udpcfg.txt echo "netmodparm=$netmodparm" >> /udpcfg.txt fi if [ "$dhcp" = "" ]; then #echo -e "$COLTXT" echo "Pas de preselection du mode DHCP." else echo "dhcp=$dhcp" >> /udpcfg.txt fi if [ "$enableDiskmodule" = "yes" ]; then echo "enableDiskmodule=yes" >> /udpcfg.txt echo "diskmodule=$diskmodule" >> /udpcfg.txt echo "diskmodparm=$diskmodparm" >> /udpcfg.txt fi if [ "$port" = "" ]; then #echo -e "$COLTXT" echo "Pas de port defini." else echo "port=$port" >> /udpcfg.txt fi if [ "$compr" = "" ]; then #echo -e "$COLTXT" echo "Pas de niveau de compression defini." else echo "compr=$compr" >> /udpcfg.txt fi if [ "$disk" = "" ]; then #echo -e "$COLTXT" echo "Pas de disque dur preselectionne." else echo "disk=$disk" >> /udpcfg.txt fi echo "mode=0" >> /udpcfg.txt echo "umode=$umode" >> /udpcfg.txt #echo "udpcparam=$udpcparam" >> /udpcfg.txt #echo "udpcparam=`echo $udpcparam | tr '?' ' ' | tr '.' '-'`" >> /udpcfg.txt #echo "udpcparam=$udpcparam" >> /udpcfg.txt udpcparam=`echo "$udpcparam" | sed -e "s/|/ /g"` echo "udpcparam=$udpcparam" >> /udpcfg.txt #echo "udpcparam=`echo $udpcparam | tr '_' ' '`" >> /udpcfg.txt fi if [ "$kusb" = "1" -o "$kusb" = "o" -o "$kusb" = "y" ]; then echo -e "$COLTXT" echo "Chargement des pilotes pour le support d'un clavier USB." echo -e "$COLCMD" modprobe uhci-hcd modprobe ohci-hcd modprobe usbkbd fi #echo "$COLTXT" #echo "Tentative d'ejection du CD..." #echo "$COLCMD" #modprobe ide-cd #/bin/udpc_dialog init #( cd /proc/ide ; for i in hd? ; do if fgrep -q cdrom $i/media ; then eject /dev/$i ; echo ejecting /dev/$i ; fi ; done) echo -e "$COLTITRE" echo "Fin" #read PAUSE if [ -e "/bin/date" ]; then datedebut=`/bin/date "+%Y-%m-%d %H:%M:%S"` else datedebut=`date "+%Y-%m-%d %H:%M:%S"` fi echo "Debut: $datedebut" > /tmp/dates.txt sleep 1 # u1 netmodule=AUTO enableDiskmodule=no disk=/dev/hda udpcparam=..autostart?12 #echo "Appuyez sur une touche pour poursuivre" #read PAUSE ======================================== My predialog script: ======================================== #!/bin/sh # Script Udpcast (genere par Cast-o-matic et modifie par Stephane Boireau) # Dernière modification: 20080111 # Chargement du module: modprobe ide-cd # Preparation du dialogue de fin de boot: /bin/udpc_dialog init # # Tentative d ejection du CD: # modprobe ide-cd # #( cd /proc/ide ; for i in hd? ; do if fgrep -q cdrom $i/media ; then eject /dev/$i ; echo ejecting /dev/$i ; fi ; done) # # Le support /proc/ide n'est plus dans le noyau # #periph_cd=`fgrep -l cdrom /sys/block/*/device/media | sed 's/\/sys\/block\/\(.*\)\/device\/media/\1/'` # periph_cd=`fgrep -l cdrom /sys/block/*/device/media | cut -d"/" -f4` # if [ ! -z "$periph_cd" ]; then # echo "" # echo "Ejection du cdrom: /dev/$periph_cd" # ls -l /dev/$periph_cd # eject /dev/$periph_cd # if [ "$?" != 0 ]; then # ls /dev/ # read PAUSE # fi # fi # Generation du fichier de preferences /udpcfg.txt sh /bin/udpcfg_txt.sh # Apres ce predialog, l'interface du menu udpcast est affichee... ======================================== My prescript: ======================================== #!/bin/sh # Tentative d ejection du CD: #/bin/eject_cd.sh modprobe ide-cd #( cd /proc/ide ; for i in hd? ; do if fgrep -q cdrom $i/media ; then eject /dev/$i ; echo ejecting /dev/$i ; fi ; done) # Le support /proc/ide n'est plus dans le noyau #periph_cd=`fgrep -l cdrom /sys/block/*/device/media | sed 's/\/sys\/block\/\(.*\)\/device\/media/\1/'` periph_cd=`fgrep -l cdrom /sys/block/*/device/media | cut -d"/" -f4` if [ ! -z "$periph_cd" ]; then echo "" echo "Ejection du cdrom: /dev/$periph_cd" #ls -l /dev/$periph_cd eject /dev/$periph_cd #if [ "$?" != 0 ]; then # ls /dev/ # read PAUSE #fi fi # Prevenir l extinction de l ecran #/bin/no_blank_screen.sh echo -e '\033[9;0]' ======================================== And postscript: ======================================== #!/bin/sh # Script d affichage des dates de debut et de fin # Auteur: Stephane Boireau # Derniere modification: 19/01/2008 #echo "Variables: $*" # Resultat du clonage: resultat=$1 #Couleurs COLTITRE='\033[1;35m' # Rose COLPARTIE='\033[1;34m' # Bleu COLTXT='\033[0;37m' # Gris COLCHOIX='\033[1;33m' # Jaune COLDEFAUT='\033[0;33m' # Brun-jaune COLSAISIE='\033[1;32m' # Vert COLCMD='\033[1;37m' # Blanc COLERREUR='\033[1;31m' # Rouge COLINFO='\033[0;36m' # Cyan echo -e "$COLTITRE" echo "***********************" echo "* Resultat du clonage *" echo "***********************" succes="" if [ -z "$resultat" ]; then echo -e "$COLTXT" echo "Le clonage n a pas retourne de resultat (succes ou echec)." else if [ "$resultat" = "0" ]; then echo -e "$COLTXT" echo "SUCCES." succes="y" else echo -e "$COLERREUR" echo "ECHEC." succes="n" fi fi echo -e "$COLTITRE" echo "*****************" echo "* Duree ecoulee *" echo "*****************" echo -e "$COLTXT" echo "Voici les dates relevees..." echo -e "$COLCMD" if [ -e "/bin/date" ]; then datefin=`/bin/date "+%Y-%m-%d %H:%M:%S"` else datefin=`date "+%Y-%m-%d %H:%M:%S"` fi echo "Fin: $datefin" >> /tmp/dates.txt cat /tmp/dates.txt echo -e "$COLINFO" echo "Ces dates peuvent etre incorrectes si les machines n etaient pas a l heure." echo "Mais la difference entre les heures de debut et de fin donne le temps de" echo "clonage." #test=$(grep reboot /proc/cmdline) #if [ ! -z "$test" ]; then # IFS=" " # while read A # do # B=$(echo "$A" | grep reboot | cut -d"=" -f2) # if [ ! -z "$B" ]; then # sleep $B # reboot # fi # done < /proc/cmdline if grep "auto_reboot=always" /proc/cmdline > /dev/null; then sleep 5 reboot else if grep "auto_reboot=success" /proc/cmdline > /dev/null; then if [ "$succes" = "y" ]; then sleep 5 reboot else echo -e "$COLERREUR" echo "Un probleme s est produit lors du clonage." read PAUSE fi else echo -e "$COLTXT" echo "Vous pouvez rebooter..." read PAUSE fi fi ======================================== From adn.terrastacruz at terra.com.br Mon Sep 22 12:06:39 2008 From: adn.terrastacruz at terra.com.br (Donizeti - CTTSC) Date: Mon, 22 Sep 2008 07:06:39 -0300 Subject: [Udpcast] help Message-ID: Good morning, I need to go SATA HD clone how to proceed? hug everyone. Donizeti. -------------- next part -------------- An HTML attachment was scrubbed... URL: From alain at knaff.lu Mon Sep 22 13:41:05 2008 From: alain at knaff.lu (Alain Knaff) Date: Mon, 22 Sep 2008 13:41:05 +0200 Subject: [Udpcast] help In-Reply-To: References: Message-ID: <48D78451.4040003@knaff.lu> Donizeti - CTTSC wrote: > Good morning, I need to go SATA HD clone how to proceed? > hug everyone. > Donizeti. > > > ------------------------------------------------------------------------ > > _______________________________________________ > Udpcast mailing list > Udpcast at udpcast.linux.lu > https://lll.lgl.lu/mailman/listinfo/udpcast Well, you just boot up the udpcast CD or floppy, as you would for a PATA disk, but near the end, you chose to load a "hard disk driver" module. By default, it only proposes you modules corresponding to hardware (SATA controllers) present in your machine, but for the case where it is wrong, you can chose "other", and then you get the complete list. If the correct module is chosen, you should see your SATA disks as /dev/sda, /dev/sdb, etc. and its partitions as /dev/sda1 , /dev/sda2 or similar. Regards, Alain From archon at pjwstk.edu.pl Tue Sep 23 22:05:25 2008 From: archon at pjwstk.edu.pl (=?ISO-8859-2?Q?Pawe=B3_Ufnalewski_//_BSS?=) Date: Tue, 23 Sep 2008 22:05:25 +0200 Subject: [Udpcast] multi computer cast problem Message-ID: <48D94C05.6000307@pjwstk.edu.pl> Hello, I've got problem with multicasting to many computers at once. I've got server with newest udp-sender (20071228) which is sending files from ext3 partition (with command ./udp-sender --pipe 'tar -B -S -cpf - -C /usr/share/systemimager/boot/i386/pjwstklenny .' --portbase 9006 --min-clients 2 --min-wait 15 --interface eth1 --max-bitrate 70M --mcast-all-addr 234.1.1.162 --ttl 10 and I'm trying to receive it with command: ./udp-receiver --portbase 9006 --nosync --ttl 10 --mcast-rdv-address 234.1.1.162 --pipe "tar -f - -x -vv -C /disk" on client computer. Problem is that, when I'm doing it one-by-one (I mean server-1 client) I get full speed - ~70MB/s, but when I'm trying to to this with >= 2 computers transfer drops to >0,5Mb/s. Why? I tried diffrent and the same subnet, I'm using 3com & cisco 3-layer switches (I also tried putting server and clients on the same switch - the same effect). Please help, cause I've got >200 computers to clone ;) Best regards Paul Ufnalewski // BSS Polish Japanese Institute of Information Technology From alain at knaff.lu Tue Sep 23 22:32:22 2008 From: alain at knaff.lu (Alain Knaff) Date: Tue, 23 Sep 2008 22:32:22 +0200 Subject: [Udpcast] Request - include netcat In-Reply-To: <20080312190528.tlsucpsnuoocksgk@polibyte.com> References: <20080312190528.tlsucpsnuoocksgk@polibyte.com> Message-ID: <48D95256.4050302@knaff.lu> brian at polibyte.com wrote: > Hi, > > It would be nice if netcat were included in the CD and PXE images. > Busybox has a version, so adding it shouldn't take much. > > All the best, > Brian This is now done in today's version (20080914) Regards, Alain From alain at knaff.lu Tue Sep 23 22:37:53 2008 From: alain at knaff.lu (Alain Knaff) Date: Tue, 23 Sep 2008 22:37:53 +0200 Subject: [Udpcast] Sender's timeout for waiting for receivers In-Reply-To: References: Message-ID: <48D953A1.6090203@knaff.lu> Dmitry Popov wrote: > Hi everyone, > > Please confirm my guess (or explain how to implement it). > > I need a "sender-timeout", a period of time while sender waits for receivers > to connect, and if none are connected - sender exits without transmission. > The only way to implement this is shell/perl/... script, which starts > udp-sender with --min-receivers option and monitors its stderr. If no > "Starting transfer" is found during specified period of time - it kills > udp-sender process. > > Regards, > Dmitry Starting with today's version (20080914), you can combine the --rexmit-hello-interval and --autostart flags to achieve the desired result. --rexmit-hello-interval instruct udp-sender to retransmit its announcement (hello) packet once every so many milliseconds (rather than only once at the beginning). --autostart instructs udp-sender to automatically start the transmission after this many hello packets. Starting from today's version, it will exit if no receivers have registered during that time (except in async mode) So, for instance the following command would wait for 3 seconds, and then start transmitting if there are receivers, and exit if there are none: udp-sender --rexmit-hello-interval 300 --autostart 10 Regards, Alain From dmaclachlan at hatsize.com Tue Sep 23 22:45:25 2008 From: dmaclachlan at hatsize.com (Darin MacLachlan) Date: Tue, 23 Sep 2008 14:45:25 -0600 Subject: [Udpcast] Network card Error Message-ID: <78C50AF9-6F40-419C-B720-5EE561223344@hatsize.com> 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: Udp-sender 2007-03-23 No suitable network interface found The following interfaces are available: lo 127.0.0.1 eth2 10.46.0.251 eth2:1 10.46.0.1 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. From alain at knaff.lu Tue Sep 23 22:47:26 2008 From: alain at knaff.lu (Alain Knaff) Date: Tue, 23 Sep 2008 22:47:26 +0200 Subject: [Udpcast] throttle output of udp-cast In-Reply-To: <4755E754.6090701@ket.org> References: <4755E754.6090701@ket.org> Message-ID: <48D955DE.2000207@knaff.lu> Sorry for the slow answers, I've been busy with other projects (LLL) for a while. Let's hope it's not too late yet. David Crider wrote: > Is it possible to do dynamically throttled UPDcast transmission? We need > to throttle the data flow to a Logic Innovations IP encapsulator (with > LI's documentation attached with their permission). > The udpcast mutlticast address is considered a single route to the IPE. > The IPE sends out flow-control messages (described in document) that > shows how many bytes are available for traffic for each route every 100 > milliseconds in a multicastand comes from a user specified multicast of > its own. Attached is the LI document, again with the manufactures > permission. Also, you can contact Theo Aukerman, taukerman at logici.com > for any additional info. In today's version (20080914), I've implemented a possibility to plug in so called "rate governor" modules. These are modules that decide how fast udpcast transmits. The examples/rateGovernor subdirectory contains as an example a rateGovernor listeing to the Logic Innovations IPE's flow control messages. The example can be compiled by typing "make" in that directory, after having installed the udpcast/rateGovernor.h file under /usr/include To activate it, add the following option to the udp-sender command line: udp-sender -g ipe.so:ip=224.1.2.3,port=5555 this instructs the module to listen for flow control packets on the multicast address 224.1.2.3 on port 5555. I assumed that all integer values in these flow control packets are in network byte order. Should this not be the case, this can be changed easily. The plugin architecture also allows to easily add support for other IP encapsulators. > I'm asking these questions because IF this is possible, then this would > be an almost complete framework for an open source Data-casting network, > and can be used for over the air data-broadcasting from any DTV > transmitter or any other system with null packets. I currently work as > an engineer for a TV station that does data transmission, but would like > to move to an open source model. Congratulation for your decision to move to open source. Let's hope it'll still be useful despite the long delay. Sorry again. Regards, Alain From alain at knaff.lu Tue Sep 23 23:01:43 2008 From: alain at knaff.lu (Alain Knaff) Date: Tue, 23 Sep 2008 23:01:43 +0200 Subject: [Udpcast] Network card Error In-Reply-To: <78C50AF9-6F40-419C-B720-5EE561223344@hatsize.com> References: <78C50AF9-6F40-419C-B720-5EE561223344@hatsize.com> Message-ID: <48D95937.8050200@knaff.lu> Darin MacLachlan wrote: > 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: > Udp-sender 2007-03-23 > No suitable network interface found > The following interfaces are available: > lo 127.0.0.1 > eth2 10.46.0.251 > eth2:1 10.46.0.1 > > 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. You can only use a network card if an address is associated to it. Is this the case? If so, which address does it have? Could you also try running udp-sender under strace and send me the output? Regards, Alain From dmaclachlan at hatsize.com Tue Sep 23 23:04:32 2008 From: dmaclachlan at hatsize.com (Darin MacLachlan) Date: Tue, 23 Sep 2008 15:04:32 -0600 Subject: [Udpcast] Network card Error In-Reply-To: <48D95937.8050200@knaff.lu> References: <78C50AF9-6F40-419C-B720-5EE561223344@hatsize.com> <48D95937.8050200@knaff.lu> Message-ID: <8FB4AF77-8D57-46F7-B6B3-124020444FAB@hatsize.com> the network card has 192.168.9.254 associated to it, it also has 9 virtual IP as well 192.168.0.254 thru 192.168.8.254. I will try the strace option. On 23-Sep-08, at 3:01 PM, Alain Knaff wrote: Darin MacLachlan wrote: > 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: > Udp-sender 2007-03-23 > No suitable network interface found > The following interfaces are available: > lo 127.0.0.1 > eth2 10.46.0.251 > eth2:1 10.46.0.1 > > 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. You can only use a network card if an address is associated to it. Is this the case? If so, which address does it have? Could you also try running udp-sender under strace and send me the output? Regards, Alain From alain at knaff.lu Tue Sep 23 23:09:55 2008 From: alain at knaff.lu (Alain Knaff) Date: Tue, 23 Sep 2008 23:09:55 +0200 Subject: [Udpcast] multi computer cast problem In-Reply-To: <48D94C05.6000307@pjwstk.edu.pl> References: <48D94C05.6000307@pjwstk.edu.pl> Message-ID: <48D95B23.3090405@knaff.lu> Paweł Ufnalewski // BSS wrote: > Problem is that, when I'm doing it one-by-one (I mean server-1 client) I > get full speed - ~70MB/s, but when I'm trying to to this with >= 2 > computers transfer drops to >0,5Mb/s. Why? This is most likely a switch issue. Many switches limit (throttle) multicast traffic, as they consider it "not important". Fortunately, this can be configured on most switches. Another thing to watch out for is the lonely network printer (or other ancient device) that can't take data at more than one Mb/s. If you broadcast or multicast, most switches send out the data to all ports, and adapt the speed to the slowest device connected. Try to find out if that is the case by only connecting a bunch of "known-good" PC's to a switch (no uplink, no unknown devices). Some high-end switches do actually understand the IGMP messages by which receivers inform that they are interested in the transmission. However, these devices are rare, and even if they do support IGMP snooping, it is often switched off by default. Another thing you can try is switch off flow control. Some switches even allow to do this on a per port basis. Regards, Alain From dmaclachlan at hatsize.com Tue Sep 23 23:12:45 2008 From: dmaclachlan at hatsize.com (Darin MacLachlan) Date: Tue, 23 Sep 2008 15:12:45 -0600 Subject: [Udpcast] Network card Error In-Reply-To: <8FB4AF77-8D57-46F7-B6B3-124020444FAB@hatsize.com> References: <78C50AF9-6F40-419C-B720-5EE561223344@hatsize.com> <48D95937.8050200@knaff.lu> <8FB4AF77-8D57-46F7-B6B3-124020444FAB@hatsize.com> Message-ID: ifconfig for eth3 eth3 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.9.254 Bcast:192.168.9.255 Mask: 255.255.255.0 inet6 addr: fe80::21c:c4ff:fea7:f6ea/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:260 (260.0 b) TX bytes:810 (810.0 b) Interrupt:90 Memory:fa000000-fa011100 eth3:0 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.0.254 Bcast:192.168.0.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:1 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.1.254 Bcast:192.168.1.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:2 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.2.254 Bcast:192.168.2.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:3 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.3.254 Bcast:192.168.3.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:4 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.4.254 Bcast:192.168.4.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:5 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.5.254 Bcast:192.168.5.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:6 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.6.254 Bcast:192.168.6.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:7 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.7.254 Bcast:192.168.7.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:8 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.8.254 Bcast:192.168.8.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 On 23-Sep-08, at 3:04 PM, Darin MacLachlan wrote: the network card has 192.168.9.254 associated to it, it also has 9 virtual IP as well 192.168.0.254 thru 192.168.8.254. I will try the strace option. On 23-Sep-08, at 3:01 PM, Alain Knaff wrote: Darin MacLachlan wrote: > 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: > Udp-sender 2007-03-23 > No suitable network interface found > The following interfaces are available: > lo 127.0.0.1 > eth2 10.46.0.251 > eth2:1 10.46.0.1 > > 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. You can only use a network card if an address is associated to it. Is this the case? If so, which address does it have? Could you also try running udp-sender under strace and send me the output? Regards, Alain From dmaclachlan at hatsize.com Tue Sep 23 23:36:17 2008 From: dmaclachlan at hatsize.com (Darin MacLachlan) Date: Tue, 23 Sep 2008 15:36:17 -0600 Subject: [Udpcast] Network card Error In-Reply-To: References: <78C50AF9-6F40-419C-B720-5EE561223344@hatsize.com> <48D95937.8050200@knaff.lu> <8FB4AF77-8D57-46F7-B6B3-124020444FAB@hatsize.com> Message-ID: <26A58433-CFBC-47A3-B515-892BAC920E83@hatsize.com> strace file -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: udpsendererror.txt URL: -------------- next part -------------- On 23-Sep-08, at 3:12 PM, Darin MacLachlan wrote: ifconfig for eth3 eth3 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.9.254 Bcast:192.168.9.255 Mask: 255.255.255.0 inet6 addr: fe80::21c:c4ff:fea7:f6ea/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:260 (260.0 b) TX bytes:810 (810.0 b) Interrupt:90 Memory:fa000000-fa011100 eth3:0 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.0.254 Bcast:192.168.0.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:1 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.1.254 Bcast:192.168.1.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:2 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.2.254 Bcast:192.168.2.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:3 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.3.254 Bcast:192.168.3.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:4 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.4.254 Bcast:192.168.4.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:5 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.5.254 Bcast:192.168.5.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:6 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.6.254 Bcast:192.168.6.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:7 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.7.254 Bcast:192.168.7.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:8 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.8.254 Bcast:192.168.8.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 On 23-Sep-08, at 3:04 PM, Darin MacLachlan wrote: the network card has 192.168.9.254 associated to it, it also has 9 virtual IP as well 192.168.0.254 thru 192.168.8.254. I will try the strace option. On 23-Sep-08, at 3:01 PM, Alain Knaff wrote: Darin MacLachlan wrote: > 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: > Udp-sender 2007-03-23 > No suitable network interface found > The following interfaces are available: > lo 127.0.0.1 > eth2 10.46.0.251 > eth2:1 10.46.0.1 > > 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. You can only use a network card if an address is associated to it. Is this the case? If so, which address does it have? Could you also try running udp-sender under strace and send me the output? Regards, Alain From dmaclachlan at hatsize.com Tue Sep 23 23:46:10 2008 From: dmaclachlan at hatsize.com (Darin MacLachlan) Date: Tue, 23 Sep 2008 15:46:10 -0600 Subject: [Udpcast] Network card Error In-Reply-To: <26A58433-CFBC-47A3-B515-892BAC920E83@hatsize.com> References: <78C50AF9-6F40-419C-B720-5EE561223344@hatsize.com> <48D95937.8050200@knaff.lu> <8FB4AF77-8D57-46F7-B6B3-124020444FAB@hatsize.com> <26A58433-CFBC-47A3-B515-892BAC920E83@hatsize.com> Message-ID: think i might have found the issue It looks like the number of virutal IPS is more that the udpsender can handle. I have removed all the virtual IP addresses from eth2 and now the sender will activate on eth3. On 23-Sep-08, at 3:36 PM, Darin MacLachlan wrote: strace file On 23-Sep-08, at 3:12 PM, Darin MacLachlan wrote: ifconfig for eth3 eth3 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.9.254 Bcast:192.168.9.255 Mask: 255.255.255.0 inet6 addr: fe80::21c:c4ff:fea7:f6ea/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:260 (260.0 b) TX bytes:810 (810.0 b) Interrupt:90 Memory:fa000000-fa011100 eth3:0 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.0.254 Bcast:192.168.0.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:1 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.1.254 Bcast:192.168.1.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:2 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.2.254 Bcast:192.168.2.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:3 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.3.254 Bcast:192.168.3.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:4 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.4.254 Bcast:192.168.4.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:5 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.5.254 Bcast:192.168.5.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:6 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.6.254 Bcast:192.168.6.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:7 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.7.254 Bcast:192.168.7.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:8 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.8.254 Bcast:192.168.8.255 Mask: 255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 On 23-Sep-08, at 3:04 PM, Darin MacLachlan wrote: the network card has 192.168.9.254 associated to it, it also has 9 virtual IP as well 192.168.0.254 thru 192.168.8.254. I will try the strace option. On 23-Sep-08, at 3:01 PM, Alain Knaff wrote: Darin MacLachlan wrote: > 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: > Udp-sender 2007-03-23 > No suitable network interface found > The following interfaces are available: > lo 127.0.0.1 > eth2 10.46.0.251 > eth2:1 10.46.0.1 > > 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. You can only use a network card if an address is associated to it. Is this the case? If so, which address does it have? Could you also try running udp-sender under strace and send me the output? Regards, Alain From dmaclachlan at hatsize.com Tue Sep 23 23:59:23 2008 From: dmaclachlan at hatsize.com (Darin MacLachlan) Date: Tue, 23 Sep 2008 15:59:23 -0600 Subject: [Udpcast] Network card Error In-Reply-To: References: <78C50AF9-6F40-419C-B720-5EE561223344@hatsize.com> <48D95937.8050200@knaff.lu> <8FB4AF77-8D57-46F7-B6B3-124020444FAB@hatsize.com> <26A58433-CFBC-47A3-B515-892BAC920E83@hatsize.com> Message-ID: <7102C1A6-C40D-416A-A7F5-30A1DD08F483@hatsize.com> Looks like the limit for the Virtual IP is around 100. I think that if I change my networking around and put the UDPcast server on the first interface, then the number of Virtual IP's will not play a role. On 23-Sep-08, at 3:46 PM, Darin MacLachlan wrote: think i might have found the issue It looks like the number of virutal IPS is more that the udpsender can handle. I have removed all the virtual IP addresses from eth2 and now the sender will activate on eth3. On 23-Sep-08, at 3:36 PM, Darin MacLachlan wrote: strace file On 23-Sep-08, at 3:12 PM, Darin MacLachlan wrote: ifconfig for eth3 eth3 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.9.254 Bcast:192.168.9.255 Mask:255.255.255.0 inet6 addr: fe80::21c:c4ff:fea7:f6ea/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:260 (260.0 b) TX bytes:810 (810.0 b) Interrupt:90 Memory:fa000000-fa011100 eth3:0 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.0.254 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:1 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.1.254 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:2 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.2.254 Bcast:192.168.2.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:3 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.3.254 Bcast:192.168.3.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:4 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.4.254 Bcast:192.168.4.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:5 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.5.254 Bcast:192.168.5.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:6 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.6.254 Bcast:192.168.6.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:7 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.7.254 Bcast:192.168.7.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 eth3:8 Link encap:Ethernet HWaddr 00:1C:C4:A7:F6:EA inet addr:192.168.8.254 Bcast:192.168.8.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:90 Memory:fa000000-fa011100 On 23-Sep-08, at 3:04 PM, Darin MacLachlan wrote: the network card has 192.168.9.254 associated to it, it also has 9 virtual IP as well 192.168.0.254 thru 192.168.8.254. I will try the strace option. On 23-Sep-08, at 3:01 PM, Alain Knaff wrote: Darin MacLachlan wrote: > 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: > Udp-sender 2007-03-23 > No suitable network interface found > The following interfaces are available: > lo 127.0.0.1 > eth2 10.46.0.251 > eth2:1 10.46.0.1 > > 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. You can only use a network card if an address is associated to it. Is this the case? If so, which address does it have? Could you also try running udp-sender under strace and send me the output? Regards, Alain From archon at pjwstk.edu.pl Wed Sep 24 11:16:33 2008 From: archon at pjwstk.edu.pl (=?UTF-8?B?UGF3ZcWCIFVmbmFsZXdza2kgLy8gQlNT?=) Date: Wed, 24 Sep 2008 11:16:33 +0200 Subject: [Udpcast] multi computer cast problem In-Reply-To: <48D99B8E.24564.1CEA667@mikes.kuentos.guam.net> References: <48D94C05.6000307@pjwstk.edu.pl> <48D99B8E.24564.1CEA667@mikes.kuentos.guam.net> Message-ID: <48DA0571.7050704@pjwstk.edu.pl> Both server (debian etch) and client (knoppix 5.1 with downloaded and compiled new version of udpcast) don't have firewalls. Maybe it is something with kernel version (on both server and client)? I will try udpcast boot cd... Michael D. Setzer II pisze: > Just a follow up to the other reply you have already gotten. If you have a firewall running on > the client and servers, you need to open both the 9006 port and the 9007 ports. Not sure if > this would effect you. I was sending a file to many machine, and it also worked with one > client, but more, it didn't work. I think the transfer is done on the main port, but the clients talk > back to the sender machine via the next port. I also had the same switch problem, but using > udpcast boot cds don't have the firewall, but the Fedora systems do. > > > > On 23 Sep 2008 at 22:05, Paweł Ufnalewski // BSS wrote: > > Date sent: Tue, 23 Sep 2008 22:05:25 +0200 > From: Pawe³ Ufnalewski // BSS > To: udpcast at udpcast.linux.lu > Subject: [Udpcast] multi computer cast problem > > >> Hello, >> >> I've got problem with multicasting to many computers at once. I've >> got server with newest udp-sender (20071228) which is sending files from >> ext3 partition (with command ./udp-sender --pipe 'tar -B -S -cpf - -C >> /usr/share/systemimager/boot/i386/pjwstklenny .' --portbase 9006 >> --min-clients 2 --min-wait 15 --interface eth1 --max-bitrate 70M >> --mcast-all-addr 234.1.1.162 --ttl 10 >> >> and I'm trying to receive it with command: >> >> ./udp-receiver --portbase 9006 --nosync --ttl 10 --mcast-rdv-address >> 234.1.1.162 --pipe "tar -f - -x -vv -C /disk" >> >> on client computer. >> >> Problem is that, when I'm doing it one-by-one (I mean server-1 client) I >> get full speed - ~70MB/s, but when I'm trying to to this with >= 2 >> computers transfer drops to >0,5Mb/s. Why? I tried diffrent and the same >> subnet, I'm using 3com & cisco 3-layer switches (I also tried putting >> server and clients on the same switch - the same effect). >> >> Please help, cause I've got >200 computers to clone ;) >> >> Best regards >> >> Paul Ufnalewski // BSS >> Polish Japanese Institute of Information Technology >> >> >> _______________________________________________ >> Udpcast mailing list >> Udpcast at udpcast.linux.lu >> https://lll.lgl.lu/mailman/listinfo/udpcast >> > > > +----------------------------------------------------------+ > Michael D. Setzer II - Computer Science Instructor > Guam Community College Computer Center > mailto:mikes at kuentos.guam.net > mailto:msetzerii at gmail.com > http://www.guam.net/home/mikes > Guam - Where America's Day Begins > +----------------------------------------------------------+ > > http://setiathome.berkeley.edu (Original) > Number of Seti Units Returned: 19,471 > Processing time: 32 years, 290 days, 12 hours, 58 minutes > (Total Hours: 287,489) > > BOINC at HOME CREDITS > SETI 6,443,581.5070 | EINSTEIN 1,996,973.6209 | ROSETTA 618,619.3627 > > From archon at pjwstk.edu.pl Thu Sep 25 11:56:41 2008 From: archon at pjwstk.edu.pl (=?UTF-8?B?UGF3ZcWCIFVmbmFsZXdza2kgLy8gQlNT?=) Date: Thu, 25 Sep 2008 11:56:41 +0200 Subject: [Udpcast] multi computer cast problem In-Reply-To: <48D95B23.3090405@knaff.lu> References: <48D94C05.6000307@pjwstk.edu.pl> <48D95B23.3090405@knaff.lu> Message-ID: <48DB6059.7000801@pjwstk.edu.pl> None of this works for me. I think it's something wrong with ACKs from clients. Alain Knaff pisze: > Paweł Ufnalewski // BSS wrote: > >> Problem is that, when I'm doing it one-by-one (I mean server-1 client) I >> get full speed - ~70MB/s, but when I'm trying to to this with >= 2 >> computers transfer drops to >0,5Mb/s. Why? >> > > > This is most likely a switch issue. Many switches limit (throttle) > multicast traffic, as they consider it "not important". Fortunately, > this can be configured on most switches. > But why when there's one client it goes full speed and when there are >= 2 it drops to 0.29? It's problem with unicast not the mulitcast. > Another thing to watch out for is the lonely network printer (or other > ancient device) that can't take data at more than one Mb/s. If you > broadcast or multicast, most switches send out the data to all ports, > and adapt the speed to the slowest device connected. Try to find out if > that is the case by only connecting a bunch of "known-good" PC's to a > switch (no uplink, no unknown devices). > Tried that - only 1gb nics connected to 100Mb/s backbone. > Some high-end switches do actually understand the IGMP messages by which > receivers inform that they are interested in the transmission. However, > these devices are rare, and even if they do support IGMP snooping, it is > often switched off by default. > It's on. > Another thing you can try is switch off flow control. Some switches even > allow to do this on a per port basis. > > Regards, > > Alain > > From alain at knaff.lu Thu Sep 25 12:13:51 2008 From: alain at knaff.lu (Alain Knaff) Date: Thu, 25 Sep 2008 12:13:51 +0200 Subject: [Udpcast] multi computer cast problem In-Reply-To: <48DB6059.7000801@pjwstk.edu.pl> References: <48D94C05.6000307@pjwstk.edu.pl> <48D95B23.3090405@knaff.lu> <48DB6059.7000801@pjwstk.edu.pl> Message-ID: <48DB645F.3050707@knaff.lu> Paweł Ufnalewski // BSS wrote: > But why when there's one client it goes full speed and when there are >= > 2 it drops to 0.29? It's problem with unicast not the mulitcast. Indeed, in one case, it's unicast, and in the other it is multicast. If there is only one client, the sender falls back on unicast, which is handled much better by most switches. [...] > Tried that - only 1gb nics connected to 100Mb/s backbone. ^^^^^^^^^^^^^^^^^^^ Please do try it with only 3 PC's (1 sender, 2 receivers) connected to the switch. Nothing else. And I do mean, nothing else (well, except the power, of course...). And from there work your way upwards until it becomes slow. Indeed, as soon as a switch is connected to another switch (uplink, backbone, ...), it also becomes vulnerable to whatever else is connected to that other switch (flow control propagates, unfortunately). I know, it does take some patience, but AFAIK, this is the only way to find out what is triggering the slowdown. Regards, Alain