-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jan Harkes wrote:
| The response to Coda's volume location request only has a single
| ip-address. So that causes a bit of a headache for multi-homed hosts.
| The only solution really is to pick one address, and stick to that as
| much as possibly, using routing tricks to make sure that anyone on
| either network can reach that one address.

	Speaking of routing tricks, how well does Coda play with NAT? I did
have NAT operating between wired and wireless, but once I smacked myself
in the head and realized a static route on my broadband router appliance
would do the same job, I turned it off. Hasn't solved my problem,
though, and I did unset ipaddress= in my server.conf and tell all my
clients to use 192.168.0.2 when talking to the server.
	Time to trawl through /vice.

- --
Nicholas Haggin

A.M.D.G.

Find my public keys at my website: http://nhaggin.freeshell.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBM26iYbuXiaDnyW4RAq28AJ0bl8SEzMxblc+uBtKkaXqsW1Or1QCgjrYU
ALwcYUvyNHBCtxl73YYLXik=
=Nlko
-----END PGP SIGNATURE-----