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

    Blocking specific host on LAN from accessing remote IPSec networks

    Scheduled Pinned Locked Moved Firewalling
    4 Posts 2 Posters 338 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.
    • C
      chris.ett
      last edited by

      I want to block a specific host on the local network from accessing the remote networks on the other end of my site-to-site IPSec VPNs. The first thing I tried is to add the following rule under Firewall>Rules>IPSec:

      • Action: Reject
      • Interface: IPSec
      • Address Family: IPv4
      • Protocol: any
      • Source: 172.20.0.100
      • Destination: any

      This did not work, so I edited the rule and moved the host IP from Source to Destination. This did not work either.

      I then tried adding a rule under Firewall>Rules>LAN:

      • Action: Reject
      • Interface: LAN
      • Address Family: IPv4
      • Protocol: any
      • Source: 172.20.0.100
      • Destination: (alias) MyRemoteNetworks

      This rule achieved the desired result. This is fine... However I would like to understand why it did not work when I put the rule on the IPSec interface (group?).

      N 1 Reply Last reply Reply Quote 0
      • N
        netblues @chris.ett
        last edited by

        @chris-ett Simply because rules are applied on the interface packets arrive.

        1 Reply Last reply Reply Quote 1
        • C
          chris.ett
          last edited by

          @netblues Okay, simple enough. To clarify, does that mean I would use rules on the IPSec interface group when I want to allow/block traffic coming from the remote networks?

          N 1 Reply Last reply Reply Quote 0
          • N
            netblues @chris.ett
            last edited by

            @chris-ett Absolutely.
            On ipsec, you also have the possibility to"protect" ie allow networks, but thats an ipsec feature only.

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