Hi,

On 30/08/16 18:42, Bhushan Patil wrote:
Hi JJK, I tried lowering the 'ping' rate from 10 seconds to e.g. 5 seconds using
  keepalive 5 120
But still I can't ping to server on 10.8.0.6 from client.

You said
"This happens most often when a bad switch is used that is not able to handle UDP traffic or if a firewall is blocking traffic."
So tried following

 1. Stopped OpenVPN server
 2. on server nc -l -u 1194
 3. on client nc -u 10.1.2.12 1194

From above, I can communicate using UDP protocol from client to server in the same network. So does that means my network can handle UDP traffic ??

your network was already capable of setting up a UDP connection - otherwise the log files would not have shown anything. What remains to be seen is whether your network can *sustain* a UDP connection. Start your 'nc' example , let it sit for 3 minutes and then type something on either end.


I have also uploaded client-server logs with timestamp sync.
https://drive.google.com/open?id=0B_XxQm6n7m4la1VPczdoNXM2NGs

your config files look perfectly fine, BTW. And the log files show that both ends were able to read & write data - but for some reason the connection was reset anyways... I'm puzzled. I'm kinda hoping that the "nc+delay" test will show that there's a bad switch or router involved, otherwise I'm out of ideas.


HTH,

JJK

On Fri, Aug 26, 2016 at 12:59 PM, Jan Just Keijser <[email protected] <mailto:[email protected]>> wrote:

    Hi,

    On 25/08/16 18:10, Bhushan Patil wrote:
    I have uploaded all configuration and logs on
    /https://drive.google.com/drive/folders/0B_XxQm6n7m4la1VPczdoNXM2NGs
    <https://drive.google.com/drive/folders/0B_XxQm6n7m4la1VPczdoNXM2NGs>/

    careful examination of the log files shows that communications
    between the client and server break down after the initial
    connect. In the server log you can find

    WWWWRRWWWWWWWWWWWWWWWWWWWWWWWWWWThu Aug 25 11:50:45 2016 us=366024
    pi2/10.1.2.14:42992 <http://10.1.2.14:42992> [pi2] Inactivity
    timeout (--ping-restart), restarting


    which shows that the server is writing packets (W) but not
receiving any (R or r) - which eventually triggers the restart. This happens most often when a bad switch is used that is not able
    to handle UDP traffic or if a firewall is blocking traffic.

    If you have no control over the firewall or switches you could try
    lowering the 'ping' rate from 10 seconds to e.g. 5 seconds using
      keepalive 5 120


    HTH,

    JJK


    PS the timestamps are completely off when comparing the server and
    the client log - it is best to keep the clocks in sync. That makes
    it much easier to debug things like this.

    On Thu, Aug 25, 2016 at 9:34 PM, Bhushan Patil
    <[email protected] <mailto:[email protected]>> wrote:

        I don't see any errors or warnings in server logs. Attachment
        contain server, client side logs as well as configuration.

        On Wed, Aug 24, 2016 at 1:40 PM, Jan Just Keijser
        <[email protected] <mailto:[email protected]>> wrote:

            On 23/08/16 19:43, Bhushan Patil wrote:

            Yes, I am.

            On Jul 26, 2016 7:24 PM, "Alarig Le Lay"
            <[email protected] <mailto:[email protected]>> wrote:
            >
            > On Tue Jul 26 06:20:36 2016, [email protected]
            <mailto:[email protected]> wrote:
            > > In my office, I am trying to connect Raspberry Pi as
            a client to OpenVPN
            > > server(Ubuntu 14.04.3). When I try to connect client
            to server, I get
            > > following log on terminal
            > >
            > > *Initialization Sequence Completed*After this, when
            i ping to OpenVPN
            > > server (ping 10.8.0.1), I don't get reply.
            > > But if I change protocol to TCP then I can ping. Can
            anyone point me to
            > > right direction ?
            >


            without config files and more log output it is impossible
            to tell what is happening. Connect over UDP with the
            client with verbosity set to 5 (--verb 5)  and post
            anonymized client *and* server side log files. Also,
            check the server log for anything related to WARNING or
            ERROR.

            JJK





    
------------------------------------------------------------------------------


    _______________________________________________
    Openvpn-users mailing list
    [email protected]  
<mailto:[email protected]>
    https://lists.sourceforge.net/lists/listinfo/openvpn-users  
<https://lists.sourceforge.net/lists/listinfo/openvpn-users>




------------------------------------------------------------------------------


_______________________________________________
Openvpn-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openvpn-users

------------------------------------------------------------------------------
_______________________________________________
Openvpn-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openvpn-users

Reply via email to