On Wed, 2004-Nov-10 09:22:39 -0500, Michael Butler wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>> Maybe you should allow everything on lo0, in and out.
>
>127/8 should always be allowed on the loopback interface,
>127/8 should always be dropped from all other interfaces.
>
>I am "uncom
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Maybe you should allow everything on lo0, in and out.
127/8 should always be allowed on the loopback interface,
127/8 should always be dropped from all other interfaces.
I am "uncomfortable" saying that everything should be allowed ..
Michael Butl
* Gunnar Flygt <[EMAIL PROTECTED]> (20041110 14:48):
> What is it that makes KDE so slow when using pf with these simple rules.
> Have I missed something?
Maybe you should allow everything on lo0, in and out.
--
olive
___
[EMAIL PROTECTED] mailing list
I reply to my own question. Since I found out it was pf causing this I
started to use tcpdump on pflog0 and found that traffic from 127.0.0.1
to 127.0.0.1 was blocked. So I added as in the examples for ipf :
# allow localhost
pass in quick on lo0
pass out quick on lo0
after the antispoof rule in
I've had problems with DKE 3.3 since I upgraded to 5.3-RELEASE.
I compared the same machine (Dell Latitude D600) with a different HD
where Gentoo Linux (Sorry for that:) resides. Om the Gentto box KDE 3.3
starts promply from kdm, no extra delays, but with FreeBSD 5.3 it takes
about 2 minutes to get
