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

    Firewall alias issue after adding a wrong alias

    Scheduled Pinned Locked Moved Firewalling
    1 Posts 1 Posters 343 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.
    • M
      michel_de
      last edited by

      Hi,

      We figure out a bug when using an alias group into firewall rules. Here are the steps that we use to reproduce it :
      • Add a non-existing alias into the alias group “GR_TEST_alias”
      • Apply config
      • ALL IS OK and server source can reach their destination provided by the firewall rule and the alias that are used
      • Remove non-existing alias
      • Apply configuration change
      • ISSUE REACHED (group is like “bugged”) and communications allowed by the rule are not working
      • Edit alias group
      • Save (without doing any change)
      • Apply configuration change
      • ISSUE FIXED and communications are restablished

      Note : alias group contains VM alias. And VM alias contains IP.
      Issue has been tested and confirmed on our firewal on versions 2.3.2 (amd64) and 2.2.6 (amd64).

      ==>Does anyone reached it ? Thanks for your support :)

      Capture.PNG
      Capture.PNG_thumb

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