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

Rule with port alias not working

Scheduled Pinned Locked Moved Firewalling
6 Posts 4 Posters 1.9k 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.
  • B
    BemBile
    last edited by May 19, 2017, 9:29 AM

    Hi,

    I'm setting up firewall rules on a new Pfsense installation (2.3.4), and I'm having problems with a rule that uses a port alias to block out the ports to the management interface on my firewall.

    I'v set up my firewall rules and the port alias exactly like it's done in this guide: https://doc.pfsense.org/index.php/Restrict_access_to_management_interface
    but my rule won't trigger.

    If I make 3 separate rules each blocking one of the ports, instead of using the port alias, the management interface gets blocked. The rule is on top of the list, and I have no floating rules.

    I can't find anything on this so I figure that I must be doing something wrong, and it's driving me nuts.
    Thanks for your help! ;)

    firewall-alias.png
    firewall-alias.png_thumb
    firewall-rule.png
    firewall-rule.png_thumb

    1 Reply Last reply Reply Quote 0
    • N
      nodau
      last edited by Oct 11, 2017, 2:14 PM

      i want to revive this post, as i'm experiencing the same issue on 2.3.4 p1.

      i have different port aliases to use for tcp and udp. tcp ports work fine with the alias whereas udp ports alias don't.

      any ideas?

      Norman

      virtualized pfSense 2.7.2 HA-Cluster on vsphere 8

      1 Reply Last reply Reply Quote 0
      • B
        BemBile
        last edited by Oct 11, 2017, 2:34 PM

        Hi bahsig,

        I never found a solution myself, and I got no input here here as you can see.
        It's good to know that I'm not the only one who has this problem.

        Regards, B.

        1 Reply Last reply Reply Quote 0
        • P
          PlatinumBlack
          last edited by Apr 11, 2018, 6:02 PM

          Has anyone found a solution to this yet as im experiencing the same issue?

          1 Reply Last reply Reply Quote 0
          • B
            Birke
            last edited by Apr 12, 2018, 9:40 AM

            one error of the op might be the wrong port for https in the alias: its not 433, its 443.
            not sure if that could be your problem too. can you post your alias and the rule?

            1 Reply Last reply Reply Quote 0
            • P
              PlatinumBlack
              last edited by Apr 13, 2018, 7:22 PM

              @Birke:

              one error of the op might be the wrong port for https in the alias: its not 433, its 443.
              not sure if that could be your problem too. can you post your alias and the rule?

              Essentially what i am trying to do is stop access to he admin login page on all vlans bar the management vlan, I was able to resolve this issue though :)

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                This community forum collects and processes your personal information.
                consent.not_received