-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday 29 March 2003 17:58, Tito Flagella wrote:
I had the same error due to lackness of the /var/run/zorp directory. created that directory and i didn't get that error messages anymore, thx.
At least with my configuration zorp needed to do an udp socket there. not really a socket but
debian:/var/run/zorp# l total 0 srwxr-xr-x 1 root root 0 Mar 31 10:38 zorpctl.extern srwxr-xr-x 1 root root 0 Mar 31 10:38 zorpctl.intern not very secure
intern -v3 -p /etc/zorp/policy.py --autobind-ip autobind='1.1.1.1' extern -v3 -p /etc/zorp/policy.py --autobind-ip autobind='1.1.1.2' Are you sure about the autobind syntax? We are using "-B 1.1.1.1", from the usage info it would seem that you should use "--autobind-ip 1.1.1.1" I know also of the -B stuff, I can also take that one ;-)
We are now using one of the server's ip, and I didn't observe any difference from using a dummy interface. my problem is that a bridge has only one ip on all interfaces, and I believe I can only bind on instance to an ip.
- -- Regards, Robert - ---------------- Robert Penz robert.penz AT outertech.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE+h//l8tTsQqJDUBMRAtTAAJ9buj5mBluo/jKVpJ9EOdggPzOH1wCfWBS7 XlKzkme9+Oj6e4HE4mKUiiE= =dPAB -----END PGP SIGNATURE-----