On Wednesday 14 February 2007 1:29 pm, Stuart Henderson wrote:
On 2007/02/14 11:47, Tim Kuhlman wrote:
So what is happening? It seems to me that either pf is broken or his
linux kernel is broken and pf is catching it. Any ideas as to which is
the cause?
Ruleset more likely. If you post
Whoops, I forgot about attachments being stripped.
$ tcpdump -nr dmz_production_if-side -vv
reading from file dmz_production_if-side, link-type EN10MB (Ethernet)
16:32:15.627327 IP (tos 0x0, ttl 63, id 49423, offset 0, flags [DF], proto:
TCP (6), length: 60) 10.10.10.150.57818 10.11.0.5.80: S,
On 2/15/07, Tim Kuhlman [EMAIL PROTECTED] wrote:
So my ruleset has some problems. I took some time to work through my rules and
re-read the state tracking section of the pf faq (which by the way is well
done, thanks). I found what I think are a couple of problems, I needed to
have the flags S/SA
On Thursday 15 February 2007 10:12 am, Darren Spruell wrote:
On 2/15/07, Tim Kuhlman [EMAIL PROTECTED] wrote:
So my ruleset has some problems. I took some time to work through my
rules and re-read the state tracking section of the pf faq (which by the
way is well done, thanks). I found what
I have pf running on an OpenBSD 4.0 (patches 1-5, 7) router and I have one
user with two Gentoo Linux machines with kernel 2.6.18 who is having
troubles. Everyone else is having no problem at all. This user is having any
tcp connection he makes dropped by the firewall. The state shows up when I
On 2/14/07, Tim Kuhlman [EMAIL PROTECTED] wrote:
I have pf running on an OpenBSD 4.0 (patches 1-5, 7) router and I have one
user with two Gentoo Linux machines with kernel 2.6.18 who is having
troubles. Everyone else is having no problem at all. This user is having any
tcp connection he makes
On Wed, 14 Feb 2007, Tim Kuhlman wrote:
[snip]
So what is happening? It seems to me that either pf is broken or his linux
kernel is broken and pf is catching it. Any ideas as to which is the cause?
One other point I needs some clarification on, in my searching around I did
find an
On Wednesday 14 February 2007 12:11 pm, Darren Spruell wrote:
On 2/14/07, Tim Kuhlman [EMAIL PROTECTED] wrote:
I have pf running on an OpenBSD 4.0 (patches 1-5, 7) router and I have
one user with two Gentoo Linux machines with kernel 2.6.18 who is having
troubles. Everyone else is having no
On 2007/02/14 11:47, Tim Kuhlman wrote:
So what is happening? It seems to me that either pf is broken or his linux
kernel is broken and pf is catching it. Any ideas as to which is the cause?
Ruleset more likely. If you post it, people can make suggestions.
Might be useful to capture a SYN
On 2007/02/14 12:11, Darren Spruell wrote:
Yeah, when I went through it scrub rules had nothing to do with it.
All state, period. (Note that in -current the default is now to
implicitly build rules with both 'keep state' and 'S/SA' without
having to specify; default stateful behavior makes
10 matches
Mail list logo
