Quoting "Simon L. Nielsen" <[EMAIL PROTECTED]>:
On 2005.05.26 14:17:32 -0700, Jon Simola wrote:
On 5/26/05, Edwin L. Culp <[EMAIL PROTECTED]> wrote:
> this configuration there is no dns resolution. The first problem.
> tcp_services = "{ 22, 25, 53, 80, 110, 113, 123, 143, 389 }"
> block all
Quoting Jon Simola <[EMAIL PROTECTED]>:
On 5/26/05, Edwin L. Culp <[EMAIL PROTECTED]> wrote:
this configuration there is no dns resolution. The first problem.
tcp_services = "{ 22, 25, 53, 80, 110, 113, 123, 143, 389 }"
block all
pass in on $ext_if inet proto tcp from any to ($ext_if) p
On 2005.05.26 14:17:32 -0700, Jon Simola wrote:
> On 5/26/05, Edwin L. Culp <[EMAIL PROTECTED]> wrote:
>
> > this configuration there is no dns resolution. The first problem.
>
> > tcp_services = "{ 22, 25, 53, 80, 110, 113, 123, 143, 389 }"
>
> > block all
> > pass in on $ext_if inet proto tcp
On 5/26/05, Edwin L. Culp <[EMAIL PROTECTED]> wrote:
> this configuration there is no dns resolution. The first problem.
> tcp_services = "{ 22, 25, 53, 80, 110, 113, 123, 143, 389 }"
> block all
> pass in on $ext_if inet proto tcp from any to ($ext_if) port
> $tcp_services flags S/SA keep stat
# macros
I am trying to learn to use pf. I basically took this from a home
office example and made some modifications. That is probably the
problem ;)
I have installed this on three different servers and the only change
from one to another are the int_if and ex_if values. The three servers
Hi there,
Some time ago I complained here that in my environment state entries
would expire too fast when pfsync was active. I've just upgraded
my production routers to FreeBSD 5.4-STABLE + PF 3.7 and I no longer
can observe the problem, pfsync working like a charm now. Many
thanks to Max Laier
