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

    IPSec works between sites.. but not for PfSense

    Scheduled Pinned Locked Moved IPsec
    3 Posts 2 Posters 953 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.
    • G
      gonzague
      last edited by

      Hi!
      So basically, not a very complicated setup
      my PfSense VM works very well and has two network interfaces
      LAN : 192.168.200.0/24  => and the IP of pfsense is 192.168.200.1
      WAN : with its public IP

      I have two IPSec Site to Site setup .. :
      one to 192.168.0.0/24
      one to 192.168.1.0/24

      My problem is as follows: both site to site are perfectly fine , from 192.168.200.0 i can access 192.168.0.X and 1.X .. and vice versa
      BUT… If i try to ping one of the devices that in 192.168.0.X .. actually the unit i wanna ping is 192.168.0.103.. from pfSense (Diagnostics menu => Ping and its default settings), it fails until i select the LAN interface instead of "default"

      This reflects on the whole pfsense system: I wanted to use Active directory (reachable at 192.168.0.103) to authenticate my mobile VPN users etc but the pfSense VM wont speak to 192.168.0.103 unless I create a route for 192.168.0.0/24 going through 192.168.200.1

      So far that would be okay but when i create that route, then the hosts in 192.168.0.0/24 can only reach 192.168.200.1 and nothing else anymore.

      Any clue of what I might be doing wrong? I'd just like to be able to ping and communicate with devices on 192.168.0.X from my pfsense .. but i think when i try to reach 192.168.0.X from it, it doesnt use the right interface.

      Any ideas are welcome :)

      thanks a lot!

      1 Reply Last reply Reply Quote 0
      • C
        cmb
        last edited by

        https://doc.pfsense.org/index.php/Why_can't_I_query_SNMP,_use_syslog,_NTP,_or_other_services_initiated_by_the_firewall_itself_over_IPsec_VPN

        1 Reply Last reply Reply Quote 0
        • G
          gonzague
          last edited by

          @cmb:

          https://doc.pfsense.org/index.php/Why_can't_I_query_SNMP,_use_syslog,_NTP,_or_other_services_initiated_by_the_firewall_itself_over_IPsec_VPN

          Hi, thanks CMB .. Thats what I did as I think I explained .. :)

          So it doesnt really work because when I create the static routes, it works for my pfsense box and the Active Directory interfacing i want but the machines on the distant network  side cant use the VPN anymore

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