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

    Unable to add any type of firewall alias in latest snapshot 2.1

    Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
    3 Posts 2 Posters 1.4k 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.
    • I
      iamzam
      last edited by

      I first saw this behavior in pfsense 2.1 snapshot from march 27 obtained via http://snapshots.pfsense.org .

      I only noticed it today and I ran gitsync yesterday and today so it's possibly related to some recent update.

      To reproduce, just go to Firewall -> Aliases and click the + button to add a new alias, or even edit an existing alias, then click the + button to add a new entry.  In my pfsense there is no field for the entry.  There is only a checkbox under the IP column, another greyed-out checkbox and the Description field.

      I just updated to the latest full update and rebooted, and the behavior is still there for me:
      http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/amd64/pfSense_HEAD/updates/pfSense-Full-Update-2.1-DEVELOPMENT-amd64-20120329-0846.tgz

      My complete version:

      2.1-DEVELOPMENT (amd64)
      built on Thu Mar 29 09:56:08 EDT 2012
      FreeBSD pfsense 8.3-RC2 FreeBSD 8.3-RC2 #1: Thu Mar 29 09:55:44 EDT 2012 root@FreeBSD_8.3_pfSense_2.1.snaps.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_SMP.8 amd64

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        It's working for me on that same snapshot.

        Try clearing your browser cache?

        What browser are you using?

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • I
          iamzam
          last edited by

          Firefox 11

          I just figured it out, for some reason the redirect cleaner plugin https://addons.mozilla.org/en-US/firefox/addon/redirect-cleaner/ which was just updated March 27 was blocking that field.

          I added my domain to the whitelist and it works now…

          Sorry, i should have checked that first, thanks for your time...

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