From alain at knaff.lu Tue Nov 3 07:56:58 2009 From: alain at knaff.lu (Alain Knaff) Date: Tue, 03 Nov 2009 07:56:58 +0100 Subject: [Udpcast] Adding a no receiver timeout In-Reply-To: References: Message-ID: <4AEFD43A.8090704@knaff.lu> David Margetts 1 wrote: > Hello, > > > > I am having quite a lot of success with udp-cast, it is proving to be > very useful in shifting large hard disk images across the network. > > If there is a chance of new features, one I would like to see is the > ability to set a time-out if no receivers connect to the sender in a > given amount of time. > > I am using it for imaging notebooks and once I have done a set, I move > on to a different image. It would be nice if it would quit after a day > of being idle. > > > > > > Many Thanks, > > > > David This is now implemented in version 20091031. The option already existed for the receiver (--start-timeout). Now the same option is also supported for the sender. > ____________________________________________________________________ > > You might be interested in this... > > RM Technical Seminars - Autumn 2009 > Coming to a venue near you from 2nd November to 4th December. > Book your place now... > > http://www.rm.com/technicalseminars > > ____________________________________________________________________ > > P.S. Think Green - don't print this email unless you really need to. > > This message is confidential, so please treat it appropriately and for its intended purpose only. In particular, if it refers to any technical data, terms or prices not generally available or known, such items are "commercially sensitive information" within the terms of the Freedom of Information Act 2000 and related laws. As it would be prejudicial to RM's commercial interests if these were disclosed, please refrain from doing so. > > > > As Internet communications are not secure, please be aware that RM cannot accept responsibility for its contents. Any views or opinions presented are those of the author only and not of RM. If you are not the intended recipient of this e-mail, please accept our apologies and arrange for copies of it to be deleted. For your information, RM may intercept incoming and outgoing email communications. > > > > RM Education plc > Registered Office: New Mill House, 183 Milton Park, Abingdon, Oxfordshire, OX14 4SE, England > Registered Number: 1148594 > Did you think that transmitting more data also consumes more electricity, which raises carbon footprint? And did you think that poor formatting might reflect on content, which in this case would needlessly cast "Green" in a bad light? Especially since everything else except the small "ad-let" is formatted correctly... Regards, Alain From alain at knaff.lu Tue Nov 3 08:12:51 2009 From: alain at knaff.lu (Alain Knaff) Date: Tue, 03 Nov 2009 08:12:51 +0100 Subject: [Udpcast] Creating files within dhcp.script In-Reply-To: <76ce20420910111134v5e597588t114a4e29f3b0bf30@mail.gmail.com> References: <76ce20420908241433s65ced43cs3e012ccd1e248556@mail.gmail.com> <4A9D99F9.9030604@knaff.lu> <76ce20420909211333s4d30ce94qfeda36e8b4860812@mail.gmail.com> <76ce20420909220403t75c2bab1icea2bcc310dafa89@mail.gmail.com> <76ce20420910111134v5e597588t114a4e29f3b0bf30@mail.gmail.com> Message-ID: <4AEFD7F3.30404@knaff.lu> Jens Breuer wrote: > Hello List, > hello Alain, > > we finally tracked down the problem. > > If dhcp is set to yes in the udpc.config and udpcdialog detects that > the "ip" environment variable (set by pxelinux) is set, it will use > the extracted IP together with the hardcoded interface name "eth0". > Since eth0 hasn't got link in my testsetup ifconfig will fail and > udpcdialog presents the error message described in my previous posts. > > A workaround is to introduce an new config option where one can set > the interface to use. The easiest workaround would have been not to use the IPAPPEND option... But this is now fortunately moot after your and my fixes (see below). > The patch is added as an attachment (patch #04) of this email. Maybe > you and others find it useful and maybe you could include it in the > next version of udpcast (udpcdialog). > The config option is called "defNic" and you use it by specifying a > string like "eth1" to override the hardcoded "eth0" (e.g.: > defNic=eth1). The patches are now applied to version 20091031, after some cleanup (removed needless appending of spaces at end of some lines) and along with some refactoring in interface choosing code (support of BOOTIF, interface choosing also for other methods than dhcp). > Additionally while walking through the code, I think I spotted some > potential errors. > > Patch #01 fixes a potential buffer size problem. Might have been a typo. > I saw a warning from gcc when building busybox. Agreed & applied > Patch #02 fixes a compiler issue with gcc 4.3.3 which demands a third > parameter to the open syscall. > The build process of busybox stopped with an error. Agreed & applied > Patch #03 makes sure that the correct option gets preselected in the > use-dhcp-dialog-box. No it doesn't. It choses exactly the contrary of what was configured. And what's worse, this is the _only_ thing that it does... > I hope that you get the time to review the patches and that you find > them useful for inclusion in udpcdialog. 1, 2 and 4 were indeed useful, and are now applied. Thanks for these. > All of this has been done with the additional help of Tobias Selzer. > > Kind regards, > Jens As a result of refactoring, now IPAPPEND 2 or IPAPPEND 3 should be used, rather than IPAPPEND 1. Thanks, Alain From alain at knaff.lu Tue Nov 3 08:15:47 2009 From: alain at knaff.lu (Alain Knaff) Date: Tue, 03 Nov 2009 08:15:47 +0100 Subject: [Udpcast] UDP Cast ready-made boot images and i686 issues In-Reply-To: <4AB0D355.4090407@ist.utl.pt> References: <875c3252d3a9566981b3eb58ee39adcf.squirrel@webmail.sodki.org> <4974ACA9.3050000@knaff.lu> <4AB0D355.4090407@ist.utl.pt> Message-ID: <4AEFD8A3.7010503@knaff.lu> Henrique Rodrigues wrote: > On Mon, January 19, 2009 17:39, Alain Knaff wrote: >> Henrique Rodrigues wrote: >>> Hello, >>> >>> I've been using UDP Cast extensively for a while now and I love it, but >>> I >>> had an issue last week and I want to share it witou you. >>> >>> The UDP Cast website provides handy ready-made boot images. Apparently, >>> those images are compiled for i686 and I couldn't make them work on an >>> older machine because the processor doesn't implement the CMOV >>> operation. >>> The problem seem to belong to GCC, because it thinks that every i686 >>> processor implements the optional CMOV operation, which is not true. >>> >>> I solved the problem by compiling my own UDP Cast kernel, but I suggest >>> that the next UDP Cast ready-made boot images drop the i686 requirement >>> and stick to i386, for compatibility reasons. >>> >>> Is this a reasonable request? >>> >>> Thank you and best regards, >>> >>> Henrique Rodrigues >>> >> I'll take note of this for the next release >> >> Alain > > > Hello, > > I just want to remind that this is still a problem. The issue can be > reproduced with QEMU. Example: > > $ qemu -cpu 486 -boot d -cdrom /home/hmr/udpcd.iso > > With my custom kernel, compiled for i386, it works fine. > > Best regards, > Henrique Rodrigues > This is now fixed with the new 2.6.31 kernel in 20091031. There is some memory issue however (needs 192 Megs in qemu/kvm), which will be hopefully addressed in the next version. Regards, Alain From alban.rodriguez at univ-lr.fr Tue Nov 3 16:49:07 2009 From: alban.rodriguez at univ-lr.fr (Rodriguez Alban) Date: Tue, 3 Nov 2009 16:49:07 +0100 Subject: [Udpcast] udpcast accross routers Message-ID: <6173EB90-44B8-410B-A1BB-634624DCF442@univ-lr.fr> - Tout le monde a l'air de poster en anglais alors je fais de même ... - Hi Alain, I was just wondering how can I setup udpcast in order for my udp- sender to communicate with its receivers on another vlan. I am aware on the TTL need to be greater than 1. The problem is more about establishing the session. It seems the receivers and the sender are finding each others broadcasting their HELLO command on the subnet; of course these don't pass through the gateway and receivers will never see their sender. I looked at the mcast-rdv-address command line switch but I don't known how to use it : should it point to the IGMP router address ? maybe I missed something. Thanks for you help Have a nice day Alban From alain at knaff.lu Tue Nov 3 19:50:47 2009 From: alain at knaff.lu (Alain Knaff) Date: Tue, 03 Nov 2009 19:50:47 +0100 Subject: [Udpcast] udpcast accross routers In-Reply-To: <6173EB90-44B8-410B-A1BB-634624DCF442@univ-lr.fr> References: <6173EB90-44B8-410B-A1BB-634624DCF442@univ-lr.fr> Message-ID: <4AF07B87.5010204@knaff.lu> Rodriguez Alban wrote: > - Tout le monde a l'air de poster en anglais alors je fais de même ... - > > Hi Alain, > > I was just wondering how can I setup udpcast in order for my udp- > sender to communicate with its receivers on another vlan. > I am aware on the TTL need to be greater than 1. The problem is more > about establishing the session. It seems the receivers and the sender > are finding each others broadcasting their HELLO command on the > subnet; of course these don't pass through the gateway and receivers > will never see their sender. > I looked at the mcast-rdv-address command line switch but I don't > known how to use it : should it point to the IGMP router address ? > maybe I missed something. There are two ways to use this command line switch: 1. Supply it both on the sender and receiver, and use a multicast address (pick any, such as 235.1.2.3) 2. Use it only the receiver, and pass the sender's unicast address to it, and make sure to start receivers _after_ the sender. However, in order to make it work correctly, you need, in both cases, to make sure that all routers on the path from sender to receiver correctly support multicast routing. Method 2 will work even without multicast routing if there is only a single receiver. > Thanks for you help > > Have a nice day > Alban Regards, Alain From Ralf.Lohmann at informatik.hs-fulda.de Sun Nov 8 00:13:02 2009 From: Ralf.Lohmann at informatik.hs-fulda.de (Ralf Lohmann) Date: Sun, 08 Nov 2009 00:13:02 +0100 Subject: [Udpcast] multicast sender error on Solaris "Invalid argument" Message-ID: <1257635582.21324.49.camel@zyklon> Hello, I have a problem with the multicast mode of udp-sender. On Solaris 10 X86 and Solaris 10 Sparc it is the same error. One udp-receiver works perfect (unicast), but if I use two udp-receivers (I think then udp-sender switches to unicast mode) the sender gives the following error after starting the transfer with the anykey on the server: Udp-sender 2009-10-31 Set multicast send interface: Invalid argument and then the server stops. The Error is with udpcast-20091031 on Solaris 10 sparc and also on Solaris 10 x86! I compiled it with a hack, because the missing strndup in Solaris. I also have compiled udpcast-20070602 without a hack on Solaris 10 X86, because the news are saying it is Solaris 10 x86 ready. But I got the same error with the invalid argument. The same error occurs, when i set --ttl from 1 to 2. I think it is not a problem with the hardware or the network, because udpcast with the same hardware , but with Mandriva did work. It seems to be an Solaris related issue. Two Solaris-receivers with one Mandriva-sender did also work. Only the sender breaks on Solaris. Can you please help me? Best Regards Ralf From Ralf.Lohmann at informatik.hs-fulda.de Mon Nov 9 09:46:03 2009 From: Ralf.Lohmann at informatik.hs-fulda.de (Ralf Lohmann) Date: Mon, 09 Nov 2009 09:46:03 +0100 Subject: [Udpcast] multicast sender error on Solaris "Invalid argument"] Message-ID: <1257756363.21324.58.camel@zyklon> Hello, I solved the problem for me by deleting some Code around "Set multicast send interface" in socklib.c. Unfortunately I m not firm in C, so I could not make a Patch. Now I only have to discover, why after the successful transmission the udp-sender do not terminate. Therefore it is not possible using deamon Mode. Best Regards Ralf -------------- next part -------------- An embedded message was scrubbed... From: Ralf Lohmann Subject: [Udpcast] multicast sender error on Solaris "Invalid argument" Date: Sun, 08 Nov 2009 00:13:02 +0100 Size: 4996 URL: From alain at knaff.lu Mon Nov 30 23:57:44 2009 From: alain at knaff.lu (Alain Knaff) Date: Mon, 30 Nov 2009 23:57:44 +0100 Subject: [Udpcast] SATA driver In-Reply-To: References: Message-ID: <4B144DE8.6010102@knaff.lu> Bert Van Vreckem wrote: > Hello, > > I'm trying to build a UDPCast image for a classroom of Dell Optiplex > 760 machines. This machine has SATA drives that need the ata_generic > and pata_acpi kernel modules. These don't appear in the menu, but > apparently the actual modules are included in the standard ISO image. > How can I get the correct modules loaded? > > Cheers, > > bert In the "Chose hard disk controller module" menu, chose OTHER, and then you get proposed a larger menu Regards, Alain