Property:eid bcm mgmt.txt

---

BoxMatrix >> Configuration >> eid_bcm_mgmt.txt

@ 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

---

Static-Config

Bin-Files

Audio-Files

Crypto-Files

Vartar-Items

TFFS-Config

Temp-Files

Data-Dirs

Inet-Providers

VoIP-Providers

Firmware

Research

---

Static-Configuration

File:	eid_bcm_mgmt.txt   -   type Config	Wiki	Freetz	IPPF	whmf	AVM	Web
Location:	Configuration >> Static-Configuration   -   Origin: AVM
Path:	Release: /etc/cms_entity_info.d Lab+Rel: /etc/cms_entity_info.d
Properties:	Size: 3.9k - 4.3k   -   Firmware: 6.54 - 7.90
Function:	smd entity definition file for Broadcom management executables

Goto:   GPL-Browser  -  Dependencies   -   Model-Matrix   -   SMW-Browser

Details

eid_bcm_mgmt.txt is the entity definition file for Broadcom management executables.

It is interpreted by libcms_util.so for the Broadcom system daemon smd.

Each entry is encapsulated in a BEGIN / END clause and my contain:

• eid - the Entity ID, an enum defined in cms_eid.h
• name - the name of an executable to launch unless path or altPath are specified
• runArgs - optional commandline arguments to pass
• flags - property flags also defined in cms_eid.h

The flags may define an automatical launch of the respective executable:

• EIF_LAUNCH_IN_STAGE_1 - launch during stage 1 of CMS startup
• EIF_LAUNCH_ON_BOOT - launch on system boot (during stage 2)

Executables which are EIF_MESSAGING_CAPABLE connect smd through the smd_messaging_server_addr socket.

Full quote 7530ax fw 7.56 from the GPL-Browser below:

#
# This file replaces the first 15 entries in entityInfoArray in eid.c
# 3 types of entities are listed in this file:
# a. the tr69c app itself
# b. subscriber LAN side configuration apps.  TR-069 can always control
#    the MDM write access of these apps.
# c. other management apps whose MDM write access can be controlled by TR-069

# See cms_eid.h and TR-069 A.3.2.4 for more details.

# Only 15 entries are allowed in this file.  Do not add any
# more entries here.  If you are adding a management app whose access
# to the MDM can/should be controlled by TR69, look for AVAILABLE or
# delete an entry that is not used in your system, e.g. TR64
#
# Fields not set here are initialized to zero or NULL.
# All field values must be on a single line
#
# Starting in 504L03, smd will launch TR69 on boot only in CMS classic mode.
# In BDK mode, tr69_md will launch tr69c on boot.  In all configs, tr69c will
# open its own server socket, there is no more inetd style spawning for tr69c.
# Also, tr69c will not exit-on-idle; so once started, it will keep running as
# long as the system is up.

# AVM: no tr69c in Fritz!OS
# BEGIN
#   eid         = EID_TR69C        /*      1, TR69C instance 1 */
#   accessBit   = NDA_ACCESS_TR69C /* 0x0001 */
#   name        = tr69c
#   runArgs     = "-I 1"
#   flags = EIF_MDM | EIF_LAUNCH_ON_BOOT | EIF_MESSAGING_CAPABLE | EIF_DESKTOP_LINUX_CAPABLE | EIF_IPV6
# END

BEGIN
  eid         = EID_HTTPD        /*      3 */
  accessBit   = NDA_ACCESS_HTTPD /* 0x0004 */
  name        = httpd
  flags = EIF_MDM | EIF_SERVER | EIF_SERVER_TCP | EIF_MESSAGING_CAPABLE | EIF_DESKTOP_LINUX_CAPABLE | EIF_IPV6
  backLog     = 3
  port        = HTTPD_PORT
END

# AVM: no snmpd in Fritz!OS
# BEGIN
#   eid         = EID_SNMPD        /*      4 */
#   accessBit   = NDA_ACCESS_SNMPD /* 0x0008 */
#   name        = snmpd
#   runArgs     = -v0
#   flags       = EIF_MDM | EIF_MESSAGING_CAPABLE
#   port        = SNMPD_PORT
# END

BEGIN
  eid         = EID_CONSOLED        /*      5 */
  accessBit   = NDA_ACCESS_CONSOLED /* 0x0010 */
  name        = consoled
  flags       = EIF_MDM | EIF_MESSAGING_CAPABLE | EIF_DESKTOP_LINUX_CAPABLE
END

# AVM: no telnetd in Fritz!OS
# BEGIN
#  eid         = EID_TELNETD         /*      6 */
#  accessBit   = NDA_ACCESS_TELNETD  /* 0x0020 */
#  name        = telnetd
#  flags = EIF_MDM | EIF_SERVER | EIF_SERVER_TCP | EIF_MESSAGING_CAPABLE | EIF_DESKTOP_LINUX_CAPABLE | EIF_IPV6
#  backLog     = 3
#  port        = TELNETD_PORT
# END

# AVM: no sshd in Fritz!OS
# BEGIN
#  eid         = EID_SSHD            /*      7 */
#  accessBit   = NDA_ACCESS_SSHD     /* 0x0040 */
#  name        = sshd
#  flags = EIF_MDM | EIF_SERVER | EIF_SERVER_TCP | EIF_MESSAGING_CAPABLE | EIF_DESKTOP_LINUX_CAPABLE | EIF_IPV6
#  backLog     = 3
#  port        = SSHD_PORT
# END

# AVM: no broadcom upnpd in Fritz!OS
# BEGIN
#  eid         = EID_UPNP            /*      8 */
#  accessBit   = NDA_ACCESS_UPNP     /* 0x0080 */
#  name        = upnp
#  flags       = EIF_MDM | EIF_MESSAGING_CAPABLE | EIF_DESKTOP_LINUX_CAPABLE
# END

BEGIN
  eid         = EID_BDK_MD                /*      9 */
  accessBit   = NDA_ACCESS_BDK_MD     /* 0x0100 */
  name        = avail1
END

BEGIN
  eid         = EID_AVAILABLE10        /*     10 */
  accessBit   = NDA_ACCESS_AVAILABLE10 /* 0x0200 */
  name        = avail10
END

BEGIN
  eid         = EID_AVAILABLE11        /*     11 */
  accessBit   = NDA_ACCESS_AVAILABLE11 /* 0x0400 */
  name        = avail11
END

BEGIN
  eid         = EID_AVAILABLE12        /*     12 */
  accessBit   = NDA_ACCESS_AVAILABLE12 /* 0x0800 */
  name        = avail12
END

BEGIN
  eid         = EID_AVAILABLE2        /*     13 */
  accessBit   = NDA_ACCESS_AVAILABLE2 /* 0x1000 */
  name        = avail2
END

BEGIN
  eid         = EID_AVAILABLE14        /*     14 */
  accessBit   = NDA_ACCESS_AVAILABLE14 /* 0x2000 */
  name        = avail14
END

BEGIN
  eid         = EID_AVAILABLE15        /*     15 */
  accessBit   = NDA_ACCESS_AVAILABLE15 /* 0x4000 */
  name        = avail15
END

#BEGIN
#  eid         = EID_TR69C_2        /*      16, TR69C instance 2 */
#  accessBit   = NDA_ACCESS_TR69C /* 0x0001 */
#  name        = tr69c_2
#  runArgs     = "-I 2"
#  flags = EIF_MDM | EIF_SERVER | EIF_SERVER_TCP | EIF_LAUNCH_ON_BOOT | EIF_MESSAGING_CAPABLE | EIF_DESKTOP_LINUX_CAPABLE | EIF_IPV6
#  backLog     = 1
#  port        = TR69C_2_CONN_REQ_PORT
#END

GPL-Browser

Daily updated index of all eid_bcm_mgmt.txt code findings on the GPL-Browser. Last update: 2024-04-25 04:12 GMT.
The Browse column points to the Path containing the respective source code on the gpl.boxmatrix.info service.
The SoC column lists the Chip-Codenames, the Model column lists the nicks of the Box-Models.
The Diff column links the comparison of the AVM Kernel to the pristine original from Kernel.org.
The Download column links the full tarball the respective directory content is extracted from.
The presence of the source does not mean it fits the respective model and architecture. See the Model-Matrix where it's used.

Browse	Path	SoC	Arch	Model	Firmw	Diff	Download
bcm63-7530ax-756	packages/vendor_sdk/public/libs/cms_util/scripts	BCM63	ARM	7530ax	7.56	4.19.183	Download
1 directory containing eid_bcm_mgmt.txt source code

Dependencies

Daily updated index of all dependencies of this file. Last update: 2024-04-25 06:34 GMT.
A * in the Mod column marks info from Supportdata-Probes, which will always stay incomplete.

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

Model-Matrix

Daily updated index of the presence, path and size of this file for each model. Last update: 2024-04-25 05:44 GMT.
Showing all models using this file. 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 is merged from Firmware-Probes of all known AVM firmware for a model, including Recovery.exe and Labor-Files.

Model	Firmw	Path	Size
FRITZ!Box 7530 AX	7.20 - 7.90	/etc/cms_entity_info.d	4.3k
FRITZ!Box 7581	6.54 - 7.16	/etc/cms_entity_info.d	3.9k
FRITZ!Box 7582	6.83 - 7.17	/etc/cms_entity_info.d	3.9k
3 models use this file

SMW-Browser

Property:eid bcm mgmt.txt

Information is currently being retrieved from the backend.