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

OpenVPN problem connect LAN

Scheduled Pinned Locked Moved OpenVPN
5 Posts 2 Posters 1.0k 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.
  • T
    tripperhat
    last edited by Jun 6, 2017, 9:54 AM

    Hi,

    I ask for help for configuring OpenVPN PfSense.

    My configuration is as follows:

    WAN ADSL -> SG-4860 Appliance (default gateway for lan)

    I have set up the VPN tunnel, I can connect without problems and ping the network's default gateway.

    My problem is that I can not ping the lan hosts.

    For example, if I run a ping at 192.168.2.250 (gw) it responds.
    If I try a ping or remote desktop connection to a 192.168.2.19 client does not work.

    What can it be?

    Thank you all

    tripper

    1 Reply Last reply Reply Quote 0
    • V
      viragomann
      last edited by Jun 6, 2017, 1:24 PM

      Check if the access is blocked by the remote device's firewall. Windows firewalls for instances block access from other subnets by default.

      1 Reply Last reply Reply Quote 0
      • T
        tripperhat
        last edited by Jun 6, 2017, 2:22 PM

        Hi,
        The client firewall is disabled.
        I entered the static route into the client to reach the OpenVPN network and connected.
        The question is: why? If I try to create routing configuration on pfsense I can not connect.

        1 Reply Last reply Reply Quote 0
        • V
          viragomann
          last edited by Jun 6, 2017, 3:35 PM

          This is only needed if the VPN server is not the default gateway on the client and it does also only make a difference in that case.
          But you've mentioned above the pfSense is the default GW in LAN. So one of these must be wrong.

          1 Reply Last reply Reply Quote 0
          • T
            tripperhat
            last edited by Jun 7, 2017, 9:17 AM

            Ok, problem solved. Client Gateway pointing to another firewall pfsense (I have two).

            thank you

            tripper

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