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

	To recap from my previous emails: I have a machine that recently became
multihomed that is, among other things, the Coda server for my home
network; its two IP addresses are 192.168.0.2 and 192.168.1.1.
/etc/hosts on every machine in my house is configured to translate the
unqualified hostname 'taniquetil' to 192.168.0.2, and I have used said
hostname in configuring both codasrv and venus. The realms config file
on every machine where Coda is installed also maps the realm
'taniquetil' to the IP address 192.168.0.2.
	After reinitializing the server, nothing much has changed; machines on
192.168.0.0/24 work, but I can't talk to Coda from 192.168.1.0/24.
rpc2ping on a 192.168.1. machine is able to connnect with taniquetil,
but when I try

# ls /coda/taniquetil

I receive the following:

lrw-r--r--  1 root nobody 3 Sep  1 21:30 /coda/taniquetil -> #@.

Analyzing some packets with Ethereal reveals that Coda requests/replies
from my 192.168.1. machine are going to/from 192.168.1.1 rather than
192.168.0.2. I have had no prior problems with the unqualified hostname;
is it possible that I am now? Alternatively, what else could be the matter?

- --
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

iD8DBQFBNoxkYbuXiaDnyW4RAktCAJsGBI4YqRm6I5NekKzAZnwUEwnMFQCfbdk1
AIgm468lI390bjexkYiURyA=
=e9L9
-----END PGP SIGNATURE-----