Date: Sun, 18 May 2008 10:29:19 -0700 From: "Kian Mohageri" <kian.mohageri@gmail.com> To: "=?UTF-8?Q?Johan_Str=C3=B6m?=" <johan@stromnet.se> Cc: Alex Trull <alex@trull.org>, freebsd-net@freebsd.org, freebsd-stable <freebsd-stable@freebsd.org>, freebsd-pf@freebsd.org Subject: Re: connect(): Operation not permitted Message-ID: <fee88ee40805181029x31755a75i3b61731864e995fd@mail.gmail.com> In-Reply-To: <B44C565F-65A5-498A-9B79-3FFE15E33A7A@stromnet.se> References: <678A03F5-5E8A-4CF6-90DF-AA9A4F30FBE1@stromnet.se> <1211037564.6326.27.camel@porksoda> <679DB462-75D6-45CC-949C-1BE8E12C22CD@stromnet.se> <482FD877.6050707@infracaninophile.co.uk> <B44C565F-65A5-498A-9B79-3FFE15E33A7A@stromnet.se>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, May 18, 2008 at 3:33 AM, Johan Ström <johan@stromnet.se> wrote: > On May 18, 2008, at 9:19 AM, Matthew Seaman wrote: > >> Johan Ström wrote: >> >>> drop all traffic)? A check with pfctl -vsr reveals that the actual rule >>> inserted is "pass on lo0 inet from 123.123.123.123 to 123.123.123.123 flags >>> S/SA keep state". Where did that "keep state" come from? >> >> 'flags S/SA keep state' is the default now for tcp filter rules -- that >> was new in 7.0 reflecting the upstream changes made between the 4.0 and >> 4.1 >> releases of OpenBSD. If you want a stateless rule, append 'no state'. >> >> http://www.openbsd.org/faq/pf/filter.html#state > > Thanks! I was actually looking around in the pf.conf manpage but failed to > find it yesterday, but looking closer today I now saw it. > Applied the no state (and quick) to the rule, and now no state is created. > And the problem I had in the first place seems to have been resolved too > now, even though it didn't look like a state problem.. (started to deny new > connections much earlier than the states was full, altough maybee i wasnt > looking for updates fast enough or something). > I'd be willing to bet it's because you're reusing the source port on a new connection before the old state expires. You'll know if you check the state-mismatch counter. Anyway, glad you found a resolution. -Kian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fee88ee40805181029x31755a75i3b61731864e995fd>