Hi Martin,
Martin Mokrejs wrote:
Hi Jan,
I am sorry for the long delay, I was away some days and then just overloaded
by other duties. I have increased the verbosity on both client and server.
I see some weird IP address on the server in the log: 94.112.118.14 is not
my physical eth0 IP addres
Martin Mokrejs wrote:
> Hi Jan,
> I am sorry for the long delay, I was away some days and then just overloaded
> by other duties. I have increased the verbosity on both client and server.
> I see some weird IP address on the server in the log: 94.112.118.14 is not
> my physical eth0 IP address no
Hi Martin,
the '0' and '1' are direction parameters for the ta.key file. I actually
made a mistake when I posted
ta.key 0
for both client and server - that will never work. Either omit the
parameter or use 0 on the server and 1 on the client.
For the error that you are seeing the ta.key fil
Hi,
I am re-sending my answer from June 22 to this thread:
http://thread.gmane.org/gmane.network.openvpn.devel/3703
It must have somehow fallen deeply in your email boxes. ;-) The text below show
that the two certificates Jan
Just Keijser generated the days before could not be used on my Gentoo
David Sommerseth wrote:
> On 09/06/10 23:56, Martin MOKREJ` wrote:
>> The patches in Gentoo I for example here:
I use Gentoo, I believed that was a "typo" of Jan and did not comment
on that.
>> Please improve the openVPN docs. Further, isn't it possible to
>> provide two openssl.cf files, one
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/06/10 23:56, Martin MOKREJŠ wrote:
> The patches in Gentoo I for example here:
> http://mirror.averse.net/gentoo-portage/net-misc/openvpn/files/
>
>>> On the client:
>>> I use net-misc/openvpn-2.1.0-r1, I see there are two patches applying to
Hi,
Martin Mokrejs wrote:
Hi,
David Sommerseth wrote:
On 08/06/10 18:24, Martin Mokrejs wrote:
Hi,
I had a look into the original bug report I sent and the summary is this:
at some version openvpn implemented a more strict check for certificate
values and if teh cjeck fails one yiel
Hi,
David Sommerseth wrote:
> On 08/06/10 18:24, Martin Mokrejs wrote:
>> Hi,
>> I had a look into the original bug report I sent and the summary is this:
>> at some version openvpn implemented a more strict check for certificate
>> values and if teh cjeck fails one yields "unsupported certifica
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/06/10 18:24, Martin Mokrejs wrote:
> Hi,
> I had a look into the original bug report I sent and the summary is this:
> at some version openvpn implemented a more strict check for certificate
> values and if teh cjeck fails one yields "unsupport
Hi,
I had a look into the original bug report I sent and the summary is this:
at some version openvpn implemented a more strict check for certificate
values and if teh cjeck fails one yields "unsupported certificate purpose"
message.
I figured out that few more allowed values have to be includ
Hi,
I think the easy-rsa/openssl.cnf file should be modified so thet client
CERTs would match current openVPN expectations. Please see my bug report
at http://bugs.gentoo.org/show_bug.cgi?id=320171 . For convenience, I am
attaching the patch here. Did I get it right what has to be done? Would
som
11 matches
Mail list logo