[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[coldsync-hackers] Re: inetd netsync
- To: coldsync-hackers at lusars dot net
- Subject: [coldsync-hackers] Re: inetd netsync
- From: Alessandro Zummo <azummo-coldsync2 at towertech dot it>
- Date: Mon, 04 Nov 2002 22:42:07 +0100
- In-Reply-To: <NEBBJEJDOJKNMNOFCBEAKEHEENAA.robb@empire2.com>
- Organization: Tower Technologies
- Reply-To: coldsync-hackers at lusars dot net
- Sender: owner-coldsync-hackers at lusars dot net
On 04-Nov-02 at 20:21:03,
Rob Bloodgood <robb@empire2.com> wrote:
>> Anyone knows _when_ pi-csd is required? It's my Palm Desktop
>> totally faulty?
> The UDP daemon (pi-csd) was NOT required in my testing on a localhost or
> same subnet lan. It was ABSOLUTELY required to connect to a NAT'd coldsync
> server from the Internet via Palm modem. I think it's needed whenever
> there is routing (eg the network addresses of the Palm and the coldsync
> server aren't the same). Hmmm now that I think of it, I never did figure
> out if setting netmasks or leaving it blank made any difference on that
> score.
Until now, i leaved them blank. We should implement something like pi-csd
in coldsync...
> But when communicating with my Nat'd host, I'm inclined to *guess* (don't
> actually know) that the netsync protocol includes the server's (and/or
> client's) addresses as payload vs envelope. Meaning that the NAT which
> re-addresses the envelop will show inconsistent results with the payload.
As far as i remember, that's true.
> I see pi-csd send essentially a redirect, via udp,
> to say, "No, go to THIS host for network communications"
> (which was the same as the host it was talking to, but had a different
> envelope address).
I should investigate this further.
--
- alex.
--
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.