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

    Can't Get It Working

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    29 Posts 7 Posters 5.9k 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.
    • johnpozJ Offline
      johnpoz LAYER 8 Global Moderator
      last edited by

      So you want to BLOCK going anywhere but that lan segment?  That is what that rule would do.

      Post your lan rules so we can see exactly what other rules you have in place, etc.  That rule by itself would block everything but the lan segment.  So you would not be able to go to the internet..  Is that what your after?

      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 25.07.1 | Lab VMs 2.8, 25.07.1

      1 Reply Last reply Reply Quote 0
      • ? This user is from outside of this forum
        Guest
        last edited by

        Enter firewall block rules on the "LAN" or "OPT1" for port 80 and 443 from "LAN" or "OPT1" to "IP of ROUTER", then nobody can reach the interface from this LAN / OPT1

        1 Reply Last reply Reply Quote 0
        • stephenw10S Offline
          stephenw10 Netgate Administrator
          last edited by

          Hmm, that rule is definitely wrong. It will never (or should never) match any traffic as you will never see any packets going into the LAN interface that have source 'SERVER subnet'.

          What exactly are you trying to achieve?

          Steve

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

            I didn't even catch the server source ;)  Yeah that would never even trigger.

            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 25.07.1 | Lab VMs 2.8, 25.07.1

            1 Reply Last reply Reply Quote 0
            • B Offline
              bluegrass
              last edited by

              What I'm trying to do is keep the SERVER and LAN ports from being able to communicate with each other.

              I don't want anyone on my home network to accidently get access to my little web server and screw something up. And I don't want any traffic for the server getting onto my home network.

              1 Reply Last reply Reply Quote 0
              • B Offline
                bluegrass
                last edited by

                Ok I think I got it fixed. I looked in the 'Definitive Guide to PFSense' and it said: "Rules in PFSense are applied on a per-interface basis, always in the inbound direction on that interface. This means traffic initiated from the LAN is filtered using the LAN interface rules.Traffic initiated from the Internet is filtered with the WAN interface rules."

                So I changed the source on Server TO server and source on LAN to LAN and now the two ports don't appear to be able to access each other.

                1 Reply Last reply Reply Quote 0
                • stephenw10S Offline
                  stephenw10 Netgate Administrator
                  last edited by

                  Sounds good.
                  If you're in any doubt post up some screen shots of your rules.  :)

                  Steve

                  1 Reply Last reply Reply Quote 0
                  • B Offline
                    bluegrass
                    last edited by

                    Ok, here's the rules for my LAN and SERVER ports.

                    ![LAN Rules 2.JPG](/public/imported_attachments/1/LAN Rules 2.JPG)
                    ![LAN Rules 2.JPG_thumb](/public/imported_attachments/1/LAN Rules 2.JPG_thumb)
                    ![Server Rules 2.JPG](/public/imported_attachments/1/Server Rules 2.JPG)
                    ![Server Rules 2.JPG_thumb](/public/imported_attachments/1/Server Rules 2.JPG_thumb)
                    ![LAN Rules.JPG](/public/imported_attachments/1/LAN Rules.JPG)
                    ![LAN Rules.JPG_thumb](/public/imported_attachments/1/LAN Rules.JPG_thumb)
                    ![Server Rules.JPG](/public/imported_attachments/1/Server Rules.JPG)
                    ![Server Rules.JPG_thumb](/public/imported_attachments/1/Server Rules.JPG_thumb)

                    1 Reply Last reply Reply Quote 0
                    • stephenw10S Offline
                      stephenw10 Netgate Administrator
                      last edited by

                      Looks good, that should block all IPv4 traffic between the LAN and SERVER subnets.  :)
                      It won't block IPv6 traffic if you are using IPv6 at all. Change the TCP/IP version to 'any' if you want to block v6 too.

                      Steve

                      1 Reply Last reply Reply Quote 0
                      • B Offline
                        bluegrass
                        last edited by

                        Thanks for all the help.

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