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

    Simple FW rule not being matched

    Scheduled Pinned Locked Moved General pfSense Questions
    6 Posts 4 Posters 583 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
      Justin53
      last edited by

      I have a pfSense 23.05.1 VM with attached vSphere distributed port group interface set to "VLAN" mode with the appropriate VLAN ID.

      In pfSense this is configured as a interface and the static IP is assigned to it. I created a simple rule on the interface allowing any IPv4 traffic from the "_net" to "_net":
      99be9386-94a8-4ac4-b972-74af8a6dc2c0-brave_2023-11-02_13-50-39.png

      yet if I do a test connection from one VM to another VM both using the same distributed port group obviously for port 445 I can see it hits the default deny rule:
      4556eb56-f1bd-4bbb-afe4-0207e05b3fdd-brave_2023-11-02_13-51-27.png

      Anyone have any ideas why it's not matching? both IPs are within the subnet assigned to the interface and part of the aliased default _net group.

      V 1 Reply Last reply Reply Quote 0
      • V
        viragomann @Justin53
        last edited by viragomann

        @Justin53
        Most probably because of this

        both IPs are within the subnet assigned to the interface

        Traffic between devices in the same network segment doesn't pass the router as long as they are not connected to different bridged network ports.

        Not clear, why this traffic should even pass pfSense in either direction, but the blocks in the log concerns reply packets. So obviously pfSense has no state for it, because it didn't see the initial SYN packet.
        Seems there is something wrong in your network setup. But need more info to get closer.

        J 1 Reply Last reply Reply Quote 1
        • J
          Justin53 @viragomann
          last edited by Justin53

          @viragomann Good point strange why the response traffic was picked up but the initial connection was not. It's very basic setup here just a distributed port group with VLAN ID attached to it with the interface mapped in pfSense. Both machines have the default gateway set to the static IP in pfSense.

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

            @Justin53 why pfsense is only seeing the return, ie SA screams asymmetrical traffic...

            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.8, 24.11

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

              Yup one of those hosts probably has the wrong subnet mask set so is sending replies to it's gateway (pfSense) incorrectly.

              J 1 Reply Last reply Reply Quote 0
              • J
                Justin53 @stephenw10
                last edited by

                @stephenw10 this was exactly it thank you! one of the VMs was not on /24 immediately fixed after correcting it

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