• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Chromecast over multiple networks.

pfSense Packages
2
4
680
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B
    belrpr
    last edited by Apr 10, 2019, 1:13 PM

    Hi,

    I am trying to let my guest users access to my chromecast.
    My Chromecast resides on my "LAN" network while the guest users are in the "DMZGUEST" network.

    LAN network:
    Pfsense ip4: 10.10.5.1/16
    DNS suffix: home.lan

    DMZGUEST network:
    Pfsense ip4: 172.15.1.1/24
    DNS suffix: guest.lan

    I've installed the AVAHI package.
    Configured it likes this:
    login-to-view

    My domain:
    login-to-view

    Current rules from DMZGuest:
    login-to-view

    Used this windows tool to debug bonjour service: https://hobbyistsoftware.com/bonjourbrowser

    Result when using it in the "LAN"
    login-to-view

    Result when using it in the "DMZGUEST"
    login-to-view

    I see the correct IP address of the chromecast 10.10.2.13
    From the DMZGuest it is pingeable:
    login-to-view

    When I hit the cast button in the DMZguest no device is found.
    In the LAN the chromecast is found perfectly.

    Tried to follow this youtube:
    https://www.youtube.com/watch?v=kYKfmS5_3r0

    but the AVAHI package seems different.

    D 1 Reply Last reply Apr 17, 2019, 4:46 PM Reply Quote 0
    • D
      dennypage @belrpr
      last edited by Apr 17, 2019, 4:46 PM

      @belrpr The network segments should be in the same DNS domain. Also, delete the "Override domain". Many services do not seem to work correctly with domain override. Lastly, after you make/save the config changes for Avahi, be sure to restart both ends of the communication (the Chromecast and the client trying to access it).

      B 1 Reply Last reply Apr 17, 2019, 5:09 PM Reply Quote 0
      • B
        belrpr @dennypage
        last edited by Apr 17, 2019, 5:09 PM

        @dennypage so the DHCP scope DNS option should be the same between both?

        D 1 Reply Last reply Apr 17, 2019, 7:08 PM Reply Quote 0
        • D
          dennypage @belrpr
          last edited by Apr 17, 2019, 7:08 PM

          @belrpr If you do not specify a domain name in the DHCP server, it will use the domain name of the firewall. This is almost certainly what you want. Unless you are trying to achieve something very specific, I would recommend staying with the defaults (delete the domain name specification from both DHCP and from Avahi).

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.