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.
Property:l2tpv3cfg
BoxMatrix >> System >> l2tpv3cfg | @ 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: | l2tpv3cfg - type State | Wiki | Freetz | IPPF | whmf | AVM | Web |
Location: | System >> AVMIPC-Datastore - Origin: AVM | ||||||
Listeners: | me_l2tpv3d.ctl, me_multid.ctl | ||||||
Properties: | Firmware: 7.01 - 7.90 | ||||||
Function: | State of the L2TPv3 tunneling in JSON format. |
Goto: JSON-Data - Dependencies - Model-Matrix - Help Supportdata2 - SMW-Browser
Details
l2tpv3cfg provides the realtime state of the L2TPv3 tunneling in JSON format.
This state is sent by libl2tpv3d.so which is used by l2tpv3d, multid and showl2tpstat.
showl2tpstat just dumps the state, l2tpv3d has a listening endpoint, so this state is likely sent by multid or rextd.
JSON-Data
Mesh master: Sample output of a 7520 fw 7.29 calling aicmd avmipcd datastore query l2tpv3cfg full
l2tpv3cfg: local:l2tpv3d DATA: <<!EOF! l2tpv3cfg { mode = l2tpv3_mode_server; myaddr = 192.168.178.1; fixed_server = ::; remote_end_ids = "fritz.box:guest"; } // EOF !EOF!
Mesh repeater: Sample output of a 6490 fw 7.29 calling aicmd avmipcd datastore query l2tpv3cfg full
l2tpv3cfg: local:l2tpv3d DATA: <<!EOF! l2tpv3cfg { mode = l2tpv3_mode_client; myaddr = 192.168.178.2; fixed_server = 0.0.0.0; } // EOF !EOF!
Dependencies
Daily updated index of all dependencies of this state. Last update: 2024-12-20 18:05 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 |
---|---|---|---|---|---|---|
Listener | sock | me_l2tpv3d.ctl | 25** | 7.01 - 7.90 | avmipc_command endpoint of l2tpv3d | AVM |
Sender | lib | libl2tpv3d.so | - | 6.51 - 8.00 | Layer 2 tunneling protocol v3 | AVM |
Sender | cmd | multid (avmcmd) | - | 1.133 - 8.00 | LAN management daemon. | AVM |
Sender | cmd | rextd (avmcmd) | - | 4.65 - 7.63 | WLAN repeater management daemon. | AVM |
4 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 18:05 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.
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!