[Live-devel] RTP sink to serial

[Yedidia Amit]

Thanks for the answer.
2 more:
1. Does the SLIP needs full duplex channel (I need data transfer only in
one direction)
2. If I want to add some error detection and error resilience bits,
outside the Live555 (the live will receive/send normal IP packets
from/toward the SLIP), is there clean way to implement it?


Regards,


Amit Yedidia
Elbit System Ltd.

Email: amit.yedidia at elbitsystems.com
Tel: 972-4-8318905
----------------------------------------------------------

 

> -----Original Message-----
> From: live-devel-bounces at ns.live555.com 
> [mailto:live-devel-bounces at ns.live555.com] On Behalf Of Paul Clark
> Sent: Thursday, November 20, 2008 2:33 PM
> To: LIVE555 Streaming Media - development & use
> Subject: Re: [Live-devel] RTP sink to serial
> 
> Yedidia Amit wrote:
> > But I am limited to 1006 bytes datagram which increase the UDP/RTP
> > header overhead.
> >   
> 
> Not exactly...  The kernels at each end should 
> fragment/reassemble large 
> UDP datagrams across multiple SLIP packets, just as they do across 
> multiple Ethernet MAC frames if you send a UDP datagram more 
> than 1472 
> bytes.  There is a slight IP+SLIP overhead here, but the 
> UDP/RTP headers 
> are not repeated.
> 
> The RFC's recommended 1006 MTU doesn't apply if you're in control of 
> both ends, anyway.  You can request a higher MTU with ifconfig:
> 
> # ifconfig sl0 192.168.200.1 pointopoint 192.168.200.2 mtu 8192
> 
> My kernel will accept anything up to 64K (although I haven't 
> tested it),
> 
> Regards
> 
> Paul
> --
> Paul Clark
> Packet Ship Technologies Limited
> http://www.packetship.com
> _______________________________________________
> live-devel mailing list
> live-devel at lists.live555.com
> http://lists.live555.com/mailman/listinfo/live-devel
> 

The information in this e-mail transmission contains proprietary and business 
sensitive information.  Unauthorized interception of this e-mail may constitute 
a violation of law. If you are not the intended recipient, you are hereby 
notified that any review, dissemination, distribution or duplication of this 
communication is strictly prohibited. You are also asked to contact the sender 
by reply email and immediately destroy all copies of the original message.