From owner-freebsd-stable@FreeBSD.ORG Wed Feb 9 14:13:41 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B06816A4CE for ; Wed, 9 Feb 2005 14:13:41 +0000 (GMT) Received: from mail.distalzou.net (203.141.139.231.user.ad.il24.net [203.141.139.231]) by mx1.FreeBSD.org (Postfix) with ESMTP id 395CA43D3F for ; Wed, 9 Feb 2005 14:13:39 +0000 (GMT) (envelope-from devin@spamcop.net) Received: from plexi.pun-pun.prv ([192.168.7.29] helo=plexi) by mail.distalzou.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.44 (FreeBSD)) id 1Cysay-000LXT-8N; Wed, 09 Feb 2005 23:13:32 +0900 Date: Wed, 9 Feb 2005 23:13:29 +0900 (JST) From: Tod McQuillin X-X-Sender: devin@plexi.pun-pun.prv To: Pete French In-Reply-To: Message-ID: <20050209231126.D64632@plexi.pun-pun.prv> References: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-93896565-1107958409=:64632" cc: freebsd-stable@freebsd.org Subject: Re: Bug in nfsd, or did I just read the manpage wrong ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Feb 2005 14:13:41 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-93896565-1107958409=:64632 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed On Wed, 9 Feb 2005, Pete French wrote: > I have a machine with three interfaces on it, two onto > internal networks, one ointo the outside world. I only want > NFS to be accessible on the two internal interfaces so I have this line > in my /etc/rc.conf: > > nfs_server_flags="-u -t -n 4 -h 192.168.3.1 -h 192.168.4.1" > > That works - but it ony enables TCP on the second interface, the > first is UDP only. I have tried all sorts of combinations and > positioning for the -t flag, but the end result is the same. UDP > on both, TCP only on 192.168.4.1. > > Hmmmm... anybody got any ideas ? Puzzling the hell out of me! Try the patch in http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/25826 That worked for me. I've also attached the patch to this email. -- tod McQuillin --0-93896565-1107958409=:64632 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=nfsd.patch Content-Transfer-Encoding: BASE64 Content-ID: <20050209231329.V64632@plexi.pun-pun.prv> Content-Description: Content-Disposition: attachment; filename=nfsd.patch SW5kZXg6IG5mc2QuYw0KPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQ0KUkNTIGZp bGU6IC91c3Ivc3JjL2N2cy1yZXBvL3NyYy9zYmluL25mc2QvQXR0aWMvbmZz ZC5jLHYNCnJldHJpZXZpbmcgcmV2aXNpb24gMS4xNS4yLjINCmRpZmYgLXUg LXIxLjE1LjIuMiBuZnNkLmMNCi0tLSBuZnNkLmMJMzAgTWFyIDIwMDQgMjA6 MjU6MzMgLTAwMDAJMS4xNS4yLjINCisrKyBuZnNkLmMJMTAgTWF5IDIwMDQg MTI6NDA6NDEgLTAwMDANCkBAIC01OTMsNyArNTkzLDggQEANCiAJCQkJZXhp dCgxKTsNCiAJCQl9DQogCQl9DQotCQlpZiAodGNwZmxhZyAmJiBGRF9JU1NF VCh0Y3Bzb2NrLCAmcmVhZHkpKSB7DQorCQlmb3IgKHRjcHNvY2sgPSAwOyB0 Y3Bzb2NrIDw9IG1heHNvY2s7IHRjcHNvY2srKykgew0KKwkJICAgIGlmICh0 Y3BmbGFnICYmIEZEX0lTU0VUKHRjcHNvY2ssICZyZWFkeSkpIHsNCiAJCQls ZW4gPSBzaXplb2YoaW5ldHBlZXIpOw0KIAkJCWlmICgobXNnc29jayA9IGFj Y2VwdCh0Y3Bzb2NrLA0KIAkJCSAgICAoc3RydWN0IHNvY2thZGRyICopJmlu ZXRwZWVyLCAmbGVuKSkgPCAwKSB7DQpAQCAtNjEzLDYgKzYxNCw3IEBADQog CQkJbmZzZGFyZ3MubmFtZWxlbiA9IHNpemVvZihpbmV0cGVlcik7DQogCQkJ bmZzc3ZjKE5GU1NWQ19BRERTT0NLLCAmbmZzZGFyZ3MpOw0KIAkJCSh2b2lk KWNsb3NlKG1zZ3NvY2spOw0KKwkJICAgIH0NCiAJCX0NCiAjaWZkZWYgbm90 eWV0DQogCQlpZiAodHA0ZmxhZyAmJiBGRF9JU1NFVCh0cDRzb2NrLCAmcmVh ZHkpKSB7DQo= --0-93896565-1107958409=:64632--