Date: Thu, 16 Sep 2004 03:56:44 -0000 From: Pyun YongHyeon <yongari@kt-is.co.kr> To: pf4freebsd@freelists.org Subject: [pf4freebsd] Re: nfsd send error 1 probably caused by pf ? Message-ID: <20031114100704.GB32359@kt-is.co.kr> In-Reply-To: <20031114093317.GB20224@insomnia.benzedrine.cx> References: <3FB2ACA6.7030302@kasimir.com> <20031112220709.GO17343@insomnia.benzedrine.cx> <3FB2B203.1030704@kasimir.com> <3FB2B5AB.50601@kasimir.com> <20031113163911.GR17343@insomnia.benzedrine.cx> <3FB3EBBA.5070405@kasimir.com> <20031114092424.GA32359@kt-is.co.kr> <20031114093317.GB20224@insomnia.benzedrine.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Nov 14, 2003 at 10:33:17AM +0100, Daniel Hartmeier wrote: > On Fri, Nov 14, 2003 at 06:24:24PM +0900, Pyun YongHyeon wrote: >=20 > > It seems that your problem is reproducable on my SMP machine. > > I used a single rule 'pass out on xl0 keep state'. > > However, I can't see 'nfsd send error' message. nfs client > > works well even though pf still outputs 'BAD state' message. >=20 > Are you running nfsd on the pf machine? If pf is blocking outgoing Yes. > packets due to state mismatches (BAD state messages), and the process > trying to send the blocked packets is running on the pf box, it gets a > an error code from the stack. If nfsd is reporting those errors, that > would imply you'd have to run nfsd on the pf box (not the nfs client). > If the theory is correct up to this point, that is ;) >=20 Yes. Florian C. Smeets reported a error message "nfsd send error 1" error code 1 is EPERM and this might come from pf's blocking. At present, I think, actual cause may be in somewhere in H/W checksum offload routine in FreeBSD pf. I need more investigation. Thanks for your comment. > Daniel >=20 Regards, Pyun YongHyeon --=20 Pyun YongHyeon <http://www.kr.freebsd.org/~yongari>;
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031114100704.GB32359>