Setting up a Wi-Fi connection
To connect your device to the cloud, you must use either Ethernet or Wi-Fi. Izuma Edge officially supports connection over Ethernet. However, if you don't have access to Ethernet or an Ethernet cable, you can connect your device to your home Wi-Fi router, access the terminal and manually configure the Wi-Fi settings.
Note: This is not an officially supported feature. It has been tested with consumer or standard Wi-Fi networks and not with corporate networks or mobile hotspots. We recommend you connect your Raspberry Pi with an Ethernet cable to a network with Internet access.
Before you can start this process, you need:
- Izuma Edge 2.4+ installed on a Wi-Fi supported target (having followed the quick start guide).
- Internet access.
- Router supporting DHCP.
- Ethernet cable or access point, or Wi-Fi enabled router.
Setting up the Wi-Fi connection
Follow these steps to set up a Wi-Fi connection:
Shell or serial into the gateway. There is only one login user by default,
fio. The default password is set to
Connect to the Wi-Fi network using the NetworkManager command-line tool:
sudo nmcli device wifi connect <your_ssid> password <your_wifi_password>
We have observed packet loss and abrupt network disconnection when both wired (ethernet) and wireless are enabled at the same time on the gateway. To provide wireless connectivity to your gateway, disconnect the ethernet cable and
rebootyour gateway. It should come back up and connect with your Wi-Fi AP.
Run this command to determine whether your Pi has acquired an IP on wlan0 interface:
Ping an external IP address to test your connectivity:
ping -I wlan0 22.214.171.124
If successful, you should see something like:
PING 126.96.36.199 (188.8.131.52) 56(84) bytes of data. 64 bytes from 184.108.40.206: icmp_seq=1 ttl=56 time=3.10 ms 64 bytes from 220.127.116.11: icmp_seq=2 ttl=56 time=4.27 ms ^C --- 18.104.22.168 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 2ms rtt min/avg/max/mdev = 3.097/3.682/4.268/0.588 ms
For troubleshooting information, please see: