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

    Site-to-Site restrict Site A from accessing something on Site B

    Scheduled Pinned Locked Moved OpenVPN
    2 Posts 1 Posters 516 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
      vinneo
      last edited by

      Site A:
      Interfaces: WAN, LAN (10.1.0.0/24), VPN, OpenVPN
      Client: 10.1.0.1/24;

      Site B:
      Interfaces: WAN, LAN (10.2.0.0/24), VPN, OpenVPN
      Server: 10.2.0.1/24;

      I want to block Client 10.1.0.1 from accessing Server 10.2.0.1, how can I do this without adding any firewall rules to Site A? My problem is I don't understand the difference between the default OpenVPN interface of pfsense, and the custom interface if you add the ovpnc1? I though traffic from Site A will arrive at Site B in the "VPN (ovpnc1)" interface and I can block it there but It goes straight to LAN.

      VPN1.png
      VPN1.png_thumb
      VPN2.png
      VPN2.png_thumb

      1 Reply Last reply Reply Quote 0
      • V
        vinneo
        last edited by

        Update:
        Okay, I got this far that firewall rules added to the default OpenVPN interface work (i.e. drop all traffic from client 10.1.0.1 on Site B firewall), but if I add the same rule to the ovpnc1 (VPN) interface nothing happens. What is the purpose of adding ovpnc1 if firewall rules applied to it don't work?

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