Hi,
I'm getting things started with coda step by step and it's advancing.
After I got my client running on the same machine as the server/cell,
I'm now trying to get a connection to the cell from a client via
internet. The cell is identified by it's domain name `richtercloud.de`
which is a dynamic DNS (DDNS) address updated in a reliable time (< 2
minutes over night when I didn't do any connection attempts so far). I
am very sure that the issue(s) described below isn't caused DDNS name
resolution problems.

Is it possible to use coda in the above described scenario? The ancestor
of coda OpenAFS requires a fixed IPv4 address which makes it unusable
for non-millionaires which cannot buy some of the few addresses
available for sale.

After a sucessful start of the `coda-client` `systemd` unit I see

    $ ls -la /coda
    insgesamt 3
    dr-xr-xr-x 1 root nogroup 2048 Jul 12 23:16 .
    drwxr-xr-x 1 root root     438 Jul  7 17:35 ..
    lrw-r--r-- 1 root nogroup   18 Jul 12 23:17 richtercloud.de ->
#@richtercloud.de

which is very similar to the [issue I had for the client access on the
server
machine](http://www.coda.cs.cmu.edu/maillists/codalist/codalist-2016/9502.html),
but it's not resolved by starting `venus` with the `-init` flag or
running `cfs purgeml`. `cfs checkservers` returns `All servers up`. `cfs
listvol /coda` returns

    $ cfs listvol /coda/
      Status of volume ff000001 (4278190081) named "CodaRoot"
      Volume type is Backup
      Connection State is Reachable
      Reintegration age: 0 sec, time 0.000 sec
      Minimum quota is 0, maximum quota is unlimited
      Current blocks used are 0
      The partition has 0 blocks available out of 0

and `cfs listvol /coda/richtercloud.de` returns `/coda/richtercloud.de:
No such file or directory`. `codacon` prints messages in the form of

    unreachable 192.168.179.1 ( 20:45:12 )
    DisconnectFS ( 20:45:12 )
    BeginStatusWalk [2] ( 20:45:19 )
       [0, 0, 0, 0] [0] ( 20:45:19 )
    EndStatusWalk [2] ( 20:45:19 )
       [0, 0, 0, 0] [0, 0, 0] [1, 0, 0.0] ( 20:45:19 )
    BeginDataWalk [4] ( 20:45:19 )
    EndDataWalk [4] ( 20:45:19 )
       [1, 0, 0.0] [0, 0, 0, 0] ( 20:45:19 )
    Probe ( 20:45:42 )
    BackProbe dslc-082-082-043-120.pools.arcor-ip.net ( 20:45:45 )

during `cfs listvol /coda/richtercloud.de`. I don't understand why the
192.168.0.0/16 address is contacted which seems to be a good explanation
for the connection failure.

Looking forward to great help again :)

-Kalle