Florian Lohoff <[EMAIL PROTECTED]> writes:
> On Tue, Sep 28, 1999 at 10:08:30AM +0200, Dag Brattli wrote:
> > o Fixed bug which prevented incomming connections
> >
> > PS. The latest 2.3.18ac series contains some bug-fixes to IrCOMM, so it
> > could be worth a try if you have problems with IrCOMM.
>
> Is this concerning some MTU problems ? I discovered this with
> doing UUCP over GSM S25 (ircomm). I had problems with non standard
> settings in the frame size (default: 64 tried: 1024)
Hmm, I'm not sure what you are asking about, but the MTU problem was only
that IrCOMM (and other IrDA services) would just use 2 bytes less than
whats allowed in a full sized frame. Everything would therefore work OK,
but performance would in some cases be less than optimal.
As for services running on top of IrCOMM, I can only say that IrCOMM is a
STREAM protocol and does not have any concept of frame/packet sizes,
message boundaries etc (it will split/join data as necessary), so framing
_must_ be taken care of by the service running on top of IrCOMM (like PPP
which does HDLC).
-- Dag
--
/ Dag Brattli | The Linux-IrDA Project /
// University of Tromsoe, Norway | Infrared communication for Linux //
/// http://www.cs.uit.no/~dagb | http://www.cs.uit.no/linux-irda/ ///
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www4.pasta.cs.UiT.No/mailman/listinfo/linux-irda
