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

    Is it possible to change an alias dynamically?

    Scheduled Pinned Locked Moved Firewalling
    46 Posts 6 Posters 6.6k 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.
    • johnpozJ
      johnpoz LAYER 8 Global Moderator @Tobi
      last edited by

      @tobi yeah just grasping at straws on why when you pick lan3 net that says no source defined.

      An intelligent man is sometimes forced to be drunk to spend time with his fools
      If you get confused: Listen to the Music Play
      Please don't Chat/PM me for help, unless mod related
      SG-4860 24.11 | Lab VMs 2.8, 24.11

      T 1 Reply Last reply Reply Quote 0
      • T
        Tobi
        last edited by

        @johnpoz said in Is it possible to change an alias dynamically?:

        maybe try it with ipv6 turned off on the interface.

        This chances nothing

        # source address is empty.  label "USER_RULE: Ping"
        # source address is empty.  label "USER_RULE: Ping"
        
        1 Reply Last reply Reply Quote 0
        • T
          Tobi @johnpoz
          last edited by Tobi

          @johnpoz said in Is it possible to change an alias dynamically?:

          yeah just grasping at straws on why when you pick lan3 net that says no source defined.

          Yes it's true but this happens with each interface/ LanX Net I'm trying. Not only lan3

          And If I try to modiify the Rule

          Ping from Yellow_Network to LAN4 Net then in in rules.debug I see "destination address is empty"

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Hmm... well that's extremely odd!

            This is in pfSense 2.6?

            Are you using any of the System Aliases (LANx Net) in any firewall rules successfully?

            Do you see the 'system aliases' section in the rules.debug file?
            Is LAN3 referencing the correct interface?
            I expect both those to be true because the traffic is being blocked correctly still.

            Try adding the v4 and v6 rules as separate lines in the config.
            The scripts create then as separate rules line anyway but it could be trying to validate the LANx net alias as both v4 and v6 at the same time and failing both somehow.

            Steve

            T 1 Reply Last reply Reply Quote 0
            • T
              Tobi @stephenw10
              last edited by Tobi

              @stephenw10 said in Is it possible to change an alias dynamically?:

              This is in pfSense 2.6?

              Yes
              22-07-_2022_08-56-52.jpg

              @stephenw10 said in Is it possible to change an alias dynamically?:

              Are you using any of the System Aliases (LANx Net) in any firewall rules successfully?

              No.

              @stephenw10 said in Is it possible to change an alias dynamically?:

              Do you see the 'system aliases' section in the rules.debug file?

              #System aliases
              
              loopback = "{ lo0 }"
              WAN = "{ pppoe0 }"
              LAN0 = "{ igb1 }"
              LAN1 = "{ igb2 }"
              LAN2 = "{ igb3 }"
              LAN3 = "{ igb4 }"
              LAN4 = "{ igb3.150 }"
              LAN5 = "{ igb3.250 }"
              LAN6 = "{ igb3.20 }"
              LAN7 = "{ igb2.30 }"
              LAN8 = "{ igb2.40 }"
              LAN9 = "{ igb2.50 }"
              OpenVPN = "{ openvpn }"
              
              

              @stephenw10 said in Is it possible to change an alias dynamically?:

              Try adding the v4 and v6 rules as separate lines in the config.

              Yesterday I tryed to disable ipv6 from this interface and create also a new rule only for IPv4 - nothing changes

              T 1 Reply Last reply Reply Quote 0
              • T
                Tobi @Tobi
                last edited by

                The only thing with system alias works here is my WAN Interface. I can create rule with "WAN Net" oder "WAN Address" and this works, but no other interfaces.

                1 Reply Last reply Reply Quote 0
                • T Tobi referenced this topic on
                • First post
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.