Setting are loaded in pf via /etc/rc.d/pf start
Why do these things differ?
EC These are the timeout settings for set optimization aggressive. If
EC it appears after your set timeout lines, then it will take
EC precedence. If this doesn't appear within your pf.conf, then this
EC probably
Fresh news.
I've noticed all unblocked packets have tcp window suggestion set to 0
(zero). I tried to block these packets on external interface:
~sudo ipfw add 10 deny log tcp from 192.168.0.0/16 to any via external out
tcpwin 0
This rule is the first rule in ipfw.
Then I looked for such
On Jul 13, 2007, at 2:17 AM, Alexey Sopov wrote:
While thinking about why it happens once in 5 seconds and has only
ACK bit
set, I tried to check some timeout variables and found interesting
thing.
These lines are in /etc/pf.conf:
set timeout { tcp.first 120, tcp.opening 30, tcp.established
While thinking about why it happens once in 5 seconds and has only ACK bit
set, I tried to check some timeout variables and found interesting
thing.
These lines are in /etc/pf.conf:
set timeout { tcp.first 120, tcp.opening 30, tcp.established 86400 }
set timeout { tcp.closing 900, tcp.finwait 45,
Why these packets weren't translated by pf nat rules or filtered by pf
block rule?
Note they appear once in five seconds. Tried to modify frag parameter,
but this didn't help. Also I noticed they all have ACK bit set.
Thank you.
SU What is the date of your build (uname -a). There was a
Hi
On my machine with FreeBSD 6.2-STABLE #4 I noticed there are
outgoing packets from net 192.168.0.0/16 on external interface
Some details:
Here 1 a,b,c,d,e,f 254
~ ifconfig internal
internal: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
On 7/12/07, Alexey Sopov [EMAIL PROTECTED] wrote:
Hi
On my machine with FreeBSD 6.2-STABLE #4 I noticed there are
outgoing packets from net 192.168.0.0/16 on external interface
Some details:
Here 1 a,b,c,d,e,f 254
~ ifconfig internal
internal:
