Page History
- The Bridge-Utils binary in RDKB is implemented in the ccsp-misc module, which provides a bridge configurations across Ethernet, MoCA, WiFi, and GRE interfaces.
- It defines APIs for initialization, vendor-specific pre/post configuration, memory handling, and logging, ensuring reproducible and vendor-agnostic bridge operations.
- Bridge Utils binary will be invoked based on the multinet sysevents.
Bridge Util Architecture in RDKB
Design Overview
- Bridge Util Provides APIs for bridge creation, deletion, and updates.
- Handles QoS, IPv4 configuration, and connection enable/disable.
- Integrates with OVS (Open vSwitch) for interface management.
- Initialization APIs HandlePreConfigVendor() → Ensures vendor-specific settings before bridge setup.
- HandlePostConfigVendor() → Applies vendor-specific settings after bridge changes.
Components
- bridge_util_hal.h → Defines constants, macros, and global variables
- DeviceMode → router (0) or bridge (2).
- BridgeOprInPropgress → flag for ongoing bridge operations.
- Logging via /rdklogs/logs/bridgeUtils.log.
- GRE handler script: /etc/utopia/service.d/service_multinet/handle_gre.sh.
Interface Association
- Supports binding of Ethernet (eth0), MoCA (moca0), WiFi (wifi0), GRE tunnels to the bridge.
API Specifications
- Initialization, configuration, cleanup routines.
- Data Types & Constants – Interface sizes, logging buffers, bridge names.
- Vendor Hooks – Pre/Post config functions for OEM-specific handling.
Operational Requirements
- Thread/process/memory models.
Logging & Debugging
- Centralized logs for bridge operations.
Vendor Dependency
- OEMs must implement pre/post config correctly
- misimplementation can cause bridge instability.
Overview
Community Forums
Content Tools
Tasks