Does anyone know if Chromecast straight up doesn't function over IPv6?

I haven't tried using this in a bit, but a good while back I got things functioning to be able to cast a stream of our networked security cameras up to our TV, by way of a Chromecast 4K through Home Assistant. This uses the Google Cast integration for HA.

I haven't used it in ages because we switched to just casting it to a little local display in our bedroom using lnxlink.

Today, though, our folks were watching the kids while we were out, and I went to cast the cameras to the TV for them to have that view of the outside. But, the device just wasn't available.

When we got back, I checked all of the various things: mDNS is reachable, can resolve and v6 ping it, ports are open, etc. At one point in the past I had dropped the TV on a restricted VLAN but even that was ripped out a while back in terms of making direct casting (display mirroring) work for devices on the main WLAN.

When I try to establish a TCP connection to port 8009 on the Chromecast device from e.g. the server LAN where Home Assistant reside (that would be sending the media), a TCP connection appears to establish and then immediately disconnects.

This is using the mDNS name for the device. I can confirm that other service ports on the device, e.g. 8443 (Google Home things) or 6466 (Android TV Remote support) connect and remain connected.

Packet capture shows that after the 3-way handshake completes I just get an immediate FIN from the Chromecast.

I run v6-mostly at home. To validate the theory here, I temporarily turned off option 108 / IPv6-only preferred and restarted the Chromecast to force it to fetch addressing again.

That directly confirmed it:
TCP 8009 on v6 gets immediately closed.
TCP 8009 on v4 connects and remains established without issue, as expected.

Anyone else?

#ipv6

@allthingsopen Your site is still missing its AAAA records. https://developers.cloudflare.com/network/ipv6-compatibility/ #ipv6

@Sascha
@coba

Leider ist die Instanz gruene.social und bonn.social genauso wie viele andere Instanzen technisch defekt und federiert nicht richtig.
Damit sieht man eure Toots nicht überall und kann nicht interagieren.

#barrierefrei #IPv6

@technik kann hier helfen.

@goetz @jak2k

RFC 6540 still exists!

In my opinion, we shouldn't write RFCs mandating IPv6 for every single service.

#ipv6 is the internet

Good #IPv6 morning to #GitHub (with a little help from #FOSDEM)

% host github-debug.com
github-debug.com has address 140.82.121.2
github-debug.com has IPv6 address 2606:50c0:c0de:a00::390
%

Getting there..

Yesterday I played a little bit with #clat on different OS.
Guess which one has the lowest #mtu under equal conditions?
(in iOS I wasn't able to ping, so it's not listed here)

#ipv4 #ipv6only #ipv6

#IPv6 je pro reklamní účely jak stvořené. Každé zařízení ma unikátní adresu a většinou ji dostane vždy stejnou díky odvozování od MAC. Reklamní agentury a eshopy uz nepotřebují schválení cookies pro špehování a sdílení "s třetími stranamy s oprávněným zajmem". Stačí ta ip adresa.

#ads

Watching the premier of the Python documentary ( https://www.youtube.com/watch?v=GfH4QL4VqJ0 ). Reminded how the Python 2 -> 3 transition has a lot of parallels to the IPv4 -> #IPv6 transition.

AWS Client VPN now supports connectivity to IPv6 resources
Posted on: Aug 26, 2025
https://aws.amazon.com/about-aws/whats-new/2025/08/aws-client-vpn-connectivity-ipv6-resources/

#aws #ipv6

One slightly weird thing I had is that inbound #ipv6 traffic on both SSH and HTTPS was returning a "connection reset by peer" for a while. It seems to be working now, but if some IPv6 folks can check https://cablespaghetti.dev loads properly over v6 for them now, it would put my mind at rest.

#aws
#ipv6
#ripe88

https://ripe88.ripe.net/wp-content/uploads/submissions/Architect-IPv6-networks-on-AWS-RIPE88-5-16-2024.pdf