Gert, I'm subscribed to mail list, please reply to list, not directly to me.
No.
Paint a picture with all machines that would see the IP packet, and
check routes in both direction on *all* machines
Could you give an explanation, how exactly this should happen?
== A ==
As I said I have
Hi,
On Thu, Mar 14, 2019 at 07:14:28PM +0300, sergio wrote:
> The sort question is:
>
> "Is it true, that making one client to be default gateway for another
> client is impossible with routed setup (OK, without NAT on vpn server),
> and this is another argument for bridged setup, not listed in
Hello.
I've already tried to discuss this in IRC as I thought it's simple and
short question, but it seems that it is not.
The sort question is:
"Is it true, that making one client to be default gateway for another
client is impossible with routed setup (OK, without NAT on vpn server),
and
Am 14.03.19 um 15:03 schrieb Ralf Hildebrandt:
* Stefanie Leisestreichler :
Thu Mar 14 14:46:48 2019 UDPv4 link remote: xxx.xxx.xxx.xxx:1194
Thu Mar 14 14:47:48 2019 TLS Error: TLS key negotiation failed to occur within
60 seconds (check your network connectivity)
That could be a firewall
Hi,
On Thu, Mar 14, 2019 at 02:54:16PM +0100, Stefanie Leisestreichler wrote:
> Thu Mar 14 14:46:48 2019 UDPv4 link local: [undef]
> Thu Mar 14 14:46:48 2019 UDPv4 link remote: xxx.xxx.xxx.xxx:1194
> Thu Mar 14 14:47:48 2019 TLS Error: TLS key negotiation failed to occur
> within 60 seconds (chec
* Stefanie Leisestreichler :
> Thu Mar 14 14:46:48 2019 UDPv4 link remote: xxx.xxx.xxx.xxx:1194
> Thu Mar 14 14:47:48 2019 TLS Error: TLS key negotiation failed to occur
> within 60 seconds (check your network connectivity)
That could be a firewall or routing issue.
--
Ralf Hildebrandt
Hi.
Am 14.03.19 um 14:00 schrieb Gert Doering:
I'd just circumvent this - if this is only for a migrational period,
generate a private key without passphrase, done.
Thanks for your input, I did what your recommended. It seems like now I
am a step further, but have an issue, still:
Thu Mar 1
Hi,
On 14/03/2019 14:00, Gert Doering wrote:
> Hi,
>
> On Thu, Mar 14, 2019 at 01:53:44PM +0100, Stefanie Leisestreichler wrote:
>> Am 14.03.19 um 13:42 schrieb Gert Doering:
>>> ... actually, it's barely 10 years, but it's*so* old that it's not
>>> really worth looking into trouble reports - Op
Hi,
On Thu, Mar 14, 2019 at 01:53:44PM +0100, Stefanie Leisestreichler wrote:
> Am 14.03.19 um 13:42 schrieb Gert Doering:
> > ... actually, it's barely 10 years, but it's*so* old that it's not
> > really worth looking into trouble reports - OpenVPN has bugs, the SSL
> > library it will be using
Am 14.03.19 um 13:42 schrieb Gert Doering:
... actually, it's barely 10 years, but it's*so* old that it's not
really worth looking into trouble reports - OpenVPN has bugs, the SSL
library it will be using has crucial bugs.
I know it is old, that is the reason why the server will be migrated
Hi,
On Thu, Mar 14, 2019 at 12:50:50PM +0100, Stefanie Leisestreichler wrote:
> This is an older version of OpenVPN. The key is setup with:
> --digest=sha512 --keysize=4096. If this is causing the error, could you
> please recommend supported settings to use with OpenVPN version 2.1_rc20?
2.1_r
Greetings.
I am getting the following error message, when trying to start an
openvpn client even I am sure to use the correct password.
This is an older version of OpenVPN. The key is setup with:
--digest=sha512 --keysize=4096. If this is causing the error, could you
please recommend support
Hi Gert,
>> I tried
>> $OPENSSL ca -gencrl -days $SA_EXPIRE -out "$CRL" -config "$KEY_CONFIG"
>> but that still generated a crl file for one month.
>
> Make that "-crldays $SA_EXPIRE"
Thanks, after fixing my own type ($CA_EXPIRE, not $SA_...) it works like
expected.
Now I have a crl file th
13 matches
Mail list logo
