Can't connect to web interface or via SSH

[GoogleCodeExporter]

What steps will reproduce the problem?
1. open web browser
2. type IP of NAS box into browser address bar

or

1. open terminal
2. ssh to IP of NAS box

What is the expected output? What do you see instead?
connect to ssh server or web interface(depending on method)

What version of the product are you using? On what operating system?
Beta 4

Please provide any additional information below.

Samba/CIFS shares are fine and can be browsed to via discovery or 
smb://192.168.1.64/ in nautilus

**
Starting Nmap 5.21 ( http://nmap.org ) at 2010-09-23 22:29 BST
Nmap scan report for Dlink-DNS-323.config (192.168.1.64)
Host is up (0.00087s latency).
Not shown: 998 closed ports
PORT    STATE SERVICE
139/tcp open  netbios-ssn
445/tcp open  microsoft-ds
MAC Address: 00:22:B0:EC:67:32 (D-Link)

looks like the ports(22/80) aren't open after a flash to B4.

Any ideas on how to fix this?(or am I having a blonde moment)

Original issue reported on code.google.com by shaun.sa...@gmail.com on 23 Sep 2010 at 9:36

[GoogleCodeExporter]

Hi,

0-So, you have flashed Alt-F. Did you have any problem while using Alt-F "on 
top" of the vendor's firmware?

1-Has your box a fixed IP or is using DHCP? Are you sure you are accessing the 
right host?

2-While using Alt-F on top of the stok firmware, have you enabled smb and saved 
settings? And changed any inetd configuration and  saved settings?

Because by default samba is not enabled, and I don't understand how can nmap 
report only those open ports. On my system, nmap reports 

Discovered open port 80/tcp on 192.168.1.21
Discovered open port 23/tcp on 192.168.1.21
Discovered open port 21/tcp on 192.168.1.21
Discovered open port 22/tcp on 192.168.1.21
Discovered open port 901/tcp on 192.168.1.21
Discovered open port 515/tcp on 192.168.1.21
Discovered open port 873/tcp on 192.168.1.21

3-Have you tried pressing and *keep* pressing the front button? Does the right 
led starts flashing, then the left led? If not, Alt-F has not booted...

Original comment by whoami.j...@gmail.com on 24 Sep 2010 at 2:56

[GoogleCodeExporter]

0 - Yes, flashed from B3 to B4.

1 - Fixed IP. Ping shows box as responding.
PING 192.168.1.64 (192.168.1.64) 56(84) bytes of data.
64 bytes from 192.168.1.64: icmp_req=1 ttl=64 time=5.00 ms
64 bytes from 192.168.1.64: icmp_req=2 ttl=64 time=0.739 ms
64 bytes from 192.168.1.64: icmp_req=3 ttl=64 time=0.098 ms
^C
--- 192.168.1.64 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.098/1.945/5.000/2.176 ms

2 - Havent used stock firmware since flashing to B3. But I did save SMB 
settings on both.

3 - Yes, tried this and the lights flash amber(first the right one then the 
left one)

Trying to see if I can get the alt-f firmware loaded using ffp, but am stuck at 
how to set the ffp script to executable without telnet access as well.

Original comment by shaun.sa...@gmail.com on 24 Sep 2010 at 5:28

[GoogleCodeExporter]

attached log. alt-f is definitely starting just now web server or ssh daemon.

Original comment by shaun.sa...@gmail.com on 24 Sep 2010 at 5:31

Attachments:

• alt-f.log

[GoogleCodeExporter]

According to alt-f.log inetd is not running... why?
Have you disabled it? Did you use to telnet/ftp/ssh to the box before flashing 
B4?

Is inetd that starts it all, telnet, ssh, ftp, rsync, http... even swat.

I have not provided a back-door or last resort in Alt-F, and if inetd is not 
running the only possibility to communicate with it is using a serial port.
You don't have a serial port, do you? Big trouble.

Do you have soldering skills? http://wiki.dns323.info/hardware:serial

Original comment by whoami.j...@gmail.com on 24 Sep 2010 at 6:33

[GoogleCodeExporter]

didnt do anything unusual(i think) just used the web interface to flash B4 and 
on reboot had no web interface or sshd.

was just reading about serial connections as I had a feeling that it may come 
to this or something involving JTAG cable.

will have to put this on hold until I have all the parts and can assemble them.

at least I still have samba for the moment so can transfer files to/from the 
NAS.

probably some random flash error that did this. will check back in via 
community forums if more help is needed. But I think you've already answered 
most of what I need in a post where someone had bricked there unit.

only thing left is find a kernel file and ramdisk file

Original comment by shaun.sa...@gmail.com on 24 Sep 2010 at 7:06

[GoogleCodeExporter]

Hold-on, I might have found an alternative solution.

If you have installed Alt-F packages, you might have noticed the existence of a 
Alt-F directory in the root of one of your filesystems. The files found there 
override, at run time, the ones loaded from flash.

The only reason I see for inetd not starting is if /etc/init.d/S41inetd has not 
its execution bits set. If one creates an executable 
Alt-F/etc/init.d/S41inetd.conf file on the root of one of your filesystems, it 
will be recognized at boot and will override the non-executable one loaded from 
flash.

To avoid removing the disk from the box and installing it on another computer, 
in order to create that file, you can just use a spare usb pen you have and 
boot the box with is inserted.

1-If you have installed any Alt-F package, then remove all your disks. Its 
better to remove them anyway.

2-On another computer, create on the *root* of a usb pen the directory 
hierarchy Alt-F/etc/init.d/ In principle, a fat or ntfs formated pen will be 
OK, although I have not experimented it.

3-Copy the attached S41inetd file to the init.d directory and make sure it is 
executable. I don't know If you can do it under MS :-o

4-Insert the pen in the box and reboot it.

5-Try connecting. If successful, say hurray, enable inetd "boot at log" and 
save settings. Power off, remove the pen and reboot (you don't need to reinsert 
your disks)

6-If you can't connect, remove the pen, watch the produced log file (hmmm, you 
can't use a ntfs formated pen, no writing is possible, it has to be a fat or 
ext formated pen).
If in the "top" output you see that inetd is running, then the other 
possibility is that it's configuration file is missing or damaged.
Copy the attached inetd.conf file to the pen Alt-F/etc/ directory and repeat 
from 3.

7-Report back, as this might be a serious issue for other users.

Original comment by whoami.j...@gmail.com on 24 Sep 2010 at 9:06

Attachments:

• inetd.conf
• S41inetd

[GoogleCodeExporter]

Let's abbreviate it. Replace step 3 and 5 in the previous message with

3-Copy the attached S40telnetd file to the init.d directory and make sure it is 
executable. I don't know If you can do it under MS :-o

4-Insert the pen in the box and power it on.

5-Try telneting the box. It works, I just tried it.

I am very interested to discover what happened, and examining the saved 
settings is important. Do you mind to execute (copy/paste) the following 
commands

mkdir /tmp/mtd
mount /dev/mtdblock0 /tmp/mtd
last=$(ls /tmp/mtd/set_* | tail -1) 
cp $last /mnt/sda2/
umount /tmp/mtd

You will find in the disks root directory a file with a name similar to 
set_2010-09-25_00:48:58.tgz. It is a compressed tar archive of configuration 
files. Can you post the contents of etc/inetd.conf and permissions of 
etc/init.d/S41inetd?

Try to start inetd by issuing the commands

  rcinetd start

Any errors? Is the inetd command running? Try

  ps

Does inetd appears in the listing?

1-If yes, you can now use the web page. But before anything else, execute 3.
You can now do a poweroff, remove the pen and then poweron.

2-If not, try launching inetd directly
  inetd

Any errors? Can you acess the box web page? If not, copy the inetd.conf file
that I posted in the previous message to the /etc directory and try again:
  cp /mnt/sda2/inetd.conf /etc/

3-Save settings using the following commands:

  chmod +x /etc/init.d/S41inetd
  loadsave_settings -cf # clear flash
  loadsave_settings -sf # save flash

Please don't yet delete the set_xxx.tgz file, it might be needed for further 
diagnostics.

Please report back, it is important to figure out what happened.

Thanks,
Joao

Original comment by whoami.j...@gmail.com on 25 Sep 2010 at 12:20

• Changed state: Accepted
• Added labels: Priority-High
• Removed labels: Priority-Medium

Attachments:

• S40telnetd

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

thanks, with the above info and some playing about got it to work. 
re-downloaded B3 and B4 firmwares to be sure they hadn't been corrupted on my 
end.

1 - i used a usb pen with ext2 fs(youre right can't set +x on fat fs  and no 
write on ntfs types so has to be ext2/ext3). 

  created Alt-F/etc/init.d directory on it
  placed S40telnetd and S41inetd in init.d
  placed inetd.conf in etc
  rebooted

nmap:

Starting Nmap 5.21 ( http://nmap.org ) at 2010-09-25 10:40 BST
Nmap scan report for Dlink-DNS-323.config (192.168.1.64)
Host is up (0.0013s latency).
Not shown: 997 closed ports
PORT    STATE SERVICE
23/tcp  open  telnet
139/tcp open  netbios-ssn
445/tcp open  microsoft-ds
MAC Address: 00:22:B0:EC:67:32 (D-Link)

Nmap done: 1 IP address (1 host up) scanned in 0.59 seconds

2 - logged in via telnet - executed command to copy settings state for you(file 
attached - i cleared the websecret file;but its untouched apart from that)

and tried the first command to start inetd but got an error:

$ rcinetd start
mkdir: cannot create directory '': No such file or directory

however, just typing inetd worked ps.txt for dump. got all services running. 
Got B4 web interface.

3 - then copied relevant scripts and conf files to / . cleared flash and saved 
using loadsave_settings commands above. then removed usb drive. on reboot still 
no joy. 

4 - so i had an idea to re-flash back to B3 and try flashing again. so plugged 
usb drive back in. this worked. got back to a B3 web interface. 
logged in via ssh and cleared flash settings.
and then tried flashing B4 again via web interface(when i checked clear flash 
settings, it gave an error about not finding default, but then went back to the 
image file selection screen. leaving unchecked flashed normally - i may have 
had to pull the power cord to reboot here - but only after it gave the option 
to reboot and then didn't - 5mins of waiting to see if it would or not).

5 - after reboot

nmap:
Starting Nmap 5.21 ( http://nmap.org ) at 2010-09-25 10:58 BST
Nmap scan report for Dlink-DNS-323.config (192.168.1.64)
Host is up (0.0011s latency).
Not shown: 991 closed ports
PORT    STATE SERVICE
21/tcp  open  ftp
22/tcp  open  ssh
23/tcp  open  telnet
80/tcp  open  http
139/tcp open  netbios-ssn
445/tcp open  microsoft-ds
515/tcp open  printer
873/tcp open  rsync
901/tcp open  samba-swat
MAC Address: 00:22:B0:EC:67:32 (D-Link)

Nmap done: 1 IP address (1 host up) scanned in 0.62 seconds

incidentally this as the same as it was when flashed back to B3.

5 - all settings were cleared and set back to defaults. also there was a niggly 
issue with firefox caching web pages. 
i had to clear the firefox cache as the web interface for B4 had the B4 status 
page and the B3 index page(reload after clearing firefox cache sorted that out).

6 - changed the settings back to the way I use them and then saved settings.

7 - on reboot everything is working as i would have expected.

I'm guessing my initial flash which caused the problems may have been a bad one.

Original comment by shaun.sa...@gmail.com on 25 Sep 2010 at 10:29

Attachments:

• ps.txt
• set_2010-09-11_14:21:53.tgz

[GoogleCodeExporter]

Excelent!

I found the problem, and it can affect other users as well.

When you flashed B4, you didn't clear settings first (not your fault, it is not 
in the instructions)

During B4 startup, the inetd init script calls the vsftp init script.
The vsftp init script tries to create a directory whose name is in vsftpd.conf.

The problem is that the *B3* vsftpd.conf file does not contains the name of 
such directory, and as such the mkdir command fails. As the init script has 
"set -e", it fails and the inetd init script also fails, not launching inetd!
Without inetd we have no http (web interface), ssh, telnet, ftp...

And why is B4 using the B3 vsftpd.conf? Because at boot time the flashed 
settings overwrites the filesystem default settings.

Part of my instructions in the previous post are in error: clearing the flashed 
settings and saving them again has no effect unless one changes some settings 
first!

Apart from that, I dont understand why inetd.conf is not present in the 
settings file you posted. Without inetd.conf, even if inetd where running, it 
would not provide any services.

Don't know why anybody else has complained... I will post a warning and provide 
a solution.

Thanks!

Original comment by whoami.j...@gmail.com on 25 Sep 2010 at 4:09

[GoogleCodeExporter]

Just glad we could get to the bottom of this and find a solution which didnt 
involve a serial/JTAG cable.

As of present the download count for B4 bin is 8 and I know 2-3 of those are 
me, so maybe not many people have run into this by chance yet.

Thanks. :)

Original comment by shaun.sa...@gmail.com on 25 Sep 2010 at 6:23

[GoogleCodeExporter]

Just for completeness, here is the posted fix message

If you intent to flash 0.1B4, please follow the steps bellow, in order 
to avoid a more complex recovery procedure. 
While still in 0.1B3, *either* flashed or running "on top" of the 
vendor's firmware:

0-If you have never saved settings under Alt-F, you can flash 0.1B4. 
But to be sure that you have never saved settings, go to the Settings 
web page and be sure that no choices are offered under "Select one". 
Go to step 7 
1-If you don't mind loosing *all* your settings (including the 
vendor's firmware ones), go to the Settings web page and click the 
ClearSettings button.  Go to step 7 

2-telnet or ssh the box 
3-Remove /etc/vsftpd.conf by executing the command
  rm /etc/vsftpd.conf
4-Remove /tmp/settings_saved by executing the command
  rm /tmp/settings_saved 
5-Save settings by executing the command
  loadsave_settings -sf 
6-log out 

7-Flash 0.1B4 using the Firmware web page 

Original comment by whoami.j...@gmail.com on 27 Sep 2010 at 2:07

• Changed state: Verified

[GoogleCodeExporter]

I have the same issue. I had it running perfectly, decided to reboot, no 
connections possible anymore. I didn't modify anything.

Is there an easier way to fix this? I only have a Windows PC so I can't format 
an USB stick with ext2.

Original comment by aschep...@gmail.com on 3 Jul 2014 at 3:24

[GoogleCodeExporter]

aschepers: this is pretty old now, search the forum for a simple solution or 
read the wiki https://sourceforge.net/p/alt-f/wiki/About%20Buttons%20and%20Leds/

Original comment by whoami.j...@gmail.com on 10 Jul 2014 at 10:32