obviously this requires multicast=YES in rc.conf.local
> On 2017. Dec 25., at 1:17, Robert Nagy <rob...@openbsd.org> wrote:
>
> CVSROOT: /cvs
> Module name: ports
> Changes by: rob...@cvs.openbsd.org 2017/12/24 17:17:32
>
> Modified files:
> www/chromium : Makefile
> www/chromium/patches: patch-net_base_address_tracker_linux_h
> patch-net_socket_udp_socket_posix_cc
> Added files:
> www/chromium/patches:
>
> patch-extensions_browser_api_networking_private_networking_private_delegate_factory_cc
>
>
> patch-extensions_common_api__permission_features_json
> patch-extensions_common_feature_switch_cc
> patch-extensions_common_features_feature_cc
> patch-net_base_address_tracker_linux_cc
> patch-tools_json_schema_compiler_feature_compiler_py
> patch-tools_json_schema_compiler_model_py
>
> Log message:
> Make Chromecast devices and casting work by doing several different things:
>
> - the media router extension which handles chromecast is only enabled
> on official Chrome builds so enable it on chromium as well
>
> - our multicast implementation is a legacy one so patch it around
> to make it work and use SO_REUSEADDR and SO_REUSEPORT on the socket
> to make other clients able to bind to the same port and address so
> that everything will work smoothly together and chromium will not
> "block" the multicast ports
>
> - enable a good amount of features that are used in the javascript extension
> code that were only enabled for linux and used by the media router
> extension
>
> Everything works from youtube casting, desktop casting to browser tab casting.
> The only thing that does not work is the actual initial setup of the
> chromecast
> device because that requires connecting to the device's wifi network and the
> browser
> cannot do that on OpenBSD so another device has to be used for that, but I
> guess
> everyone has a smartphone nowadays :)
>
