[PROBLEM] Ethernet works fine playing music, Wi-Fi doesn't

[Joseph.Barrow]

Leave WiFi as configured, reboot and then look at the status for the NFS share you are mounting.

Code:

mount | grep nfs4

Example from one of my systems that mounts an NFS share hosted on another Pi.

Code:

pi@moode:~ $ mount | grep nfs4
192.168.1.199:/media/VFAT128/FLAC on /mnt/NAS/TRX-NFS-FLAC type nfs4 (ro,relatime,vers=4.2,rsize=131072,wsize=131072,namlen=255,soft,proto=tcp,timeo=10,retrans=1,sec=sys,clientaddr=192.168.1.121,local_lock=none,addr=192.168.1.199)

Before reboot, with Ethernet:

Code:

joe@wireless:~ $ mount | grep nfs4
192.168.18.16:/media/depot/audio/audio on /mnt/NAS/TheTome type nfs4 (ro,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,timeo=10,retrans=1,sec=sys,clientaddr=192.168.18.30,local_lock=none,addr=192.168.18.16)

After reboot, without Ethernet:

Nothing.

After reboot, with Ethernet:

Code:

joe@wireless:~ $ sudo mount | grep nfs4
192.168.18.16:/media/depot/audio/audio on /mnt/NAS/TheTome type nfs4 (ro,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,timeo=10,retrans=1,sec=sys,clientaddr=192.168.18.30,local_lock=none,addr=192.168.18.16)

I'm not proficient with NFS aside from looking up stuff to set it up, so I don't know what differences I'd be looking for. But... it seems to me that the 'clientaddr' needs to point to my Wi-Fi address, not my Ethernet address. Granted, with just Wi-Fi, it's not mounting anything at all, and a 'mount -a' isn't doing anything... and I've just remembered that I don't have any NFS mounts in the new fstab that I might have had in the old one. Still... it mounted with an Ethernet connection and ignored Wi-Fi.

 If I'm right, then how do I fix it?

And congratulations for 10 years, while I'm thinking about it!