Perl UPnP Toolbox

Hey, so I finally used Perl UPnP Toolbox to debug that smart home device that kept disappearing from the network...

You know how my office has all those IoT gadgets – smart plugs, media streamers, network switches – and sometimes they just vanish from the controller app? Yeah. So I found Perl UPnP Toolbox – this macOS utility that discovers and interacts with UPnP devices on your network – and honestly, it's been invaluable for figuring out what's actually happening. But of course, getting it to reliably discover everything on a VLAN-segmented network was a whole thing.

The "devices on other VLANs don't appear" wall

So I installed Perl UPnP Toolbox, launched it, and hit "Start Discovery." It immediately found all the UPnP devices on my main network – media server, printer, a couple of smart plugs. Great. But it completely missed the devices on my IoT VLAN (where most of the smart home stuff lives). I know they're UPnP-enabled and working – the controller app on my phone can see them fine.

First dumb move: I assumed the toolbox was broken or missing some devices. Spent an hour reinstalling, checking firewall settings, even tried different network interfaces. Same result.

What I didn't realize is that UPnP discovery uses multicast traffic (SSDP), which by default doesn't cross VLAN boundaries unless your network router is configured to forward it. The Perl UPnP Toolbox was only seeing devices on the same subnet as my Mac.

What actually fixed it

I had to configure my network to allow SSDP multicast forwarding between VLANs. On my UniFi setup, that meant:

1. Creating a multicast network policy that allows IGMP snooping across VLANs
2. Enabling UPnP forwarding on the firewall rules
3. Setting up an mDNS reflector (since some devices use both UPnP and Bonjour)

After that, Perl UPnP Toolbox discovered everything on the IoT VLAN. But I also learned you can manually specify IP ranges to scan, which bypasses multicast limitations entirely. In the "Advanced Discovery" section, I added my IoT subnet (192.168.2.0/24), and it found devices even before I fixed the VLAN routing.

The Perl UPnP Toolbox network configuration guide explained the multicast limitations, and the UPnP Device Architecture docs helped me understand why discovery works differently across subnets. Also the UniFi multicast docs were useful for the VLAN-specific settings.

What else I learned

Once I got full network visibility, Perl UPnP Toolbox proved incredibly useful for way more than just discovery:

• Service inspection – For each device, you can see every service it offers and the exact actions available. My "smart plug" turned out to have 20+ services I didn't know about, including power monitoring that the official app doesn't expose.
• SOAP message monitoring – The real-time view of UPnP transactions is fascinating. I could see exactly what commands the controller app was sending when I toggled a plug. Helped me debug why one device wasn't responding – it was expecting a different argument format.
• Code generation – For a developer, this is gold. It generates Perl code snippets for interacting with any discovered service. I used it to write a small script that polls my media server's status every minute and logs it.
• Event subscription – You can subscribe to UPnP events and see real-time state changes. My printer broadcasts "toner low" events that the manufacturer's software never shows.

The SOAP message format specs helped me interpret the XML, and the Perl UPnP library docs were useful for understanding the generated code.

Quick checklist for next time (or if you try it)

If you ever use Perl UPnP Toolbox in a segmented network, here's what I wish I'd known:

• Multicast doesn't cross VLANs by default – Either configure your router to forward SSDP/mDNS, or use the manual IP range scan feature.
• Check firewall settings – Some security software blocks UPnP discovery. Temporarily disable to test, then add exceptions.
• Use the SOAP monitor for debugging – When a device isn't responding as expected, watch the actual messages being sent/received. The problem is almost always there.
• Save device profiles – Once you find a device, save its profile. The app stores them, so you don't need to rediscover every time.

The Perl UPnP Toolbox scripting examples have ready-to-run scripts for common tasks like port forwarding and media server queries.

Anyway, I now know exactly why that one smart plug was flaky – it was broadcasting malformed UPnP responses that confused the controller, but the Perl Toolbox showed me the raw data so I could see the problem. If you ever need to understand what's really happening with network devices, this tool is worth the VLAN configuration hassle. Let me know if you try it and need help with the multicast settings – that was definitely the hidden trap.