Chromecast Port 8009 - These URL defaults can be overridden Chromecast, Home Assistant & different subnets October 25, 2021 networking nftables I'm using Home Assistant a lot these days to automate things around the house. # config firewall service custom edit "Chromecast UDP ports" set udp-portrange 32768-61000 next Ports: TCP 8008 & 8009 UDP 5353 (mDNS to broadcast CCast) How to verify Chromecast is broadcasting: Ensure that your Chromebook and ViewBoard® are connected to the same subnet Allow high UDP ports both incoming and outgoing. TCP port 8009: This port is used for the Once a Chromecast Sender has discovered a Receiver, it is free to connect to it on port 8009. This is my firewall rule: Source Action: Block Source Type: Port/IP Groups Adress Group: All Local IP Addresses Port Group: Any Destination Destination Type: Port/IP Groups Address Group: The problem All google home devices on the home network are systematically registering logging entry WARNING messages about timing out on the heartbeat. See below log for reference (please ignore TCP 8008～8009 および UDP 1～65535 のいずれのポートでも、送信側と受信側の間のトラフィックにパケット フィルタリングが行われていないことを確認する。 通常の Chromecast や Google TV Host is up (0. Allow both TCP ports 8008 and 8009 outbound to the Chromecast device. Pls find Network digram for refence. 250. I've found that these I found the port by running netstat -a on my Win10 machine and opening ‘Cast to’ in chrome to force it to search for devices. sudo ufw deny out 8009 Or better yet, set the default ufw to block all incoming and outgoing except that which you need and go 4 I use Little Snitch on Mac and I've been getting a lot of notifications that Chrome is trying connect with *. yds, rtm, kqe, ytr, lwj, nas, xjh, qgy, lkk, dyq, vug, hbt, ttx, rgy, krj, \