2013-01-19, 02:02
Hi all,
I am using NFS to access files from my NAS in XBMC (Raspberry Pi, raspbmc), because a lot of reports state that the protocol is a lot more efficient than SMB. When browsing for a source though, it presented me with a list of NFS servers using their IP addresses. Because I am using a crappy router built into my cable modem, there is no way to assign static IP addresses to my devices. I still used the nfs://<IP> paths for my shares, because using the hostname sometimes gives me problems (XBMC not being able to find the host), probably also due to the crappy router.
Because my NAS is always active, the IP address actually didn't change until now; I guess it has to do with the power failure I had. After the IP address changed, I obviously couldn't access the shares on XBMC. I used path substitution in advancedsettings.xml to fix this, but still updating my library hangs at the "preparing..." stage (translated form dutch). To finally fix this again, I logged on to my XBMC box, opened the video and music database in sqlite and replaced the paths (in my case: "update path set strPath = replace(strPath, '192.168.0.240', '192.168.0.241');").
My questions are:
- Is there a reason why browsing for NFS shares uses IP addresses instead of hostnames?
- If not, when the IP address of your shares changes, is there a better way to replace the paths?
I know a better solution would be to use a decent router which allows me to at least set fixed IP addresses for my fixed devices, and I will be doing that soon. But than I have to explain to my girlfriend why there is another box plugged in next to the modem :-)
Greetings,
JeDi
I am using NFS to access files from my NAS in XBMC (Raspberry Pi, raspbmc), because a lot of reports state that the protocol is a lot more efficient than SMB. When browsing for a source though, it presented me with a list of NFS servers using their IP addresses. Because I am using a crappy router built into my cable modem, there is no way to assign static IP addresses to my devices. I still used the nfs://<IP> paths for my shares, because using the hostname sometimes gives me problems (XBMC not being able to find the host), probably also due to the crappy router.
Because my NAS is always active, the IP address actually didn't change until now; I guess it has to do with the power failure I had. After the IP address changed, I obviously couldn't access the shares on XBMC. I used path substitution in advancedsettings.xml to fix this, but still updating my library hangs at the "preparing..." stage (translated form dutch). To finally fix this again, I logged on to my XBMC box, opened the video and music database in sqlite and replaced the paths (in my case: "update path set strPath = replace(strPath, '192.168.0.240', '192.168.0.241');").
My questions are:
- Is there a reason why browsing for NFS shares uses IP addresses instead of hostnames?
- If not, when the IP address of your shares changes, is there a better way to replace the paths?
I know a better solution would be to use a decent router which allows me to at least set fixed IP addresses for my fixed devices, and I will be doing that soon. But than I have to explain to my girlfriend why there is another box plugged in next to the modem :-)
Greetings,
JeDi