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

    pfBlocker with GEO IP not block IPSEC

    IPsec
    2
    4
    871
    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
      Piter 0
      last edited by Piter 0

      I have configured firewall with GEO block for IPSEC.
      After all, in the IPSEC logs I see attempts to connect to addresses outside of geolocation, e.g.:

      Jan 4 07:18:18 charon 98918 03[NET] received unsupported IKE version 6.15 from 45.33.46.249, sending INVALID_MAJOR_VERSION

      Geolocation works properly, because I do not see blocked addresses on the list. The VPN alias ports are 500 and 4500. Where do these entries come from? Shouldn't the firewall cut them out?

      IPSEC Firewall rules:
      IPSEC.jpg
      WAN Firewall rules:
      WAN.jpg

      keyserK 1 Reply Last reply Reply Quote 0
      • keyserK
        keyser Rebel Alliance @Piter 0
        last edited by

        @piter-0 That depends on you having disabled the “built-in” rules that allows VPN Server access.
        By default pfSense has built-in rules to allow access to UDP 500, 4500 and ESP - these rules have a higher ppreference than user created rules.
        So if you want to GEO block access to your VPN service, you need to disable the built-in rules, and then create som “allow VPN rules” after your block rules.

        You can disable the built-in rules in SYSTEM->ADVANCED->FIREWALL&NAT

        Love the no fuss of using the official appliances :-)

        P 2 Replies Last reply Reply Quote 1
        • P
          Piter 0 @keyser
          last edited by

          @keyser Thanks, sounds reasonable. I'll test it when I have time :)

          1 Reply Last reply Reply Quote 0
          • P
            Piter 0 @keyser
            last edited by

            @keyser Works fine, thx :)

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