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

	Greetings, all.

	The machine I use as my Coda server at home also serves as several
other things, being in effect a multipurpose network workhorse. I've
recently installed a second Ethernet adapter in it, which is connected
to my 802.11 access point; my current project is securing said access
point with a captive portal and IPSec. The server has IP address
192.168.0.2 on the wired side and 192.168.1.1 on the wireless.
	In the process I've found that Coda is now broken on the wireless side;
I get the dreaded "Connection timed out" error when attempting to access
files on a Coda volume. Everything still works fine on the wired side,
and the firewall rules between wireless and wired are not interfering
with Coda traffic.
	The ipaddress parameter in my server.conf is currently set to
192.168.0.2; should I unset it? Or do I have to tell Coda to start up
two server processes, one for each interface? Or could something else 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

iD8DBQFBL6NvYbuXiaDnyW4RAkMtAJ4t61IdczwrBexv1G9Lk7pF5rVGIgCfU7jx
N6Mk0izvS19UOW8xyNc6H0k=
=Chg5
-----END PGP SIGNATURE-----