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.

0
U

Property:nfs4

From BoxMatrix
(Redirected from nfs4)


BoxMatrix >> System >> nfs4 @ 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

Linux-Filesystem

Goto:   Dependencies   -   Model-Matrix   -   Missing Supportdata   -   SMW-Browser

Details

nfs4 is the Network File System version 4. See the NFS article.

It is used in early 6490 firmware to mount ATOM ressources on the ARM side.
This is performed through the lan-0 interface on both sides, which is intended for the Emergency-IP.
The ARM side uses the standard Emergency-IP 169.254.1.1, the ATOM side uses 169.254.1.2.

ARM mount   ATOM share   Comment
169.254.1.1 169.254.1.2 IP of lan-0
/var/remote / rootfs
/var/media/ftp /var/media/ftp NAS
/var/remote/var/media/ftp /var/media/ftp NAS
/var/remote/var/tmp /var/tmp Temp-Files
/usr/www/avm/dvb/m3u /var/tmp/tv Channel lists for cableinfo

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 filesystem. Last update: GMT.
A * in the Mod column marks info from Supportdata-Probes, which will always stay incomplete.
A ** in the Mod column marks info from Supportdata2 probes, which by their nature will stay way more incomplete.
A - in the Mod column marks manual research, the Firmware then shows where the item occurs, not the Relation.

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

Model-Matrix

Daily updated index of the presence, path and size of this filesystem for each model. Last update: 2024-07-22 06:47 GMT.
Showing all models using this filesystem. Click any column header (click-wait-click) to sort the list by the respective data.
The (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 comes from Supportdata-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 supportdata file or just a disabled feature.

Missing Supportdata

The data in this article 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.

SMW-Browser

Information is currently being retrieved from the backend.