Is SSDP functionality connected to UPnP?

[AveryFreeman]

Hi,

I can't seem to find anything about SSDP in the pfSense manual.

Is SSDP connected to UPnP settings in pfSense?  I'd like to be able to turn on SSDP without UPnP, since I need my network to support SSDP broadcasts from my HDHomerun Prime to a Windows 10 computer.

Most literature recommends turning on UPnP but the devices do not need access to ports on the WAN, just the LAN, and I'd rather not create an unnecessary security risk.

Thanks
-Avery

[Higgiefresh]

@AveryFreeman:

I'd like to be able to turn on SSDP without UPnP, since I need my network to support SSDP broadcasts from my HDHomerun Prime

I need help with this too.  I cannot for the life of me figure out how to let devices outside the LAN subnet (which my HDHR is connected to), talk to my HDHR.

[jimp]

UPnP would have nothing to do with internal communications, only with allowing LAN hosts to open ports on WAN.

Try using the Avahi package.

[MikeV7896]

UPnP is used for more than just setting port forwards on a router/gateway. There are media operations that it's also capable of, and many devices that support DLNA will also detect UPnP devices (for example, my smart TV will detect all of my Sonos speakers, even though my Sonos speakers only speak UPnP, not DLNA).

Windows Media Player's media library sharing functionality also uses UPnP.

[jimp]

Locally, perhaps, but that has nothing to do with the firewall itself.

[johnpoz]

Use of protocols that are designed for the same local network, be it broadcast or multicast.. Are meant for devices on the same L2 network.. If you have a TV that wants to find your sonos speakers for an example via such a protocol.. Simple solution put them on the same network! Done..

Jimp point here is that what protocols your devices use on some local network has zero to do with pfsense..  If they want to talk UPnP or or SSDP or DLNA between each other you have zero to do on pfsense for that to happen..  If you have some sort of broadcast or multicast protocol you can try out avhai which helps with mdns, etc.  Or you can play with igmp proxy for your multicast stuff.  Which is most likely done better on your switch setup..

To be honest devices that require such nonsense as having to be on the same L2 to work, I wouldn't use those - vote with your dollars..  Nice that they want to make these things easy for the idiot user to just plug and discover via some broadcast/multicast protocol.  Great.. But allowing me to put in an IP or a FQDN of the device it wants to talk to should also be a option..