12 Aug
2009
12 Aug
'09
9:54 a.m.
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.
31 Aug
31 Aug
10:07 p.m.
Selçuk Cevher wrote:
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.
Actually, it is supported, albeit roundabout way: you simply specify the
pointopoint address as a data address (-m option), and drop the
-pointopoint option:
udp-sender --fec 8x8 --async src2 -m 192.168.1.5 --max-bitrate 8m
This will send to the unicast address 192.168.1.5 in async mode.
Regards,
Alain
1 Sep
1 Sep
5:51 a.m.
But it still requires at least one connection from the udp-receiver clients,
doesn't it ?
Can I force udp-sender not to wait for at least one connection from the
clients without modifying the source code ? or Do I have to modify it ?
On Tue, Sep 1, 2009 at 1:07 AM, Alain Knaff <alain(a)knaff.lu> wrote:
Selçuk Cevher wrote:
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.
Actually, it is supported, albeit roundabout way: you simply specify the
pointopoint address as a data address (-m option), and drop the
-pointopoint option:
udp-sender --fec 8x8 --async src2 -m 192.168.1.5 --max-bitrate 8m
This will send to the unicast address 192.168.1.5 in async mode.
Regards,
Alain
7:23 a.m.
On 09/01/09 07:51, Selçuk Cevher wrote:
But it still requires at least one connection from the
udp-receiver clients,
doesn't it ?
Can I force udp-sender not to wait for at least one connection from the
clients without modifying the source code ? or Do I have to modify it ?
On Tue, Sep 1, 2009 at 1:07 AM, Alain Knaff <alain(a)knaff.lu> wrote:
Async mode in unidirectional, there are no connections from clients needed.
Regards,
Alain
2 p.m.
I have one more question.
Does udp-receiver provide an option to specify a specific IP address to
listen on ?
I am asking this because I want to try udp-receiver with some application
other than udp-sender on the sending side.
On Tue, Sep 1, 2009 at 10:23 AM, Alain Knaff <alain(a)knaff.lu> wrote:
On 09/01/09 07:51, Selçuk Cevher wrote:
But it still requires at least one connection
from the udp-receiver
clients,
doesn't it ?
Can I force udp-sender not to wait for at least one connection from the
clients without modifying the source code ? or Do I have to modify it ?
On Tue, Sep 1, 2009 at 1:07 AM, Alain Knaff <alain(a)knaff.lu> wrote:
Async mode in unidirectional, there are no connections from clients needed.
Regards,
Alain
9:37 p.m.
Selçuk Cevher wrote:
I have one more question.
Does udp-receiver provide an option to specify a specific IP address to
listen on ?
You can specify an address to use to listen for the HELLO packet
(--mcast-rdv-address option), which itself will then contain a suggested
address for the multicast transfer.
If your machine has more than one ethernet card, you may also pick which
card to use using the -i option. This influences the unicast adress that
the receiver uses.
Regards,
Alain
I am asking this because I want to try udp-receiver
with some application
other than udp-sender on the sending side.
On Tue, Sep 1, 2009 at 10:23 AM, Alain Knaff <alain(a)knaff.lu> wrote:
On 09/01/09 07:51, Selçuk Cevher wrote:
------------------------------------------------------------------------
_______________________________________________
Udpcast mailing list
Udpcast(a)udpcast.linux.lu
https://udpcast.linux.lu/cgi-bin/mailman/listinfo/udpcast But it still requires at least one connection
from the udp-receiver
clients,
doesn't it ?
Can I force udp-sender not to wait for at least one connection from the
clients without modifying the source code ? or Do I have to modify it ?
On Tue, Sep 1, 2009 at 1:07 AM, Alain Knaff <alain(a)knaff.lu> wrote:
Async
mode in unidirectional, there are no connections from clients needed.
Regards,
Alain
2 Sep
2 Sep
6:01 a.m.
You can specify an address to use to listen for the HELLO packet
(--mcast-rdv-address option), which itself will then contain a suggested
address for the multicast transfer.
But there won't be any HELLO message coming from the sending side since the
sender is another application other than udp-sender. Does it mean that
sending side should provide HELLO messages with the same format as
udp-sender ?
If your machine has more than one ethernet card, you
may also pick which
card to use using the -i option. This influences the unicast adress that
the receiver uses.
As far as I know, by default, udp-receiver listens for its unicast address
as well. Is udp-receiver capable of listening every UDP packet coming to its
port numbered 9000 without expecting any HELLO message from the other side ?
Thanks.
6:06 a.m.
Selçuk Cevher wrote:
Yes, obviously. It's the same thing as with ftp: If your ftp client does
not know how to handle control and data connection, it can't connect to
the server...
No, the HELLO packet is an integral part of the protocol. Just like ftp
can't do without a control connection, udpcast can't do without HELLO.
Regards,
Alain
You can
specify an address to use to listen for the HELLO packet
(--mcast-rdv-address option), which itself will then contain a suggested
address for the multicast transfer.
But there won't be any HELLO message coming from the sending side since the
sender is another application other than udp-sender. Does it mean that
sending side should provide HELLO messages with the same format as
udp-sender ? If your
machine has more than one ethernet card, you may also pick which
card to use using the -i option. This influences the unicast adress that
the receiver uses.
As far as I know, by default, udp-receiver listens for its unicast address
as well. Is udp-receiver capable of listening every UDP packet coming to its
port numbered 9000 without expecting any HELLO message from the other side ?
Thanks.
4679
days inactive
4700
days old
7 comments
2 participants
participants (2)
-
Alain Knaff -
Selçuk Cevher