31,703
edits
Changes
Template:Networking rutos manual firmware (view source)
Revision as of 09:14, 9 January 2023
, 09:14, 9 January 2023→Firmware verification
{{Template: Networking_rutos_manual_fw_disclosure
{{Template: Networking_rutos_manual_fw_disclosure
| fw_version = {{{series}}}_R_00.07.01{{#ifeq:{{{series}}}|RUT9|.1|}}
| fw_version ={{Template: Networking_rutos_manual_latest_fw
| series = {{{series}}}
| series = {{{series}}}
| name = {{{name}}}
}}
}}
}}
{{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} Firmware (legacy WebUI)|click here]]</b> for the old style WebUI (FW version RUT9XX_R_00.06.08.3 and earlier) user manual page.</i>|}}
{{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} Firmware (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_rutos_manual_latest_fw | series = RUT9XX}} and earlier) user manual page.</i>|}}
{{#ifeq: {{{series}}} | RUT2 |<br><i><b>Note</b>: <b>[[{{{name}}} Firmware (legacy WebUI)|click here]]</b> for the old style WebUI (FW version RUT2XX_R_00.01.14.1 and earlier) user manual page.</i>|}}
{{#ifeq: {{{series}}} | RUT2 |<br><i><b>Note</b>: <b>[[{{{name}}} Firmware (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_rutos_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}}
==Summary==
==Summary==
=={{{name}}} Firmware==
=={{{name}}} Firmware==
New firmwares are periodically uploaded to this Wiki. To download firmware images for {{{name}}} devices, click <b>[[{{#ifeq:{{{series}}} | TRB14X | {{{name}}}_Firmware_(EU)| {{{name}}}_Firmware_Downloads}}|here]]</b>.
New firmwares are periodically uploaded to this Wiki. To download firmware images for {{{name}}} devices, click <b>[[{{{name}}}_Firmware_Downloads}}|here]]</b>.
The name of the image file can provide some basic information about the firmware. Names for {{{name}}} firmware image files are structured as so:
The name of the image file can provide some basic information about the firmware. Names for {{{name}}} firmware image files are structured as so:
<{{#ifeq:{{{name}}} | RUT850 | NAME | {{#ifeq:{{{series}}} | TRB14x | NAME_REGION | SERIES}}}}>_<TYPE>_<VERSION>{{#ifeq:{{{series}}} | TRB14x | | _WEBUI}}.bin
<{{#ifeq:{{{name}}} | RUT850 | NAME | SERIES}}>_<TYPE>_<VERSION>_WEBUI.bin
<b>example</b>: {{#ifeq:{{{name}}} | RUT850 | {{{name}}}_R_00.00.00.bin | {{#ifeq:{{{series}}} | TRB14x | {{uc:{{{name}}}}}0_R_00.00.00.bin | {{uc:{{{series}}}}}{{#ifeq:{{{name}}}|RUT241|M|}}_R_00.00.00.bin}}}}
<b>example</b>: {{#ifeq:{{{name}}} | RUT850 | {{{name}}}_R_00.00.00.bin | {{uc:{{{series}}}}}_R_00.00.00.bin}}
Where:
Where:
<ul>
<ul>
<li><b><{{#ifeq:{{{name}}} | RUT850 | NAME | {{#ifeq:{{{series}}} | TRB14x | NAME_REGION | SERIES}}}}></b> - the {{#ifeq:{{{name}}} | RUT850 | name | {{#ifeq:{{{series}}} | TRB14x | name and intended region of use | series of the device}}}}. For {{{name}}} devices, the {{#ifeq:{{{name}}} | RUT850 | NAME | {{#ifeq:{{{series}}} | TRB14x | NAME | SERIES}}}} string should always be <b>{{#ifeq:{{{name}}} | RUT850 | {{{name}}} | {{#ifeq:{{{series}}} | TRB14x | {{{name}}} | {{uc:{{{series}}}}}{{#ifeq:{{{name}}}|RUT241|M|}}}}}}</b>{{#ifeq:{{{series}}} | TRB14x | .<br> The REGION symbol indicates the intended region of use. Possible values are:
<li><b><{{#ifeq:{{{name}}} | RUT850 | NAME | SERIES}}></b> - the {{#ifeq:{{{name}}} | RUT850 | name | series of the device}}. For {{{name}}} devices, the {{#ifeq:{{{name}}} | RUT850 | NAME | SERIES}} string should always be <b>{{#ifeq:{{{name}}} | RUT850 | {{{name}}} | {{uc:{{{series}}}}}}}</b>
</li>
</li>
<li><b><TYPE></b> - indicates the type of the firmware image. Possible values are:
<li><b><TYPE></b> - indicates the type of the firmware image. Possible values are:
<ul>
<ul>
<li><b>R</b> - release. These versions usually undergo extensive testing and are fitted for mass distribution. This is also the only type of firmware that gets uploaded to the <b>{{#ifeq:{{{series}}} | TRB14X | [[{{{name}}}_Firmware_(EU)|downloads page]] | [[{{{name}}}_Firmware_Downloads|downloads page]]}}</b></li>
<li><b>R</b> - release. These versions usually undergo extensive testing and are fitted for mass distribution. This is also the only type of firmware that gets uploaded to the <b>[[{{{name}}}_Firmware_Downloads|downloads page]]</b></li>
<li><b>T_R</b> - test release. A test firmware is usually compiled for internal testing purposes</li>
<li><b>T_R</b> - test release. A test firmware is usually compiled for internal testing purposes</li>
<li><b>T_DEV</b> - test development. </li>
<li><b>T_DEV</b> - test development. </li>
The figure below is an example of the Flash New Firmware Image section and the table below provides information on the fields contained in that section:
The figure below is an example of the Flash New Firmware Image section and the table below provides information on the fields contained in that section:
{{#ifeq: {{{series}}} | TRB1 | [[File:Networking_rutos_manual_firmware_modem_{{{mobile}}}_v2.png|border|class=tlt-border]] | [[File:Networking_rutos_manual_firmware_modem_{{{mobile}}}_v1.png|border|class=tlt-border]]}}
<table class="nd-mantable">
<table class="nd-mantable">
<td>File | Server; default: <b>File</b></td>
<td>File | Server; default: <b>File</b></td>
<td>Source of the firmware image. Can be either downloaded from FOTA (Server) or uploaded from a computer (File).</td>
<td>Source of the firmware image. Can be either downloaded from FOTA (Server) or uploaded from a computer (File).</td>
</tr>{{#ifeq: {{{series}}} | TRB2 ||
</tr>{{#ifeq: {{{series}}} | TRB1 |
<tr>
<tr>
<td>Firmware type</td>
<td>Firmware type</td>
<td>Device firmware{{#ifeq:{{{series}}}|TRB2||{{#ifeq:{{{mobile}}}|1| <nowiki>|</nowiki> Modem firmware |}}}}; default: <b>Device Firmware</b></td>
<td>Device firmware <nowiki>|</nowiki> Modem firmware; default: <b>Device Firmware</b></td>
<td>{{#ifeq:{{{series}}}|TRB2|Firmware type used for upgrade.|Select which type of firmware is going to be uploaded.}}</td>
<td>Firmware type used for upgrade.</td>
</tr>|}}
</tr>|}}
<tr>
<tr>
When you upload a firmware image, the device will have to verify the validity of that image. If the verification was successful, you will be redirected to window with a message such as this:
When you upload a firmware image, the device will have to verify the validity of that image. If the verification was successful, you will be redirected to window with a message such as this:
[[File:Networking rutx manual firmware verification v2.png]]
[[File:Networking rutx manual firmware verification v2.png|border|class=tlt-border]]
This means that the uploaded firmware image is compatible with your device. The indication also displays the file's Checksum. A <b>checksum</b> is a sequence of hexadecimal symbols generated after running an algorithm called a cryptographic hash function on a file. Calculating a checksum and comparing it with the one provided by the file source can be used as a file authenticity check method.
This means that the uploaded firmware image is compatible with your device. The indication also displays the file's Checksum. A <b>checksum</b> is a sequence of hexadecimal symbols generated after running an algorithm called a cryptographic hash function on a file. Calculating a checksum and comparing it with the one provided by the file source can be used as a file authenticity check method.
