Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • J jami-daemon
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 100
    • Issues 100
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • savoirfairelinux
  • jami-daemon
  • Issues
  • #416
Closed
Open
Created Feb 01, 2021 by Mohamed Chibani@mchibani1Developer

UPNP Connectivity Change - Perform a full restart only on actual change

In the current implementation of UPNP, upon reception of the "connectivity change" notification, a full restart of the provisioning process is performed. Meaning that all existing provisioned mappings will be removed and requested anew. The notification can be sent on various connectivity activities which do not always result in an actual connectivity change (change of the local and/or access point addresses). To prevent performing unnecessary processing, the upnp-context must first perform a check on the connectivity before performing a full restart.

Edited Feb 01, 2021 by Mohamed Chibani
Assignee
Assign to
Time tracking