SSDP Proxying/Forwarding

[reggie14]

I recently set up a guest wifi network on a different VLAN, and ideally I'd like to move most of my wifi clients to it. And/or I'd like to create a separate VLAN for my more trusted wifi devices that have to communicate with my internal servers.

One of the biggest things holding me up is my Sonos system.  For various reasons, I want to be able to access my Sonos system from the LAN  and the guest VLAN (and the wifi VLAN, if I set it up).  Because I use wired and wireless controllers, no matter what I'll end up with a situation where I have clients on a separate VLAN. But, Sonos relies on the Simple Service Discovery Protocol to allow controllers to find the Sonos components.  SSDP doesn't cross subnets.

While pfSense has an IGMP proxy, there's no SSDP proxy.  I found an old thread where people were talking about creating one, but I'm guessing nothing ever came from it.  Are there any work-arounds?

[jimp]

The only other similar suggestion might be to give Avahi a try.

[superweasel]

I installed Avahi onto pfSense 2.2.3 last night. At first I could not see Sonos across VLANs, however after a Sonos component power cycle, I now have access to Sonos across VLANs.

[reggie14]

@superweasel:

I installed Avahi onto pfSense 2.2.3 last night. At first I could not see Sonos across VLANs, however after a Sonos component power cycle, I now have access to Sonos across VLANs.

Interesting.  Thanks, superweasel and jimp.

superweasel- I'm a little confused by the configuration.  Do I want Avahi to listen on both my LAN and WiFi VLANs, or just one?  If it's just one, do you listen on the Sonos controller side, or the Sonos component side?

Also, what do I put in the "browse domain" box?  I assume I put in my local domain name, although I don't really understand how that particular setting works.

[superweasel]

Yes, you want Avahi to listen on all VLANs that have services you want to access.

In my case I have four VLANs, however, I only need access to services on three of those VLANs. The VLAN for gaming consoles routes directly out to the WAN and I do not need any services available from that VLAN. I denied that VLAN in Avahi and by default the WAN is also denied.

As for browse domain, local is all you should need. This is the default domain for each VLAN. If you have an iPhone or iPad, Discovery is an app you can use to browse any available domains to view available services - https://itunes.apple.com/us/app/discovery-bonjour-browser/id305441017?mt=8


[raphus]

this working for anyone else? i enabled avahi, restarted sonos components but no dice. 2.3.1-RELEASE-p1

[morreale]

@raphus:

this working for anyone else? i enabled avahi, restarted sonos components but no dice. 2.3.1-RELEASE-p1

I cant seem to get it working either.

[reggie14]

@raphus:

this working for anyone else? i enabled avahi, restarted sonos components but no dice. 2.3.1-RELEASE-p1

I just stumbled on this thread again.  It's still working for me.  It worked yesterday under 2.3.1, and it's working now under 2.3.2

It seems like I have restart a Sonos component every time I restart my pfsense box.  But after 30-45 seconds it starts working again.

[kroem]

I've never used Avahi, but need to get Sonos working accorss VLANS - could someone with a working setup post their config maybe?

I have one "media" VLAN and one "main" VLAN with controllers(ipads/phones) in the main one.

[bafonso]

@kroem:

I've never used Avahi, but need to get Sonos working accorss VLANS - could someone with a working setup post their config maybe?

I have one "media" VLAN and one "main" VLAN with controllers(ipads/phones) in the main one.

I believe the only way will be to rebroadcast sonos' broadcasts on its own vlan.