Chromecast not working
-
The setting is in Services > DNS Resolver:
-
@stephenw10
Again, thank you. Unfortunately, that doesn't exist for me...it's super strange. I'm also less concerned about this unless of course it would somehow allow Chromecast to start working. -
Are you running Plus with Kea for DHCP? That isn't an option in Kea yet in 24.03. It's just been added in 24.08-dev. Try switching back to ISC if so.
But, yes, it's hard to imagine that would make any difference to Chromecast.
-
@krismortensen said in Chromecast not working:
Unfortunately, that doesn't exist for me
If that checkbox option @stephenw10 highlighted is not present on your system, then perhaps you have enabled the Kea option instead of ISC DHCP. DHCP Registration is not currently supported with Kea (it is coming with the next pfSense update, though).
-
@krismortensen said in Chromecast not working:
The difference between then and now is that the access point is actually a wifi router, so it used to be my gateway etc. All I did was turn off DHCP services on it and connected it to the LAN port of the pfsense.
It is quite possible that when DHCP was enabled on your Wi-Fi router that it was doing the client DHCP registration automagically for you and thus Chromecast could find the other "clients" on your network by device name. Once you turned off DHCP on the Wi-Fi router, that name registration would be broken.
Did you change the Wi-Fi router to "bridge" or "AP" mode?
When you set up pfSense, if you changed the DHCP server to Kea from ISC DHCP, then client DHCP registration will not work. That could be the problem. Change back to ISC DHCP. You can do that under SYSTEM > ADVANCED > NETWORKING:
Once you make the change back to ISC DHCP, then follow @stephenw10's instructions to enable the DHCP Registration option.
-
As enumerated in thousands of post on this forum (true, half of them are probably mine
), I have to warn you about this option :
as it comes with a 'side effect'. If you can live with it, then ok, no big deal.
Also, the upcoming, next pfSense version will propose a far better KEA implementation, and we can put the issue to rest.
-
I would still test it because it's one of the few things that might have changed here.
-
@Gertjan
Is the side effect you are referring to the reload of the resolver cache? If yes, then that sounds annoying, but I can probably deal with it.Also, when is the new Kea version set to release?
-
@bmeeks
I went ahead and reverted away from KEA and enabled registration in the resolver settings. Unfortunately, this did not solve my problem.
I didn't do anything on my old wireless router except turn off DHCP, so maybe the mDNS traffic for Chromecast is getting "stuck" inside the wireless router as if it's a layer 3 boundary? ...but then again, if that were the case, then none of my DHCP traffic should be working either because I don't have a relay set up anywhere, and the DHCP requests wouldn't make it past a layer 3 boundary on the wireless router either...I do think that trying to turn off any sort of routing capabilities on the wireless router is a reasonable step if it can even be done though...
-
If it's running as an access point it should be layer2 only. It could still isolate wireless clients. Simpl changing the DHCP settings there shouldn't make any difference though.
-
@stephenw10
I feel SUPER dumb. I did a sloppy job by not turning off all of the routing and firewalling capabilities on the old router, and that is exactly what the problem was. As soon as I disabled all the things, casting worked. I'm pretty sure that this wasn't a routing thing though because I only have the LAN port of the wireless router plugged in (and DHCP would have failed), but this router had firewall services applied to the physical LAN ports which had never been used before. Guessing that the firewall services didn't kick in for WiFi clients (which is dumb) and that's why I didn't have problems in the past.Thank you all for being so helpful and dealing with my ignorance!
