Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
gst-rtsp-server
gst-rtsp-server
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 80
    • Issues 80
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 11
    • Merge Requests 11
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamer
  • gst-rtsp-servergst-rtsp-server
  • Issues
  • #47

Closed
Open
Opened Aug 03, 2018 by Bugzilla Migration User@bugzilla-migration

Add API to allow/disallow specific multicast destinations

Submitted by Patricia Muscalu

Link to original bug (#796916)

Description

The current implementation relies on the address pool:
the server checks if the suggested destination/port is present in the pool and reserves the address (doing that, no other clients are allowed to request the same multicast group, which is not correct, see the discussion in https://bugzilla.gnome.org/show_bug.cgi?id=793441).

Probably, the pre-configured address pool should be only involved in choosing the server-selected address/port pairs. Thus we would need an additional security step for checking if the the destination suggested by the client is allowed.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gstreamer/gst-rtsp-server#47