Re: [pfSense Support] 1:1 NAT Entry issue - Bug or mistake?

2011-01-21 Thread Ermal Luçi
On Fri, Jan 21, 2011 at 4:11 AM, Dimitri Rodis
dimit...@integritasystems.com wrote:
 On Thu, Jan 20, 2011 at 9:28 PM, Dimitri Rodis 
 dimit...@integritasystems.com wrote:
 pfSense 2.0-BETA5 (i386) built on Wed Jan 19 12:45:14 EST 2011



 When I try to use an alias in the Internal IP field (suppose the alias
 was
 ) I receive the following error upon saving (or trying to save):



 The following input errors were detected:

      is not a valid internal IP address





 I know in 2.0 you could not use aliases in the 1:1 fields, but in
 this version the boxes are RED, implying that aliases are allowed. I
 don't know if this is a bug or just a mistake (in formatting the
 fields RED) but in any event it looks like something needs to be fixed
 or changed. I did not try using an Alias in the External Subnet IP field, 
 although it is RED also.


That's correct, the fields shouldn't be red though, I just fixed that.
Aliases aren't supported in binat in pf.

 Even if binat doesn't support them, they could theoretically be resolved 
 via code prior to updating the rulesin 2.1 :)

You can put a feature request on redmine.pfsense.org so it does not
get forgotten.



-- 
Ermal

-
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com

Commercial support available - https://portal.pfsense.org



Re: [pfSense Support] 1:1 NAT Entry issue - Bug or mistake?

2011-01-20 Thread Chris Buechler
On Thu, Jan 20, 2011 at 9:28 PM, Dimitri Rodis
dimit...@integritasystems.com wrote:
 pfSense 2.0-BETA5 (i386) built on Wed Jan 19 12:45:14 EST 2011



 When I try to use an alias in the Internal IP field (suppose the alias was
 ) I receive the following error upon saving (or trying to save):



 The following input errors were detected:

      is not a valid internal IP address





 I know in 2.0 you could not use aliases in the 1:1 fields, but in this
 version the boxes are RED, implying that aliases are allowed. I don’t know
 if this is a bug or just a mistake (in formatting the fields RED) but in any
 event it looks like something needs to be fixed or changed. I did not try
 using an Alias in the External Subnet IP field, although it is RED also.


That's correct, the fields shouldn't be red though, I just fixed that.
Aliases aren't supported in binat in pf.

-
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com

Commercial support available - https://portal.pfsense.org



RE: [pfSense Support] 1:1 NAT Entry issue - Bug or mistake?

2011-01-20 Thread Dimitri Rodis
On Thu, Jan 20, 2011 at 9:28 PM, Dimitri Rodis dimit...@integritasystems.com 
wrote:
 pfSense 2.0-BETA5 (i386) built on Wed Jan 19 12:45:14 EST 2011



 When I try to use an alias in the Internal IP field (suppose the alias 
 was
 ) I receive the following error upon saving (or trying to save):



 The following input errors were detected:

      is not a valid internal IP address





 I know in 2.0 you could not use aliases in the 1:1 fields, but in 
 this version the boxes are RED, implying that aliases are allowed. I 
 don't know if this is a bug or just a mistake (in formatting the 
 fields RED) but in any event it looks like something needs to be fixed 
 or changed. I did not try using an Alias in the External Subnet IP field, 
 although it is RED also.


That's correct, the fields shouldn't be red though, I just fixed that.
Aliases aren't supported in binat in pf.

Even if binat doesn't support them, they could theoretically be resolved via 
code prior to updating the rulesin 2.1 :)

-
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com

Commercial support available - https://portal.pfsense.org