Personal tools

Log in

Changes

From IGEP - ISEE Wiki

Jump to: navigation, search

Using Ethernet to communicate

2,363 bytes removed, 13:42, 29 August 2012
m
Install Putty
{{Message/Information Message|title=|message= In this guide is used [[ IGEP firmware Yocto ]]}}
__TOC__
=== Overview ===
You can log into IGEP via many interfaces, such Serial, Wifi, USB-Ethernet Gadget, etc. In this tutorial we are going to connect to the board via its Ethernet interface. By default, all IGEP Processor boards have a static IP in their Ethernet interface which is 192.168.5.1 and dynamic IP address assigned via DHCP.
=== Requirements ===
There are some requisites to follow this guide:
*IGEP Processor Board with Ethernet
*Host PC
==Configure Host PC= Connect to IGEP device ==== Linux ==='''NOTE:''' You don't need to configure anything if you use [http://labs.isee.biz/index.php/IGEP_SDK_Virtual_Machine IGEP SDK Virtual Machine]
==== If you are running Linux ====in your PC, open a Terminal session and set the IP of the Ethernet interface in which IGEP is connected (for example eth0):
'''NOTE:''' You should have the usbnet module available for your Linux kernel. On most distributions, this is the case by default. If this is not the case for your distribution, you will need to enable USB networking support in the kernel. If you build your own kernel then you want 'CDC Ethernet support' in USB Network adaptors. IGEP SDK Virtual Machine has this module enabled.
<section begin=USB_linux />
*In the file /etc/network/interfaces, you should add:
<pre>iface usb0 eth0 inet dhcp</pre> *Plug an USB Type-A to USB Type-A mini cable between your host PC and the USB OTG from IGEP deviceiface eth0:0 inet staticaddress 192.168. Use a powered USB Hub if you use IGEP COM MODULE or PROTON Board5. 10*If you use IGEP&nbsp;SDK&nbsp;VM you need to attach the [http://labsnetmask 255.isee255.biz/index255.php0</IGEP_SDK_Virtual_Machine#Attach_removable_devices_to_Virtual_Machine removable device] RNDIS driver. pre>
*Type in a terminal:
<pre>sudo ifup usb0eth0:0</pre>
*Revise that:
<pre>jdoe@ubuntu ~ $ ifconfig
...
usb0 eth0:0 Link encap:Ethernet HWaddr 6608:cc00:f227:bead:510c:b6 ad inet addr:192.168.75.10 Bcast:1920.1680.70.255 0 Mask:255.255.255.0 inet6 addr: fe80::64cc:f2ff:febe:51b6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14 errors:0 dropped:0 overruns:0 frame:0 TX packets:44 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2496 (2.4 KB) TX bytes:8794 (8.7 KB)...</pre> *Connect to IGEP device  jdoe@ubuntu ~ $ ssh root@192.168.7.1 The authenticity of host '192.168.7.1 (192.168.7.1)' can't be established. ECDSA key fingerprint is 80:be:2d:b6:fe:b1:09:c3:3b:ac:0f:1d:f2:43:f2:20. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '192.168.7.1' (ECDSA) to the list of known hosts. root@igep00x0:~# uname -a Linux igep00x0 2.6.37 #1 Thu Jul 19 09:07:47 CEST 2012 armv7l GNU/Linux root@igep00x0:~# <section end=USB_linux />==== Troubleshooting ==== ===== WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! ===== In the case of the SSH client in Linux, a changed host key results in the client refusing to connect and showing an remote host identification has changed error   @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that the RSA host key has just been changed. The fingerprint for the RSA key sent by the remote host is 8d:0b:29:f0:0a:a1:f5:56:0c:12:18:b0:26:02:6d:9d. Please contact your system administrator. Add correct host key in /home/eballetbo/.ssh/known_hosts to get rid of this message. Offending key in /home/eballetbo/.ssh/known_hosts:57 RSA host key for 192.168.7.1 has changed and you have requested strict checking. To fix the problem edit your ~/.ssh/known_hosts and remove the line corresponding to this host.&nbsp;  ===== NFS in root filesystem ===== Don't use NFS in root filesystem combined with USB Ethernet Gadget === Windows and MAC OSX<br> === You should use [[IGEP SDK Virtual Machine|IGEP&nbsp;SDK&nbsp;Virtual Machine]] to develop under IGEP&nbsp;Technology == Configure == First of all, adjust the IP of your PC in order to be in the right subnet of IGEP, for example: 192.168.5.10 '' Linux: '' '''NOTE:''' You don't need to configure anything if you use [http://labs.isee.biz/index.php/IGEP_SDK_Virtual_Machine IGEP SDK Virtual Machine] If you are running Linux in your PC, open a Terminal session and set the IP of the Ethernet interface in which IGEP is connected (for example eth0):
Run the following commands:=== Windows and MAC OSX ===
sudo ifconfig eth0 down sudo ifconfig eth0 192.168.5.10 up'''NOTE:''' you should use [[IGEP SDK Virtual Machine|IGEP&nbsp;SDK&nbsp;Virtual Machine]] but you can use these steps:
''' Windows: '''
If you are running Windows in your PC, depending of your OS version and your configuration the steps might be slightly different:
# Close all the dialogs
'''MAC OSX:'''
 
'''(Please contribute)'''
 
== Connect to IGEP device ==
=== Install Putty ==='''ConnectNOTE:'''You don't need install anything if you use [[IGEP SDK Virtual Machine|IGEP&nbsp;SDK&nbsp;Virtual Machine]].
Now you are ready to log into IGEP via its Ethernet interface. You just need a program with a SSH client.
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
Install and run using executable or using apt-get command (in Linux):<pre>sudo apt-get install putty </pre> === Run Putty. === It will look like this:
[[Image:Putty ssh.png|center]]
user:root
password: (no password for this user: press return)
=== Troubleshooting ===
==== WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! ====
In the case of the SSH client in Linux, a changed host key results in the client refusing to connect and showing an remote host identification has changed error
''' Know more ''' @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that the RSA host key has just been changed. The fingerprint for the RSA key sent by the remote host is 8d:0b:29:f0:0a:a1:f5:56:0c:12:18:b0:26:02:6d:9d. Please contact your system administrator. Add correct host key in /home/eballetbo/.ssh/known_hosts to get rid of this message. Offending key in /home/eballetbo/.ssh/known_hosts:57 RSA host key for 192.168.7.1 has changed and you have requested strict checking.
In To fix the pre-installed software, the default configuration for all the network interfaces is: *eth0 - 192problem edit your ~/.168.5.1*eth0:0 - via dhcp*wlan0 - 192.168.6.1*usb0 - 192.168.7.1   By default, the IP of the Ethernet interface is 192.168.5.1 Once you are logged in, you can see which interfaces are up in IGEP. In ssh/known_hosts and remove the SSH console, run:  ifconfig It will list all the active network interfaces. If you want line corresponding to change, for example, ''eth0'' you can use the following commands (if you do it now, it will close the SSH session, as it will change the Ethernet IP):  ifconfig eth0 < new IP > In order to make permanent changes (save the configuration upon next start), you will have to edit the /etc/network/interfaces file in your IGEPthis host.&nbsp;
[[Category:Ethernet]]
4,199
edits