W
Thought I would share my experience for whatever it's worth. First, a great big shout out of thanks to Qinn for his work on this!
A brief description of my setup: I have three separate physical interfaces (not VLANS) labeled LAN, WIFI and SONOS . My desktop clients are all wired to my LAN interface. My wireless mobile clients (all Apple devices) connect through an access point on my WIFI interface and all my SONOS devices are connected to the SONOS interface. All my destop clients and SONOS devices have statically assigned IP's. My mobile devices all receive DHCP leases.
I was able to successfully communicate across all three subnets when I installed pimd manually as initially described by Qinn. After extensive testing I determined that I needed to enable "Allow packets with IP options to pass" on the SONOS interface but not the other two interfaces. BTW my wireless devices are all iphones and ipads, no android devices. Although I am certainly no expert, this makes sense to me as I would expect the source of such packets to be coming from my Sonos devices and thus would be filtered by the SONOS interface.
I also experienced that the pimd.conf file gets deleted on reboot as initially descibed by vacquah. The pimd daemon, however, is still present but the service cannot restart because pimd.conf is not present. I discovered that if I kept a copy of my edited configuration file in /usr/local/etc that it was not deleted. I could just copy it back to /var/etc and restart the service. Unlike Qinn, I could NOT turn off the service as he described being able to do and still have my Sonos devices be discovered. Every time I attempted to do so made my Sonos network undiscoverable. In my setup, pimd has to be a continually running service. I have given alot of thought to this and have wondered if there may be some differences in the discovery process of the different Sonos devices. What got me to thinking about this was a message that popped up on my iphone when I opened the Sonos app after reinstalling it. It stated "Sonos would like to use Bluetooth. Sonos uses Bluetooth to find nearby speakers". Turns out, I am not using any Sonos speakers. My sonos devices consist of a single wired bridge and four amps which do not use Bluetooth. My knowledge of such matters is very limited but could Bluetooth be figuring into the discovery process and explain some of the different experiences which have been described?
Although I experienced success manually installing pimd, I have not had the same success when I tried installing the recent pfSense pimd package. I tried using both "bind to all" under the general tab as well as the default "bind to none" and then selectively binding my three interfaces under the interfaces tab without any success. All other options I left as default. Neither my wired desktop or my wireless devices could discover my Sonos system . BTW, on my desktop I tried using both the recent Sonos 10.6 desktop app as well as an older 10.3 version I had running on another computer. I have tried both Windows and Mac operating systems. I made sure the service was enabled and running. I tried rebooting every device on my network multiple times. All to no avail. I then deleted the pimd package and then manually reinstalled it with instant success on all clients. There must be something that is being configued with the manual installation that is not configured by default on the pfSense package. Unfortunately, I am not knowledgable enough to figure it out. I will leave my current set-up running until I learn from others how to configure the new package.
