Avrakadeaver wrote:
You don’t have to be on the same network, mine is secured af and I just had someone with a device called dart68 attempt to cast to my tv, I get prompts for this so I blocked them from all future attempts. But still I was lead to believe the person needed to be on your network in order to do so which apparently isn’t true
First off, there is a need to distinguish between screen mirroring/screen sharing (=Miracast-based for Roku) and app-based casting (=DIAL-based in the case of Roku).
(NOTE: There is now AirPlay2 support for some models, which includes both mirroring and casting functionality, however, AP2 can be entirely disabled, though by default is on.)
(NOTE2: There is no Chromecast support in Roku devices - the DIAL-based support in some apps (YT/NF) is often confused with/for Chromecast support in the Rokus when used. Chromecast (like AirPlay) has both mirroring and casting functionality)
Casting (in-app via DIAL) requires that the devices be on the same network. (e.g. the YT app on a Samsung phone casts to the YT app on a Roku, controlling the playback)
Mirroring (Miracast) being a P2P protocol based on WiFi Direct, does not require devices be on the same network. (e.g. SmartShare on a Samsung phone mirrors the screen to a Roku, using the Roku to display the phone screen on a TV)
Note that the OP was discussing (DIAL-based) casting, though some subsequent posts were discussing (Miracast-based) mirroring, conflating/confusing the two. Unfortunately, due to "terminology looseness", and the fact that both the Chromecast & AirPlay protocols combine mirroring and casting functionality under one "protocol brand name", this is very common.
In your case, you weren't being cast (DIAL) to, you were being mirrored (Miracast) to - which is where the confusion arises (casting requires same network, mirroring does not).
