Howto:Get Access to Gateways if the Assistant doesn't boot the Device: Difference between revisions
| Line 13: | Line 13: | ||
A manual reboot (powercyle) won't help here. The Assistant will be shown again. | A manual reboot (powercyle) won't help here. The Assistant will be shown again. | ||
A booting with sending a !boot (< | A booting with sending a <code>!boot</code> (<code>http://</code><''ip of gateway''><code>/!boot</code>) ends in an non-reacting http-Server. | ||
It is still there but has no content. | It is still there but has no content. | ||
Dealing with the | Dealing with the tftp mode and gwload to update firmware or bootcode doesn't help either. | ||
But you can get access to part of the gateway's | But you can get access to part of the gateway's web-gui when calling | ||
<code>http://</code><''ip of gateway''><code>/CMD0/mod_cmd.xml?cmd=xml-modes&menu=maintenance.xml&xsl=tab.xsl&help=Maintenance</code> | |||
in your | |||
in your web-browser. | |||
This will show the part of the gui where you can deal with firmware bootcode and config. | This will show the part of the gui where you can deal with firmware bootcode and config. | ||
Downloading the config, editing the config in the line with | Downloading the config, editing the config in the line with | ||
<code>config change HTTP0 /home SETUP/wizard.xml</code> | |||
to | to | ||
<code>config change HTTP0</code> | |||
and upload it to the gateway with a reboot afterwards will lead to a reacting | and upload it to the gateway with a reboot afterwards will lead to a reacting web-gui. | ||
I couldn't find an appropriate '''!mod cmd syntax''' for it but it may exist. | I couldn't find an appropriate '''!mod cmd syntax''' for it but it may exist ([[User:Ckl|ckl]] 15:08, 7 July 2016 (CEST) actually, it does not exist). | ||
== Related Articles == | == Related Articles == | ||
Revision as of 15:08, 7 July 2016
Applies To
concerns
- IP 811, V11, V12 (at least observed here)
More Information
A gateway should reboot after ending the setup-assistant. Sometimes that will not happen. I have seen such behavior at a IP811 after uploading the last v12 rc1 after the factory reset, i.e. pressing the reset-button long until the led flashes green and quick, wait until led turns red and powercyle the device.
A manual reboot (powercyle) won't help here. The Assistant will be shown again.
A booting with sending a !boot (http://<ip of gateway>/!boot) ends in an non-reacting http-Server.
It is still there but has no content.
Dealing with the tftp mode and gwload to update firmware or bootcode doesn't help either.
But you can get access to part of the gateway's web-gui when calling
http://<ip of gateway>/CMD0/mod_cmd.xml?cmd=xml-modes&menu=maintenance.xml&xsl=tab.xsl&help=Maintenance
in your web-browser. This will show the part of the gui where you can deal with firmware bootcode and config.
Downloading the config, editing the config in the line with
config change HTTP0 /home SETUP/wizard.xml
to
config change HTTP0
and upload it to the gateway with a reboot afterwards will lead to a reacting web-gui.
I couldn't find an appropriate !mod cmd syntax for it but it may exist (ckl 15:08, 7 July 2016 (CEST) actually, it does not exist).