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

    Why are my VLANs not isolated?

    Firewalling
    3
    6
    398
    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.
    • R
      Roy360
      last edited by Roy360

      I have a few VLAN setup on my network.

      192.168.1.0 for LAN
      192.168.20.0 for Guest
      192.168.30.0 for IOT
      192.168.40.0 for IPCameras (this should have no access to the Internet)

      Aside for a few exceptions (which I will define using alias) I want traffic to be segregated by the VLAN they are in.

      Here's how my rules are setup:
      LAN
      91e4242a-c366-4fb8-8f98-1303d03610ea-image.png
      Guest
      a3a4d7d1-1090-4892-81b4-137cfe1c1ed0-image.png
      IOT
      60d026a4-820e-450b-8612-cd6f8c5e975c-image.png
      IPCameras
      94f179bf-742a-4934-b747-9bb0dccb60d2-image.png

      However I don't think I did this correctly as clients on the LAN are able to access the IP cameras despite "IPcameraViewers" being empty.
      Ie. I can access 192.168.40.11 's webui from 192.168.1.22

      J johnpozJ 2 Replies Last reply Reply Quote 0
      • J
        Jarhead @Roy360
        last edited by Jarhead

        @Roy360 You're not blocking LAN to CAMERAS anywhere I see. Just the CAMERA address is blocked.
        Why do you have an OPENVPN CLIENT rule on your LAN?
        You also have some redundant rules that will never trigger and aren't needed.

        R 1 Reply Last reply Reply Quote 1
        • johnpozJ
          johnpoz LAYER 8 Global Moderator @Roy360
          last edited by johnpoz

          @Roy360 said in Why are my VLANs not isolated?:

          IP cameras despite "IPcameraViewers" being empty.

          Rules are evaluated top down, first rule to trigger wins and no other rules are evaluated. If you only want Ips that are in your alias to be allowed to camera network, then below where you allow that, and before your any any rule at the bottom for internet you would need to block it, or it will fall thru all the rules until it gets to your any rule and be able to get to the camera vlan, because that rule allows any.

          Notice as @Jarhead mentioned, your reject there is to camera address, not the whole subnet.

          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 24.11 | Lab VMs 2.7.2, 24.11

          1 Reply Last reply Reply Quote 0
          • R
            Roy360 @Jarhead
            last edited by Roy360

            @Jarhead said in Why are my VLANs not isolated?:
            > @Roy360 You're not blocking LAN to CAMERAS anywhere I see. Just the CAMERA address is blocked.

            Why do you have an OPENVPN CLIENT rule on your LAN?
            You also have some redundant rules that will never trigger and aren't needed.

            That's embarrassing. I didn't see that.
            I think the fixed up the LAN (and moved the rules in the correct order)
            I can no longer access Camera subnet from LAN anymore unless they are defined in the alias.
            f4a8a939-2ed8-4491-96d8-b92bbb7384ce-image.png

            The OpenVPN rule is there so certain LAN clients go through it. Is that not how you do it? I just followed a dated guide on Reddit.
            https://www.reddit.com/r/PFSENSE/comments/6edsav/how_to_proper_partial_network_vpn_with_kill_switch/

            Can you point out one of the redundant rules? (unless you meant the duplicated ones, Not sure how that happened, but I removed those)

            johnpozJ J 2 Replies Last reply Reply Quote 0
            • johnpozJ
              johnpoz LAYER 8 Global Moderator @Roy360
              last edited by

              @Roy360 those look better from a quick glance - you could prob just create alias for rfc1918 address space so that those 3 rules would be come 1 rule..

              Here is example of locked down network, that prevents this vlan from going to any of my other vlans. Nice about using an alias with all rfc1918 space in, if I add another vlan its auto covered..

              alias.jpg

              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 24.11 | Lab VMs 2.7.2, 24.11

              1 Reply Last reply Reply Quote 1
              • J
                Jarhead @Roy360
                last edited by

                @Roy360 Yeah, I meant the duplicates, which is what that OpenVPN client rule was, but that's gone now.
                Most people do what John suggested as to the RFC 1918 Alias, it really makes life easier in the long run.

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