old-www/HOWTO/html_single/Wireless-Sync-HOWTO/index.html

981 lines
14 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML
><HEAD
><TITLE
>Wireless Sync HOWTO</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
><BODY
CLASS="ARTICLE"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="ARTICLE"
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="TITLE"
><A
NAME="WIRELESSJPILOT"
></A
>Wireless Sync HOWTO</H1
><H2
CLASS="SUBTITLE"
>Using <B
CLASS="COMMAND"
>jpilot</B
> to sync your PalmOS device to your desktop across a wireless (802.11b) network.</H2
><DIV
CLASS="AUTHORGROUP"
><A
NAME="AEN6"
></A
><H3
CLASS="AUTHOR"
><A
NAME="AEN7"
>Eric Womack</A
></H3
><DIV
CLASS="AFFILIATION"
><SPAN
CLASS="ORGNAME"
>Las Vegas Data LLC.<BR></SPAN
><DIV
CLASS="ADDRESS"
><P
CLASS="ADDRESS"
> <TT
CLASS="EMAIL"
>&#60;<A
HREF="mailto:eric@lasvegasdata.com"
>eric@lasvegasdata.com</A
>&#62;</TT
><br>
</P
></DIV
></DIV
></DIV
><DIV
CLASS="REVHISTORY"
><TABLE
WIDTH="100%"
BORDER="0"
><TR
><TH
ALIGN="LEFT"
VALIGN="TOP"
COLSPAN="3"
><B
>Revision History</B
></TH
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 0.13</TD
><TD
ALIGN="LEFT"
>2002-03-01</TD
><TD
ALIGN="LEFT"
></TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>deamon mode correction</TD
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 0.12.1</TD
><TD
ALIGN="LEFT"
>2002-01-27</TD
><TD
ALIGN="LEFT"
></TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>CVS Test</TD
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 0.12</TD
><TD
ALIGN="LEFT"
>2001-12-12</TD
><TD
ALIGN="LEFT"
></TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>FGPL added, list of notes to booklet change begun</TD
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 0.11</TD
><TD
ALIGN="LEFT"
>2001-12-12</TD
><TD
ALIGN="LEFT"
></TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>Links corrected, version tracking added, address completed</TD
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 0.1</TD
><TD
ALIGN="LEFT"
>2001-12-07</TD
><TD
ALIGN="LEFT"
></TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>Initial realease for comments</TD
></TR
></TABLE
></DIV
><DIV
><DIV
CLASS="ABSTRACT"
><A
NAME="AEN37"
></A
><P
></P
><P
> This document explains how to perform a wireless, network sync between a <SPAN
CLASS="HARDWARE"
>Handspring Visor</SPAN
> and <B
CLASS="COMMAND"
>jpilot</B
> or <B
CLASS="COMMAND"
>jpilot-sync</B
>. Although this concentrates on specific hardware, the techniques and information should translate to all similar devices.</P
><P
></P
></DIV
></DIV
><HR></DIV
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
>1. <A
HREF="#INTRO"
>Introduction</A
></DT
><DT
>2. <A
HREF="#COMPONENTS"
>Components Used &#38; Required Software</A
></DT
><DD
><DL
><DT
>2.1. <A
HREF="#HARDWARECOMP"
>The Hardware components used for this document are:</A
></DT
><DT
>2.2. <A
HREF="#SOFTWARECOMP"
>Software required and version used</A
></DT
></DL
></DD
><DT
>3. <A
HREF="#SETUP"
>Setup</A
></DT
><DD
><DL
><DT
>3.1. <A
HREF="#VISOR"
><SPAN
CLASS="HARDWARE"
>Visor</SPAN
></A
></DT
><DT
>3.2. <A
HREF="#MODULE"
>SpringPort Module</A
></DT
><DT
>3.3. <A
HREF="#SOFTWARE"
>Software Configuration</A
></DT
></DL
></DD
><DT
>4. <A
HREF="#OPERATION"
>Operation</A
></DT
><DT
>5. <A
HREF="#LICENSE"
>License</A
></DT
></DL
></DIV
><P
> This procedure has been tested on the <SPAN
CLASS="HARDWARE"
>Handspring Visor Deluxe</SPAN
>. It <EM
>should</EM
> work on all <SPAN
CLASS="APPLICATION"
>PalmOS</SPAN
> based devices as well.</P
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="INTRO"
></A
>1. Introduction</H1
><P
> I had just acquired my 802.11b module for my Visor, and decided that I wanted to do away with the need for the cradle that would keep me locked to a desktop for syncing purposes. After all, the whole point of being wireless and handheld was to be mobile. After many hours of careful reading in entirely too many sources, I have distilled the necessary information into this short HOWTO. If at anytime you find yourself going through the HOWTO and have to stop and lookup how to do something I have listed, please email that to me so I can add it and help the next person who reads this.</P
><P
> Also, please send me reports of success (and failures) of hardware devices other than those listed so that I may append it to this document.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="COMPONENTS"
></A
>2. Components Used &#38; Required Software</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="HARDWARECOMP"
></A
>2.1. The Hardware components used for this document are:</H2
><P
></P
><UL
><LI
><P
> <A
HREF="http://www.handspring.com/products/visordeluxe/index.jhtml?"
TARGET="_top"
><SPAN
CLASS="HARDWARE"
>Visor Handheld Deluxe</SPAN
></A
>
</P
></LI
><LI
><P
> <A
HREF="http://www.xircom.com/cda/page/0,1298,1-840-1_1-1633,00.html"
TARGET="_top"
><SPAN
CLASS="HARDWARE"
>Xircom SpringPort Wireless Ethernet Module </SPAN
></A
>
</P
></LI
><LI
><P
> <A
HREF="http://www.smc.com"
TARGET="_top"
><SPAN
CLASS="HARDWARE"
>EZ Connect 11 Mbps Wireless Access Point </SPAN
></A
>
</P
></LI
></UL
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="SOFTWARECOMP"
></A
>2.2. Software required and version used</H2
><P
></P
><UL
><LI
><P
> <A
HREF="http://www.redhat.com"
TARGET="_top"
><SPAN
CLASS="APPLICATION"
>RedHat 7.2</SPAN
></A
>
</P
></LI
><LI
><P
> <A
HREF="http://www.jpilot.org"
TARGET="_top"
><SPAN
CLASS="APPLICATION"
>jpilot-0.99.1pre</SPAN
></A
> with <A
HREF="http://www.moongroup.com/archives/jpilot/2001-11/msg00082.html"
TARGET="_top"
>patch to correct <B
CLASS="COMMAND"
>jpilot-sync</B
></A
>
</P
></LI
><LI
><P
> <A
HREF="http://www.pilot-link.org"
TARGET="_top"
><SPAN
CLASS="APPLICATION"
>pilot-link 0.9.5-pre3</SPAN
></A
>
</P
></LI
><LI
><P
> <A
HREF="http://www.handspring.com"
TARGET="_top"
><SPAN
CLASS="APPLICATION"
>PalmOS v. 3.1H2</SPAN
></A
>
</P
></LI
></UL
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="SETUP"
></A
>3. Setup</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="VISOR"
></A
>3.1. <SPAN
CLASS="HARDWARE"
>Visor</SPAN
></H2
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="SERVICE"
></A
>3.1.1. Configure a new service to use for syncing.</H3
><P
>Click <SPAN
CLASS="GUIBUTTON"
>Prefs</SPAN
> on the <SPAN
CLASS="HARDWARE"
>Visor</SPAN
>. In the upper right-hand corner is a drop down menu. Click and select <SPAN
CLASS="GUISUBMENU"
>Network</SPAN
>. Click the main drop down menu by clicking the drop down icon in the lower left corner of the visor, next to the graffiti screen. From the menu that drops down, click <SPAN
CLASS="GUISUBMENU"
>New</SPAN
> and configure a new serverice according to the following.</P
><P
></P
><UL
><LI
><P
> <TT
CLASS="ENVAR"
>Username</TT
>
</P
><P
> The username used to log onto the network.
</P
></LI
><LI
><P
> <TT
CLASS="ENVAR"
>Password</TT
>
</P
><P
> The username used to log onto the network.
</P
></LI
><LI
><P
> <TT
CLASS="ENVAR"
>Phone Number</TT
> 00
</P
><P
> This will tell the <SPAN
CLASS="HARDWARE"
>Visor</SPAN
> to use a network connection.
</P
></LI
><LI
><P
> <TT
CLASS="ENVAR"
>Connection Type</TT
> PPP
</P
></LI
><LI
><P
> <TT
CLASS="ENVAR"
>Query DNS</TT
> should be checked
</P
></LI
><LI
><P
> <TT
CLASS="ENVAR"
>IP Address</TT
>
</P
><P
> Automatic should be checked if DHCP is running.
</P
></LI
></UL
></DIV
><DIV
CLASS="SECT3"
><HR><H3
CLASS="SECT3"
><A
NAME="PCSETUP"
></A
>3.1.2. Configure your Primary PC Setup to the workstation that will be running <B
CLASS="COMMAND"
>jpilot</B
>.</H3
><P
></P
><UL
><LI
><P
> <TT
CLASS="ENVAR"
>Primary PC Name</TT
>
</P
><P
> This is the full network name of the workstation.
</P
></LI
><LI
><P
> <TT
CLASS="ENVAR"
>Primary PC Address</TT
>
</P
><P
> The IP of the workstation. If using DHCP, it is a good idea to map the number to the MAC address of the NIC so the it will remain constant. This will save you from having to re-enter this info.
</P
></LI
></UL
></DIV
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="MODULE"
></A
>3.2. SpringPort Module</H2
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="CLIENT"
></A
>3.2.1. Configure Client Settings</H3
><P
></P
><UL
><LI
><P
> <TT
CLASS="ENVAR"
>Client Name</TT
>
</P
><P
> Set to whatever you wish. This will be the name that the <SPAN
CLASS="HARDWARE"
>Visor</SPAN
> announces to the network as it's own.
</P
></LI
><LI
><P
> <TT
CLASS="ENVAR"
>Profile</TT
>
</P
><P
> The Xircom module supports 3 separate setups. Select one for use in your system.
</P
></LI
><LI
><P
> <TT
CLASS="ENVAR"
>Network ID (SSID)</TT
>
</P
><P
> For maximum security, this should be a unique name shared among all the 802.11b devices that are attached to your network.
</P
></LI
><LI
><P
> <TT
CLASS="ENVAR"
>Encryption </TT
>
</P
><P
> For maximum security, this should be enabled and set to the highest available that is supported by all the devices. Use the <SPAN
CLASS="HARDWARE"
>WAP</SPAN
> to create the key to install to all the 802.11b devices that are attached to your network.
</P
></LI
><LI
><P
> <TT
CLASS="ENVAR"
>MAC Address </TT
>
</P
><P
> Enter this into the MAC allowed list and re-enable MAC filtering.
</P
></LI
></UL
><DIV
CLASS="TIP"
><P
></P
><TABLE
CLASS="TIP"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TH
ALIGN="LEFT"
VALIGN="CENTER"
><B
>Obtaining the MAC address on the Xircom Wireless Ethernet Module</B
></TH
></TR
><TR
><TD
>&nbsp;</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> The MAC address should be printed on the label that is sandwiched between the <SPAN
CLASS="HARDWARE"
>Visor</SPAN
> and the module. If that is unreadable, it will have to be found out another way. The easiest way I have found to do this is to disable MAC filtering on the <SPAN
CLASS="HARDWARE"
>WAP</SPAN
>, configure the above and connect. Clicking <SPAN
CLASS="GUISUBMENU"
>Status/IP Information</SPAN
> will bring up a screen showing the MAC of the module.</P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="SECT3"
><HR><H3
CLASS="SECT3"
><A
NAME="AEN169"
></A
>3.2.2. Configure Network Settings</H3
><P
> This is handled by the "Configure New Service" section above.</P
></DIV
><DIV
CLASS="SECT3"
><HR><H3
CLASS="SECT3"
><A
NAME="AEN172"
></A
>3.2.3. Configure HotSync Settings</H3
><P
> This is handled by the "Configure New Service" section above.</P
></DIV
><DIV
CLASS="SECT3"
><HR><H3
CLASS="SECT3"
><A
NAME="WAP"
></A
>3.2.4. <SPAN
CLASS="HARDWARE"
>Wireless Access Point</SPAN
></H3
><P
> Setup your access point according to your manufacturer's directions. The following services are recommended:</P
><P
></P
><UL
><LI
><P
> <TT
CLASS="ENVAR"
>128bit Encryption</TT
>
</P
></LI
><LI
><P
> <TT
CLASS="ENVAR"
>MAC Filtering</TT
>
</P
></LI
><LI
><P
> <TT
CLASS="ENVAR"
>Unique SSID enabled</TT
>
</P
></LI
><LI
><P
> <TT
CLASS="ENVAR"
>DHCP - Either from network or Access Point, but not both.</TT
>
</P
></LI
></UL
></DIV
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="SOFTWARE"
></A
>3.3. Software Configuration</H2
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="SOFTJPILOT"
></A
>3.3.1. <B
CLASS="COMMAND"
>jpilot</B
></H3
><P
> Run <B
CLASS="COMMAND"
>jpilot</B
> and set the following under <SPAN
CLASS="GUISUBMENU"
>File/Preferences/Settings</SPAN
>.</P
><P
></P
><UL
><LI
><P
> <TT
CLASS="ENVAR"
>Serial Port</TT
> .
</P
><P
> For clarity, the setting is a single period. This will signify to underlying pilot-link subsystem to expect a network connection.
</P
></LI
><LI
><P
> <TT
CLASS="ENVAR"
>Serial Rate</TT
>
</P
><P
> This can be put to the hightest setting.
</P
></LI
></UL
></DIV
><DIV
CLASS="SECT3"
><HR><H3
CLASS="SECT3"
><A
NAME="SOFTJPILOTSYNC"
></A
>3.3.2. <B
CLASS="COMMAND"
>jpilot-sync</B
></H3
><P
> To configure <B
CLASS="COMMAND"
>jpilot-sync</B
>, configure <B
CLASS="COMMAND"
>jpilot</B
> as describe above, then exit.</P
><P
> Next, use the following command to run in a daemon-like mode.</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
> jpilot-sync -l &#62;&#38; /dev/null &#38;</PRE
></FONT
></TD
></TR
></TABLE
><DIV
CLASS="WARNING"
><P
></P
><TABLE
CLASS="WARNING"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> Do not attempt to sync using <B
CLASS="COMMAND"
>jpilot</B
> while <B
CLASS="COMMAND"
>jpilot-sync</B
> is running by pressing <SPAN
CLASS="GUIBUTTON"
>Sync</SPAN
> in <B
CLASS="COMMAND"
>jpilot</B
>. This may or may not work the first time, but will certainly crash both at the completion.</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="NOTE"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> You can run <B
CLASS="COMMAND"
>jpilot</B
> while <B
CLASS="COMMAND"
>jpilot-sync</B
> is running, and even edit/add entries or sync. Simply allow <B
CLASS="COMMAND"
>jpilot-sync</B
> to run in the background to pick up the sync request.</P
></TD
></TR
></TABLE
></DIV
><P
>Alternatively, for a pure command-line approach, edit the <TT
CLASS="FILENAME"
>jpilot.rc</TT
> file and change <TT
CLASS="ENVAR"
>port</TT
> to .. and <TT
CLASS="ENVAR"
>rate</TT
> to 10.</P
></DIV
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="OPERATION"
></A
>4. Operation</H1
><P
> With all the above configured correctly, operation is quite simple. Click <SPAN
CLASS="GUIBUTTON"
>HotSync</SPAN
> icon on the <SPAN
CLASS="HARDWARE"
>Visor</SPAN
>, then click <SPAN
CLASS="GUIICON"
>ModemSync</SPAN
>. Allow the client to negotiate a connection with the network, then click <SPAN
CLASS="GUIBUTTON"
>Sync</SPAN
> on <B
CLASS="COMMAND"
>jpilot</B
>.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="LICENSE"
></A
>5. License</H1
><P
>GNU Free Documentation License
<A
HREF="http://www.gnu.org/copyleft/fd1.html"
TARGET="_top"
>http://www.gnu.org/copyleft/fd1.html</A
></P
><P
>Copyright (C) 2001 Eric Womack</P
><P
>Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.</P
></DIV
></DIV
></BODY
></HTML
>