Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login
    Introducing Netgate Nexus: Multi-Instance Management at Your Fingertips.

    Allow Rule not working

    Scheduled Pinned Locked Moved L2/Switching/VLANs
    2 Posts 2 Posters 159 Views 2 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.
    • E Offline
      eagledtony
      last edited by

      Greetings, I have been having lots of trouble lately with some rules I made to allow printing across different VLANS, and this is happening with similar configurations at different sites. Firewalls software versions range between 24.11 to the latest. I have three VLANS in an interface group and have their rules assigned there. The printers reside on a physical interface. From top to bottom on the interface group, I have rules allowing communication to the printer on the ports needed for printing followed by a block rule for the physical interface subnet and finally an allow all rule. On the physical interface I have the same rules. The printer and its ports are aliases. I've also installed Avachi (I think that is how its spelled) to help with discovery. The issue I'm having is that two out of three VLANS in the group can talk to the printer. The other can't, I check the system logs, and I don't see anything relating to block. These rules have been working for about year and only have been giving me issues within the last two weeks. I have upgraded some firewalls to the latest firmware and there are others I haven't gotten to yet. There is a managed switch in the mix, with the same config since initially being installed. I'm thankful for any and all suggestions and I'll work to provide what information I can share (safely) for clarification.

      GertjanG 1 Reply Last reply Reply Quote 0
      • GertjanG Offline
        Gertjan @eagledtony
        last edited by Gertjan

        @eagledtony

        Most will have troubles reading what you've just wrote.
        Your Enter key seams to be broken also ( ^^ ).

        As no details (images) are available, so only some general advise :
        If you can, remove all 'VLAN' setup, go bare bone classic "VLAN 0" or no VLAN no where.
        This makes the setup simpler .... and issue start to vanish fast.

        If an issue arrives 'suddenly' then the last think you want to do is 'upgrading'.
        Upgrading will not (can not) resolve sudden local issues, but can create new issues.

        So, first, resolve the issue, which can be as simple as :
        Save the current pfSense config.
        Now get a config from 'before 2 weeks'.
        Issue solved : go question the pfSense admin, torture him if needed, and you will get to the bottom of things. The 'diff' between the current and 2 weeks old config will tell you what changed.
        Issue not solved : get the current config back and now you'll be sure : the issue isn't pfSense related. Go have a talk with the other (VLAN) stuff, and do question the "admin" gain.

        edit :

        Your pfSense has a config history :

        99464f43-9690-4b60-ba2f-740cb54e5dc3-image.png

        No "help me" PM's please. Use the forum, the community will thank you.

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