Ok6410 mounting fedora NFS solves mount: RPC: unable to receive; errno = No route to host

One Platform

1. ok6410 a Development Board host fedora 18

2. Basic Steps 1.

Mkdir NFS chmod 777 nfs cd nfs mkdir work
Chmod 777 work
CD work

Touch nihao

2. Configure the NFS service

Fedora includes the Portmap service in rpcbind, without Portmap. Therefore, rpcbind is installed.

Yum-y install rpcbind nfs-kernel-Server

3. edit/etc/exports

VI/etc/exports

The first entry should be a new file with no content

Add the following line

/Nfs/work * (RW, sync, no_root_squash)

/Nfs/work is the directory to be shared. * indicates that all IP addresses can be mounted.

4. Start the NFS service

Service NFS start enable service NFS status to view the status

Service NFS Stop Service NFS restart Restart service

You can also set it to boot NFS service systemctl enable nfs-server.service

Similarly, start the rpcbind service.

Service rpcbind start

5. Disable the firewall (Be sure to disable it)

1. If it is not disabled, it will appearMount: RPC: unable to receive; errno = No route to host.

For more information about the firewall, sometimes the service iptables stop will not be mounted successfully.

To completely disable the firewall: see (Http://www.boh.so/html/2013/doc_0202/1800.html)

Systemctl stop firewalld. Service Systemctl disable firewalld. Service
2. It is also important to disable SELinux.
Temporarily disable setenforce 0
Permanently disable VI/etc/sysconfig/SELinux
Modify SELinux =Disabled

6. Ping the Development Board and host

1. Run ifconfig on the Virtual Machine Linux to know that the virtual machine IP address is 192.168.1.101. Start the Development Board to enter the Linux system (we can use minicom or the Super Terminal to communicate with the Development Board through serial port). 2. Enter ifconfig on the terminal.

In fact, in the latest Linux kernel, The setip interactive interface is already available under forlinx test on the main interface. We can

View, you can also change the IP address.

The IP address of the Linux development board is ..... 3. if the IP address is not in the same CIDR block as the IP address of the VM, modify ifconfig eth0 192.168.1.110 (you can change it using setip). 4. ping 5. enter Ping 192.168.1.101 on the terminal to ping 125.217.32.237 (125.217.32.237): 56 data bytes
64 bytes from 125.217.32.237: seq = 0 TTL = 64 time = 24.942 MS
64 bytes from 125.217.32.237: seq = 1 TTL = 64 time = 1.518 MS
64 bytes from 125.217.32.237: seq = 2 TTL = 64 time = 1.025 MS
64 bytes from 125.217.32.237: seq = 3 TTL = 64 time = 0.906 MS
64 bytes from 125.217.32.237: seq = 4 TTL = 64 time = 0.743 MS Ctrl + C Exit packets transmitted, 5 packets received, 0% packet loss at this time Ping

6. First hanging on your host to see if it can be mounted

Enter Mount-t nfs 192.168.1.101:/nfs/root/mnt on the host

Ls/mnt

If you can see nihao, it will be successful.

Unmount: umount/mnt

7. Mount TO THE DEVELOPMENT BOARD

Enter ON THE DEVELOPMENT BOARD

Mount-t nfs 192.168.1.101:/nfs/root/mnt-O nolock

Description: Host IP Address: NFS Directory of the host. The Mount directory of the Development Board.

In this way, you can succeed.

3. Mount: RPC: unable to receive; errno = No route to host

1. Most of them are firewall problems. You must disable the firewall as mentioned above.
Systemctl stop firewalld. Servic

Systemctl disable firewalld. Service
2. Disable selocation
3. The Development Board must ping the host.
4. Restart NFS and rpcbind services