Devialet Chat

Full Version: Using a VLAN
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
I created an IoT VLAN and dropped my Phantom/Dialog pair onto it. (Actually, just the Dialog, as the Phantom connects to it via PLC). I can see the Dialog via AirPlay, since my router forwards mDNS across VLANs, and I opened up the high ports. All good there.

But the Spark app (both iOS and Mac) doesn’t see it. I think the Dialog invents a 10.201.42/24 network and assumes that it’ll route locally, but as that’s both crazy and improper it doesn’t work.

How are people handling this kind of a situation?

Thanks!
And what’s even more nuts is that the Phantom app for changing the volume, has no problems connecting to the Phantom crossing the VLAN, while the Spark app flounders.
Sigh. So it’s all broadcasts to the local network, not anything like mDNS and DNS-SD like any other sane system.
Spark must use the same IP range.
A VLan is not recommended at all because there is no benefit to isolate the speakers on a dedicated VLan.
Some protocols won't cross the networks or even sub-net because there are not meant for this use.
(06-Aug-2019, 15:20)daibaron Wrote: [ -> ]Spark must use the same IP range.
A VLan is not recommended at all because there is no benefit to isolate the speakers on a dedicated VLan.
Some protocols won't cross the networks or even sub-net because there are not meant for this use.

There can be a number of reasons for putting the speakers on a different VLAN, e.g. ensuring that only a selected number of airplay devices is visible to the connected iPhone while having a joint internet connection...

I am having major issues getting the Phantoms to work on a separate VLAN (both Phone and Phantom on same VLAN, same Class C subnet). If anyone has any ideas how to solve this, I am happy to hear about it.
(21-Jul-2020, 21:05)drizzt81 Wrote: [ -> ]
(06-Aug-2019, 15:20)daibaron Wrote: [ -> ]Spark must use the same IP range.
A VLan is not recommended at all because there is no benefit to isolate the speakers on a dedicated VLan.
Some protocols won't cross the networks or even sub-net because there are not meant for this use.

There can be a number of reasons for putting the speakers on a different VLAN, e.g. ensuring that only a selected number of airplay devices is visible to the connected iPhone while having a joint internet connection...

I am having major issues getting the Phantoms to work on a separate VLAN (both Phone and Phantom on same VLAN, same Class C subnet). If anyone has any ideas how to solve this, I am happy to hear about it.

What about using NAT of some kind? Mapping fixed IPs on one side to the Phantom IPs on the other network?
(21-Jul-2020, 22:17)ogs Wrote: [ -> ]
(21-Jul-2020, 21:05)drizzt81 Wrote: [ -> ]
(06-Aug-2019, 15:20)daibaron Wrote: [ -> ]Spark must use the same IP range.
A VLan is not recommended at all because there is no benefit to isolate the speakers on a dedicated VLan.
Some protocols won't cross the networks or even sub-net because there are not meant for this use.

There can be a number of reasons for putting the speakers on a different VLAN, e.g. ensuring that only a selected number of airplay devices is visible to the connected iPhone while having a joint internet connection...

I am having major issues getting the Phantoms to work on a separate VLAN (both Phone and Phantom on same VLAN, same Class C subnet). If anyone has any ideas how to solve this, I am happy to hear about it.

What about using NAT of some kind? Mapping fixed IPs on one side to the Phantom IPs on the other network?
I do not want Airplay to work across the VLAN / Networks. I have one VLAN per Apartment and want to ensure people only see the devices in their apartment.
I see. I use VLANs in my home network. One for all my devices including Roon and wifi, the other to transport WAN from the ISP modem, via two switches, to my firewall's 'outside' interface. I've never had any problems with this.
Is there a router interface/default gateway in each VLAN?
I believe that they are using Bonjour / mDNS do discover each other and those protocol make the strong assumption that all the devices to be discovered are on the same L2 network.

Jean-Marie
@drizzt81
In you case you haven't really "isolated" the Phantoms... you just have separate networks managed by Vlans.
Make sure the Subnet is different for each Vlan.
The Phantom whole setup must be dedicated for one current Vlan.
Pages: 1 2