The first thing to do is to install the software that allows the gateway to connect to the Wanesy Management Cockpit.
The minimum version to use is 5.9.
Check firmware version on a gateway
Firmware update and configuration
Quick link to firmware
To setup connectivity between the Gateway and the Wanesy™ Management Cockpit, the following network configuration is required:
| Port | Protocol | Direction | Destination | Source | Mandatory / Optional | Comments |
|---|---|---|---|---|---|---|
| 67 UDP | DHCP | out | DHCP server in local network | Gateway | Mandatory | Not mandatory if static IP is used in the network |
| 68 UDP | DHCP | in | Gateway | DHCP server in local network | Mandatory | Not mandatory if static IP is used in the network |
| 53 UDP | DNS | out | DNS server in local network | Gateway | Mandatory | Not mandatory if name resolution is hard-coded in gateway configuration files |
| 123 UDP | NTP | out | pool.ntp.org | Gateway | Mandatory | Default destination used from KerOS 5.x. For firmware < KerOS 5.x, destinations will be x.pool.ntp.org (with x = 0 to 3). |
| 80 TCP | HTTP | in | - | Local laptop | Optional | For local web access if needed |
| 443 TCP | HTTPS | out | upgrade.wanesy.com gateway.warc.wanesy.com | Gateway | Mandatory | For automatic gateway SW update, configuration and monitoring (Magic Link, ZTP, ....etc), for KerOS >=4.3.3 |
| 443 TCP | HTTPS | out | gateways-logs-files-production.s3.amazonaws.com | Gateway | Mandatory | To collect logs file via Wanesy Cockpit, for KerOS >=4.3.3 |
| 22 TCP | SSH | in | Gateway | Local laptop | Optional | For SSH access to the gateway |
| - | ICMP | out | 8.8.8.8 | Gateway | Mandatory | Factory default flow configured for network monitoring |
| 80 TCP | HTTP | out | http://ipv4.connman.net/online/status.html | Gateway | Optional | Useful only when 2 different backhaul are used on the gateway (for example cellular backhaul and ethernet backhaul) |