From owner-freebsd-stable@FreeBSD.ORG Tue Jul 26 15:46:08 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 D8B5916A420 for ; Tue, 26 Jul 2005 15:46:08 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id A09ED43D45 for ; Tue, 26 Jul 2005 15:46:08 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin01-en2 [10.13.10.146]) by smtpout.mac.com (Xserve/8.12.11/smtpout15/MantshX 4.0) with ESMTP id j6QFk8Th026957; Tue, 26 Jul 2005 08:46:08 -0700 (PDT) Received: from [10.1.1.209] (nfw1.codefab.com [199.103.21.225]) (authenticated bits=0) by mac.com (Xserve/smtpin01/MantshX 4.0) with ESMTP id j6QFk5Bs002036; Tue, 26 Jul 2005 08:46:06 -0700 (PDT) In-Reply-To: <20050726153842.GA8215@torch.higis.ru> References: <20050726153842.GA8215@torch.higis.ru> Mime-Version: 1.0 (Apple Message framework v733) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <89A8B284-47B2-41C1-A5ED-47597059C721@mac.com> Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Tue, 26 Jul 2005 11:45:56 -0400 To: Dmitriy Kirhlarov X-Mailer: Apple Mail (2.733) Cc: freebsd-stable@freebsd.org Subject: Re: nfs problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jul 2005 15:46:09 -0000 On Jul 26, 2005, at 11:38 AM, Dmitriy Kirhlarov wrote: > Problem in the netmask. When I try 192.168.2.1 all work fine. > How I can fix the problem? You might have to restart portmap, and/or feed it the -h option: -h Specify specific IP addresses to bind to for UDP requests. This option may be specified multiple times and is typically necessary when running on a multi-homed host. If no -h option is speci- fied, portmap will bind to INADDR_ANY, which could lead to prob- lems on a multi-homed host due to portmap returning a UDP packet from a different IP address than it was sent to. Note that when specifying IP addresses with -h, portmap will automatically add 127.0.0.1 to the list. -- -Chuck