🛠 Configurer le WiFi et piloter Linino en SSH

Objectives

Take control of the Linux side of the Tian: join the network (dual-band 2.4/5 GHz 802.11n WiFi provided by the AR9342, or Ethernet), access the web configuration panel, then connect via SSH to Linino (the OpenWRT-based distribution) to manage packages with opkg. This is the skill that turns the Tian into a true mini-server.

Hardware

• 1 Arduino Tian + stable USB power supply (Linux boot draws more current than a simple LED blink)
• A WPA2 WiFi network or an Ethernet cable to your router
• An SSH terminal: OpenSSH on Linux/macOS, PuTTY or the built-in "ssh" on Windows 10+

Procedure

1. Power the Tian and wait for the full boot (Linux status LED steady on).
2. Access the card's web network configuration panel — the default address follows the convention for Arduino Linux boards (192.168.240.1 on the USB side). >
3. Configure the WiFi client (SSID + WPA2 passphrase) or leave Ethernet connected, note the IP assigned by DHCP.
4. Via SSH: ssh root@<tian-ip> then the card's password. >
5. For packages, the standard OpenWRT recipe:

opkg update
opkg list-installed | head
opkg install curl ca-bundle    # outils absents de l'image de base selon les versions

Expected Verification

The OpenWRT shell responds, the prompt changes (BusyBox), cat /etc/openwrt_release confirms Linino's OpenWRT base, and opkg update reports the package list. Final test: reboot restarts Linux without touching the SAMD21 sketch, which continues to run during the reboot — the two systems remain independent.

Common Errors

• Confusing sketch reset and Linux reset: the card's reset button affects both; a software reboot via SSH does not touch the Arduino program.
• Blindly modifying /etc/config/network via SSH and cutting your own lifeline: work over Ethernet or with the fallback serial port open before changing the IP.
• Storing data in the root directory: the Tian's flash space is modest (16 MB typical for Arduino-Linux boards in this range). >
• Exposing SSH on the local network without changing the factory password, or worse, on the Internet: the platform no longer receives security patches, stay on an isolated network.
• Forgetting opkg update before an install: the absence of an updated index produces misleading 404 errors.