is wiim app even allow wiim devices on different vlan?
- Thread starter r2d2
- Start date
-
- Tags
- wiim home app
hgo58
Major Contributor
The interface between the WiiM Home App and the WiiM devices uses the Universal Plug and Play (UPnP) protocol for discovery and initial control and that is designed to work within a single local network (LAN) only.
So as long this protocol is used, the app will only work within the same lan.
I don't think that will ever change.
The "on other networks" message is because the device has been discovered before (and saved by the app) but are not seen on the current lan.
Last edited:
Machiavelli
Senior Member
i hope it will never change. see chaos on the horizon 
It uses mDNS which does work across vlans if discovery broadcasts are relayed.
I currently have my Pro on the same vlan as I wanted to use the UPnP interface (which I haven't managed to get working across vlans), but management should work across vlans; I'll shift mine back shortly and test.
EDIT:
I moved the Pro back to my iOT vlan and it's still accessible from the WHA.
I'm using 'UDP Broadcast Relay' in OPNSense to enable discovery and firewall rules to allow the outbound (Home to iOT) connection.
Last edited:
hgo58
Major Contributor
Maybe the WiiM documentation is wrong then?
Enable UPnP: Ensure that Universal Plug and Play (UPnP) is enabled on your router. This feature facilitates the automatic discovery and configuration of network devices, thereby enhancing compatibility and connectivity.
From: https://faq.wiimhome.com/en/support...ooting-wiim-device-not-found-in-wiim-home-app
I don't see any references in WiiM documentation to mDNS. On the other hand it would be natural to use it, so you may be right.
To be able to communicate with another vlan it will however require that you can access it from the Internet and not just on your local router, except if you set up a bridge between the vlans.
Last edited:
I'm not even sure what that means at a router level; I assume it's referring to IGD rather than the UPnP protocol as a whole.
UPnP is certainly required for the UPnP interface, but I don't believe it's necessary for the management of a device, nor for non-UPnP playback e.g. Quboz/Tidal/Spotify connect e.t.c.
Not sure I follow. VLAN to VLAN is all local; no internet required.
I'm currently casting from a DLNA server on one VLAN to the Chromecast interface of my Pro on another.
hgo58
Major Contributor
Hmm. For Chromecast to work locally the same vlan is required.
Chromecast devices and the device you’re casting from must be on the same vlan for discovery and communication to work. mDNS traffic do not cross vlan boundaries by default.
If you want Chromecast to work across vlans, your router/switch must support multicast routing and be configured to forward mDNS traffic between VLANs.
Maybe you have this setup?
Yes, as I said in my first post
Relaying the broadcasts might be what the OP is missing.
hgo58
Major Contributor
Doing that can be both a security risk and a performance issue. So be careful. This is not a normal setup.
hgo58
Major Contributor
If both vlans are local, there may not be any issues. In that case it will just work as one bigger network with all multicast requests going to both.
In that case it would be better to just merge the local networks into one.
Multiple vlans are usually for network isolation. So why having them if you open for cross lan communication?
Just relaying broadcasts doesn't allow communication, that's down to firewall rules. Whilst on my iOT VLAN WiiM can only respond to the WHA on my phone, so whilst it does present an attack vector it's very limited.
My Hikvision NVR on the other hand is much more restricted.
Similar threads
- Suggestion
