[SOLVED] Access denied by the host (nfs.mount from the Slackware64-current installer)
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Access denied by the host (nfs.mount from the Slackware64-current installer)
I am attempting a NFS install of Slackware64-current (up to date as of now) in a VirtualBox VM.
I do "setup 2>ERRORS", in the SOURCE step I choose "Install from NFS", choose the automatic DHCP configuration, check it with "route" in tty2. The gateway is 10.0.2.2 and I can ping it.
Then I input the Slackware source directory as /archives/versions.
The mount command
Code:
mount -r -t nfs -o vers=3 10.0.2.2/archives/versions /var/log/mount
fails and in /ERRORS in the installer I see:
Code:
if addaddress6: Operation not supported # This doesn't hurt, I think.
mount.nfs: access denied by server while mounting 10.0.2.2/archives/versions # This is fatal.
You are exporting to only 10.0.2.2 which as I understand is that NFS server machine itself (the gateway?).
Try using a subnet that covers the IP address of your VM.
You are exporting to only 10.0.2.2 which as I understand is that NFS server machine itself (the gateway?).
Try using a subnet that covers the IP address of your VM.
Yes it is the gateway. How should I write the command to cover the whole subnet? Sorry, I am a pure newbie in networking. The IP address of the VM as reported by "route" in the VM itself is 10.0.2.0.
Last edited by Didier Spaier; 02-21-2016 at 04:43 PM.
Add "insecure" to your mount options in /etc/exports and the error about the illegal port will disappear.
It worked, thanks Eric!
I still the same error on the client side, but "ls /var/log/mount/" shows the series of packages and I could install the Y series although very slowly (maybe because actually I mounted 10.0.2.2:/archives/versions/slackware64/slackware?). I will continue my investigations later. Still curious why this port is used though. This could be a VirtualBox setting but Google gave me no clue. In VBox.log, I just see the DHCP lease, maybe I can increase the verbosity.
Well, the NFS daemons assign random ports to incoming connection requests from clients, that is why you see these strange high port numbers.
The SlackDocs wiki contains an article about NFS, and it documents how you can select fixed port numbers for the NFS services, which will make it possible to make holes in a firewall for instance: http://docs.slackware.com/howtos:net...home_nfs_howto
Slow transfers will have nothing to do with the particular directory you mapped, it will be a network related issue.
To do that I made an ISO from an up to today local mirror, named it /archives/images_iso/slackware64-current-install-dvd.iso and used it as virtual DVD in a VM. Then when asked I chose install from NFS, accepted the automatic dhcp connection, provided the IP of the VM's gateway, confirmed the NFS settings, then was told that an ISO image of Slackware install DVD was found and gratefully accepted to have it mounted and used as a package source.
Notes.
Do not tell INCISO that the ISO image I used is not a genuine one. That could make it angry
Yes, doing that is uselessly convoluted as I could have chosen "install from a Slackware DVD" instead, but that's not the point here.
"grep INCISO usr/lib/setup/*" in the initramfs tells me that I could do something similar with the ISO on a hard disk partition or an already mounted directory. I will try that as well just for fun.
Caveat emptor: with this setting the exported directory is writable from anyone anywhere. This is probably not ideal from a security point of view, so enhance it to better secure your data.
Last edited by Didier Spaier; 02-29-2016 at 03:18 AM.
Reason: Caveat emptor added.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.