On Tuesday, September 18, 2012 11:50:57 PM UTC+1, Talandir wrote:
El martes, 18 de septiembre de 2012 23:04:18 UTC+2, Joao Cardoso escribió:
On Tuesday, September 18, 2012 8:51:16 PM UTC+1, Talandir wrote:Hi all,
I flashed Alt-F around three weeks ago (RC2). It worked properly and was able to set up the RAID on ext-4 hard disks.
Suddenly it stopped responding to the web page, shares and telnet. The blue light is steady on, and it responds to the main button (to reset or power off).
So Alt-F is working.
I tried a reset, turning it off and on again... same result. Waited for one whole day just in case it was performing an fsck or any other task (even when the blue light was steady). Still no result.
Tried the 10 seconds, 20 seconds, 40 seconds reset just in case... the box resets itself but same situation. No telnet on port 26 either.
Are your using a fixed or a dynamic (DHCP) IP? Have you checked your router DHCP server client lease? The box might have changed IP. Can you ping it?
Ping doesn't work.
So you are not using the right IP, as Alt-F itself is working (the front and back button works)
I am using dynamic DHCP, with fixed address in the router. The DHCP screen doesn't have anything that could be the box in any other address.
It looks like Alt-F is not getting an IP.
A strange symptom. When I try to access with Firefox it splits the screen in two and gives the message of "not responding" on both. So at least I can be sure the address is right. It is just not working.
I don't believe on browser "diagnostics". Try pinging the box to make sure that the IP that you are using is right.
No ping. I also just checked the ARP table and the ethernet address of the DNS is not there either. Actually this should mean that the response to the web request should just not be there... I'm puzzled.
As I said, don't believe on browser "diagnostics" for this kind of situations.
You could use 'nmap' to discover all hosts on your network, but if your DHCP router doesn't list the 323, than it might not have an IP.
In order to get and IP, Alt-F uses:
# get an ip using the following priority:
# 1st, use kernel cmd line ip= (kexec or fonz reloaded/"on top")
# 2nd, use defaults stored in flash
# 3d, try to read vendor sib.conf (previous DLink IP, is static)
# 4th, try to use a dhcp server
# 5th, find and use a non-used ip address from 192.168.1.254 to 230 range
-As you have flashed Alt-F, then 1 don't apply.
-When you performed a hard-reset (pressing the back button for more than 20 seconds), all flash saved settings was erased, so 2 and 3 does not apply.
-As your DHCP server does not lists the box, than 4 don't apply.
-So the box must have the 192.168.1.254 IP (or 192.168.1.252 if 192.168.1.254 is in use, etc)
Of course, all this assumes a good network cable. Have you tried another one? I know, I know, you have not messed with it, but try another one first.