|BoxMatrix >> Environment >> ANNEX||@|
|Variable:||ANNEX - type Text||Wiki||Freetz||IPPF||whmf||AVM||Web|
|Location:||Environment >> AVM-Environment - Origin: rc.conf|
|Properties:||Firmware: 1.120 - 7.51|
|Defines:||The computed system wide ADSL Annex to use.|
It can be
B and is set in rc.conf using this priority:
Annexvariable in the
dslglobalconfigsection of ar7.cfg (only if CONFIG_DSL_MULTI_ANNEX = y)
- annex variable in the Bootloader-Environment
- CONFIG_ANNEX default
For very old Firmware ANNEX was hardcoded to
This is old text which will disappear today:
The system annex is taken either from the Bootloader-Environment variable annex or from a hardcoded fallback default in the Firmware. For very old Firmware this was hardcoded 'B', later CONFIG_ANNEX was used as the fallback default.
Daily updated index of the presence and value of this variable for each model. Last update: 2023-01-30 05:13 GMT.
Showing all models using this variable. Click any column header (click-wait-click) to sort the list by the respective data.
(main/scrpn/boot/arm/prx/atom) label in the
Model column shows which CPU is meant for models with multiple Linux instances.
Note that this list is merged from Firmware-Probes of all known AVM firmware for a model, including Recovery.exe and Labor-Files.
If the 'Value' column contains '<comp>' the variable is computed at runtime. '<empty>' means the variable is present but empty (rare).
Multiple values typically show a conditional static assignment or different values in different firmware.