FLUX Network Requirements
Minimum System Requirements
FLUX supports WiFi and wired networks. To make your network "FLUX ready” and provide the best possible experience, please ensure the following:
1. Network Architecture
We recommend to use a separated, dedicated and professional network - it will drastically improve the stability and performance. We can recommend following brands of professional gear: Ruckus, Cisco, Ubiquiti and similar vendors, even though you can run FLUX with any network that fulfils the requirements. Transmitter and receiver must be within the same (virtual) network / IP range and be able to communicate on UDP/IP level. It's essential that the used IP addresses are able to connect to each other.
2. Frequency Band
Unless your WiFi network can be configured in such a way, that devices are ensured to use a single band (2.4GHz or 5GHz) all the time, we recommend to use only 1 frequency band: either 802.11n (2.4GHz) or 802.11ac (5GHz). This is essential, especially if you run both frequency bands using the same SSID and devices start to roam between the two, connection problems and interruptions will occur. NOTE: some Android devices do not support 802.11ac.
3. Client Isolation
Client Isolation, also often called Access Point Isolation, prevents clients from directly communicating with each other via WiFi. If the client are connected via Ethernet cable, the Client Isolation setting will become irrelevant and can be either ON or OFF. If the clients are connected via WiFi, Client Isolation must be turned OFF.
FLUX is using the multicast feature to detect other FLUX clients within the network. We use group 188.8.131.52 on port 5055 to do so. To run FLUX successfully, Multicasting must be turned ON and configured correctly. When clients are within different subnets multicast forwarding must be configured on a network level.
5. DHCP Settings
We recommend to set the DHCP lease time to as long as possible, at least to the amount of hours FLUX will be used. Changing the IP address during the streaming process will result in unexpected behavior.
6. Quality of Service
We recommend the usage of Quality of Service within the entire network. It should be optimised for VoIP in mind. We recommend DSCP value of EF (46 or 101110 in binary) and CoS value of VO (5). Please refer to this Cisco guides about QoS and VoIP for more information.
7. WiFi Channel
Multiple WiFi networks in the same venue and running on the same channel might transmit at the same time and their radio signals will collide and become garbled resulting in data corruption or complete frame loss. If there is an excessive amount of collisions, data would never be transmitted successfully and the wireless network would be unusable.
To prevent such interference, we recommend to choose a channel for your WiFi network that is used by no/as few as possible other networks in range. Please refer to this Cisco Guide about Channel Planning for more information.
8. Bandwidth Usage
Our patented network technology will adapt bandwidth usage based on the network environment. You should expect about: • 0,2 kbyte/sec for each client that is connected but not actively communicating • 10 kbyte/sec per audio direction per client, so PTT (half duplex) takes 10 kbyte/sec and permanent (full duplex) 20 kbyte/sec
Please contact us at firstname.lastname@example.org