Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Clients cannot communicate with each other.

    Scheduled Pinned Locked Moved OpenVPN
    42 Posts 8 Posters 7.1k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      scilek
      last edited by

      This morning, knowing that there would very little or no need to access the Internet, I decided to remotely configure all the three routers from scratch. I removed all the static routes and then the clients and servers. After that, I redefined OpenVPN servers and then the clients. But this time, I rebooted the routers after I configured them, which I had not done previously as the users could not afford even a minute of downtime. After each reboot, the VPN routes appeared to be offline for about 20 seconds or so, then got online and then I was able to connect to remote networks. So it appears that the OpenVPN was not to blame after all.

      I think settles the matter for good. I have learned through hardship that it is a good idea to reboot your router after configuring router OpenVPN clients/servers and deploy them only when you know you have configured them properly. This was my first VPN job, so I think I am entitled to making mistakes.

      DerelictD 1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate @scilek
        last edited by Derelict

        @scilek said in Clients cannot communicate with each other.:

        I have learned through hardship that it is a good idea to reboot your router after configuring router OpenVPN clients/servers

        A reboot is not necessary. Only stating this so future readers will know.

        Glad you got past whatever problem it is you were having.

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.