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 be working for
that only occasionally.
How could I implement "sending data and checking the response"? I'd
need to get that working in an automated manner.
in theory the server does not need to have a VPN IP address - or the
server could be configured to block all access to it; if I were running
a VPN setup where paying customers are connecting this is exactly what
I'd do - I wouldn't want a rogue customer to attack my server.
Having said that, in 99.9% of the cases the server IP will always be
<subnet>.1 - which use cases are you trying to address in which this is
not the case?
HTH,
JJK
30. Mar 2017 09:00 by g...@greenie.muc.de <mailto:g...@greenie.muc.de>:
Hi,
On Wed, Mar 29, 2017 at 03:27:55PM +0200, saato...@keemail.me
<mailto: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 useful comes
back.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users
