On Thu, Apr 9, 2015 at 9:20 PM, Gregory Boyce <gregory.boyce@xxxxxxxxx> wrote: > On Thu, Apr 9, 2015, 8:23 PM Trond Myklebust > <trond.myklebust@xxxxxxxxxxxxxxx> wrote: > > On Thu, Apr 9, 2015 at 3:34 PM, Gregory Boyce <gregory.boyce@xxxxxxxxx> > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
