From owner-freebsd-questions@FreeBSD.ORG Tue May 31 19:58:02 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2CA5B16A41C; Tue, 31 May 2005 19:58:02 +0000 (GMT) (envelope-from skylar@cs.earlham.edu) Received: from cs.earlham.edu (cs.earlham.edu [159.28.230.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2EA143D4C; Tue, 31 May 2005 19:58:01 +0000 (GMT) (envelope-from skylar@cs.earlham.edu) Received: from [159.28.57.98] (wir057098.rpa.earlham.edu [159.28.57.98]) (authenticated bits=0) by cs.earlham.edu (8.13.4/8.13.3) with ESMTP id j4VJvu2e088707 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 31 May 2005 14:57:57 -0500 (EST) (envelope-from skylar@cs.earlham.edu) Message-ID: <429CC1BC.1050704@cs.earlham.edu> Date: Tue, 31 May 2005 14:57:48 -0500 From: Skylar Thompson Organization: Earlham College Computer Science Department User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jon Dama References: <200505270711.j4R7BTMf078204@gw.catspoiler.org> <429C867A.5040909@cs.earlham.edu> In-Reply-To: X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig63A298A94E8D527FE8FF3D65" X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (cs.earlham.edu [159.28.230.3]); Tue, 31 May 2005 14:57:58 -0500 (EST) X-Virus-Scanned: ClamAV 0.85.1/900/Tue May 31 05:50:19 2005 on quark.cs.earlham.edu X-Virus-Status: Clean X-Sanitizer: This message has passed the MIMEDefang sanitizer. X-Sanitizer-URL: http://www.cs.earlham.edu/applied-groups/admin/ X-Sanitizer-Version: MIMEDefang/ECSanitizer $Revision: 1.18 $ X-Sanitizer-Config-Version: $Revision: 1.180 $ X-Scanned-By: MIMEDefang 2.51 on 159.28.230.3 X-Spam-Status: No, score=-2.8 required=8.0 tests=ALL_TRUSTED autolearn=failed version=3.0.3 X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on quark.cs.earlham.edu Cc: Don Lewis , freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Weird NFS problems X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2005 19:58:02 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig63A298A94E8D527FE8FF3D65 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Jon Dama wrote: >Yes, but surely you weren't bridging gigabit and 100Mbit before? > > >Did you try my suggestion about binding the IP address of the NFS server >to the 100Mbit side? > > Yeah. Unfortunately networking on the server fell apart when I did that. Traffic was still passed and I could get through to the server on the 100Mb/s side, but not on the 1000Mb/s. It looked like the arp tables weren't being forwarded properly, but I couldn't convince FreeBSD to do proxy arp. After doing some more poking around, it actually looks like it might be a misfeature in the Linux 2.4 kernel wrt ipfilter (which is running on the bridge). Apparently 2.4 fragments UDP packets in the reverse order that every other UNIX-like operating system does, which throws off ipfilter's state tables. I'm going to do some testing to see if the difference between UDP and TCP NFS is negligible enough for us to disregard. Thanks for the suggestions! -- -- Skylar Thompson (skylar@cs.earlham.edu) -- http://www.cs.earlham.edu/~skylar/ --------------enig63A298A94E8D527FE8FF3D65 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCnMHAsc4yyULgN4YRApxkAJ9Brs4MyTHWATca8AWm/sAZY5R+nACgoQYW QgIiFW+IK3DvHKQDx07B1jM= =0utg -----END PGP SIGNATURE----- --------------enig63A298A94E8D527FE8FF3D65--