Ungoogled-chromium: SSDP / mDNS / Casting packets on start-up even if Media Router flag is disabled

Created on 12 Dec 2019  路  2Comments  路  Source: Eloston/ungoogled-chromium

Bug: When ungoogled chromium is first started, it sends m/DNS/SSDP packets looking for castable devices

Debugging: I have gone to chrome://flags and disabled the following

  1. Load Media Router Component Extension
  2. Connect to Cast devices on all IP addresses
  3. Cast Media Route Provider
  4. DIAL Media Route Provider

And used Wireshark to capture the packets on start-up

Expected behavior

  1. By default I would NOT expect ungoogled-chromium to have SSDP enabled or send these packets
  2. With flags disabled I wouldn't expect to see any SSDP/mDNS traffic

Screenshots
(Sorry direct attaching screenshots seemed to fail)
https://imgur.com/a/knPLJ6o
https://imgur.com/VZgPqFy
https://imgur.com/ktK2Nkt

Environment:

  • Debian Buster Linux
  • ungoogled-chromium version: ungoogled-chromium_78.0.3904.108-2.buster1
duplicate

Most helpful comment

The only way to avoid this type of traffic is to use a managed policy, see https://ungoogled-software.github.io/ungoogled-chromium-wiki/user-resources#disable-media-router, #436.

All 2 comments

The only way to avoid this type of traffic is to use a managed policy, see https://ungoogled-software.github.io/ungoogled-chromium-wiki/user-resources#disable-media-router, #436.

Thanks @xsmile. Closing.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

playgithub picture playgithub  路  3Comments

Zoraver picture Zoraver  路  3Comments

lipici picture lipici  路  3Comments

brianegan picture brianegan  路  3Comments

T-vK picture T-vK  路  4Comments