From selcuk.cevher at ctech.com.tr Wed Aug 5 07:50:25 2009 From: selcuk.cevher at ctech.com.tr (selcuk cevher) Date: Wed, 05 Aug 2009 08:50:25 +0300 Subject: [Udpcast] udpcast wibdows version Message-ID: <1249451425.6045.6.camel@c2tech> Hi, I tried to download the executable windows versions of udpcast receiver and sender from http://udpcast.linux.lu/exe.html. Unfortunately, I could not download them since the links seemed not to be working. Can anybody fix it ? If not, are the sources of udpcast receiver and sender portable ? That is, can I compile the source under Windows without any problems ? Which steps are required for a successful compilation ? Thanks. -- Selcuk Cevher, MSc Solution Architect / Cozum Mimari C Tech Bil. Tek. San. ve Tic. A.S. (C2Tech) TUBITAK TEKSEB C-210 Gebze, Kocaeli, Turkey Tel: +90 262 644 90 48 Fax: +90 262 644 90 47 www.ctechsoft.com www.ctech.com.tr From alain at knaff.lu Wed Aug 5 11:25:39 2009 From: alain at knaff.lu (Alain Knaff) Date: Wed, 05 Aug 2009 11:25:39 +0200 Subject: [Udpcast] udpcast wibdows version In-Reply-To: <1249451425.6045.6.camel@c2tech> References: <1249451425.6045.6.camel@c2tech> Message-ID: <4A795013.5050708@knaff.lu> On 08/05/09 07:50, selcuk cevher wrote: > Hi, > > I tried to download the executable windows versions of udpcast receiver > and sender from http://udpcast.linux.lu/exe.html. > > Unfortunately, I could not download them since the links seemed not to > be working. > > Can anybody fix it ? > > If not, are the sources of udpcast receiver and sender portable ? That > is, can I compile the source under Windows without any problems ? Which > steps are required for a successful compilation ? > > Thanks. I've now uploaded this. It should be working now. Regards, Alain From emj at tiq.com Thu Aug 6 12:23:31 2009 From: emj at tiq.com (Erik Johansson) Date: Thu, 6 Aug 2009 12:23:31 +0200 Subject: [Udpcast] R: R: [SPAM] - Re: castomize udpcast iso image - Emailfound in subject In-Reply-To: <76ce20420904280810l142b9493kd7e1d6e70d376e7e@mail.gmail.com> References: <3f774a470904280339u3d5e8ccfx421e45cc33a4f67@mail.gmail.com> <76ce20420904280437y55f72af1s628383d2d83c02b6@mail.gmail.com> <76ce20420904280505j2e233f29k4704c682f8407fd5@mail.gmail.com> <76ce20420904280810l142b9493kd7e1d6e70d376e7e@mail.gmail.com> Message-ID: On Tue, Apr 28, 2009 at 5:10 PM, Jens Breuer wrote: > On Tue, Apr 28, 2009 at 2:50 PM, Autuori Gianluigi > wrote: >> I start the first pc with iso image of udpcast. >> I configure eth manualy >> Then I start sender and it waits for connection >> >> Now I switch on second pc and I select boot from network, but it doesn't find any dhcp server available > > udpcast does neither include a dhcp server nor a tftp server. > As PXE booting is a somewhat more complex setup, As far as I know Knoppix includes a tftp+dhcp server that you can use, it's pretty easy to add an udpcast payload. From cevhers at gmail.com Wed Aug 12 11:11:27 2009 From: cevhers at gmail.com (=?ISO-8859-1?Q?Sel=E7uk_Cevher?=) Date: Wed, 12 Aug 2009 12:11:27 +0300 Subject: [Udpcast] --pointopoint option Message-ID: <803a75c30908120211h4029baa7jfc5ea1915e0eef6c@mail.gmail.com> Hi, I want to use "pointopoint" option of udpcast to transfer data since there is only one receiver. However, it seems like I don't need to specify a destination IP address when using this option. If this is the case, how does udpcast handle unicast data transmission without a specified unicast destination address ? Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cevhers at gmail.com Wed Aug 12 11:12:44 2009 From: cevhers at gmail.com (=?ISO-8859-1?Q?Sel=E7uk_Cevher?=) Date: Wed, 12 Aug 2009 12:12:44 +0300 Subject: [Udpcast] portability issues for Windows Message-ID: <803a75c30908120212m7a793594lf38930e915bccc74@mail.gmail.com> Hi, Is the source code of udpcast easily portable to Windows ? Or can I compile it under Windows as is ? Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cevhers at gmail.com Wed Aug 12 11:54:34 2009 From: cevhers at gmail.com (=?ISO-8859-1?Q?Sel=E7uk_Cevher?=) Date: Wed, 12 Aug 2009 12:54:34 +0300 Subject: [Udpcast] using async and pointopoint options together Message-ID: <803a75c30908120254v1f43c212vc1daf2f1639e4d85@mail.gmail.com> Hi All, Does udpcast currently allow using async and pointopoint options together ? That is, I want to specify the unicast address of the participant manually from the command line. I noticed that the same question was raised in last January, 2009, and the answer was "not -yet- supported": http://udpcast.linux.lu/pipermail/udpcast/2009-January/000956.html Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomc at bio.umass.edu Thu Aug 13 23:04:04 2009 From: tomc at bio.umass.edu (Tom Carpenter) Date: Thu, 13 Aug 2009 17:04:04 -0400 Subject: [Udpcast] cast-o-matic Message-ID: <1250197444.16904.10.camel@grouper> There's no option to choose the forcedeth module on the current cast-o-matic web site; is that intentional? I did find it in the .deb package containting the 2.6.30 pre-compiled kernel and modules. -Tom C. From vergueira.marco at gmail.com Thu Aug 20 00:07:47 2009 From: vergueira.marco at gmail.com (Marco Vergueira) Date: Wed, 19 Aug 2009 23:07:47 +0100 Subject: [Udpcast] Udpcast!!! Message-ID: Great tool, Thanks for all team!!! -- Marco Vergueira @ 2009 @ Portugal -------------- next part -------------- An HTML attachment was scrubbed... URL: From cevhers at gmail.com Thu Aug 20 14:47:28 2009 From: cevhers at gmail.com (=?ISO-8859-1?Q?Sel=E7uk_Cevher?=) Date: Thu, 20 Aug 2009 15:47:28 +0300 Subject: [Udpcast] multicast address to listen on Message-ID: <803a75c30908200547h47a96289tbdd7f9ad105d045b@mail.gmail.com> Hi, Does udp-sender include the Ethernet multicast address for the receiver to listen on in HELLO messages ? There seems not to be any other mechanism to pass this information around (?) Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bongokader at gmail.com Fri Aug 21 22:36:23 2009 From: bongokader at gmail.com (Abdoulkadri BONGO) Date: Fri, 21 Aug 2009 20:36:23 +0000 Subject: [Udpcast] downloads menu on the main web page Message-ID: Hi, On the web page (http://udpcast.linux.lu/), on Downloads menu we don't have Deb in this list : RPM packages and Sources.Please update it to "Deb RPM packages and Sources"; or replace "RPM" by "Deb" :-) Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: From breuer.jens at googlemail.com Mon Aug 24 23:33:08 2009 From: breuer.jens at googlemail.com (Jens Breuer) Date: Mon, 24 Aug 2009 23:33:08 +0200 Subject: [Udpcast] Creating files within dhcp.script Message-ID: <76ce20420908241433s65ced43cs3e012ccd1e248556@mail.gmail.com> Hello List, hello Alain, I am playing around with the "udpcast image generator" and I need to store the next-server address in the filesystem for later processing. I am using kernel-udpcast_2.6.30-rc5_all.deb and udpcast-mkimage_20081213_all.deb. This is what my dhcp.script looks like: === snip === #!/bin/sh [ -n "$broadcast" ] && BROADCAST="broadcast $broadcast" [ -n "$subnet" ] && NETMASK="netmask $subnet" case "$1" in deconfig) /sbin/ifconfig $interface 0.0.0.0 ;; renew|bound) /sbin/ifconfig $interface $ip $BROADCAST $NETMASK /sbin/echo $siaddr > /etc/server.ip ;; esac === snap === This works as expected when generating cd-images. If I generate a initrd and boot via PXE, the file /etc/server.ip never gets created. I tried to create the file in many places (/tmp, /sbin, etc.) but it doesn't work. Is there something important that I am missing? I thought that there is no difference between a cd-image and a plain initrd (besides syslinux/pxelinux and the kernel being separate). Additionally FYI, when using the latest kernel and mkimage I get some weird behaviour. I use VirtualBox 2.2 for testing purposes and both cd-image and initrd crash the VM when trying to write to the filesystem from within dhcp.script. Any help/suggestion is much appreciated. Thanks in advance. Regards Jens From alain at knaff.lu Sat Aug 29 20:16:00 2009 From: alain at knaff.lu (Alain Knaff) Date: Sat, 29 Aug 2009 20:16:00 +0200 Subject: [Udpcast] downloads menu on the main web page In-Reply-To: References: Message-ID: <4A997060.5010006@knaff.lu> Abdoulkadri BONGO wrote: > Hi, > > On the web page (http://udpcast.linux.lu/), on Downloads menu we don't have > Deb in this list : RPM packages and > Sources.Please update it to "Deb > RPM packages and Sources"; or replace "RPM" by > "Deb" :-) > > Regards > Thanks for the note, this is now fixed Alain From alain at knaff.lu Sun Aug 30 09:29:12 2009 From: alain at knaff.lu (Alain Knaff) Date: Sun, 30 Aug 2009 09:29:12 +0200 Subject: [Udpcast] multicast address to listen on In-Reply-To: <803a75c30908200547h47a96289tbdd7f9ad105d045b@mail.gmail.com> References: <803a75c30908200547h47a96289tbdd7f9ad105d045b@mail.gmail.com> Message-ID: <4A9A2A48.2030708@knaff.lu> Selçuk Cevher wrote: > Hi, > > Does udp-sender include the Ethernet multicast address for the receiver to > listen on in HELLO messages ? Yes, this is indeed transmitted in the HELLO message > There seems not to be any other mechanism to pass this information around > (?) > > Thanks. ... however, in the event where only one receiver connects, the sender directly sends it to its unicast address. So, in order to be prepared, the receiver has to listen to both addresses (mcast address from HELLO, and unicast address) Indeed, the sender cannot yet include the unicast address in the HELLO packet, because at that stage of the protocol, it is not yet known how many receivers there will be. Regards, Alain From cevhers at gmail.com Mon Aug 31 13:25:04 2009 From: cevhers at gmail.com (=?ISO-8859-1?Q?Sel=E7uk_Cevher?=) Date: Mon, 31 Aug 2009 14:25:04 +0300 Subject: [Udpcast] multicast address to listen on In-Reply-To: <4A9A2A48.2030708@knaff.lu> References: <803a75c30908200547h47a96289tbdd7f9ad105d045b@mail.gmail.com> <4A9A2A48.2030708@knaff.lu> Message-ID: <803a75c30908310425o16e6fa9dq786e61ef13d26133@mail.gmail.com> I haven't check the source code yet. However, based on what you say, udp-receiver currently listens to both the multicast address, which is encapsulated in HELLO messages, and the unicast address, which is its own IP address appearing in the destination IP field of a UDP datagram. As far as I know, udp-sender currently does not allow specifying a certain unicast address from the command line (?) To modify the source for allowing specifying a certain unicast IP address from the command line, which part of the source should I study ? Additionally, I do not want udp-sender to wait for at least one connection from the clients before sending. Instead, it should send no matter there is any connection to it or not. I need this feature as well to see how udpcast behaves in presence of applications other than udp-receiver running on the receiving side. I noticed "--autostart n" option. However, it still waits for at least one connection. To add these features to udp-cast, what do you suggest ? Which parts of the source code should I modify ? Thanks. On Sun, Aug 30, 2009 at 10:29 AM, Alain Knaff wrote: > Selçuk Cevher wrote: > > Hi, > > > > Does udp-sender include the Ethernet multicast address for the receiver > to > > listen on in HELLO messages ? > > Yes, this is indeed transmitted in the HELLO message > > > There seems not to be any other mechanism to pass this information around > > (?) > > > > Thanks. > > ... however, in the event where only one receiver connects, the sender > directly sends it to its unicast address. So, in order to be prepared, > the receiver has to listen to both addresses (mcast address from HELLO, > and unicast address) > > Indeed, the sender cannot yet include the unicast address in the HELLO > packet, because at that stage of the protocol, it is not yet known how > many receivers there will be. > > Regards, > > Alain > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cevhers at gmail.com Mon Aug 31 14:39:20 2009 From: cevhers at gmail.com (=?ISO-8859-1?Q?Sel=E7uk_Cevher?=) Date: Mon, 31 Aug 2009 15:39:20 +0300 Subject: [Udpcast] how to by-pass HELLO message mechanism through -m option ? Message-ID: <803a75c30908310539t7ff65a4ev6780a6d91e5b0ff8@mail.gmail.com> Hi All, I want to use udpcast in unicast (or pointopoint) mode. However, I do not want udp-sender to determine whether to use unicast or multicast based on the number of connections coming from the clients since I want to test udp-sender along with another application on the receiving side other than udp-receiver (In this framework, there won't be any connections coming from the clients). Based on above, I want udp-sender to use the unicast destination IP address provided by the user from the command line or it may be even hard-coded into the source code. I tried to use -m option to specify a unicast address instead of a multicast address to "trick" udpcast. But, it did not like that. I guess that it got some kind of negative feedback from the existing udp-receiver clients, and aborted the transfer since the clients were expecting a "proper" multicast address after -m option. Any ideas to overcome this issue ? Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: