Here's what we are trying to do . I've got pfSense up and I've got 5
WAN IP addresses in the WAN subnet.
a.b.c.d
a.b.c.d+1
a.b.c.d+2
a.b.c.d+3
a.c.d.d+4
I would like to NAT by specific address, and add VPN functionality to
only specific IPs. So d is
On Wed, May 9, 2012 at 9:45 PM, Ugo Bellavance wrote:
> OpenVPN Remote Access Server Setup Wizard
>
>
> Firewall Rule Configuration
>
> Firewall Rules control what network traffic is permitted. You must add rules
> to allow traffic to the OpenVPN server's IP and port, as well as allowing
> traffic
OpenVPN Remote Access Server Setup Wizard
Firewall Rule Configuration
Firewall Rules control what network traffic is permitted. You must add
rules to allow traffic to the OpenVPN server's IP and port, as well as
allowing traffic from connected clients through the tunnel. These rules
can be a
On 2012-05-09 10:54, Ugo Bellavance wrote:
On 2012-05-09 10:51, Jim Pingle wrote:
On 5/9/2012 10:42 AM, Ugo Bellavance wrote:
Is there a reason why hyphens are not allowed in aliases names?
Aliases have to be valid pf macro/table keywords, iirc hypens are not
allowed there.
From pf.conf(5)
M
Hi,
Here is a suggestion for negated aliases. For example, I'd like to have
an aliases that is called "Internet", which would be a negation of my
"Internal Networks" alias. I can still achieve my goal by using the
'not' checkbox in rules, but I think it would be cleaner with negated
aliases
On 2012-05-09 10:51, Jim Pingle wrote:
On 5/9/2012 10:42 AM, Ugo Bellavance wrote:
Is there a reason why hyphens are not allowed in aliases names?
Aliases have to be valid pf macro/table keywords, iirc hypens are not
allowed there.
From pf.conf(5)
MACROS
Macros can be defined that will la
On 5/9/2012 10:42 AM, Ugo Bellavance wrote:
> Is there a reason why hyphens are not allowed in aliases names?
Aliases have to be valid pf macro/table keywords, iirc hypens are not
allowed there.
>From pf.conf(5)
MACROS
Macros can be defined that will later be expanded in context. Macro
names
Hi,
Is there a reason why hyphens are not allowed in aliases names?
Thanks,
Ugo
___
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list