Re: [coldsync-hackers] Palm m505 and serial cradles.

[Andrew Arensburger <arensb+CShackers@ooblick.com>]

On Fri, 7 Dec 2001, Ingo Oeser wrote:
> On Fri, Dec 07, 2001 at 12:25:03PM -0500, Andrew Arensburger wrote:
> > 	I meant that I had managed to successfully forward a connection
> > from a Palm attached to a Linux box, to a Windows machine running Palm's
> > software. ColdSync both sends and accepts the Network HotSync protocol, so
> > you don't need a Windows machine on the receiving end. You can use a Unix
> > box running ColdSync in daemon mode.
>
> Could you (or someone else) write a short HowTo for doing this?
>
> At least the Unix<->Unix case with coldsync on both ends?

	I haven't tested the following, and it may be wrong, but this is
the general idea:

	On the machine with the cradle, run ColdSync the way you normally
do, but add a "forward:" line to the appropriate pda{} block:

                 forward: *;
                      Forward to wherever the Palm says.
                 forward: hostname;
                      Forward to <hostname>.
                 forward: hostname alias;
                      Forward to <hostname> and use <alias> in the
                      NetSync wakeup packet.

(I don't remember what the <alias> thing was supposed to be, though it's
probably trying to be too clever. Ignore that for now.)

	So if you have

	pda "Forwarded Connection" {
		snum: "189X7M27GA63-N";
		username: "Andrew Arensburger";
		userid: 1000;
		forward: syncserver.ooblick.com;
	}

then when ColdSync gets a connection from that particular PDA, it won't
sync locally, but will try to forward the connection, using Network
HotSync, to syncserver.ooblick.com . That machine might be running Palm's
Network HotSync server, or a pilot-link utility, or ColdSync, or whatever.

	Note that a "forward:" entry unconditionally turns on forwarding.
ColdSync does not (yet) check to see whether the given hostname
corresponds to the local host. Thus, if you have

		forward: localhost;

it will open a connection to the network HotSync port on 127.0.0.1. Yes,
this is considered a bug.

	If you want to accept Network HotSync connections using ColdSync,
see the instructions in "README.daemon" in the distribution.

> I have a local cradle connected to Linux and would like to
> forward the sync of the attached palm to another computer
> attached via TCP/IP networking running coldsync, too.

	If you have ColdSync working locally, the simplest thing to do is
to take out the "directory:" line from your .coldsyncrc and replace it
with a "forward:" line, as above.

> Absolutely perfect would be a solution involving some stunnel or
> ssh, if possible (I think there will be problems with the UDP
> announce), but this is secondary.

	This might happen at some point in the future.

-- 
Andrew Arensburger                      Actually, these _do_ represent the
arensb@ooblick.com                      opinions of ooblick.com!
                        Generic Tagline V 6.01

This message was sent through the coldsync-hackers mailing list.  To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body.  For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.