Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Known Issues and Limitations

...

RDKB EMU - rdk-next

  • T48 – Parental Control - Managed Sites - Blocked keyword - Browsing did not happen even though wired client/mobile have been added as trusted computers (Known issue)

RDKB RPI - rdk-next

  • T15 - Parental Control - Managed Sites - After adding a site under blocked sites, only Http sites got blocked. Https sites are not blocked.
  • T30 - Remote Management - Clicking on Disable button for http port still allows access to webui through remote management.

  • T54, T56 - MAC Filtering – Through dmcli, Client’s device name got entered in MAC filter table and blacklisted. But, blacklisted MAC got connected to and able to browse.

RDKB RPI - Containerization

  • Due to limitation in running wifi driver inside container, current environment/image needs wifi container to be invoked manually (steps are mentioned in user manual).
  • Due to some issues faced while using xml based mounting (especially while mounting volatile directories var, nvram and wifi libraries which are created during run time by existing RDKB Architecture), some of the system binaries (non -rdkb ) are copied inside container using service/script running in host.
  • WiFi connectivity is tested only with 2.4 GHz band. 5GHz is yet to be supported.
  • Data model containerization is in progress which is not supported in latest image/environment.
  • RDKB Components CR, PSM, PandM and WiFi are containerized and others has to be supported. 
  • Enhancements is needed for working containers that includes data models for containers.
  • Webui authentication fails when connected through connected clients.


  • To Do

Project Documentation

...

Below are the list of supporting documents that are part of release

...

1System Test Plan & Test Report
Multiple test cases and test results are being captured
2Release NotesRelease Notes -This document
3Requirement Traceability TableThis document tracks the requirement/feature from end to end (For Eg: from design,coding,testing,documentation are tracked for an particular feature. This enables the user to have a quick references of a particular feature

...