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

    Particular computer not accessible through OpenVPN tunnel

    Scheduled Pinned Locked Moved OpenVPN
    4 Posts 3 Posters 586 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.
    • P Offline
      Pontiac_CZ
      last edited by

      I set up my first OpenVPN instance on our pfSense (inspired by this video - https://www.youtube.com/watch?v=xiy52Hn5bTc)

      • tunnel network 10.0.15.0/24
      • local network 10.0.0.0/24
      • I assigned OPT3 interface to this OpenVNP instance, restarted OpenVPN service afterwards
      • deleted the default pass rule from "OpenVPN" firewall tab, created it in "OPT3" tab instead

      Test connection works, the test laptop was assigned 10.0.15.2, routes were created. I could ping devices in 10.0.0.0/24 - like 10.0.0.1, 10.0.0.6 or 10.0.0.39 (my PC). The only one I cannot ping is 10.0.0.118 (which actually is the one I set up VPN for).

      But I can ping 10.0.0.118 from my PC (10.0.0.39) at the same time.

      What could I have wrong?

      1 Reply Last reply Reply Quote 0
      • V Offline
        viragomann
        last edited by

        Maybe 10.0.0.118 blocks access from the VPN tunnel subnet. Check the firewall of that device.

        1 Reply Last reply Reply Quote 0
        • johnpozJ Offline
          johnpoz LAYER 8 Global Moderator
          last edited by

          Yup viragomann hit on the most likely problem.  Firewall on device not like traffic from other than local segment.  Windows out of the box firewall will block ping from outside its own segment for example.

          Other possible and common reason is device your trying to reach not using pfsense as its gateway.  So there is no way for it to even answer if it wanted too.  Have seen say IP camera's not have a way to set a gateway even..  So without source natting the traffic at pfsense its not possible to talk to them from other segments.

          An intelligent man is sometimes forced to be drunk to spend time with his fools
          If you get confused: Listen to the Music Play
          Please don't Chat/PM me for help, unless mod related
          SG-4860 24.11 | Lab VMs 2.8, 24.11

          1 Reply Last reply Reply Quote 0
          • P Offline
            Pontiac_CZ
            last edited by

            Looks like that was it. The box with 10.0.0.118 was provided by out external supplier and when first connecting it to our network, they chose "public network" (for whatever reason). I changed it to "home network" and I can ping it now as well as connect to RDP. I can sure tune the Win 7 firewall in advanced settings but it is good for now.

            Gateway is okay, the PC got its IP from our DHCP server.

            Thank you, guys!  :)

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