Hello All, Bind_address appears to be ignored in NFS Ganesha 2.7 to NFS Ganesha 3.4? This used to work in Ganesha 2.6. Do I need to add a parameter to my config to make this work again? [root@nfs03 ~]# vi /etc/ganesha/ganesha.conf [root@nfs03 ~]# [root@nfs03 ~]# [root@nfs03 ~]# grep -Ei Bind_addr /etc/ganesha/ganesha.conf Bind_addr = 192.168.0.125; [root@nfs03 ~]# [root@nfs03 ~]# grep -EiB5 Bind_addr /etc/ganesha/ganesha.conf KeytabPath = /etc/krb5.keytab ; Active_krb5 = YES ; } NFS_Core_Param { Bind_addr = 192.168.0.125; [root@nfs03 ~]# [root@nfs03 ~]# [root@nfs03 ~]# netstat -pnltu|grep -Ei 2049 tcp 0 0 0.0.0.0:2049 0.0.0.0:* LISTEN 5412/ganesha.nfsd udp 0 0 192.168.0.125:2049 0.0.0.0:* 5412/ganesha.nfsd [root@nfs03 ~]# rpm -aq|grep -Ei ganesha nfs-ganesha-mount-9P-2.7.6-2.el7.x86_64 nfs-ganesha-utils-3.4-1.el7.x86_64 centos-release-nfs-ganesha28-1.0-3.el7.centos.noarch nfs-ganesha-3.4-1.el7.x86_64 nfs-ganesha-proxy-3.4-1.el7.x86_64 nfs-ganesha-vfs-3.4-1.el7.x86_64 centos-release-nfs-ganesha30-1.0-2.el7.centos.noarch nfs-ganesha-gluster-3.4-1.el7.x86_64 [root@nfs03 ~]# -- Thx, TK.