ODROID MAGAZINE 9
sole
i f
X11
is not run-
ning.]
In order to connect to your
ODROID, you’ll need to discover the
hostname or IP address of the board.
For the Ubuntu server image we used
on our XU+E cluster, the default host
-
name is “odroid-server”, while for other
images we’ve used, it’s been “odroid”.
Most home networks should support
DNS by default, which will allow you to
connect simply by the hostname. If this
fails, you can alternatively connect using
the IP address assigned to the ODROID
by your router instead. If neither of the
hostnames resolves for you, check your
router’s lease table to search for the IP
address, often labeled as the DHCP cli
-
ent table in the router’s admin panel.
Since we used identical copies of the
same image on both nodes, by default
they had a hostname conict, which we
resolved by bringing them online one at
a time, then changing the individual net
-
work settings. If you don’t have access
to the router’s admin panel, you can also
make use of the nmap command to
scan your network for hosts to nd
the ODROIDs, if you know your
network information. For ex
-
ample: “nmap 192.168.1.0/24”.
Look for a host that has port 22
open.
Power on one of the
ODROIDs, then enter “ssh
odroid@ubuntu-server” (or
“ssh odroid@xxx.xx.xx.xxx”,
if using the IP address) in the
Terminal or Putty window of
the host computer, which will
establish a secure connection to
the ODROID. To login, type
“odroid” as the password.
Once the command prompt ap
-
pears, you may want to run “sudo apt-
get update && sudo apt-get upgrade” to
ensure that your OS is up to date. Fur
-
thermore, we recommend you run the
“passwd” command and change the pass
-
word for the odroid user to something a
little more secure, or creating new user
accounts with the “adduser” command,
such as by running “sudo adduser kilroy”.
(Generally speaking, do three things key
with your node passwords: make them
long, make them hard to guess, and store
it in a secure location.)
Configuring
Networking
Before getting both ODROIDs on-
line, we need to change a few settings as
to eliminate hostname and MAC address
conicts that may occur on your home
network with an ODROID cluster. To
change the hostname, we will need to
edit two les, /etc/hostname and /etc/
hosts, changing “odroid-server’ to the
hostname of your choice and rebooting
the machine so the changes take eect.
For the purposes of this article we will
use odroid-server0 and odroid- server1
to refer to the rst and second ODROID
respectively. Alternatively, if your operat
-
ing system supports it, you can also type
“sudo odroid-cong” to change the host
-
name. You can use other names of your
choice; they have to be unique to each
node.
e MAC address conict was a sub
-
tle issue that we encountered when we
rst set up multiple ODROID XU+E’s.
We found that, by default, the onboard
ethernet devices all shared the same
MAC address, which made it impossible
to work on a single ODROID if mul
-
tiple were powered online and on the
same network. If the two ODROIDs
you’re working have identical MAC ad
-
dresses, there are two straightforward
ways to resolve this: 1) congure one (or
both) of the ODROIDs to use a dierent
MACaddress, or 2) setup USB ethernet
dongles, which should all have unique
MAC addresses. e specic values you
choose really don’t matter, as long as you
keep them unique on your Local Area
Network (LAN).
To change the MAC address of the
onboard device, edit
/etc/network/
interfaces with your text editor of
choice, and add the line “hwaddress
ether newmac”, where newmac is an ad
-
dress in the format “b6:8d:67:7b:cb:e0”
underneath the following labels:
auto eth0
iface eth0 inet dhcp
en, reboot the ODROID so the
changes take eect. Make sure to verify
the new address using the ifcong com
-
mand. Alternatively, you can opt to plug
your USB Ethernet adapters into the
USB 3.0 slot, and then run “ifcong -a |
grep eth”, which should yield a list simi
-
lar to this:
eth0 Link encap:Ethernet
HWaddr b6:8d:67:7b:cb:e0
eth2 Link encap:Ethernet
HWaddr 00:13:3b:99:92:b1
By default, eth0 will be the onboard
10/100 ethernet connection, while the
second ethernet device (in this case,
HPC AT HOME