It’s widespread practice to isolate devices using Vlans in local network. It’s usually has not problems on correctly set up network and firewall rules.
But VictronConnect neither can find Victron in local network vlan segment neither has ability to manually add by IP.
And why don’t VictronConnect rely on mDNS here?
How can I make Victron discoverable in other vlan with full access from main vlan? mDNS is enebled for both vlans, but seems not used by the app.
How do you come to this conclusion? Just recently i looked at how VC discovers devices in the local network, and it sends out mdns queries, which the respective devices respond to.
Are you sure that mdns forwarding across vlans is enabled? Depending on the router, that might not even be an option, and some other device would need to be used as a forwarder. Simply enabling mdns on both vlans is not enough, the service needs to be forwarded from one vlan to the other.
Also check the firewall rules, the multicast IP 224.0.0.251:5353 needs to have a local-only exception
yes, on my Unifi system there is vlan multicast mDNS option enabled. Using it for my smart home devices apropriatly.
Firewall system Allow rule
because foud similar mDNS broadcast messages on both vlans (changed wifi conenction)
Main subnet:
IoT subnet:
But VictronConnect can’t find MP2, while ofcourse i do can access it directly by IP
Hi,
VictronConnect uses SSDP for the discovery of GX devices on the network.
With kind regards,
Thiemo van Engelen
1 Like