From: Adam P. <apa...@be...> - 2004-06-15 01:48:47
|
On Monday, June 14, 2004 8:20 PM [GMT-5=EST], James Yonan <ji...@yo...> wrote: >> Which attributes of the certs need to be the same; and which >> attributes need to be different? >> >> I initially created certs for both the server and client with the >> exact same parameters and received an error while creating the >> client cert (TXT_DB error number 2), apparently because its >> attributes were identical to the server's cert. >> >> Then I created a server key with a commonName of something like >> 'OpenVPN-Server' and then used 'OpenVPN-Client' for the client's >> cert. >> >> When I test the connection using the custom-tailored sample configs >> from the release notes, the TLS handshake fails, and the server >> spits out "Error: Windows resource limit WSA_MAXIMUM_WAIT_EVENTS >> (64) has been exceeded" errors while the client reports "TLS Error: >> Unroutable control packet received from ip.address.of.server:port >> (si=3 op=P_CONTROL_V1)". > > The WSA_MAXIMUM_WAIT_EVENTS error is a real bug in beta4 and has been > fixed in beta5. Thanks for the info - I will move up to the current version. And please forgive my ignorance and inexperience, but am I creating my certs correctly? It looks as though my TLS handshake issue will still be problematic on beta5. -Adam |