Hello!
I didn't realize there's a new release, thanks for the info! I'm really
tempted to order a copy now.I see you use OpenVPN 2.4 in the book, do you
discuss the new tls-crypt feature in the book?
Kind regards,SaAtomic
3. Apr 2017 10:14 by janj...@nikhef.nl:
> > Hi,
>
>
Hi,
On 30/03/17 10:06, saato...@keemail.me wrote:
Hello!
Yes, I could "unix ping" the tunnel's server IP (e.g. ping -c 1 -W 2
-I tun0 172.16.0.1), but I haven't found a reliable way to
automatically identify the server's IP address yet.
The environmental variable $route_network_1 appears to
Hello!
Yes, I could "unix ping" the tunnel's server IP (e.g. ping -c 1 -W 2 -I tun0
172.16.0.1), but I haven't found a reliable way to automatically identify the
server's IP address yet.The environmental variable $route_network_1 appears to
be working for that only occasionally.
How could I
Hi,
On Wed, Mar 29, 2017 at 03:27:55PM +0200, saato...@keemail.me wrote:
> How can I confirm that the data channel is working correctly after
> "Initialization Sequence Completed" on the client?
"ping the server", like, with "unix ping"?
Send data over the data channel and see if something
Is there a way to verify if an established tunnel is actually working properly
on the client side?
For instance, if I connect to an OpenVPN server (ncp-disable on server &
client) using a different cipher on the client than on the server, the client
will connect and print:
Initialization
