When setting up a network for your light show, do you guys use a separate physical network or just run it on it's own VLAN?
Both Ways. I personally use a separate physical network, but others have created VLANS. I like the separate network because even w/ a VLAN all the traffic is still on the same physical equipment (as your home network?) so if it is getting congested, it will still get congested.
Glycerine wrote:When setting up a network for your light show, do you guys use a separate physical network or just run it on it's own VLAN?
From a routing/switching perspective, there little difference. Me personally, my light network is behind an old DD-WRT router, with its own firewall. I chose not to do a separate physical network so that I could remotely access the show terminal running Vixen. In addition to remote access, I also do not have to worry about any household broadcast domains being flooded with either show traffic or the kids "YouTube" traffic.
-Tony
Ok, thanks guys, I'll give it some thought. I'm mostly thinking about whether or not I want to purchase additional (networking) equipment.
Another question on this subject: I am seeing that the Raspberry Pi can be configured as a wireless access point. Has anyone done this? Could it be the same pi that is running FPP? Was thinking that if I use many individual wireless pixel controllers I could just do this to create my network, instead of needing to invest in another wireless router/access point.
I do the VLAN thing. It allows for more software flexibility so you don't need to go around moving cables to reconfigure things.
I don't recommend using the Pi as an AP for the purpose of sending data to wireless controllers. While it can function as an AP, it's not a particularly good one. You're better served with a proper AP with a proper antenna. But the AP mode can be used for things like backdoor access to the pi in case of primary network failure.
The PI can do a lot of neat things but if you're planning to use FPP on it to run your show, don't add unnecessary overhead by making the PI also be an access point. You'll likely run into some stuttering in your light show if you overtax a PI.
Understood. Thanks.
And yet another question. When using a raspberry pi running FPP: I would set the ethernet IP to be something on my "show" network, but set the wifi (wlan) IP to be on my home network, so that I can still access it from a computer for config purposes, correct?
Glycerine wrote:And yet another question. When using a raspberry pi running FPP: I would set the ethernet IP to be something on my "show" network, but set the wifi (wlan) IP to be on my home network, so that I can still access it from a computer for config purposes, correct?
It depends. Are you intentionally setting up two independent networks? Do you want the FPP to be the primary path between the two networks? If so then yes. If you also want to access the controllers on that other network them you will need to configure the FPP to enable forwarding between interfaces.
