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

Using aliase to specify a list of ports - V1.2 interface change problem

Scheduled Pinned Locked Moved Firewalling
4 Posts 2 Posters 1.8k 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.
  • P
    Pootle
    last edited by Jun 23, 2007, 12:37 PM

    I'm adding some more to the wiki on setting up multi WAN in version 1.2, but I've run into a little problem  :-[

    In the old version- 1.1 (see this wiki page)
    [url=http://doc.pfsense.org/index.php/Multi-Wan/Load-Balancing#Set_up_useful_aliases]http://doc.pfsense.org/index.php/Multi-Wan/Load-Balancing#Set_up_useful_aliases
    you can set up the alias and then setup the rule with the Destination field referencing the aliase.

    In 1.2 youcan still set up the alias OK, but the firewall rule now splits the destination into destination and destination port range.

    I can only put the alias for the port list into the destination field, but this never triggers.

    I could just put in a rule for each port required, but this is clumsy compared to the old way.

    Is there (will there soon) be a better way to do this?

    1 Reply Last reply Reply Quote 0
    • P
      Pootle
      last edited by Jul 7, 2007, 4:48 PM

      Bump - or I document load balancing the hard way…...

      1 Reply Last reply Reply Quote 0
      • S
        sullrich
        last edited by Jul 7, 2007, 9:29 PM

        I am afraid we had to change this behavior to fix a number of other bugs.  I doubt we will be changing it back.

        1 Reply Last reply Reply Quote 0
        • P
          Pootle
          last edited by Jul 14, 2007, 5:39 PM

          OK, I'll write it up with one rule per port

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
            [[user:consent.lead]]
            [[user:consent.not_received]]