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

    Critique my design, please?

    Scheduled Pinned Locked Moved General pfSense Questions
    19 Posts 12 Posters 2.4k 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.
    • J
      jsaad
      last edited by

      I've changed it to POINT_OF_SALE.

      The camera system is a single windows computer (analog cameras) and there are only 2 other windows computers.

      This is an effort at PCI compliant solution that requires the point of sale equipment on the network to be isolated. obviously other measures need to be taken on the actual PCs and point of sale equipment.

      1 Reply Last reply Reply Quote 0
      • T
        tim.mcmanus
        last edited by

        I would have left it as POS, the rest of these nerds be damned!  I support POS installations, both kinds.

        1 Reply Last reply Reply Quote 0
        • J
          jsaad
          last edited by

          We've set this up.  Customer wants to print to a LAN printer on the POS_NETWORK from the STAFF_NETWORK.

          However If I open up firewall rules to allow for windows printing 137-139 and 445. won't that defeat the purpose of separate networks?  Won't it be wide open, then?

          Can the firewall rules allow specific ports to a specific IP address?

          1 Reply Last reply Reply Quote 0
          • P
            phil.davis
            last edited by

            Make sure the printer has a known static IP in LAN. Then add a firewall rule on POS to pass source POSnet destination Printer-IP ports 137-139,445
            It is easy if you make an alias "LANprinters" for the IP of the LAN printer - then you can add to that when another printer appears. And make a ports alias for the list of ports that need to be open to the printer.

            As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
            If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

            1 Reply Last reply Reply Quote 0
            • D
              doktornotor Banned
              last edited by

              137-139 and 445 is not for printing. It's for the crappy network browsing. Really cannot see how's this needed? Just point the damned printing to an FQDN or IP of the printer.

              1 Reply Last reply Reply Quote 0
              • MikeV7896M
                MikeV7896
                last edited by

                Printer ports would be 9100 TCP for HP JetDirect or 515 TCP for LPR/LPD. As mentioned, the other ports mentioned in this topic are for Windows networking (NetBIOS, SMB, etc.).

                The S in IOT stands for Security

                1 Reply Last reply Reply Quote 0
                • K
                  kejianshi
                  last edited by

                  Is your POS pfsense rig working ok?

                  1 Reply Last reply Reply Quote 0
                  • J
                    jsaad
                    last edited by

                    ok, great advice. thanks! enjoy the weekend!

                    1 Reply Last reply Reply Quote 0
                    • DerelictD
                      Derelict LAYER 8 Netgate
                      last edited by

                      We've set this up.  Customer wants to print to a LAN printer on the POS_NETWORK from the STAFF_NETWORK.

                      I would put the printer on the LAN network and make firewall rules so the POS stations could print to the printer on LAN instead of punching holes in the firewall in the other direction from LAN (unprotected) to POS (protected)..

                      My LAN rule would be:

                      reject any source any dest POS Net

                      I would also make the two networks more random and contained in one subnet, say (staying in 10/8 which is ill-advised to begin with):

                      10.67.234.0/24
                      10.67.235.0/24

                      Then the site can be referenced with a single /23.

                      Chattanooga, Tennessee, USA
                      A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                      DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                      Do Not Chat For Help! NO_WAN_EGRESS(TM)

                      1 Reply Last reply Reply Quote 0
                      • J
                        jsaad
                        last edited by

                        @kejianshi:

                        Is your POS pfsense rig working ok?

                        Runs good. Ordered another!

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