From owner-freebsd-hackers@freebsd.org Fri Sep 8 14:24:54 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 80810E1AB9B for ; Fri, 8 Sep 2017 14:24:54 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0509781380 for ; Fri, 8 Sep 2017 14:24:54 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x22c.google.com with SMTP id q132so6000716lfe.5 for ; Fri, 08 Sep 2017 07:24:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=Nd9L+tIcvEQx4zIOII/FNZTl1pYqrS8xACcDeuYxqbY=; b=CLprVg3+RNt1o56obFoqTpzG/H21hRnhw0EKPnBC9SVLTS5a8bQnpMcnSok/rX/sx5 28mJgDIw8Qrea+Osnzj/fmTSVHv0wrrIrWtC5hBuMq0BQ3k2GozqKBKMeUgAd//3K/T2 CH/MmYZ6w/QL2rUWb0ILow9MEN1iCfABY2r4blwqQoULRS68GKCQQuaNeIXF9v7hFXm3 DtQQxwhzbaq/fetUSFqYsTB6yPUM25xBu54TT05qetx1zlMYIEXtqBwwWLxMUBOR5SNN uGuxW/DkwwHuydgXhzh5LAWyfBitgD5uZMkN9YtH3usghNJleJPrnrR5r8Hrw9TKgipl kFKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=Nd9L+tIcvEQx4zIOII/FNZTl1pYqrS8xACcDeuYxqbY=; b=AttZDPrH5vlllEyXV2m+MWvzrA73DerwzXP7+R1y7UDf72ptRH6VbB/Kd7zt3bjq3j euoIhVqS+pwNn07km6tHwuuWDfPBgYgviSmvsfsAB/XsLQzrHgjQSsXQ7zGvdGp4If5Z KPqPeBslgyhmz1S5vVSXaesauNAOamS/FYWcQKc3MugDis9mjXKtGEdn1SynrFt/zDY5 iQ2GRSTRVOXrY2V96ZTHNg9ZqhKXs/FYrEAk3MjauBkcdMNyw+mJ4okUkK88AB5xK798 de6lNq/neS8lRuCfoAAZaiDsISi4Jnp6zUCY4I9eRv1DuIm3fp/IZ7sZg0TyNovMgXQ8 K1hw== X-Gm-Message-State: AHPjjUh/bvwLvaq7OgcMtW4kDa6TfPa2VutJfPONqZ2cYQMMjnXwqu73 5NE3kf1hI6/Zl2Wd4I4qmrLkvl7DZw== X-Google-Smtp-Source: AOwi7QDPOxeozNl9g+ajMHaVkoSlm7mvXgTSeEdVxVGTakv9S2Y5qHapU/nwr2Q2GHezFJjuqRJNjDYH9zfXWRPEfS0= X-Received: by 10.25.87.74 with SMTP id l71mr993000lfb.193.1504880692090; Fri, 08 Sep 2017 07:24:52 -0700 (PDT) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.179.26.6 with HTTP; Fri, 8 Sep 2017 07:24:51 -0700 (PDT) In-Reply-To: References: From: Alan Somers Date: Fri, 8 Sep 2017 08:24:51 -0600 X-Google-Sender-Auth: _Myk4HMsrGGKv5S4AuoeGcWutaQ Message-ID: Subject: Re: Why does rpc.lockd(8) and rpc.stat(8) require a working Internet connection To: Aryeh Friedman Cc: FreeBSD Mailing List Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Sep 2017 14:24:54 -0000 On Fri, Sep 8, 2017 at 3:03 AM, Aryeh Friedman wrote: > My cable modem was out for a few hours last night and my NFS based *LOCAL* > (same subnet [192.168.11.XXX] and physical LAN) file server started > glitching up on attempting to contact lockd and statd on the server from > the client(s) saying that the service was non-responsive and/or the server > couldn't be found. I attempted to switch over to /etc/hosts based host > resolution to no avail. I also tried switching to purely IP addr based > connections to no avail. Note NIS/YP kept working. > > Several questions: > > 1. How do I make it so I can completely disconnect my LAN from the rest of > the Internet and not have NFS fail like this > > 2. Why does NFS require a live internet connection? > > -- > Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org My guess would be DNS. If your cable _modem_ (not just connection) was out, and your machines are configured to use the cable modem as their DNS server, and rpc.statd tried to do a reverse DNS lookup of your client's IP address, then that might cause it to hang. Using /etc/hosts was a sensible move. Perhaps you accidentally left out an address? If it happens again you could use tcpdump to see if anything is trying to contact the cable modem's DNS port. -Alan