OpenWrt Forum Archive

Topic: Fonera non load SSH access

The content of this topic has been archived on 9 Feb 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

hi all!!

with this my first post, i want to saying "hola" to all users of openwrt forum!!


i'm trying to flashing La Fonera..

i follow this italian guide; in the web, you can find some of similares, but this is the best!


now, i have:
- downgrade the fonera
- open the ssh port (?)
- load redboot and its config
- install kamikaze (latest version)


if i reboot the fonera, if i want to have an access from ssh port, i must connect from telnet on 192.168.1.254:9000 and launch these tw commands:
- fis load -l vmlinux.bin.17
- exec
and now i have the ssh access, until i reboot!

i must repeat this sequence every time i reboot my fonera.. why this problem?

i want have the access on ssh on 192.168.1.1 automatically, every time i reboot..!


thank's,
Trew

(Last edited by Trew on 30 Nov 2007, 10:30)

ok, i will test that command this afternoon..! thanks!

but, if i reload redboot e its config?
it's possible to delete the problem?

with my precedent fonera, i hadn't this problem..

yes, you need to add an option with fconfig to execute the fis load... command then your problem is fixed

my example:

RedBoot> fconfig -l -n
boot_script: true
boot_script_data:
.. fis load -l vmlinux.bin.l7
.. exec

boot_script_timeout: 1
bootp: false
bootp_my_gateway_ip: 0.0.0.0
bootp_my_ip: 0.0.0.0
bootp_my_ip_mask: 255.255.255.255
bootp_server_ip: 0.0.0.0
console_baud_rate: 9600
gdb_port: 9000
info_console_force: false
net_debug: false

you need to define this 2 options: boot_script and boot_script_data

something like this (not tested):

RedBoot> fconfig boot_script true
RedBoot> fconfig boot_script_data fis load -l vmlinux.bin.l7
RedBoot> fconfig boot_script_data exec

(Last edited by michu on 30 Nov 2007, 14:09)

wowwwwwwwwwwww!!

you are fuckly the best!!

now, my special guest is like this:

RedBoot> fconfig -l -n
boot_script: true
boot_script_data:
.. fis load -l vmlinux.bin.l7
.. exec

boot_script_timeout: 10
bootp: false
bootp_my_gateway_ip: 0.0.0.0
bootp_my_ip: 192.168.1.254
bootp_my_ip_mask: 255.255.255.0
bootp_server_ip: 0.0.0.0
console_baud_rate: 9600
gdb_port: 9000
info_console_force: false
net_debug: false

and now, with that two commands, the kernel switch on by itself..!

thanks still

The discussion might have continued from here.