Fails when trying to attach to a nonexistent IPv6 interface about castsponsorskip

[utrack]

Yep, I guess it's an issue on their side :) thanks! I'll report that to upstream.

> go-chromecast ls
error: unable to discover chromecast devices: unable to create new zeroconf resolver: listen udp6 [ff02::]:5353: socket: address family not supported by protocol

[utrack]

@gabe565 Yes, it does - I didn't do any rebuilds, so it seems like this issue happens with some specific OS setup.

[gabe565]

@utrack Sorry for the late response, I was busy with the holidays and missed this issue! Were you ever able to work around this?

If not, this is an interesting one. Admittedly, I don't use IPv6 either and I haven't seen this issue. Let me test with an Arch device to see if I have the same error.

I'd maybe suggest installing go-chromecast, which is the the library this repo uses to communicate with devices. Once installed, maybe just something like go-chromecast ls?

[FlyveHest]

+1 for this, happening on my system as well, I also haven't got ipv6 enabled.

Edit: If I specify IP via --devices, it connects.

[gabe565]

@FlyveHest Does it help if you bind a specific interface with the --network-interface flag or the CSS_NETWORK_INTERFACE env?

[gabe565]

@utrack I saw that go-chromecast is working again for you...is CastSponsorSkip also working?

[FlyveHest]

@FlyveHest Does it help if you bind a specific interface with the --network-interface flag or the CSS_NETWORK_INTERFACE env?

Thats what I tried first, did not make a difference, but when I bound it to an interface (I have 4) and specified my devices IP (ChromeCast is on a static lease for firewalling purposes), it skipped discovery and just connected.

Its not optimal for most people, I guess, but it works until the problem is fixed upstream, at least :)