<revremark>FGPL added, list of notes to booklet change begun</revremark>
</revision>
<revision>
<revnumber>0.11</revnumber>
<date>2001-12-12</date>
<revremark>Links corrected, version tracking added, address completed</revremark>
</revision>
<revision>
<revnumber>0.1</revnumber>
<date>2001-12-07</date>
<revremark>Initial realease for comments</revremark>
</revision>
</revhistory>
<abstract>
<para>
This document explains how to perform a wireless, network sync between a <hardware>Handspring Visor</hardware> and <command>jpilot</command> or <command>jpilot-sync</command>. Although this concentrates on specific hardware, the techniques and information should translate to all similar devices.
</para>
</abstract>
</articleinfo>
<para>
This procedure has been tested on the <hardware>Handspring Visor Deluxe</hardware>. It <emphasis>should</emphasis> work on all <application>PalmOS</application> based devices as well.
</para>
<sect1 id="intro">
<title>Introduction</title>
<para>
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.
</para>
<para>
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.
</para>
</sect1>
<sect1 id="components"><title>Components Used & Required Software</title>
<sect2 id="hardwarecomp"><title>The Hardware components used for this document are:</title>
<ulink url="http://www.jpilot.org"><application>jpilot-0.99.1pre</application></ulink> with <ulink url="http://www.moongroup.com/archives/jpilot/2001-11/msg00082.html">patch to correct <command>jpilot-sync</command></ulink>
<Sect3 id="service"><title>Configure a new service to use for syncing.</title>
<para>
Click <guibutton>Prefs</guibutton> on the <hardware>Visor</hardware>. In the upper right-hand corner is a drop down menu. Click and select <guisubmenu>Network</guisubmenu>. 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 <guisubmenu>New</guisubmenu> and configure a new serverice according to the following.
</para>
<itemizedlist>
<listitem>
<para>
<envar>Username</envar>
</para>
<para>
The username used to log onto the network.
</para>
</listitem>
<listitem>
<para>
<envar>Password</envar>
</para>
<para>
The username used to log onto the network.
</para>
</listitem>
<listitem>
<para>
<envar>Phone Number</envar> 00
</para>
<para>
This will tell the <hardware>Visor</hardware> to use a network connection.
</para>
</listitem>
<listitem>
<para>
<envar>Connection Type</envar> PPP
</para>
</listitem>
<listitem>
<para>
<envar>Query DNS</envar> should be checked
</para>
</listitem>
<listitem>
<para>
<envar>IP Address</envar>
</para>
<para>
Automatic should be checked if DHCP is running.
</para>
</listitem>
</itemizedlist>
</sect3>
<sect3 id="PCSetup"><title>Configure your Primary PC Setup to the workstation that will be running <command>jpilot</command>.</title>
<itemizedlist>
<listitem>
<para>
<envar>Primary PC Name</envar>
</para>
<para>
This is the full network name of the workstation.
</para>
</listitem>
<listitem>
<para>
<envar>Primary PC Address</envar>
</para>
<para>
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.
Set to whatever you wish. This will be the name that the <hardware>Visor</hardware> announces to the network as it's own.
</para>
</listitem>
<listitem>
<para>
<envar>Profile</envar>
</para>
<para>
The Xircom module supports 3 separate setups. Select one for use in your system.
</para>
</listitem>
<listitem>
<para>
<envar>Network ID (SSID)</envar>
</para>
<para>
For maximum security, this should be a unique name shared among all the 802.11b devices that are attached to your network.
</para>
</listitem>
<listitem>
<para>
<envar>Encryption </envar>
</para>
<para>
For maximum security, this should be enabled and set to the highest available that is supported by all the devices. Use the <hardware>WAP</hardware> to create the key to install to all the 802.11b devices that are attached to your network.
</para>
</listitem>
<listitem>
<para>
<envar>MAC Address </envar>
</para>
<para>
Enter this into the MAC allowed list and re-enable MAC filtering.
</para>
</listitem>
</itemizedlist>
<tip>
<title>Obtaining the MAC address on the Xircom Wireless Ethernet Module</title>
<para>
The MAC address should be printed on the label that is sandwiched between the <hardware>Visor</hardware> 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 <hardware>WAP</hardware>, configure the above and connect. Clicking <guisubmenu>Status/IP Information</guisubmenu> will bring up a screen showing the MAC of the module.
</para>
</tip>
</sect3>
<sect3>
<title>Configure Network Settings</title>
<para>
This is handled by the "Configure New Service" section above.
</para>
</sect3>
<sect3>
<title>Configure HotSync Settings</title>
<para>
This is handled by the "Configure New Service" section above.
Do not attempt to sync using <command>jpilot</command> while <command>jpilot-sync</command> is running by pressing <guibutton>Sync</guibutton> in <command>jpilot</command>. This may or may not work the first time, but will certainly crash both at the completion.
</para>
</warning>
<note>
<para>
You can run <command>jpilot</command> while <command>jpilot-sync</command> is running, and even edit/add entries or sync. Simply allow <command>jpilot-sync</command> to run in the background to pick up the sync request.
</para>
</note>
<para>
Alternatively, for a pure command-line approach, edit the <filename>jpilot.rc</filename> file and change <envar>port</envar> to .. and <envar>rate</envar> to 10.
</para>
</sect3>
</sect2>
</sect1>
<sect1 id="operation"><title>Operation</title>
<para>
With all the above configured correctly, operation is quite simple. Click <guibutton>HotSync</guibutton> icon on the <hardware>Visor</hardware>, then click <guiicon>ModemSync</guiicon>. Allow the client to negotiate a connection with the network, then click <guibutton>Sync</guibutton> on <command>jpilot</command>.