Coda File System

Still can't talk to multihomed host

From: Nicholas Haggin <>
Date: Wed, 01 Sep 2004 21:58:44 -0500
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 and
/etc/hosts on every machine in my house is configured to translate the
unqualified hostname 'taniquetil' to, 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
	After reinitializing the server, nothing much has changed; machines on work, but I can't talk to Coda from
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 rather than 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


Find my public keys at my website:
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird -

Received on 2004-09-01 22:55:05