LACIE D2 Network 2 Project (2)

[fvdw]

the standalone kernel assigns itself two static ip addresses 192.168.1.252 and 192.168.0.252, this is hard coded in the kernel and cannot be changed. However the kernel also tries to get a dynamic ip address from a dhcp server in the LAN, so you could check if your dhcp server (most of the time a router) has assigned an ip to you D2 network2 when the standalone kernel is loaded and then use that to let the telnet client connect (use connect button in telnet client to manual enter an ip to be used to connect).
If there is no dhcp server in the LAN then you need to change your LAN settings to use 192.168.1.xxx or 192.168.0.xxx and use the static ip's mentioned above. I do not recommend this last setup as the kernel may give up after 5 attempts to get a dynamic ip and then my become not responsive.
In reality using LAN's without dhcp server is very uncommon, almost everyone has a dhcp server running.

[musafirrlail]

Thanks for coming fvdw :applause

In reality using LAN's without dhcp server is very uncommon, almost everyone has a dhcp server running.

So I just want confirm from your explanation that many who use the DHCP feature in this process, is the probability when using STATIC can run well?

It is not feasible for me to use DHCP because unfortunately using a different IP, namely:

IP: 10.57.78.89/28
NM: 255 255 255 240

If it is still possible to use the STATIC I intend to direct live just between D2N2 <-> NIC laptops, What do you think? :shocked

[Jocko]

It is not feasible for me to use DHCP because unfortunately using a different IP, namely:

I saw with your posted pics that d2nw2 ip address is 10.57.78.81 from the fvdw-sl console window.
That means that you entered manually this address in the related fvdw-sl console field?

And if you don't use a dchp server, the standalone kernel assigns itself two static: either ip addresses 192.168.1.252 or 192.168.0.252. In this case the laptop must be also included in the smae LAN and use an IP address 192.168.1.xx or 192.168.0.xx (and also your router 192.168.1.1 or 192.168.0.1).

[musafirrlail]

Okay, Am understand for your according ..

I want try with your guidance, At least if I found any problem will tell you reply ..

[musafirrlail]

Hello, Report

Why do I always fail at step 6 when I've followed the suggestion to change the IP be 192.168.1.252 on D2N2 device, What is wrong with the way I do?

And after the 1 to 5 goes well then the process 6 always fail to notice that the telnet discconect

At below here is view untill step 3 run well :

http://tinypic.com/view.php?pic=kst9x&s=8

And this is below here view step 6 failure :

http://i62.tinypic.com/2r6lbmr.png

Am surely IP lacie D2N2 & my IP laptop is below here :

http://tinypic.com/r/16h4yf5/8

:scratch

[musafirrlail]

Hello, The discovery of what I've done

1. After I read on the installed firmware help me find some indications that I think is the cause, I think that the previous hard drive that I use is the result of a default firmware installed that I created on the hard drive with a 250GB capacity, I took the initiative to replace the hard drive with whom I have never install firmware LACIE other words partition is empty,

(Picture attach)
http://i61.tinypic.com/10ncg1l.png

2. I repeated the process of installing the firmware fvdw after I replace the new hard drive partition that is not contained therein and in step 6 runs smoothly until a data copy process

(Picture attach)
http://i61.tinypic.com/33kubti.png
http://i57.tinypic.com/66et8x.png

3. The process goes to show the received data transmission reaches 64MB, while I let the process run its course

(Picture attach)
http://i60.tinypic.com/16hso4z.png

4. But suddenly bring up notification informing that telnet back can not connect while the data copy process is still underway and running with percentage changes approaching 53%

(Picture below here)
http://i59.tinypic.com/2utq2d4.png

5. And in the end the data copy process is completed so that the peer that originally connected by itself disappears and no other activity appears to be the development of installation, Here is my show log viewer so that you would be able to assist the analysis of which I faced.

(Picture below here)
http://i59.tinypic.com/1giooz.png

I hope from what I described above can facilitate correct mistakes I did, thanks

[Jocko]

As previously written, when you have the timeout issue, that means that tftpd failed to download the standalone kernel.

This is the case with your pics http://i61.tinypic.com/10ncg1l.png. It is useless to try the next steps.

So tftpd failed to find the kernel image "TFTP error: File not found". The selected filename seems to be empty. (filename ''.)
So I think that you must just try again to select it.

[musafirrlail]

then what do I do now?

So I think that you must just try again to select it.

What you mean this and what I do with select ?

So I've done select source IMAGE from tftp folder -> nwsp2 -> xfvdw-sl-15-1-nwsp2-18feb2014

[Jocko]

What you mean this and what I do with select ?

there is something wrong how you select the standalone kernel.

At least you made this error :
at step 3, it is not the firmware image xfvdw-sl-15-1-nwsp-18feb2014.img in nwsp2 but in the parent folder tftp the file "UIMAGE-395-NWSP2CL-179-standalone" as written in the install firmware help.

[musafirrlail]

:hail :hail Yeay ... :hail :hail

http://i62.tinypic.com/zojalv.png

Learn next step