Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:sw:02-sdks:03-ssh [2018/12/04 16:56]
tomas_knot
en:sw:02-sdks:03-ssh [2019/01/28 17:21] (current)
jan_kozak [UniPi Axon]
Line 4: Line 4:
 All UniPi devices include a full-featured ARM-based Linux environment,​ which is accessible via a Secure Shell console after following the steps below. This allows the users of UniPi devices to fully leverage the incredible versatility provide by open source software packages. All UniPi devices include a full-featured ARM-based Linux environment,​ which is accessible via a Secure Shell console after following the steps below. This allows the users of UniPi devices to fully leverage the incredible versatility provide by open source software packages.
  
-The process of enabling accesss to it differs slightly between the three generations of UniPi devices, and is detailed below.+The process of enabling accesss to it differs slightly between the three generations of UniPi devices, and is detailed below for UniPi Axon. The process for UniPi 1.1 and UniPi Neuron is the same as for ordinary Raspberry  
 +Pi.
  
 ==== UniPi Axon ==== ==== UniPi Axon ====
Line 18: Line 19:
   - Wait until the device finishes booting into the UniPi service mode. This is indicated by the two rows of LEDs flashing in an alternating fashion. ​   - Wait until the device finishes booting into the UniPi service mode. This is indicated by the two rows of LEDs flashing in an alternating fashion. ​
   - Use a device with a web browser to connect to the UniPi Axon via Ethernet LAN or Wi-Fi. The process is slightly different between the two options:   - Use a device with a web browser to connect to the UniPi Axon via Ethernet LAN or Wi-Fi. The process is slightly different between the two options:
-  -  ​- Ethernet LAN: The interface will be accessible on IP address 192.168.200.200. The device will also attempt to acquire an additional dynamic IP address via DHCP, if DHCP is available.  +      ​- Ethernet LAN: The interface will be accessible on IP address 192.168.200.200. The device will also attempt to acquire an additional dynamic IP address via DHCP, if DHCP is available.  
-  ​-  ​- Wi-Fi: The UniPi Axon service mode will create a Wi-Fi access point with SSID “UNIPICONFIG” and password “unipi.technology”. The interface will be accessible on IP addresses 192.168.200.200 and 192.168.201.1+      - Wi-Fi: The UniPi Axon service mode will create a Wi-Fi access point with SSID “UNIPICONFIG” and password “unipi.technology”. The interface will be accessible on IP addresses 192.168.200.200 and 192.168.201.1
  
-After accessing the web interface you should see a screen with multiple buttons. To enable the SSH server first press the button with “Enable ssh” in the centre of the screen and then the “Restart System” button in the upper right corner of the screen.+After accessing the web interface you should see a screen with multiple buttons. To enable the SSH server first press the button with “Enable ssh” in the centre of the screen and then the “Restart System” button in the upper right corner of the scr 
 +een.
  
 ==== Setting up tools ==== ==== Setting up tools ====
Line 33: Line 35:
 You should now see a console window asking for a username and password. Use the username “unipi” and password “unipi.technology”;​ these may be changed later, but this is outside the scope of this tutorial. You should now see a console window asking for a username and password. Use the username “unipi” and password “unipi.technology”;​ these may be changed later, but this is outside the scope of this tutorial.
  
-At this point you should see a Linux command prompt with the following format “unipi@[your-device-ID]:​” – if so congratulations,​ you have connected to the internal SSH console successfully!+At this point you should see a Linux command prompt with the following format ​**“unipi@[your-device-ID]:​”** – if so congratulations,​ you have connected to the internal SSH console successfully!