Navigation

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

    Print from OPT1 to LAN printer

    Installation and Upgrades
    3
    33
    84
    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.
    • johnpoz
      johnpoz LAYER 8 Global Moderator last edited by johnpoz

      With that rule removed, then all your other rules are pointless between the anti lockout and your any any. So why have them if they don't do anything?

      To work out what rules you need, just come up with your traffic pattern.

      say 10.10.10.X wanting to talk to IP:port

      Now walk down your rules - is it allowed, or blocked? In your case the last rule would allow it, and no other rule above that would block it - so its allowed.

      5 1 Reply Last reply Reply Quote 0
      • 5
        5cub4f1y last edited by

        Ok so the rules filter DOWN...as in, if the bottom rule allows EVERYTHING, then that overrides any rules above it that allow or deny anything? So If I did want to block something, then I need to have the Allow any/any as the very top rule (under the anti-lockout)?

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

          @johnpoz said in Print from OPT1 to LAN printer:

          Rules are evaluated top down, as traffic enters an interface, first rule to match wins, no other rules evaluated.

          Yup.. as I already stated ;) and is in the docs on how rules are evaluated, etc.
          https://docs.netgate.com/pfsense/en/latest/firewall/firewall-rule-processing-order.html

          So If I did want to block something, then I need to have the Allow any/any as the very top rule (under the anti-lockout)?

          Not always.. Maybe you want to log something specific, say you wanted to log when something on the lan accesses your plex server sitting on opt.. Then you could put a rule above the any any that logs that specific traffic.

          Or maybe you want to policy route some specific traffic out a specific gateway, which again you would put above your any any, etc. Or maybe you wanted to mark some specific traffic, or maybe you wanted to redirect something.. There are more things to do with rules then just allow or block.

          1 Reply Last reply Reply Quote 0
          • 5
            5cub4f1y last edited by

            But if I put the Allow any any above any blocking rules, then wouldn't the firewall see that I have allowed anything and not go any further?

            1 Reply Last reply Reply Quote 0
            • 5
              5cub4f1y last edited by

              This post is deleted!
              1 Reply Last reply Reply Quote 0
              • johnpoz
                johnpoz LAYER 8 Global Moderator last edited by johnpoz

                Yes.. I never said anything about putting block rules below your any.. Block rules would need to be above a rule that allows any..

                1 Reply Last reply Reply Quote 0
                • 5
                  5cub4f1y @johnpoz last edited by

                  @johnpoz said in Print from OPT1 to LAN printer:

                  In your case the last rule would allow it, and no other rule above that would block it - so its allowed.

                  This is what confused me. I see that and think that because the any any is on the bottow, everything above it is ignored..

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

                    You didn't have any block rules - you only had allow rules!!

                    Dude... This is not difficult... Come up with your traffic pattern that you want to do something with.. Now walk down your rules top to bottom.. What rule triggers? On that traffic pattern - that is what happens... Once you hit a rule that matches, stop looking at any othe rules.

                    If you get to the bottm and and no rules match, then it would be blocked! Default Deny, if rule does not allow it.

                    1 Reply Last reply Reply Quote 0
                    • 5
                      5cub4f1y last edited by

                      Got it. So should the LAN have any blocking on it at all? Or just basically have the anti-lockout, and the allow any/any. (I am talking about my network only, where I want the LAN to be able to access anything on OPT1, and the internet..and anything on OPT1 to access the internet, but only the printer on LAN)

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

                        @5cub4f1y said in Print from OPT1 to LAN printer:

                        Got it. So should the LAN have any blocking on it at all? Or just basically have the anti-lockout, and the allow any/any

                        Depends - do you want to block your lan from doing anything? Here are my lan rules

                        mylanrules.png

                        I split the IPv4 and IPv6 because sometimes I might block IPv6, etc.

                        5 1 Reply Last reply Reply Quote 0
                        • 5
                          5cub4f1y last edited by

                          No. Not that I can think of. Since I control all the devices on LAN (patch managment, security updates etc...) I am not as worried about vulnerabilities as I am with everything else on OPT1

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

                            If you have questions if your rules will do what you want.. Just come up with the example traffic pattern of what you want to do something with, and just walk down the rules to see what will happen.

                            1 Reply Last reply Reply Quote 0
                            • 5
                              5cub4f1y @johnpoz last edited by

                              @johnpoz Ah thank you. Thats what I now have.

                              A 1 Reply Last reply Reply Quote 0
                              • A
                                akuma1x @5cub4f1y last edited by

                                @5cub4f1y said in Print from OPT1 to LAN printer:

                                @johnpoz Ah thank you. Thats what I now have.

                                Let's see, let's see!

                                1 Reply Last reply Reply Quote 0
                                • 5
                                  5cub4f1y last edited by

                                  LAN

                                  Annotation 2020-08-24 170730.png

                                  OPT1 I'm still figuring out, following the logic to see if these rules will do what I want them to do. Which is essentially NOT allowing OPT1 to access anything on LAN, except the printer. Still looks like this...

                                  Annotation 2020-08-24 170938.png

                                  A 1 Reply Last reply Reply Quote 0
                                  • A
                                    akuma1x @5cub4f1y last edited by

                                    @5cub4f1y Yep, those rules look good. You might need a port number on rule number 3 on your OPT1 network, but probably not. Can you print something thru this rule, does it work?

                                    Jeff

                                    1 Reply Last reply Reply Quote 0
                                    • 5
                                      5cub4f1y last edited by

                                      Yes the printer works from OPT1 hosts. I'm starting to wonder if having the printer on the LAN network makes the LAN network more vulnerable...might be easier to just put the printer on the OPT1 network since the LAN net can access anything there anyway?

                                      A 1 Reply Last reply Reply Quote 0
                                      • A
                                        akuma1x @5cub4f1y last edited by akuma1x

                                        @5cub4f1y Yeah, that's generally how to keep your "trusted" LAN network secure, don't let much of anything in like that. However, you are only allowing access to one IP address for one device, a printer, so it should be ok. Just keep the firmware on the printer up-to-date.

                                        You're not like sitting next to North Korea or China, or Russia or anything, right? Somewhere with a whole lot of hacker/crackers? If not, and you trust most of your OPT1 hosts, you kinda can leave it the way you've got it right now - OPT1 access to the printer on LAN.

                                        What I would make sure to do, however, is to put a REALLY good wifi password on your Orbi Mesh stuff. keep the firmware on it up-to-date. And maybe refresh/reset the password say every 2-3 months. Just to keep the bad guys out...

                                        Jeff

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

                                          @5cub4f1y said in Print from OPT1 to LAN printer:

                                          I'm starting to wonder if having the printer on the LAN network makes the LAN network more vulnerable

                                          Well the security question aside.. Sometimes it easier to just put the printer where its used most and how.. I have my printer on my wlan network, because it allows for the airprint to work.. And I can print from the lan without any issues, because don't use airprint from my wired lan network.

                                          1 Reply Last reply Reply Quote 0
                                          • 5
                                            5cub4f1y last edited by

                                            Great! Thank you guys! I'm understanding how this works a little better. I am learning networking and cybersecurity so I am wanting to eventually set this up so I can have a separate network/VLAN for a home lab, but that is later. Right now I just wanted to understand pfSense enough to not knock my wife off the internet...lol

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Products

                                            • Platform Overview
                                            • TNSR
                                            • pfSense
                                            • Appliances

                                            Services

                                            • Training
                                            • Professional Services

                                            Support

                                            • Subscription Plans
                                            • Contact Support
                                            • Product Lifecycle
                                            • Documentation

                                            News

                                            • Media Coverage
                                            • Press
                                            • Events

                                            Resources

                                            • Blog
                                            • FAQ
                                            • Find a Partner
                                            • Resource Library
                                            • Security Information

                                            Company

                                            • About Us
                                            • Careers
                                            • Partners
                                            • Contact Us
                                            • Legal
                                            Our Mission

                                            We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

                                            Subscribe to our Newsletter

                                            Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

                                            © 2021 Rubicon Communications, LLC | Privacy Policy