If you like BoxMatrix then please contribute Supportdata, Supportdata2, Firmware and/or Hardware (get in touch).
My metamonk@yahoo.com is not reachable by me since years. Please use hippie2000@webnmail.de instead.

Supportdata-Probes

From BoxMatrix


BoxMatrix >> Development >> Supportdata-Probes @ BoxMatrix   -   IRC-Chat   -   Translate: de es fr it nl pl
News Selectors Models Accessories Components Environment Config Commands System Webif Software Develop Lexicon Community Project Media

Tarballs GPL-Browser FW-Probes FW-History FW-News Supportdata Hardware SVN Trac Freetz-News Freetz-Timeline Freetz-Releases Freetz-Mirror OpenWRT Research

Info
One of the most powerful features for diagnosis is the ability of all Linux based AVM devices to create supportdata. Supportdata is a huge text file which includes information aquired from numerous sources of the running live system. It was designed as a tool for the AVM support but went a valuable source of information for everybody interested in the internals of FRITZ!OS. Please get in touch and contribute real life usage uncensored supportdata. Thanks! It will not be released to the public but scanned and anonymized as you can verify below.

Supportdata-Probes[edit]

Data collected from supportdata[edit]

Supportdata helps to get some insight about the dynamic part of the FRITZ!OS.
This is very difficult since everybody activates other features, so masses are needed for clean results.
So far these lists are extracted from supportdata probes, each entry with a per model reference:

AVM-Environment comes from 2 sources, only supportdata variables not found in firmware are counted here.
Supportdata is also one of the scan inputs for the HWR-Names, to fill the gaps.

How to create supportdata[edit]

This list shows how many Probes were collected so far and which model can create supportdata by which method.
The Extend column show how many of the Probes are extended supportdata probes.
The method --- means the supportdata script is missing or there was no firmware to scan (some cable models).
The method lua means support.lua could be used to create supportdata from the Webinterface.
The method html means support.html could be used to create supportdata from the Webinterface.
The remaining models could only create supportdata from the shell by calling supportdata >support.txt.
The method telnet means the telnetd link is present and you can activate telnet to get shell access.
The method bbox means the link is missing but you can call busybox telnetd to run the server (ie: from a pseudo update).
The worst method console means busybox lacks the telnetd applet and you have to use the serial console.
Please help and send more recent or missing supportdata! Thanks.
Note that recent firmware does not permit direct login at support.lua any more, it redirects to the main page.
You have use the FRITZ!Box Support link at the bottom of the Contents page of the Webinterface.

Missing Supportdata

The data in many articles is incomplete due to missing Supportdata-Probes for the models listed below.
If you own any of these models and would like to help then please get in touch.

TODO[edit]

Interpret:

Fact-Box

Facts about "Supportdata-Probes"
Extended-Probes332 +
Meta-DescriptionPer model scans of all known current and past Firmware, Labor, Recovery and Source-Code releases. +
Meta-TitleSupportdata-Probes - BoxMatrix +
Supportdata-Models139 +
Supportdata-Objects4264 +
Supportdata-Probes943 +
Supportdata-Sections23 +