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

    Illegal characters in Firewall Rule descriptions...

    HA/CARP/VIPs
    2
    5
    492
    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.
    • S
      SmokinMoJoe
      last edited by

      Hi All,

      I wanted to see if this was a known issue or a bug. It appears if I have a firewall rule that I put the date in the description, i.e. 1/6/2019 I have issues doing a HA Force Config Sync. When I change the date to 1-6-2019 my firewall rules pass immediately from the MASTER to the BACKUP.

      I am running :
      2.4.4-RELEASE-p1 (amd64)
      built on Mon Nov 26 11:40:26 EST 2018
      FreeBSD 11.2-RELEASE-p4

      Thanks,
      Joe

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        Is anything logged on either node when it fails?

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        • S
          SmokinMoJoe
          last edited by

          I also had a group description with 1/22/2017 and it was causing the users to fail to sync between the Master and backup. Maybe that is the only bug?

          1 Reply Last reply Reply Quote 0
          • DerelictD
            Derelict LAYER 8 Netgate
            last edited by

            Mine synced fine on my test cluster but the '/' characters were stripped on the secondary.

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

            1 Reply Last reply Reply Quote 0
            • DerelictD
              Derelict LAYER 8 Netgate
              last edited by

              I would say don't use '/' for the time being.

              Chattanooga, Tennessee, USA
              A comprehensive network diagram is worth 10,000 words and 15 conference calls.
              DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
              Do Not Chat For Help! NO_WAN_EGRESS(TM)

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