 So this question I've seen pop up all over the place. So I wanted to make a quick video just to answer how easy this is to do and how to do it. So the question is, how do I get my Chromecast to work if it's on a separate network? Now, first, you have to have access to that network. So whatever network you want to work from has to be able to ping back and forth with the Chromecast. They have people talk to each other. It is a definite requirement and a prerequisite to make this work. Second, you just need to install this package. And I don't know how it said AVAHI, Avaya. I don't know. It sounds like Avaya to me, but I know it's a phone system and probably not this. However you say it, AVAHI is in the package list. It's a one-click install, simple package that you can load into PF Sense. And then you go here and enable it. Now, first thing you may have noticed is that I have the domains to browse. Whatever you have called your PF Sense, if it's pfsense.localfirewall.local, or in my case, firewall.localdomain, put those here. And if you have multiple things you're calling it, you put both of them here. So I have local and space comma local domain. That is something important. If you left it by default, I think if pfsense does local out of defaults, but either way, whatever extension you see on your PF Sense, and I'll show you where you can find it at real quick. If you go to the main page, you can see mine's called firewall one.localdomain. So I have local domain here. If you don't do that, it may not work. Next thing is deny interfaces. Only deny interfaces you don't want to be able to do that. So for us, we have LAN, LAN2 and VLAN69. And we want all those to be able to talk to the MDNS protocol, which is a protocol that Chromecast uses for discovery. So these networks, I have no problem seeing the Chromecast. And from any of these networks, they can ping the Chromecast. You may or may not have done this. I don't have IPv6 turned on. And it does not give an error message if you do this. But if you disable IPv6 in your firewall, and you have this enabled, when you go to start the service, it just won't start. If you go to the logs, it'll tell you because there's no IPv6 enabled. So I actually have that unchecked. But I think the default is checked. Then all the other settings are perfectly fine at default. But there are some tweaks you can do in here. If you want, but the defaults work perfectly fine for me. Now, that's it. Now, this also enables a couple other things. So the Bonjour Zero Conf proxy, these are all part of the tools used by many devices. The Chromecast uses MDNS. I don't know enough about the Bonjour protocol. I just know it's something that Apple uses for some others. So I believe this works with Apple TV as well. I don't have an Apple TV to test that. So but I've seen other people talk about it and comments on it. But this is specifically for the Chromecast. But in general, it does support lots of other devices that use that same protocol. Now, MDNS is a whole big thing you can read about if you want to know more how it works, but essentially, like I said, the device discovery across the networks. And we'll just show you the system in action. So here is this system at the IP address of 172 1669.145. This is actually on what is the less than cleverly named VLAN 69. So this is a separate VLAN network. This VLAN does allow access to this, the dot three network where the Chromecast lives. So it's at 192 1683.108 is my Chromecast, I can ping it, I can get to it. Those are important things. Now, you can see in ping a Chromecast even without the MDNS enabled, but the discovery protocol is what you need to make this work. So I want to go here, we're going to go to cast. And it shows up Castlevania, pretty straightforward, pretty easy. It discovered it, it's in there and away you go. If I turn off the protocol after a few minutes, because once it's discovered, it caches it. If I turn off this AV AI protocol or plugin, it will then stop MDNS broadcasts. And then this goes away, I can still ping it because the ping isn't controlled from that. That's the TCP network stack that controls that. This is the MDNS protocol controlled by that, but controlled by the AV AI AV AI service. So if you have this set up and you want a Chromecast on a separate network, first, make sure you can ping it because if you can't talk to it, the MDNS doesn't really do much good telling you where it is. So first, make sure you can ping it second turn this on and make sure that the browse domains match your firewalls domain and proper extension in case you've custom named your firewall or have something other than .local and .local domain. And that's it, hit save, turn it on and your Chromecast will work. Hopefully this is helpful and relieves you some headache and googling and searching, trying to find out how to turn this on. Thanks for watching. If you like this video, go ahead and click the thumbs up, leave us some feedback below to let us know any details which you like and didn't like as well because we love hearing feedback or if you just want to say thanks, leave a comment. If you wanted to be notified of new videos as they come out, go ahead and hit the subscribe and the bell icon that lets YouTube know that you're interested in notifications. Hopefully they send them as we've learned with YouTube. Anyways, if you want to contract us for consulting services, you go ahead and hit launch systems.com and you can reach out to us for all the projects that we can do and help you. We work with a lot of small businesses, IT companies, even some large companies and you can farm different work out to us or just hire us as a consultant to help design your network. Also, if you want to help the channel in other ways, we have a Patreon, we have affiliate links, you'll find them in the description. You'll also find recommendations to other affiliate links and things you can sign up for on LawrenceSystems.com. Once again, thanks for watching and I'll see you in the next video.