Parameters for production

This page suggests a few configuration parameters which would be useful to set when deploying live. These are just a few of the possibilities.

Boot server

If you have a managed network, where you control the DHCP server used to boot the STB, then you can transmit some basic configuration parameters directly to the STB when needed. But for unmanaged, OTT networks where control of the DHCP server is not available you must make sure that the STB is able to boot once it arrives at the end-user location. This requires that you set the HttpServer and HttpPort configuration parameters as factory defaults. Depending on the network, the HttpProxy and HttpProxyPort may also be needed. To have the STB boot automatically with the HTTP protocol, set the BootOrder parameter to "363".

Networking

The ARRIS boot loader contains a simple Wi-Fi wizard, which can scan for networks, and allows the end user to enter SSIDs and passwords. But for maximum control and flexibility regarding network configuration, you should consider setting BootWithoutNet to "yes", and WifiWizardDisabled to "yes". You will also need to have a boot image with a local portal installed in the flash memory prior to distributing the STB. In this scenario, the STB will power on, boot from the boot image stored in flash, and then run a local portal. The local portal will implement a network connection wizard to aid with ethernet or Wi-Fi setup. You now have full control over the look and behavior of the Wi-Fi setup.

Securing

To prevent the end-user from entering the boot loader menu at all, set MenuHidden to "yes". You might also want to set InfoScreen to "no", to prevent it being seen. Setting IgnoreVci to "true" means that the STB will only receive its IP-address, netmask, gateway etc information from the DHCP server, and the additional KreaTV options will be ignored. This is useful when deploying into OTT networks to prevent rogue DHCP servers from overriding the factory default settings.