Property:libpcp send itemstatus

---

BoxMatrix >> System >> libpcp_send_itemstatus

@ 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-Event

AVMIPC-Event:	libpcp_send_itemstatus   -   type Event	Wiki	Freetz	IPPF	whmf	AVM	Web
Location:	System >> AVMIPC-Datastore   -   Origin: AVM
Listeners:	me_avmike-pcp-($num).ctl, me_cloudmsgd-pcp-($num).ctl, me_ctlmgr-pcp-($num).ctl, me_dsld-pcp-($num).ctl, me_multid-pcp-($num).ctl, me_pcpd-pcp-($num).ctl, me_voipd-pcp-($num).ctl, me_vpnd-pcp-($num).ctl
Properties:	Firmware: 7.01 - 7.90   -   Senders: ctlmgr, libcmapi.so
Function:	Trigger event to send all PCP port openings.

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

Details

libpcp_send_itemstatus is a trigger event to make all subscribers send their PCP port openings to libpcp_itemstatus.
All listeners are daemons which use libavmpcp.so, the Port Control Protocol (PCP) API.

This event is sent by libcmapi.so for ctlmgr using the libavmpcp.so function libpcp_trigger_itemstatus_event.

Read more about this in the libpcp_itemstatus article.

Dependencies

Daily updated index of all dependencies of this event. Last update: 2024-04-18 04:27 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_avmike-pcp-($num).ctl	3**	7.30 - 7.39	avmipc endpoint of libavmpcp.so for avmike	AVM
Listener	sock	me_cloudmsgd-pcp-($num).ctl	2**	7.39 - 7.50	avmipc endpoint of libavmpcp.so for cloudmsgd	AVM
Listener	sock	me_ctlmgr-pcp-($num).ctl	24**	7.01 - 7.90	avmipc endpoint of libavmpcp.so for ctlmgr	AVM
Listener	sock	me_dsld-pcp-($num).ctl	21**	7.01 - 7.90	avmipc endpoint of libavmpcp.so for dsld	AVM
Listener	sock	me_multid-pcp-($num).ctl	21**	7.01 - 7.90	avmipc endpoint of libavmpcp.so for multid	AVM
Listener	sock	me_pcpd-pcp-($num).ctl	21**	7.01 - 7.90	avmipc endpoint of libavmpcp.so for pcpd	AVM
Listener	sock	me_voipd-pcp-($num).ctl	10**	7.39 - 7.90	avmipc endpoint of libavmpcp.so for voipd	AVM
Listener	sock	me_vpnd-pcp-($num).ctl	9**	7.39 - 7.90	avmipc endpoint of libavmpcp.so for vpnd	AVM
Sender	cmd	ctlmgr (avmcmd)	-	1.120 - 7.90	System meta daemon also serving the Webinterface.	AVM
Sender	cmd	dsld (avmcmd)	-	1.120 - 7.90	Internet routing daemon.	AVM
Sender	lib	libcmapi.so	-	6.35 - 7.90	API library for ctlmgr and its plugins.	AVM
11 dependencies for this event

Model-Matrix

Daily updated index of the presence, path and size of this event for each model. Last update: 2024-04-18 04:27 GMT.
Showing all models using this event. 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 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 3490	7.30	me_avmike-pcp-($num).ctl, me_ctlmgr-pcp-($num).ctl, me_dsld-pcp-($num).ctl, me_multid-pcp-($num).ctl, me_pcpd-pcp-($num).ctl	0
FRITZ!Box 4020	7.01	me_ctlmgr-pcp-($num).ctl, me_dsld-pcp-($num).ctl, me_multid-pcp-($num).ctl, me_pcpd-pcp-($num).ctl	0
FRITZ!Box 4060	7.30 - 7.39	me_ctlmgr-pcp-($num).ctl, me_dsld-pcp-($num).ctl, me_multid-pcp-($num).ctl, me_pcpd-pcp-($num).ctl, me_voipd-pcp-($num).ctl, me_vpnd-pcp-($num).ctl	0
FRITZ!Box 5490	7.29	me_ctlmgr-pcp-($num).ctl, me_dsld-pcp-($num).ctl, me_multid-pcp-($num).ctl, me_pcpd-pcp-($num).ctl	0
FRITZ!Box 5590 Fiber (arm)	7.29	me_ctlmgr-pcp-($num).ctl, me_dsld-pcp-($num).ctl, me_multid-pcp-($num).ctl, me_pcpd-pcp-($num).ctl	0
FRITZ!Box 6430 Cable (arm)	7.29	-	0
FRITZ!Box 6430 Cable (atom)	7.29	me_ctlmgr-pcp-($num).ctl, me_dsld-pcp-($num).ctl, me_multid-pcp-($num).ctl, me_pcpd-pcp-($num).ctl	0
FRITZ!Box 6490 Cable (arm)	7.29 - 7.39	-	0
FRITZ!Box 6490 Cable (atom)	7.29 - 7.39	me_cloudmsgd-pcp-($num).ctl, me_ctlmgr-pcp-($num).ctl, me_dsld-pcp-($num).ctl, me_multid-pcp-($num).ctl, me_pcpd-pcp-($num).ctl, me_voipd-pcp-($num).ctl	0
FRITZ!Box 6660 Cable (atom)	7.29	me_ctlmgr-pcp-($num).ctl, me_dsld-pcp-($num).ctl, me_multid-pcp-($num).ctl, me_pcpd-pcp-($num).ctl	0
FRITZ!Box 6850 LTE	7.39	me_avmike-pcp-($num).ctl, me_ctlmgr-pcp-($num).ctl, me_dsld-pcp-($num).ctl, me_multid-pcp-($num).ctl, me_pcpd-pcp-($num).ctl, me_voipd-pcp-($num).ctl, me_vpnd-pcp-($num).ctl	0
FRITZ!Box 6850 5G	7.39	me_avmike-pcp-($num).ctl, me_ctlmgr-pcp-($num).ctl, me_dsld-pcp-($num).ctl, me_multid-pcp-($num).ctl, me_pcpd-pcp-($num).ctl, me_voipd-pcp-($num).ctl, me_vpnd-pcp-($num).ctl	0
FRITZ!Box 7362 SL	7.12	me_ctlmgr-pcp-($num).ctl, me_dsld-pcp-($num).ctl, me_multid-pcp-($num).ctl, me_pcpd-pcp-($num).ctl	0
FRITZ!Box 7430	7.29	me_ctlmgr-pcp-($num).ctl, me_dsld-pcp-($num).ctl, me_multid-pcp-($num).ctl, me_pcpd-pcp-($num).ctl	0
FRITZ!Box 7490	7.29 - 7.51	me_ctlmgr-pcp-($num).ctl, me_dsld-pcp-($num).ctl, me_multid-pcp-($num).ctl, me_pcpd-pcp-($num).ctl, me_voipd-pcp-($num).ctl, me_vpnd-pcp-($num).ctl	0
FRITZ!Box 7510	7.30	me_ctlmgr-pcp-($num).ctl, me_dsld-pcp-($num).ctl, me_multid-pcp-($num).ctl, me_pcpd-pcp-($num).ctl	0
FRITZ!Box 7520	7.29 - 7.50	me_cloudmsgd-pcp-($num).ctl, me_ctlmgr-pcp-($num).ctl, me_dsld-pcp-($num).ctl, me_multid-pcp-($num).ctl, me_pcpd-pcp-($num).ctl, me_voipd-pcp-($num).ctl, me_vpnd-pcp-($num).ctl	0
FRITZ!Box 7520 v2	7.31	me_ctlmgr-pcp-($num).ctl, me_dsld-pcp-($num).ctl, me_multid-pcp-($num).ctl, me_pcpd-pcp-($num).ctl	0
FRITZ!Box 7530	7.39	me_ctlmgr-pcp-($num).ctl, me_dsld-pcp-($num).ctl, me_multid-pcp-($num).ctl, me_pcpd-pcp-($num).ctl, me_voipd-pcp-($num).ctl, me_vpnd-pcp-($num).ctl	0
FRITZ!Box 7530 AX	7.31 - 7.51	me_ctlmgr-pcp-($num).ctl, me_dsld-pcp-($num).ctl, me_multid-pcp-($num).ctl, me_pcpd-pcp-($num).ctl, me_voipd-pcp-($num).ctl, me_vpnd-pcp-($num).ctl	0
FRITZ!Box 7581	7.17	me_ctlmgr-pcp-($num).ctl, me_dsld-pcp-($num).ctl, me_multid-pcp-($num).ctl, me_pcpd-pcp-($num).ctl	0
FRITZ!Box 7590	7.57 - 7.90	me_ctlmgr-pcp-($num).ctl, me_dsld-pcp-($num).ctl, me_multid-pcp-($num).ctl, me_pcpd-pcp-($num).ctl, me_voipd-pcp-($num).ctl, me_vpnd-pcp-($num).ctl	0 - 5
FRITZ!Box 7590 AX	7.31 - 7.39	me_ctlmgr-pcp-($num).ctl, me_dsld-pcp-($num).ctl, me_multid-pcp-($num).ctl, me_pcpd-pcp-($num).ctl, me_voipd-pcp-($num).ctl, me_vpnd-pcp-($num).ctl	0
FRITZ!Repeater 1200 AX	7.30	me_ctlmgr-pcp-($num).ctl	0
FRITZ!WLAN Repeater 1750E	7.29	me_ctlmgr-pcp-($num).ctl	0
FRITZ!Repeater 6000	7.29	me_ctlmgr-pcp-($num).ctl	0
26 models use this event

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:libpcp send itemstatus

Information is currently being retrieved from the backend.