-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: <alpine.LNX.2.00.1307140008050.16893@Telcontar.valinor> On Saturday, 2013-07-13 at 11:47 +0400, Andrey Borzenkov wrote:
В Thu, 11 Jul 2013 15:02:55 +0200 (CEST) "Carlos E. R." <> пишет:
Now I need it to work from the laptop, and it fails.
So what exactly did you change? You say it was working before so you changed something, right?
Me, nothing. I upgraded the server system from 12.1 to 12.3, an offline upgrade procedure. The exports file was not touched. The client system, the laptop, is still 11.4.
[...]
And in the client I see the package going out from port 1004 to 2049, but no answer from the server. Why no answer?
Did package reach the server at all? Use tcpdump/tshark to verify.
The server firewall logs the package as being allowed, so yes, it does reach the server.
Is there some other configuration file for NFSserver where one can specify which interfaces to listen on?
man 8 nfsd
I see nothing there about a configuration file, or related to my problem. The word "interface" does not exist. For the record, I solved the problem by forcing the client in the laptop to use NFS 3 (nfsvers=3). I changed the fstab like this: 192.168.1.14:/data/storage_c/repositorios_zypp/ /var/cache/zypp/nfs_packages nfs defaults,noauto,_netdev,nfsvers=3 0 0 And it works, which is a regression, because previously it worked with nfsvers=4. And it is weird, because two clients using 12.3 can connect with nfs 4. - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlHh0z8ACgkQtTMYHG2NR9VeTACdHClzwa+PlL81IaB5LiaikZCC 4UsAn1SJywWoJZcFbTowqlKjC8Y+NugD =9Pb9 -----END PGP SIGNATURE-----