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:bbpd (avmcmd)

From BoxMatrix


BoxMatrix >> Shell-Commands >> bbpd (avmcmd) @ 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

Startup-Scr Hotplug-Scr BusyBox-Cmds Bash-Cmds AVM-Cmds Chipset-Cmds Linux-Cmds Shared-Libs Kernel-Mods Research

Info
  
Name-Collision - multiple objects in this wiki use the name bbpd!
bbpd (avmcmd) Broadband frontend state gathering daemon.
bbpd (evsink) Event-Sink of bbpd
bbpd (evsrc) Event-Source of bbpd
bbpd (process) Broadband frontend state gathering daemon.
bbpd (watchdog) Broadband frontend state gathering daemon.

AVM-Command

Goto:   Examples  -  Events  -  Source  -  Dependencies   -   Model-Matrix   -   Symbols   -   SMW-Browser

Details

bbpd is a Broadband frontend state gathering and logging daemon, currently part of the VR11 DSL or PRX Fiber subsystems.
Depending on the access technology it either works in conjunction with dsl_monitor and dpm_manager or with fiber_monitor.
AVM calls it a broadband proxy daemon, since it proxies Broadband frontend related events into a state machine.

fw 7.39 help:

root@fritz:/var/mod/root# bbpd -h

Usage: bbpd [-D]

  -D, --daemon   Run as a daemon
  -h, --help     usage help
  -v, --verbose  more debug logging

  --type="fiber" --supportdata="param"    selected commands from fiber_monitor

Examples

On DSL models bbpd is started in E40-dsl like this:

bbpd -D
dsl_monitor -d

It creates 3 log files in /var/log:

root@fritz:/var/mod/root# cat /var/log/bbpd.log

[1970-01-01T12:34:11] [main][FORCE] AVM broadband_proxy v1.0

Events

Daily updated index of AVM-Events and AVMIPC-Datastore nodes affecting this command. Last update: 2023-12-10 05:13 GMT.
The owners of Event-Sinks and Event-Sources are manual research, which may be incomplete or even wrong.
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
Sink evsink bbpd (evsink) 8* 7.19 - 7.51 Event-Sink of bbpd AVM
Receives event dsl_set 7* 7.27 - 7.51 Set Broadband frontend config AVM
Receives event user_source_notify 8* 7.19 - 7.51 TODO AVM
Source evsrc bbpd (evsrc) 9* 7.19 - 7.51 Event-Source of bbpd AVM
Sends event dsl_connect_status 8* 7.19 - 7.51 Broadband modem sync changes AVM
Sends event dsl_get 8* 7.19 - 7.51 Broadband frontend details AVM
Sends event dsl_status 2* 7.19 - 7.39 Broadband modem sync details AVM
Sends event remote_notifier 1* 7.50 Remote Event-Source notify AVM
Endpoint sock me_bbpd-dsl.ctl 8* 7.19 - 7.51 avmipc endpoint for bbpd events from dsl_monitor AVM
Listens to avmipc @ 5** 7.29 - 7.51 Special event for listeners of nameless private messages. AVM
Endpoint sock me_bbpd-fiber.ctl 3* 7.19 - 7.50 avmipc endpoint for bbpd events from fiber_monitor AVM
Listens to avmipc @ 1** 7.29 Special event for listeners of nameless private messages. AVM
Endpoint sock me_bbpd-independent.ctl 7* 7.27 - 7.51 avmipc endpoint for bbpd events from libbbeventlog.so AVM
Listens to avmipc @ 5** 7.29 - 7.51 Special event for listeners of nameless private messages. AVM
Command cmd bbpd (avmcmd) Broadband frontend state gathering daemon. AVM
Sends avmipc BBPD_EVENT_DSL_RESET_MINMAX_SNRBIT - 7.39 - 7.51 Trigger event requesting reset of the SNR min / max recording. AVM
Sends avmipc BBPD_EVENT_DSL_RETRAIN - 7.39 - 7.51 Trigger event requesting Broadband modem retraining / resync. AVM
Sends avmipc BBPD_STATE_PARAMS_DSL - 7.29 - 7.51 State of the DSL frontend in JSON format. AVM
Sends avmipc BBPD_STATE_PARAMS_FIBER - 7.29 - 7.51 State of the Fiber frontend in JSON format. AVM
Sends avmipc BBPD_STATE_PARAMS_SFP - 7.29 - 7.51 State of the currently plugged in SFP module in JSON format. AVM
20 event relations for this command

The user_source_notify event seems to come from dsl_monitor.

bbpd in fact is an event proxy providing Broadband frontend state information.
It also uses libdslutils.so and libbb.so so it is informed about the Broadband interface.

Source

The names of source files compiled into an executable often help to understand function blocks (and show gaps in the docs).
fw 7.39 source files:

$ strings /usr/sbin/bbpd | grep -e '\.c$' -e '\.cpp$'

<empty>  

Dependencies

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

Relation Typ Object Mod Firmware Info Origin
Started by serv bbpd.service 41 7.39 - 7.62 supervisor service for bbpd. AVM
Runs as proc bbpd (process) 9* 7.19 - 7.90 Broadband frontend state gathering daemon. AVM
Registers wdog bbpd (watchdog) 9* 7.19 - 7.90 Broadband frontend state gathering daemon. AVM
Serving sock me_bbpd-dsl.ctl 9* 7.19 - 7.90 avmipc endpoint for bbpd events from dsl_monitor AVM
Serving sock me_bbpd-fiber.ctl 3* 7.19 - 7.50 avmipc endpoint for bbpd events from fiber_monitor AVM
Serving sock me_bbpd-independent.ctl 8* 7.27 - 7.90 avmipc endpoint for bbpd events from libbbeventlog.so AVM
Depends on lib ld.so 5 7.39 - 7.90 Dynamic linker / loader Linux
Depends on lib lib_bb_serialize.so 46 7.27 - 7.90 Structures for Brodband messages AVM
Depends on lib libannexctl.so 3 7.27 - 7.90 Annex changer for FIT-Image models FIT
Depends on lib libavm_event.so 46 7.21 - 7.90 AVM-Events management API AVM
Depends on lib libavmcsock.so 46 7.21 - 7.90 Networking, I/O and helper functions AVM
Depends on lib libbacktrace.so 46 7.21 - 7.90 Crash handler and logger AVM
Depends on lib libbb.so 46 7.27 - 7.90 Broadband connection information helpers AVM
Depends on lib libbootslotctl.so 3 7.39 - 7.90 Dual-Boot manager for FIT-Image models FIT
Depends on lib libboxlib.so 46 7.21 - 7.90 Box status, logging and statistics functions AVM
Depends on lib libc.so 46 7.21 - 7.90 Standard C library Linux
Depends on lib libdslutils.so 46 7.27 - 7.90 Broadband frontend information helpers AVM
Depends on lib libewnwlinux.so 46 7.39 - 7.90 Linux networking functions AVM
Depends on lib libfbconf.so 6 7.59 - 7.90 TODO AVM
Depends on lib libfbsync.so 6 7.59 - 7.90 TODO AVM
Depends on lib libgcc_s.so 46 7.21 - 7.90 GCC low-level runtime library Linux
Depends on lib libled2.so 46 7.21 - 7.90 LED API - second+third generation AVM
Depends on lib libm.so 41 7.39 - 7.90 C math library Linux
Depends on lib libstdc++.so 46 7.21 - 7.90 GNU C++ library Linux
24 dependencies for this command

Model-Matrix

Daily updated index of the presence, path and size of this command for each model. Last update: 2024-04-17 05:07 GMT.
Showing all models using this command. 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 Firmware Path Size
FRITZ!Box 4020 7.39 /usr/sbin 41.7k
FRITZ!Box 4040 7.39 /usr/sbin 41.7k
FRITZ!Box 4060 7.39 /usr/sbin 41.7k
FRITZ!Box 5530 Fiber (main) 7.21 - 7.80 /usr/sbin 22.6k - 93.8k
FRITZ!Box 5590 Fiber (arm) 7.27 - 7.90 /usr/sbin 41.7k - 81.6k
FRITZ!Box 5690 Pro (arm) 7.59 /usr/sbin 77.6k - 77.7k
FRITZ!Box 6430 Cable (arm) 7.57 /usr/sbin 45.7k
FRITZ!Box 6490 Cable (arm) 7.39 - 7.57 /usr/sbin 41.7k - 45.7k
FRITZ!Box 6590 Cable (arm) 7.39 - 7.57 /usr/sbin 41.7k - 45.7k
FRITZ!Box 6591 Cable (arm) 7.39 - 7.57 /usr/sbin 41.7k - 45.7k
FRITZ!Box 6591 Cable (atom) 7.39 - 7.57 /usr/sbin 41.7k - 45.7k
FRITZ!Box 6660 Cable (arm) 7.39 - 7.57 /usr/sbin 41.7k - 45.7k
FRITZ!Box 6660 Cable (atom) 7.39 - 7.57 /usr/sbin 41.7k - 45.7k
FRITZ!Box 6670 Cable (arm) 7.57 - 7.62 /usr/sbin 45.7k
FRITZ!Box 6670 Cable (atom) 7.61 - 7.62 /usr/sbin 45.7k
FRITZ!Box 6690 Cable (arm) 7.39 - 7.57 /usr/sbin 41.7k - 45.7k
FRITZ!Box 6690 Cable (atom) 7.39 - 7.57 /usr/sbin 41.7k - 45.7k
FRITZ!Box 6820 LTE v1 7.39 /usr/sbin 41.7k
FRITZ!Box 6820 LTE v2 7.39 /usr/sbin 41.7k
FRITZ!Box 6840 LTE 7.39 /usr/sbin 41.7k
FRITZ!Box 6850 LTE 7.39 /usr/sbin 41.7k - 43.9k
FRITZ!Box 6850 5G 7.39 /usr/sbin 41.7k
FRITZ!Box 6890 LTE 7.39 - 7.51 /usr/sbin 41.7k - 48.0k
FRITZ!Box 6890 LTE v1 7.39 - 7.51 /usr/sbin 41.7k - 48.0k
FRITZ!Box 6890 LTE v2 7.39 - 7.51 /usr/sbin 41.7k - 48.0k
FRITZ!Box 7272 7.39 /usr/sbin 41.7k
FRITZ!Box 7430 7.39 /usr/sbin 41.7k
FRITZ!Box 7490 (main) 7.39 - 7.57 /usr/sbin 40.1k - 45.7k
FRITZ!Box 7510 7.39 - 7.57 /usr/sbin 37.7k
FRITZ!Box 7520 7.39 - 7.51 /usr/sbin 37.7k - 41.7k
FRITZ!Box 7520 v2 (arm) 7.39 - 7.57 /usr/sbin 37.7k - 41.7k
FRITZ!Box 7530 7.39 - 7.56 /usr/sbin 17.5k - 41.7k
FRITZ!Box 7530 AX 7.39 - 7.90 /usr/sbin 33.7k - 45.7k
FRITZ!Box 7560 7.39 /usr/sbin 41.7k
FRITZ!Box 7583 7.50 - 7.57 /usr/sbin 48.0k
FRITZ!Box 7590 7.39 - 7.90 /usr/sbin 22.6k - 56.6k
FRITZ!Box 7590 AX 7.39 - 7.90 /usr/sbin 22.6k - 56.6k
FRITZ!Box 7690 7.59 /usr/sbin 37.6k - 41.7k
FRITZ!Repeater 600 7.39 /usr/sbin 41.7k
FRITZ!Repeater 1200 7.39 /usr/sbin 41.7k
FRITZ!WLAN Repeater 1750E 7.39 /usr/sbin 41.7k
FRITZ!Repeater 2400 7.39 /usr/sbin 41.7k
FRITZ!Repeater 3000 7.39 /usr/sbin 41.7k
FRITZ!Repeater 3000 AX 7.39 /usr/sbin 41.7k
FRITZ!Powerline 1260E 7.39 /usr/sbin 41.7k
45 models use this command

Symbols

Daily updated index of all symbols of this command. Last update: 2024-04-17 07:12 GMT.

Firmware Symbol
7.39 - 7.90 bbp::Bbp::check_arch_ready
7.90 bbp::Bbp::create_pipes
7.39 - 7.90 bbp::Bbp::create_stat_file
7.21 - 7.90 bbp::Bbp::on_avm_event_receive
7.39 - 7.90 bbp::Bbp::on_exit
7.21 - 7.90 bbp::Bbp::on_init
7.90 bbp::Bbp::on_supportdata_request
7.21 - 7.90 bbp::Bbp::on_update_leds
7.39 - 7.90 bbp::Bbp::print_supportdata
7.90 bbp::Bbp::rcv_supportdata_from_daemon
7.39 - 7.90 bbp::Bbp::run
7.70 - 7.90 bbp::Bbp::send_to_monitors
7.90 bbp::Bbp::supportdata_create
7.70 - 7.90 bbp::Bbp::update_power_mgmt_status
7.21 - 7.90 bbp::Bbp::usage
7.21 - 7.90 bbp::Bbp::~Bbp
7.21 - 7.90 bbp::Monitor::Monitor
7.39 - 7.90 bbp::Monitor::count_ipc_recv_event
7.39 - 7.90 bbp::Monitor::count_ipc_send_event
7.39 - 7.90 bbp::Monitor::event_send
7.39 - 7.80 bbp::Monitor::handle_avmipc_events
7.90 bbp::Monitor::handle_sync_state
7.39 - 7.80 bbp::Monitor::init
7.39 - 7.90 bbp::Monitor::is_newest_ipc_event
7.21 - 7.90 bbp::Monitor::msg_send
7.21 - 7.90 bbp::Monitor::on_avmipc_receive
7.90 bbp::Monitor::on_fbsync_state_changed
7.39 - 7.90 bbp::Monitor::state_set
7.39 - 7.90 bbp::Monitor::write_arch_status_to_file
7.21 - 7.90 bbp::Monitor::~Monitor
7.39 - 7.80 bbp::MonitorFiber::MonitorFiber
7.39 - 7.80 bbp::MonitorFiber::activate_image
7.70 - 7.80 bbp::MonitorFiber::apply_country_specific
7.70 - 7.80 bbp::MonitorFiber::apply_hardcode_settings
7.70 - 7.80 bbp::MonitorFiber::apply_provider_specific
7.70 - 7.80 bbp::MonitorFiber::assemble_iop_bits
7.39 - 7.80 bbp::MonitorFiber::commit_image
7.39 - 7.80 bbp::MonitorFiber::download_store_image
7.39 - 7.80 bbp::MonitorFiber::handle_remote_omci_command
7.39 - 7.80 bbp::MonitorFiber::msg_send_img_update
7.70 - 7.80 bbp::MonitorFiber::power_off_after_timeout_cb
7.39 - 7.80 bbp::MonitorFiber::reboot
7.39 - 7.51 bbp::MonitorFiber::reset_prx_from_hwk
7.39 - 7.80 bbp::MonitorFiber::restart_technology
7.39 - 7.80 bbp::MonitorFiber::set_annex_type
7.39 - 7.80 bbp::MonitorFiber::set_initial_img_info
7.39 - 7.80 bbp::MonitorFiber::update_urlader_fiber_type
7.39 - 7.80 bbp::MonitorFiber::~MonitorFiber
7.51 - 7.80 bbp::PrxControl::PrxControl
7.51 - 7.80 bbp::PrxControl::companion_chip_on
7.51 - 7.80 bbp::PrxControl::reset_claim
7.51 - 7.80 bbp::PrxControl::reset_release
7.51 - 7.80 bbp::PrxControl::reset_token_alloc
7.51 - 7.80 bbp::PrxControl::reset_token_free
7.51 - 7.80 bbp::PrxControl::~PrxControl
7.21 - 7.90 main
56 symbols for this command

SMW-Browser

Information is currently being retrieved from the backend.