On Sun, 17 Oct 2004, Alberto Gonzalez Iniesta wrote:
Incidentally, the error shown in the bug report looks like he is trying to
make a tunnel between 1.6 and 2.0 using incompatible key-method parameters.
He needs to set --key-method 2 on the 1.6 side.
Has this changed between 1.6 and 2 beta11?
The man page says --key-method defaults to 1 and the ChangeLog does not say
otherwise.
I don't think this guy changed that to 2 just after he upgraded the
package. I'll ask him anyway, yo never know...
Could a problem with the TUN/TAP driver confuse the --key-method handling code?
James, as you may see in here [1] now, it seems that setting
--key-method to 1 in the OpenVPN 2 side, solved the problem. Maybe that
changed but it's not documented? Or there's something weird going on?
It is documented, but probably not where you looked :-)
1.6 defaults to key-method 1, while 2.0 defaults to key-method 2.
I found it documented in the following two places:
The 2.0 Release Notes. [1]
The Compatibility Notes. [2]
[1] http://openvpn.sourceforge.net/20notes.html
[2] http://openvpn.sourceforge.net/compat.html
--
_____________________________________________________________
Mathias Sundman (^) ASCII Ribbon Campaign
OpenVPN GUI for Windows X NO HTML/RTF in e-mail
http://www.nilings.se/openvpn / \ NO Word docs in e-mail
