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 ?


On Sun, Aug 30, 2009 at 10:29 AM, Alain Knaff <alain@knaff.lu> 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.