Hi Don,
I found what the problem was about half an hour ago -- the clue was
found in logfiles
/var/log/syslog.1:Apr 24 10:29:19 vega mountd[1320]: refused mount
request from 127.0.1.1 for /export/home (/export/home): unmatched host
I got confused with my old configuration (Red Hat 7.3) where 'mount'
command resolved computer name into DHCP assigned ip address and not to
loopback/127.0.1.1 as it happens in Debian Wheezy/Squeezy.
Once I modified /etc/exports to
/export/home 192.168.0.0/24(rw,sync,no_subtree_check)
127.0.0.0/16(rw,sync,no_subtree_check)
everything started to work as expected-- 'mount' has changed it's
behavior what required an adjustment on my part.
Thank you Don,
Andy
On 4/24/2014 12:14 PM, Dom wrote:
On 24/04/14 18:51, Snow Leopard wrote:
Hi,
OS: wheezy / squeeze
Could somebody explain what wrong?
Why mount refuses to mount through loopback interface?
The issue can be reproduced in your system with next set of commands
root# mkdir -p /exports/home
root# cat >> /etc/exports
/export/home 192.168.0.0/24(rw,sync,no_subtree_check)
This is allowing access to all clients on network 192.168.0.0
^C
root# exportfs -ra
root# mount -t nfs 127.0.0.1:/export/home /mnt
You haven't allowed access to clients on network 127.0.0.0
You probably need something like this in /etc/exports:
/export/home 192.168.0.0/24(rw,sync,no_subtree_check)
127.0.0.0/24(rw,sync,nosubtree_check)
(all on one line, that probably got wrapped)
No bug. Just wrong configuration.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5359649a.1050...@gmail.com
