This is a maintenance release of the sensor software and resolves the following issues:
- Added checks to verify that the configured DNS servers support access to the LuJam sites.
- If the gateway is the only DNS provide in the environment, add a fail safe DNS server (quad9) in case the gateway's DNS server fails.
- On some gateways, disabling DHCP also disables DNS (this issue is resolved via the fail-safe DNS server setting). The default EE gateways are the only models where this problem has been seen.
- Sometimes, the NTP service would not restart. This could prevent some of the LuJam services from running. Prior to this release, a REBOOT of the sensor was required to resolve the issue.
- HTTPS certificates weren't being verified when connecting to AWS S3 buckets. On some networks, extern DNS servers were incorrectly re-directing the LuJam S3 buckets to the ad-server. This required us to change the AWS S3 buckets to lujam-updates.s3.amazonaws.com and lujam-datafeed.s3.amazonaws.com.
Known issue: Virgin Networks
On some Virgin networks, the LuJam sensor is unable to access the Internet after Virgin have applied a firmware upgrade. This happens very rarely, and we have not been able to reproduce the issue in a test environment. As such, the recommended approach is to power cycle the LuJam sensor (unplug the LuJam sensor from the power supply, then almost immediately reconnect it). How to detect this issue:
- Virgin customer
- Previous network outage possibly lasting days (alerted by the LuJam cloud service)
- Virgin gateway is showing it's connected to the Internet
- Cannot access any Internet sites via your Web Browser (e.g. bbc.co.uk)