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

Hosts behind OpenVPN (Local LAN) do not connect across OpenVPN client (Remote LAN) connection

Scheduled Pinned Locked Moved OpenVPN
5 Posts 2 Posters 699 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.
  • V
    vitormazuco
    last edited by Aug 24, 2021, 3:41 PM

    Hi, I have an OpenVPN server on PfSense and a local LAN of 192.168.48.0/20. And I have an openvpn client (configured with Mikrotik on it) with a remote LAN network 10.0.119.0/24

    The connection has been established, and I can connect from my Remote LAN 10.0.119.0/24 > to the 192.168.48.0/20 LAN network successfully, but if I start from any host on the 192.168.48.0/20 LAN (except by Pfsense that this with the 192.168.50.1 network, it cannot ping or any other type of connection.

    See the images below:

    Pfsense-Lan.png

    Local-LAN.png

    This problem happened after my Dynamic DNS (dyndns) had to change Public IP due to a link drop

    It seems that the hosts behind Pfsense are not able to enforce the remote LAN IP's from OpenVPN.

    traceroutepfsense.png

    Captura de tela de 2021-08-24 12-39-08.png

    Would it be a problem to update internal routes on my LAN that are not leaking?

    And remembering that only one of the clients is working correctly, by showing the letter C marking "An IP address followed by C indicates a host currently connected through the VPN."

    V 1 Reply Last reply Aug 24, 2021, 3:49 PM Reply Quote 0
    • V
      viragomann @vitormazuco
      last edited by Aug 24, 2021, 3:49 PM

      @vitormazuco
      Seems the Mikrotik is blocking the remote LAN.

      When you're able to access LAN devices in 192.168.48.0/20 from 10.0.119.0/24 devices the routes must be ok.

      V 1 Reply Last reply Aug 24, 2021, 4:16 PM Reply Quote 0
      • V
        vitormazuco @viragomann
        last edited by vitormazuco Aug 24, 2021, 4:58 PM Aug 24, 2021, 4:16 PM

        @viragomann

        hello, already disabled all firewall rules and it doesn't work anyway. This problem only appeared after changing the public IP of dyndns

        V 1 Reply Last reply Aug 24, 2021, 4:40 PM Reply Quote 0
        • V
          viragomann @vitormazuco
          last edited by Aug 24, 2021, 4:40 PM

          @vitormazuco
          You will also have to enable forwarding of the remote network or something like that on the Mikrotik.

          V 1 Reply Last reply Aug 24, 2021, 4:59 PM Reply Quote 0
          • V
            vitormazuco @viragomann
            last edited by Aug 24, 2021, 4:59 PM

            @viragomann Yes, This problem only appeared after changing the public IP of dyndns. Absolutely nothing was changed, just changed the DynDNS IP

            1 Reply Last reply Reply Quote 0
            2 out of 5
            • First post
              2/5
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
              This community forum collects and processes your personal information.
              consent.not_received