Re: [coldsync-hackers] netsync and port/proto

[Christophe Beauregard <christophe dot beauregard at sympatico.ca>]

On Saturday 19 February 2005 09:59, John wrote:
> I am unable to get coldsync to sync over the Internet.  I have tried
> version 2.2.5 as well as 3.0-pre4.  I am running on kernel 2.6.9.

You definitely want to stick with 3.0-pre4. If only because the people who 
work on coldsync aren't running anything as old as 2.2.5.

> I ran strace cold "coldsync -mI" and I can see it is binding to port
> 14237 (netsync-wakeup).  When the Palm (Treo 600) tries to connect it is
> attempting on 14238/tcp.  Clearly, there is a discrepency here.

Nope.

In standalone mode, coldsync waits on 14237  for a (UDP) wakeup packet. Once 
it gets the wakeup it creates a (TCP) socket on 14238 and listens for a 
connection. Sounds like maybe that second step isn't happening. You don't 
have some kind of firewalling happening that might be blocking the UDP 
packet do you? Connection-oriented diagnostic tools like netstat won't show 
you the attempted UDP connection, but you _should_ see the listen on 14238 
shortly after the Palm tries the connection... you'd need a packet sniffer 
to see the UDP wakeup. Cranking up the trace level on coldsync itself might 
also give you something.

Have you tried the inetd/xinetd technique for netsync? It sounds like that 
would probably work correctly since it only listens on 14238 and the Palm 
seems to be going directly there without the UDP wakeup.

c.