unicast/udp without tcp acknowledgement is what we need. The stream
needs to be sent via UDP to a storage/wide-band router device. All this
device does is store incoming packets and provide routing from the
aircraft to the ground, it can't perform any client-type interactions
and I don't think it is configured to "see" the multicast group addresses.
The network looks like this:
camera->PC LAN (10.3.1.x)->ethernet switch->wide-band router WAN
(128.102.142.x)->users
If the camera streamer can not be configured to do this then perhaps I
can use VLC on the PC to re-stream, but I am worried about CPU overhead
since the PC is used for running our other instruments. We also need to
grab the SDP information prior to the WAN and provide it to user clients
who connect to the stream.
-scott
Andrey Filippov wrote:
or alternatively can the camera streamer be configure to unicast UDP?
Scott, honestly I do not have an immediate answer - if that is
possible. As I understand unicast/multicast and tcp/udp go together -
in unicast mode the source talks to a particular client, so the
packets can be acknowledged (tcp). In multicast mode there is
naturally no way to acknowledge packets from all the clients so you
have to use udp. Why multicast/udp does not work for you? You are
trying to avoid flooding the network with the packets? That can be
solved with some router - either a dedicated hardware or just having
the camera connected to a single computer to a dedicated Ethernet port
(and use this computer as a router if you need access the camera from
another hosts).
Andrey
--
---------------------
Dr. Scott J. Janz
NASA/GSFC code 613.3
Building 33 Room E310
Greenbelt, MD 20771
ph. 301-614-5987
fax 301-614-5903
_______________________________________________
Support-list mailing list
[email protected]
http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
