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

    AVAHI and Sonos

    Scheduled Pinned Locked Moved pfSense Packages
    2 Posts 2 Posters 1.8k Views 3 Watching
    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.
    • Orion2030O Offline
      Orion2030
      last edited by

      Re: New Avahi package

      Guys, Having reviewed this topic and past Q&A related to the Avahi package, one would imagine this should be a walk-in-the-park (easy) but not so. I am putting way too much time into this and cannot seem to make any progress. Need some help with SONOS working across subnets but also ChromeCast from the TV:

      I got the following setup:

      VLAN 1 : 192.168.10.0/24 for PC and management devices
      VLAN20: 192.168.20.0/24 for TV and SONOS
      VLAN30: 192.168.30.0/24 for wireless, iphone, etc

      The communication between VLANS is confirmed to work. I can ping across all devices. Also, the SONOS controller works fine and reaches all SONOS player when in the same subnet. So for example, I connected the management PC from VLAN 1 by disconnecting the cable and reconnecting into VLAN20. I am then able to confirm and operate all SONOS devices.

      However, when I return the management PC to VLAN1, it is no longer able to connect to SONOS. The AVAHI setup looks as follows (WIFI is also selected but cannot be seen):
      cf1ea29c-6dc8-4b0d-9cb8-88077d724523-image.png

      Additionally, the FW rules for now look like this on the LAN side (VLAN1):
      5f28e338-1ac5-4b36-98ac-e926832811b8-image.png

      And on the IOT VLAN20, it looks like this:
      ae6563c5-58d1-4df6-983c-8db85b196501-image.png

      I am not seeing enough to have a clue why this is not working, but I do have a clue I am making a stupid mistake somewhere. Any help would be really really appreciated.

      1 Reply Last reply Reply Quote 0
      • SetarcosS Offline
        Setarcos
        last edited by

        Check your firewall logs for the corresponding interfaces and you will likely see UDP multicast traffic on port 5353 still being blocked. It looks like * doesn't include multicast destinations. I found another forum poster had added an alias for something like this, recreated it, and it solved my problems with Avahi traffic being blocked:
        51f6b17e-897c-4b59-8b6c-a2bb50603d3d-image.png

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