Property:ATOM IPV4 LAN

---

BoxMatrix >> System >> ATOM_IPV4_LAN

@ 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

---

Devices

Filesystems

Partitions

Sockets

Netlink

Pipes

Interfaces

Bridges

Ports

Events

Sources

Sinks

AVMIPC

Processes

Watchdogs

Memory

Slab

Vmalloc

ProcFS

SysFS

Research

---

AVMIPC-State

AVMIPC-State:	ATOM_IPV4_LAN   -   type	Wiki	Freetz	IPPF	whmf	AVM	Web
Location:	System >> AVMIPC-Datastore   -   Origin: AVM
Listeners:
Properties:	Firmware:
Function:	State of the IPv4 LAN address of the ATOM side on early 6490 firmware.

Goto:   Dependencies   -   Model-Matrix   -   Help Supportdata2   -   SMW-Browser

Details

ATOM_IPV4_LAN provides the state of the IPv4 LAN address of the ATOM side on early 6490 firmware.
The payload is just the string of the IP address.

This state is queried on the ARM side by ftpd using avmipc_state, and by libspeedtest.so directly.
It is provided on the ARM side by libcmapi.so (ctlmgr).

Background: Up to 6490 fw 6.66 FRITZ!OS was nearly completely running on ARM, like in ARM-only 63xx Puma5 models.
The ATOM Intel added was nearly unused. Early Intel Puma6 SDK named it an application processor and did not use it at all.
Later AVM ported FRITZ!OS completely to ATOM, the ARM core is only used for the DOCSIS modem since then.

However, the USB-Host is connected to the ATOM, which has way better CPU performance than the ARM.
That is why AVM implemented all NAS and USB-Host functionality on the ATOM on early 6490 firmware.

This covers printserv and ftpd being proxied by tcpproxyd on ARM, tcpproxy_ctl on ATOM controling which ports.
The NAS webserver and the management of all USB related services was provided by nas_ctlmgr.
Since tcpproxyd does not support SSL nas_ctlmgr ran on a separate IP, which resolved from fritz.nas.
Stick+Surf is also splitted into avmstickandsurf.part1 on ARM and avmstickandsurf.part2 on ATOM, see avmstickandsurf.
For UMTS modems netttyd on ATOM multiplexes the TTY devices for netttym.ko on the ARM side.

The network on the ATOM on early 6490 firmware is managed by multid2.
IPv4 and IPv6 network addresses of the respective other side are gathered by avmipc_state.
Some ATOM ressources are mounted on the ARM side using nfs4.
For network throughput tests there's the remote controllable speedtestd on ATOM.

Dependencies

Daily updated index of all dependencies of this state. Last update: 2024-12-20 17:17 GMT.
A ** in the Mod column marks info from Supportdata2 probes, which will always stay incomplete.
A - in the Mod column marks manual research, the Firmware then shows where the Object occurs, not the Relation.

Relation	Typ	Object	Mod	Firmware	Info	Origin
0 dependencies for this state

Model-Matrix

Daily updated index of the presence, path and size of this state for each model. Last update: 2024-12-20 17:17 GMT.
Showing all models using this state. Click any column header (click-wait-click) to sort the list by the respective data.
The (main/scrpn/boot/arm/prx/atom/rtl) label in the Model column shows which CPU is meant for Multi-Linux models.
Note that this list comes from Supportdata2 probes, which can have arbitrary settings and come from different firmware versions.
It doesn't say much if a model is not listed here. It may be a missing supportdata2 file or just a disabled feature.

Model	Firmware	Listeners	Size
0 models use this state

Help Supportdata2

The data in this article is incomplete since it was manually collected using the Supportdata2 project.

Unlike the Supportdata-Probes which have been collected for years Supportdata2 is brand new and only has a few probes.
If you have access to a shell then please help to extend the Supportdata2 collection to improve this data.

It's easy and it's done in minutes. Please send created data as an Email attachment to the address listed here. Thanks!

SMW-Browser

Property:ATOM IPV4 LAN

Information is currently being retrieved from the backend.