Closed GoogleCodeExporter closed 9 years ago
The box is using DHCP, it received the IP 10.0.1.213 from the 10.0.1.1 router
and configured itself OK as you can see in lines 409 and following.
Samba, and NFS, is working, you should be able access your files.
The issue is that inetd is not starting, see line 357. And it controls httpd,
ssh, telnet, ftp and other services, so you have none of these.
This is most likely caused by a corrupted configuration file (/etc/inetd.conf).
The default file is attached -- tabs and unix aware, don't edit under MS-W.
The easiest way to recover is to reset all configuration files to default
values, read the "About Leds and Buttons" wiki:
Recovery Actions
The back button also has two recovery actions if the "Enable Recovery" checkbox
in Services->System->sysctrl->Configure is checked:
4.1 If you keep the back button pressed for more than ten seconds, you can
telnet the box at port 26, as root and without password. This is a safeguard in
case you forget the password.
4.2 As a last safeguard, if you press the back button for more that twenty
seconds, all the settings saved in flash will be erased, and the box will do a
controlled reboot. This is a last resort safeguard, in case you mess the box
configuration so much that you can't do anything with it; after the reboot the
box will behave as if no settings has ever been saved, and you have to struggle
to find its IP (if you have a DHCP server enabled in your network, the box will
use it).
All settings will be erased, hope that you have saved a copy in your desktop
computer, otherwise you will have to perform a full reconfiguration.
Original comment by whoami.j...@gmail.com
on 16 Aug 2013 at 11:02
Attachments:
Jose - Thanks! I have been a user of ALT-F for several years and on 3
different boxes. I would totally be lost without your firmware...or, at least
close to broke trying to invest in hardware.
Thanks a million.
Original comment by jbqu...@gmail.com
on 17 Aug 2013 at 3:16
Not really an Alt-F issue (although inetd.conf got somehow corrupted)
Original comment by whoami.j...@gmail.com
on 17 Aug 2013 at 1:56
Original issue reported on code.google.com by
jbqu...@gmail.com
on 16 Aug 2013 at 6:43Attachments: