On Thu, Feb 5, 2009 at 11:39 AM, k_o_l wrote:
> Since you can't specify the transport protocol, then the assumption is that
> both UDP and TCP are open for that port, is that correct?
Rules specify the protocol. Aliases are strictly ports.
Auto-completion is caps sensitive at this time.
---
t: Re: [pfSense Support] Firewall: Aliases : Ports
Chris Buechler wrote:
> On Wed, Feb 4, 2009 at 5:42 AM, Paul Cockings
wrote:
>
>> PfSense 1.2.2
>>
>> If I use firewall>aliases and create an aliases:
>>
>> Name: WebDevels
>> Type: Port(s)
>>
Chris Buechler wrote:
On Wed, Feb 4, 2009 at 5:42 AM, Paul Cockings wrote:
PfSense 1.2.2
If I use firewall>aliases and create an aliases:
Name: WebDevels
Type: Port(s)
Port: 80 - http
Port: 3306 - mysql
Port: 21 - ftp
Port: 22 - ssh
Then use firewall > rules > Add
Should I be able to s
On Wed, Feb 4, 2009 at 5:42 AM, Paul Cockings wrote:
> PfSense 1.2.2
>
> If I use firewall>aliases and create an aliases:
>
> Name: WebDevels
> Type: Port(s)
> Port: 80 - http
> Port: 3306 - mysql
> Port: 21 - ftp
> Port: 22 - ssh
>
>
> Then use firewall > rules > Add
>
> Should I be able to selec
PfSense 1.2.2
If I use firewall>aliases and create an aliases:
Name: WebDevels
Type: Port(s)
Port: 80 - http
Port: 3306 - mysql
Port: 21 - ftp
Port: 22 - ssh
Then use firewall > rules > Add
Should I be able to select 'WebDevels' for the 'Destination port range' ?
FYI: Host based aliases are
