On 07/23/14 19:23, Rick Stevens wrote:
Bob, get on the NFS server and verify that it's allowing mounts from the DHCP domain. It appears your VM is using DHCP to get an IP and it may be that your NFS server isn't exporting to the network or IP your client got via DHCP.
The fact you got it mounted this time may just indicate that THIS TIME you got an IP allowed by the server. Next time, you may not be so lucky. :-/
- Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com -
I have a Cisco E3000 router using the Tomato version of DD-WRT which is set up to assign dhcp addresses to everything in the 192.168.1 xxx range.
However the VM shows 192.168.122.14, what is that, how would I deal with it with the present net assignments, I have a ton of devices assigned by dhcp as it is? Obviously things are happening that I haven't seen before and don't understand.
Everything appears to have survived a reboot this morning so for the moment I have no recognized problems ...
Tnx,
Bob
[root@localhost Downloads]# ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.122.14 netmask 255.255.255.0 broadcast 192.168.122.255 inet6 fe80::5054:ff:fedc:de35 prefixlen 64 scopeid 0x20<link> ether 52:54:00:dc:de:35 txqueuelen 1000 (Ethernet) RX packets 36637 bytes 47030975 (44.8 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 20354 bytes 2160974 (2.0 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 0 (Local Loopback) RX packets 8 bytes 764 (764.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 8 bytes 764 (764.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0