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:STATE DHCPRANGESSTATUS FBSTATE
BoxMatrix >> System >> STATE_DHCPRANGESSTATUS_FBSTATE | @ 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: | STATE_DHCPRANGESSTATUS_FBSTATE - type State | Wiki | Freetz | IPPF | whmf | AVM | Web |
Location: | System >> AVMIPC-Datastore - Origin: AVM | ||||||
Listeners: | me_multid.ctl, me_vpnd.ctl | ||||||
Properties: | Firmware: 7.39 - 7.90 | ||||||
Function: | State of the DHCP v4 lease ranges in JSON format. |
Goto: JSON-Data - Dependencies - Model-Matrix - Help Supportdata2 - SMW-Browser
Details
STATE_DHCPRANGESSTATUS_FBSTATE provides the realtime state of the DHCP v4 lease ranges in JSON format.
This covers start and end addresses of the lan and (if used) the guest interfaces, which are both Network-Bridges.
A human readable version of this info is part of the output of showfbstate.
Like every FBSTATE
event this is maintained by libavmfbstate.so, which is very helpful to find out the sender of this state.
Listeners use the function fbstate_listen_dhcprangesstatus
, these are showfbstate and vpnd.
Senders use the function fbstate_notify_dhcprangesstatus
, and this is only used by multid.
JSON-Data
Sample output of a 6850lte fw 7.39 calling aicmd avmipcd datastore query STATE_DHCPRANGESSTATUS_FBSTATE full
.
If the sample contains a size
info then it's a snippet of aicmd avmipcd datastore show full
from Supportdata2.
STATE_DHCPRANGESSTATUS_FBSTATE : size 218, set by local , local:vpnd DATA: <<!EOF! dhcprangesstatus { dhcp_ranges_status { dhcp_ranges { interface = "lan"; range_start = 192.168.178.20; range_end = 192.168.178.200; } { interface = "guest"; range_start = 192.168.179.2; range_end = 192.168.179.254; } } } !EOF!
Dependencies
Daily updated index of all dependencies of this state. Last update: 2024-11-15 05:19 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_vpnd.ctl | 9** | 7.39 - 7.90 | avmipc_command endpoint of vpnd | AVM |
Sender | cmd | multid (avmcmd) | - | 1.133 - 8.00 | LAN management daemon. | AVM |
2 dependencies for this state |
Model-Matrix
Daily updated index of the presence, path and size of this state for each model. Last update: 2024-11-15 05:19 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 |
---|---|---|---|
FRITZ!Box 4060 | 7.39 | me_vpnd.ctl | 220 |
FRITZ!Box 6850 LTE | 7.39 | me_vpnd.ctl | 218 |
FRITZ!Box 6850 5G | 7.39 | me_vpnd.ctl | 218 |
FRITZ!Box 7490 | 7.39 - 7.51 | me_vpnd.ctl | 0 |
FRITZ!Box 7520 | 7.50 | me_vpnd.ctl | 139 |
FRITZ!Box 7530 | 7.39 | me_vpnd.ctl | 0 - 221 |
FRITZ!Box 7530 AX | 7.39 - 7.51 | me_vpnd.ctl | 0 - 221 |
FRITZ!Box 7590 | 7.57 - 7.90 | me_multid.ctl, me_vpnd.ctl | 5 - 221 |
FRITZ!Box 7590 AX | 7.39 | me_vpnd.ctl | 220 |
9 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!