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

    New Vlan and Default deny rule IPv4

    Scheduled Pinned Locked Moved Firewalling
    16 Posts 3 Posters 909 Views 3 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.
    • R Offline
      ricbjo @michmoor
      last edited by

      @michmoor Hi, No I cannot ping from the client to the gateway(pfsense) but from the pfsense I can ping the clients.
      I agree, something is most likely misconfigured. But I haven't been able to find where.
      Looking at the arp cache, the client finds the pfsense and the firewall log say Deny:
      vlan13f.png

      Client ipconfig
      vlan13e.png

      M S 2 Replies Last reply Reply Quote 0
      • M Offline
        michmoor LAYER 8 Rebel Alliance @ricbjo
        last edited by

        @ricbjo Do you have floating rules? This seems like a floating rule being hit which would make sense as thats first and then interface rules.

        Firewall: NetGate,Palo Alto-VM,Juniper SRX
        Routing: Juniper, Arista, Cisco
        Switching: Juniper, Arista, Cisco
        Wireless: Unifi, Aruba IAP
        JNCIP,CCNP Enterprise

        R 1 Reply Last reply Reply Quote 0
        • S Offline
          SteveITS Rebel Alliance @ricbjo
          last edited by

          @ricbjo try reloading the rules:
          https://docs.netgate.com/pfsense/en/latest/troubleshooting/firewall.html#new-rules-are-not-applied

          Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
          When upgrading, allow 10-15 minutes to reboot, or more depending on packages, and device or disk speed.
          Upvote ๐Ÿ‘ helpful posts!

          R 2 Replies Last reply Reply Quote 0
          • R Offline
            ricbjo @michmoor
            last edited by

            @michmoor Only the pfBlock and it doesn't seem to have any traffic logged on them. I haven't really started using it.

            vlan13g.png

            I'm planning on doing a restart.

            1 Reply Last reply Reply Quote 0
            • R Offline
              ricbjo @SteveITS
              last edited by

              @SteveITS Did a reload, no errors and no difference. And one of my issues is that incoming ISAKMP and that was one of the earlier things I set up.

              1 Reply Last reply Reply Quote 0
              • R Offline
                ricbjo @SteveITS
                last edited by

                @SteveITS Sorry, there was an error:
                -There were error(s) loading the rules: /tmp/rules.debug:35: cannot define table bogonsv6: Cannot allocate memory - The line in question reads [35]: table <bogonsv6> persist file "/etc/bogonsv6"

                Sincde I don't use IPv6 (wich I think this relates to) I ignored it.

                M S 2 Replies Last reply Reply Quote 0
                • M Offline
                  michmoor LAYER 8 Rebel Alliance @ricbjo
                  last edited by

                  @ricbjo
                  Very strange. Can we try a system reload ?

                  Firewall: NetGate,Palo Alto-VM,Juniper SRX
                  Routing: Juniper, Arista, Cisco
                  Switching: Juniper, Arista, Cisco
                  Wireless: Unifi, Aruba IAP
                  JNCIP,CCNP Enterprise

                  1 Reply Last reply Reply Quote 1
                  • S Offline
                    SteveITS Rebel Alliance @ricbjo
                    last edited by

                    @ricbjo In the pfSense system options on the firewall page ensure your max table size is at least 2 million and raise as necessary.

                    Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                    When upgrading, allow 10-15 minutes to reboot, or more depending on packages, and device or disk speed.
                    Upvote ๐Ÿ‘ helpful posts!

                    R 1 Reply Last reply Reply Quote 1
                    • R Offline
                      ricbjo
                      last edited by

                      Thanks so much!!
                      I updated to the 2.7.1 version with reboot and now it seem to be working. :-)

                      1 Reply Last reply Reply Quote 0
                      • R Offline
                        ricbjo @SteveITS
                        last edited by

                        @SteveITS For future reference... I also had to raise the max table size and that made the rule loading error go away. Also when adding new rules today, they were not applied until I had raised the max table size and reloaded.

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