Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chromecast network #1080

Merged
merged 3 commits into from
Aug 31, 2024
Merged

Chromecast network #1080

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
43ac52b
Chromecast network
jameskimmel Aug 19, 2024
92be331
Chromecast Networking
jameskimmel Aug 19, 2024
c8a97a4
networking chromecast
jameskimmel Aug 19, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/general/networking/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,8 @@ HTTP and HTTPS are the primary means of connecting to the server. If using a sel

:::caution

In order for Chromecast to work on a non-public routable connection, 8.8.8.8 must be blocked on the Chromecast's Gateway. Blocking 8.8.8.8 on your router is the easiest solution to this problem.
In order for Chromecast to work on your local LAN, the easiest solution is to use IPv6 instead of IPv4. For a public routable IPv6 (not a link-local or ULA) there is no differentiation between public or local. An IPv6 address can simultaneously be publicly routable and accessible from the local LAN.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will it work if I have a link local ipv6? (One that starts with fe80)

Copy link
Contributor Author

@jameskimmel jameskimmel Aug 19, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have not tested this but I think no. Chromecast needs a valid none self signed cert last time I checked. Since you can't create a fe80 (ULA) AAAA record with a valid lets encrypt cert, the IPv6 has to be public routable.
That is why I included the hint in the brackets.

Even if Chromecast supports self signed certs, this would be more complicated than just getting a let's encrypt cert, because you would still need a DNS override or NAT reflection and blocking the hardcoded google DNS. Then it has all the same problems IPv4 has.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made some changes to hopefully make it easier to understand for newcomers.

For IPv4 connections, you need to use NAT reflection to redirect to your local LAN IPv4 or you need to block Chromecast from reaching the Google DNS servers (8.8.8.8) and add a override rules to your local DNS server to point to your local LAN IPv4

:::

Expand Down