On Tue, Dec 17, 2002 at 08:37:15PM +0100, jochen wrote:
> 20:35:37.544890 192.168.0.2.32778 > 192.168.2.1.2432: udp 297 (DF)

Client to server - request
    "Hi, I'd like to set up an unautenticated rpc2 connection".

> 20:35:37.635594 192.168.0.1.2432 > 192.168.0.2.32778: udp 80 (DF)

Server to client - response
    "Ok, no problem".

> 20:35:37.639221 192.168.0.2.32778 > 192.168.2.1.2432: udp 140 (DF)

Client to server - request
    "btw. I'm a Coda client, and would like to bind to volume 'foo'"

> 20:35:37.883370 192.168.0.1.2432 > 192.168.0.2.32778: udp 292 (DF)

Server to client - request (note this is a request)
    "Hi, I'd like to set up an unauthenticated callback connection".

> 20:35:37.887141 192.168.0.2.32778 > 192.168.0.1.2432: udp 80 (DF)

Client to server - response (note that this is sent back to the address
			     we got the request from)
    "Ok, no problem"

You can see in the rest of the log the 'udp request with length 292
bytes/udp response with length 80 bytes' is repeated about 5 times.

So from looking at this, I would say the server is not seeing any of the
responses that are coming back from the client. And it is probably
because you've 'bound' your server to only listen on the external
interface, but it is using the internal interface to send packets back
to the client.

i.e. outgoing rpc2 connections from the client know the right address
already, but incoming connections look at the address of the sender in
the headers of the IP packet. But the server is not listening on that
specific address/port so replies never make it back.

Jan