Transfer of kernel via u-boot fails

[fvdw]

The LAN setup is pretty basic. The PC and NAS are connected to the same switch. There is a router that handles WAN traffic (internet) and DHCP also connected to the same switch.

That should be ok but one thing
does the router allow communication for the whole set of ip's in the range 192.168.1 -192.168.1.254 ?

[redbeard]

I got a hold of another computer and decided to assign it a static IP and connect it to an isolated switch with only the NAS plugged into it -- no router.

It worked!
:woohoo

Thank you for the help. I owe you a beer!
:beer:

[Jocko]

Hi

Yes with this configuration fvdw-sl console can work nicely. Indeed on the nas side, there is an additional way so that it sets itself a right IP : nas detects the IP used by the laptop (fvdw-sl console) when the boot-loader is stopped and then knows what is the current subnet. So the nas assigns a temporary static IP for itself on this subnet.

And in this case no need to have a DHCP available on your subnet.

[redbeard]

Hi

Yes with this configuration fvdw-sl console can work nicely. Indeed on the nas side, there is an additional way so that it sets itself a right IP : nas detects the IP used by the laptop (fvdw-sl console) when the boot-loader is stopped and then knows what is the current subnet. So the nas assigns a temporary static IP for itself on this subnet.

And in this case no need to have a DHCP available on your subnet.

Yep after I discovered that clunc-open sends a magic packet (LUMP) to the NAS to assign an IP I realized DHCP is not necessary until after the firmware is installed. So I could use a static IP and fvdw-sl-console would still detect the subnet and perform the install without a router. :thumbup

[fvdw]

Glad to hear you got it working

About the beer, thx appreciated :-D :-D and thank you for your donation :punk