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

    Problem...Graph Shows Traffic Crossing VLANs

    Scheduled Pinned Locked Moved General pfSense Questions
    17 Posts 7 Posters 1.5k Views 7 Watching
    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 Online
      johnpoz LAYER 8 Global Moderator
      last edited by

      @ARAMP1 said in Problem...Graph Shows Traffic Crossing VLANs:

      That rule is there to allow all traffic from VLAN5 to access VLAN3

      Doesn't work that way!!! If you want vlan 3 to talk to vlan 5, then the rule would be on vlan 3 interface with vlan 5 ad the dest.. Vlan 5 could never be a source into vlan 3 interface.

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

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

        And what are you trying to do with the pass rules for ! CAMERAS?

        Put the reject rule for source CAMERAS above those and just pass to any after that.

        But either way, it's VLAN1 that I'm wondering about and why it every so often will randomly mirror VLAN3 in the traffic graph. I just reset pfSense and it's back to normal.

        Something on LAN3 sending to something on LAN1? If the port matches the Allowed_OUT_Ports_WAN alias, it will be passed to LAN1 destinations because you are not blocking those.

        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)

        N ARAMP1A 4 Replies Last reply Reply Quote 0
        • N Offline
          negarestan @Derelict
          last edited by

          how can put this .

          1 Reply Last reply Reply Quote 0
          • ARAMP1A Offline
            ARAMP1 @johnpoz
            last edited by ARAMP1

            @johnpoz said in Problem...Graph Shows Traffic Crossing VLANs:

            @ARAMP1 said in Problem...Graph Shows Traffic Crossing VLANs:

            That rule is there to allow all traffic from VLAN5 to access VLAN3

            Doesn't work that way!!! If you want vlan 3 to talk to vlan 5, then the rule would be on vlan 3 interface with vlan 5 ad the dest.. Vlan 5 could never be a source into vlan 3 interface.

            Yeah. I actually had the same rule over in VLAN5's rules. I went ahead and deleted it under VLAN3. Appreciate you pointing it out.

            1 Reply Last reply Reply Quote 0
            • ARAMP1A Offline
              ARAMP1 @Derelict
              last edited by ARAMP1

              @Derelict said in Problem...Graph Shows Traffic Crossing VLANs:

              And what are you trying to do with the pass rules for ! CAMERAS?

              All the pass rules for for invert match CAMERAS, so it should pass those rules for everything but the cameras, correct? Basically, I want to allow my Blue Iris computer to access to WAN and DNS without allowing the cameras.

              The only pass rule I have for the whole net is for port 123 to allow the cameras to have access to NTP.

              Put the reject rule for source CAMERAS above those and just pass to any after that.

              I'll rewrite.

              But either way, it's VLAN1 that I'm wondering about and why it every so often will randomly mirror VLAN3 in the traffic graph. I just reset pfSense and it's back to normal.

              Something on LAN3 sending to something on LAN1? If the port matches the Allowed_OUT_Ports_WAN alias, it will be passed to LAN1 destinations because you are not blocking those.

              Looking at my Allowed_OUT_Ports_WAN alias list now. Thanks.

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

                Its real simple to figure out what will pass and what will not..

                You know the source, you know the dest and port..

                Walk down your rules from the top on the interface the source is going to first hit pfsense on.. So vlan 3 device, on vlan 3, if vlan 1 device then vlan 1..

                To down walk through your rules.. First rule to trigger wins, no other rules are evaluted.. If you get through all the rules - and nothing passed it then the the default deny will block it.

                Your inverse camera rules, the top 3 have zero hits on them..

                Seems odd to be honest that you let cameras do anything your 5th rule, but non cameras can only go use specific ports and dns?

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

                1 Reply Last reply Reply Quote 0
                • ARAMP1A Offline
                  ARAMP1 @Derelict
                  last edited by ARAMP1

                  @Derelict said in Problem...Graph Shows Traffic Crossing VLANs:

                  Put the reject rule for source CAMERAS above those and just pass to any after that.

                  Maybe I'm not looking at this right. Will this work for my first rule? Block cameras from all except port 123.

                  Camera Rules.jpg

                  Might need to set this aside for a bit and then come back to it.

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

                    Don't check invert match. That checkbox is, in my opinion, almost never the proper solution and there is almost always a more positive, easier to understand rule set that can be created.

                    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)

                    ARAMP1A 1 Reply Last reply Reply Quote 0
                    • ARAMP1A Offline
                      ARAMP1 @Derelict
                      last edited by

                      How do I block everything except NTP? Use two separate rules?

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

                        pass NTP. Block everything else.

                        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 1
                        • N Offline
                          negarestan @Derelict
                          last edited by

                          @derelict Thanks Anyway.

                          N 1 Reply Last reply Reply Quote 0
                          • N Offline
                            negarestan1 @negarestan
                            last edited by negarestan1

                            @negarestan Thank you very much.

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