We have aliases with multiple ports that work just fine: PortsAltHTTPS 444, 8443, 8444, 8445 Alternate HTTPS Ports for COMSERVER3 PortscPanelPorts 80, 443, 2083, 2087, 22, 2096, 2095 PortsJabber 5222, 9091, 7443, 5229 PortsNetmeeting 1720, 1503 Netmeeting Ports PortsRemoteManagement 443, 22 Ports for HostsAllowedRemoteManagement PortsVintageSecurity 2001 Alarm System PortsWifiToLAN 53, 80, 443, 3389 Ports on LAN open to Wifi
We currently have no ranges defined in our rules but I just created a test alias with two port ranges of 15 ports each and created a rule to pass traffic on those ports. It seemed to work just fine. Are you trying to put the alias in the "End Port" box on the rule page? AFAIK, you only need to put it in the "Start Port" box (though pfSense will copy it to the other box after you save the rule). What version of pfSense are you running? Moshe -- Moshe Katz -- [email protected] -- +1(301)867-3732 On Fri, May 11, 2012 at 2:49 PM, Ugo Bellavance <[email protected]> wrote: > Hi, > > I want to create a rule for an application that uses 2 ranges of > destination ports. I created an alias with 2 port ranges, but when I add > it in the rule it says: > > _Ports_xxx is not a valid start destination port. It must be a port alias > or integer between 1 and 65535. > > _Ports_xxx is not a valid end destination port. It must be a port alias or > integer between 1 and 65535. > > Do I have to make 2 separate rules? > > Thanks, > > Ugo > > ______________________________**_________________ > List mailing list > [email protected] > http://lists.pfsense.org/**mailman/listinfo/list<http://lists.pfsense.org/mailman/listinfo/list> >
_______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
