@fvdwfvdw wrote:What you have set in the past as static ip address when using the Lacie firmware has no meaning anymore. (I told you that already once)
I understand your exasperation but please believe me when I assure you that I didn't ignore what you wrote the first time.
The fact remains that the ip address which my DHCP server/router has continued to assign is unchanged from the static address I originally set for the Lacie firmware. The proof (if any is needed) is that the whole of the installation of the fvdw firmware I've just carried-out was (successfully) transmitted via the telnet client to the NS2 using that ip address.
I can understand that the firmware uses the ip address assigned by the DHCP server (in my case my router). But did you really mean that the firmware can only use that address if it's dynamically assigned? ie that dynamic assignment is mandatory? Why would the firmware care...?The standard fvdw-sl firmware use a dynamic IP address assigned by dhcp server.
I do know it (because my router is telling me what it is). But no connection to the fvdw web interface is able to be made by using it.To opne the web interface you need to know the ip addres of the nas....So the only thing left to do is finding out which ip the nas has gotten from your router.
Sad to say, I've tried everything including timing it against the second-hand on my watch. Nothing has worked.PS the nswp2 should respond to the power button. But you have to use it as follow.
press it and keep it pressed for 1 second but no longer then 5 second and then release it will cause a reboot. press it en keep it pressed for more then 5 seconds will cause a power down.
