Quoting Jan Harkes <jaharkes_at_cs.cmu.edu> on Fri, Sep 19 14:01:
>
[ snip ]

> I believe you have to set both of the following options in
> /etc/coda/server.conf,
> 
>     hostname=server-hostname
>     ipaddress=192.168.1.1

Ah, no, I was just setting ipaddress, not hostname.  Woo-hoo!  When I
set both I can leave the server on 192.168.1.1 and access it from the
DMZ subnet!  I will try to set up the other clients soon to see if they
work as well, but since this case does I have strong hopes for the
others.

The netstat output is strange though:
0 > netstat.sh | egrep coda
udp    0.0.0.0 (codaauth2:370)        6915/auth2
udp    192.168.1.1 (codasrv:2432)     7688/codasrv
udp    192.168.2.1 (codasrv:2432)     4971/codasrv
udp    192.168.1.1 (codasrv-se:2433)  7688/codasrv
udp    192.168.2.1 (codasrv-se:2433)  4971/codasrv

(netstat.sh is a shell script that munges the output a little.)

I have no idea where it is getting 192.168.2.1, there are not any
instances of that or the machine name that corresponds to in /vice/**.

> For some strange reason it would be a lot easier if your server was on a
> separate machine on the local network (192.168.1.2) because then the
> kernel really just routes the packets and isn't messing around with the
> source ip-address of outgoing packets.

I thought about that, but I'm just a home user (albeit atypical ;-) and
don't really want to run a machine just for coda.

Anyhow, thanks for your help, I'm quite excited to try to consolidate
my home directories from 3 machines down to a single copy, centrally
stored.

Omen

-- 
grep me no patterns and I'll tell you no lines.