FVDW firmware "Case Install"

[fvdw]

What happens if you do no set a fixed ip in your router for the nas ?
And do not use wireless connection of your pc to the lan an be sure that the ip you use in the console is not used by another device.
I noticed in th past that u-boot uses another mac address then the kernel on the network interface. This may be the reason why u-boot is not detected by clunc as the ip broacasted is according the router linked to another device

[wd9895]

All is "hardwired", the NAS is on LAN, no WLAN
The IP is fixed in the router, in the NAS ist DHCP.

I can access the nas webinterface by using the IP address in the browser. Also in the explorer the folders are there.

[fvdw]

I edited my previous post

[wd9895]

I suppose clunc talks over the IP, not over MAC address.

How can I solve that behavior ?

[fvdw]

Yes clunc sends this ip to the nas but the nas won't be able to use it because your router has reserved this ip for a different mac address, this only true if my memory is correct that u-boot is using a different mac address. If this is the cause then you have two options.
(1) use another ip when you want to use clunc. This will not interfere with fvdw-sl firmware fixed ip as that is set by the firmware at boot and uses the ma address that probably is used in you router
(2) do not set a fixed ip in your router

If the mac address used by u-boot is not different then I don't know what the problem could be.

[fvdw]

Yes clunc sends this ip to the nas but the nas won't be able to use it because your router has reserved this ip for a different mac address, this only true if my memory is correct that u-boot is using a different mac address. If this is the cause then you have two options.
(1) use another ip when you want to use clunc. This will not interfere with fvdw-sl firmware fixed ip as that is set by the firmware at boot and uses the ma address that probably is used in you router
(2) do not set a fixed ip in your router

If the mac address used by u-boot is not different then I don't know what the problem could be.

[Jocko]

You can see if eth0 mac has been previously changed :

Code: Select all

ethtool -P eth0

will give you the original MAC address

Code: Select all

ifconfig eth0

will give the current MAC address.

If they are different, you can try to restore the original MAC address:

create a sh script with these commands (eth0 must be bring down to change its MAC address)

Code: Select all

#/bin/sh
ifconfig eth0 down
ifconfig eth0 hw ether your-original-mac
ifconfig eth0 up

to run the shell you need to background it and detach it of the terminal

Code: Select all

nohup sh ./yourscriptname.sh &

[fvdw]

If my memory is correct then u-boot uses its own mac address (hard coded in the source code). You will not discover that when you run the kernel. The only way to find that out is via u-boot console and print the environment variables. If you cannot use the uboot console of the fvdw-sl console then you need to use the serial port

[wd9895]

I'm lost now.

How should I know the IP address to tell the console programm if the IP of the NAS is not fixed in the router ?
As far as I read correctly the NAS has to be unpowered before I start the console.
That does not work.

My Fritzbox tells me a mac address of a running NAS but not a U-boot mac.
And sorry, I haven't got a clue what Jocko is talking about. I have a Windows 7 PC, I can open a CMD and a Putty SSH but not more.

My personal NWS2 I disassembled the HDD, connected it on the SATA controller and booted a Live Unbuntu from CD. That was not very handy but it worked so I was very curious to test the "case" install. It's disappointing.

[fvdw]

I'm lost now.

How should I know the IP address to tell the console programm if the IP of the NAS is not fixed in the router ?
As far as I read correctly the NAS has to be unpowered before I start the console.
That does not work.

You do not need to know it, when u-boot boots it looks for a broadcast signal, this signal is provided by the clunc program. If u-boot detects this signal it sets the ip send by clunc and switches to net console mode and after that the fvdw-sl console starts netcat in a command window and connects to the netconsole of the nas and then you have your "u-boot console" up and running.

I just checked my 5big2 and nwsp2 but on these two devices u-boot is using the same mac address as displayed when running the firmware. So forget what I said, this is probably not the problem
Is your router set that allows broadcast over the lan ? broadcasting is done via ip x.x.x.255 AFAIK if that is deactivated or you have set a netmask that exclude connection to this ip then also clunc cannot interupt boot.
(subnet mask of your network card should be 255.255.255.0)

My Fritzbox tells me a mac address of a running NAS but not a U-boot mac.

see my previous remark about mac used by u-boot and the firmware. Could be that this is not the problem

And sorry, I haven't got a clue what Jocko is talking about. I have a Windows 7 PC, I can open a CMD and a Putty SSH but not more.

when you have made a ssh connection with putty to your nas running the firmware then you get a linux prompt and can use the commands given

My personal NWS2 I disassembled the HDD, connected it on the SATA controller and booted a Live Unbuntu from CD. That was not very handy but it worked so I was very curious to test the "case" install. It's disappointing.

Well it works for many people so something in your LAN must be preventing it from working.