- Device needs to connect to EVC; can also specify local connectivity for app instances
- By default connects using DHCP/IPv4 over eth0, wlan0, and wwan0
- Will use multiple ports for failover and load spreading if available
- Can specify different ports, static IPs, enterprise proxy config, etc
- At software install time with a json file in /config/, or USB stick
- Using device API
- Device tests connectivity to EVC with fallback to old, retry of new
- Reports results using API
- Prints connectivity diagnostics on console (useful if local console; e.g., to debug proxy config)
Overview
Content Tools