Return-Path: Received: from mail-vn0-f42.google.com ([209.85.216.42]:37524 "EHLO mail-vn0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751554AbbDJSp2 (ORCPT ); Fri, 10 Apr 2015 14:45:28 -0400 Received: by vnbg129 with SMTP id g129so7652367vnb.4 for ; Fri, 10 Apr 2015 11:45:27 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: Date: Fri, 10 Apr 2015 14:45:26 -0400 Message-ID: Subject: Re: Problems mounting via UDP from a netapp with multiple interfaces From: Trond Myklebust To: Gregory Boyce Cc: Linux NFS Mailing List Content-Type: text/plain; charset=UTF-8 Sender: linux-nfs-owner@vger.kernel.org List-ID: On Thu, Apr 9, 2015 at 9:20 PM, Gregory Boyce wrote: > On Thu, Apr 9, 2015, 8:23 PM Trond Myklebust > wrote: > > On Thu, Apr 9, 2015 at 3:34 PM, Gregory Boyce > wrote: >> Folks, >> >> I've been encountering a problem with NFS clients attempting to mount >> from a netapp via UDP where the netapp is responding on the wrong >> interface. On some of our older systems, this mount worked properly, >> while on newer systems nfs-utils ends up failing the mount. Mounting >> via TCP works fine. > > > This is a server bug.. Those are not fixable on the client. > > Trond > > > > Since the clients are successfully mounting the filers right now with much > older client software, it seems to me that it can at least be worked around > on the client side. > No. You are not supposed to be able to work around security issues, and it is indeed a security issue when a client gets a reply from an IP address that it does not recognise as being the same as the one it sent an RPC to. NetApp is aware of this bug, and has had burts open for it for at least a decade now. Have you tried contacting them for a fix? Trond