Udpcast August 2004

udpcast@udpcast.linux.lu

8 participants
6 discussions

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

rogue packet
by alexandre.letort＠club-internet.fr 06 Feb '05

06 Feb '05

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

2 1

Boot problem with custom ISO...
by Richard Whittaker 14 Sep '04

14 Sep '04

Try number 2... Smaller image this time.. Hiya.. I've built a custom ISO image to boot our HP DL360 servers to image them. I've done this, because none of the images I've seen so far have support for the HP/Compaq SmartArray 5i. I belive I've done everything correctly, but I get a boot failure off the CD... Everything SEEMS to go fine, and then I get an error relating to INITRD and the RAMDisk. I'm using a custom 2.6.8 kernel with RAMDisk and ROMFS support compiled in. wh-lnxdb1:~/cdimage # ls -l total 5104 drwxr-xr-x 2 root root 4096 Aug 27 12:13 . drwx------ 13 root root 4096 Aug 27 12:12 .. -rw-r--r-- 1 root root 3484482 Aug 27 12:13 INITRD -rw-r--r-- 1 root root 15324 Aug 27 11:40 ISOLINUX.BIN -rw-r--r-- 1 root root 80 Aug 27 11:01 ISOLINUX.CFG -rw-r--r-- 1 root root 1696890 Aug 27 11:40 LINUX -r--r--r-- 1 root root 2048 Aug 27 11:01 boot.catalog wh-lnxdb1:~/cdimage # cat ISOLINUX.CFG default linux label linux kernel LINUX append root=/dev/ram0 initrd=INITRD wh-lnxdb1:~/cdimage # mkisofs -o /root/udpcast.iso -b ISOLINUX.BIN -c boot.catalog -no-emul-boot -boot-load-size 4 -boot-info-table /root/cdimage Size of boot image is 4 sectors -> No emulation Total translation table size: 2048 Total rockridge attributes bytes: 0 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 4000 2592 extents written (5 Mb) wh-lnxdb1:~/cdimage # Please see attached image for the error I'm getting.. Does anyone have any thoughts on this?.. Thanks, Richard. -- Richard Whittaker, CISSP System Manager, NorthwesTel Inc.

2 1

unable to download flopy image from web
by rsi 30 Aug '04

30 Aug '04

following link from udpcast website does not work http://www.udpcast.linux.lu/current/udpflop.img ?? -- Using Opera's revolutionary e-mail client: http://www.opera.com/m2/

2 1

How to udpcast on G5 Mac?
by Rishi R. Arora 28 Aug '04

28 Aug '04

Hi, I am interested in finding a solution to multicast a very large 21GB image onto our new G5 machines. We have got quite a few to do so ASR via Firewire is no longer an acceptable solution. Has anyone ever done this before and been successful? Background ---------- I spoke with an Apple System Engineer in Canada and he has informed me that Apple doesn't have a multicast solution in place yet. However, the developers at Apple HQ have heard our cry all the way from here and may be working on finding a solution possibly in the near future. Since I found this software last night I haven't had much time to play with it and workout all the compilation errors (missing and incomplete libraries for OSX). We have a Gb network for two brand new labs to be setup and running in a week. So I am really trying to find a more robust solution as the image may be modified during a term for repairs or a complete overhaul. For now our plan B is to use Carbon Copy Cloner from http://www.bombich.com, which is working out to be the only stable solution. Its a painfully slow process. One machine at a time. Alternatively, we can NetBoot a few machines at a time and use ASR (Apple Software Restore) but the disk isn't fast enough on our AFP shared drive to distribute data to more than 4 clients at a time. This process takes about 270-300 minutes to dump 21GB image on these clients since each connection is a unicast. Any help and comments are appreciated. -- Rishi R. Arora LAN Administrator University of Toronto at Mississauga

3 5

NEED HELP!
by Tiago Borba 12 Aug '04

12 Aug '04

I my name is Tiago, and i have a problem with UDP-SENDER, the problem is i don't get send files in udp-sender for others interfaces, the comand of server is : udp-sender --file my_file --interface tunnel0 --mcast-all-addr 224.0.0.0 --min-clients 2 it's ok. on the clients: client 1 udp-receiver -f my_file -i tunnel0 --mcast-all-addr 224.0.0.0 client 2: udp-receiver -f my_file -i eth1 the error is a time out in one client type client 2, than show in sever. how i am solve this problem ? thanks for attention!!! As informações contidas neste e-mail e nos arquivos anexados podem ser informações confidenciais ou privilegiadas. Caso você não seja o destinatário correto, apague o conteúdo desta mensagem e notifique o remetente imediatamente.

2 1

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Udpcast August 2004