old-www/HOWTO/Infrared-HOWTO/infrared-howto-s-linux-linu...

267 lines
5.7 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML
><HEAD
><TITLE
>Linux to Linux Connection</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="Linux Infrared HOWTO"
HREF="index.html"><LINK
REL="UP"
TITLE="Specific Connections and IrDA - Protocols"
HREF="infrared-howto-c-specific-connections.html"><LINK
REL="PREVIOUS"
TITLE="Microsoft-Windows and Linux/IrDA"
HREF="infrared-howto-s-windows-linux-connection.html"><LINK
REL="NEXT"
TITLE="Multiple Instances"
HREF="infrared-howto-s-multiple-instances.html"></HEAD
><BODY
CLASS="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>Linux Infrared HOWTO</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="infrared-howto-s-windows-linux-connection.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 3. Specific Connections and IrDA - Protocols</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="infrared-howto-s-multiple-instances.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="infrared-howto-s-linux-linux-connection"
></A
>3.13. Linux to Linux Connection</H1
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="AEN935"
></A
>3.13.1. Connection Methods</H2
><P
>&#13; There should be four ways to get two Linux machines connected via
Linux/IrDA.
</P
><P
>&#13;
<P
></P
><UL
><LI
><P
>&#13; Dag Brattli wrote about the IrOBEX support: "The awakened reader
may wonder what prevents the beaming of files from Linux to Linux?
Well, nothing!! (but I haven't tried that yet). This means that we
now have a "simple" way of beaming files between Linux laptops. I
think that this may be the "killer app" we all have been waiting
for!" Try to "load_misc irobex at both ends, and then try
irobex_app get on one of the machines and irobex_app put &#60;file&#62; on
the other.".
</P
></LI
><LI
><P
>&#13; Via Linux/IrDA network connection.
But the IrLAN protocol is no longer maintained
by the Linux/IrDA core team.
</P
></LI
><LI
><P
>&#13; With IrCOMM support, in other words over a serial line, which
could mean minicom, pppd, etc. If you want just now to use IrCOMM
between Linux boxes, please add this line to /etc/conf.modules of
_one_ box:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;# set ircomm protocol engine to client-only mode
options ircomm ircomm_cs=1
</PRE
></FONT
></TD
></TR
></TABLE
>
Note: Don't add it to both boxes, or they cannot accept incoming
connection each other! But since 2.2.7 there's no need to add
options ircomm ircomm_cs=1 to /etc/conf.modules anymore. Please
remove it if you are using it.
</P
></LI
><LI
><P
>&#13; <A
HREF="http://www.hpl.hp.com/personal/Jean_Tourrilhes/IrDA/index.html"
TARGET="_top"
>IrNET</A
>
</P
></LI
></UL
>
</P
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="AEN950"
></A
>3.13.2. Compression</H2
><P
>&#13; Please note this feature is still quite experimental! Dag Brattli
wrote: "Just wanted you to know I have just added COMPRESSION support
to IrLAP! As you may know, this is _not_ part of the IrDA(TM)
standard, but Linux can now negotiate with its peer and check if it
has the same compression capabilities). So obviously if you are
talking to Win95, Palm III or whatever, you will _not_ get
compression!!! This is something which is exclusive for Linux as far
as I know! The IrDA(TM) standard says that devices should ignore
unknown field in the negotiation header, so we are still "compatible"
with IrDA(TM) (have just borrowed an unused header value).
</P
><P
>&#13; If you want to try using the compression code (Linux &#60;-&#62; Linux) you
will have to insert the irda_deflate module some time before you
actually make the connection. I do it before irattach.
</P
><P
>&#13; The compression standard I have added is the deflate format used by
the zlib library which is described by RFCs (Request for Comments)
1950 to 1952 in the files ftp://ds.internic.net/rfc/rfc1950.txt (zlib
format), rfc1951.txt (deflate format) and rfc1952.txt (gzip format).
</P
><P
>&#13; The compression interface is similar to PPP, so you can add as many
different compressors as you want. Currently there is only support for
GZIP, but BSD compression will be added later. ... Have just tested
GZIP compression at 4Mbps. It was a really bad idea! Compressing the
frames takes so much time that the performance is actually worse than
when not using compression at all. The conclusion is that compression
should only be used for SIR speeds, ..."
</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="infrared-howto-s-windows-linux-connection.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="infrared-howto-s-multiple-instances.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Microsoft-Windows and Linux/IrDA</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="infrared-howto-c-specific-connections.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Multiple Instances</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>