If the server has moved or gone down, or there are network connectivity issues after configuration, the next boot of Bandshell will result in the bandshell javascript displaying a repeating loop of trying to connect to the server and failing.
However, the IP address is not displayed, so if the problem cannot be remedied by bringing the server back online (lost domain, invalid entry, etc.), the only option is to connect a keyboard to the screen.
My opinion: We should investigate possibly displaying the IP (or an obfuscated IP) on the screen after repeated errors. This should not open us up to too much pain so long as we ensure that we are not serving out HTTP on port 80 and that basic protocols such as ssh are protected properly. It would allow access to correct URLs and other settings.
If the server has moved or gone down, or there are network connectivity issues after configuration, the next boot of Bandshell will result in the bandshell javascript displaying a repeating loop of trying to connect to the server and failing.
However, the IP address is not displayed, so if the problem cannot be remedied by bringing the server back online (lost domain, invalid entry, etc.), the only option is to connect a keyboard to the screen.
My opinion: We should investigate possibly displaying the IP (or an obfuscated IP) on the screen after repeated errors. This should not open us up to too much pain so long as we ensure that we are not serving out HTTP on port 80 and that basic protocols such as ssh are protected properly. It would allow access to correct URLs and other settings.