Network Setup

From Engineered Arts Wiki
Revision as of 10:11, 28 March 2017 by W.stott (talk | contribs)
Jump to navigation Jump to search


This page describes the network setup for EA (Engineered Arts)' Robots

Normally no setup is required beyond connecting your robot to a wired network connection with internet access.

By default most routers and firewalls allow outgoing connections.

However, if you are experiencing problems or want details of the robot connections please read on.

Robot connections summary

Robots need to make following connections:

  • OUT to on PORT 443 (standard encrypted HTTPS port) - telepresence
  • OUT to on PORT 22 - web based remote admin interface for customers and EA
  • OUT to ( on PORT 2022 - command line level access required for EA to be able to support
  • IN and OUT to/from on PORT 80 - content creation and transfer to RoboThespian

If your firewall blocks outgoing connections please can you allow the above.

In depth information

Information for network administrators and/or customers who wish to know the details of the connections and what they are used for

The robot opens and maintains two outgoing connections to EA's servers through which EA can connect back to perform any administration tasks that could be performed as if EA were in front of the robot using a mouse and keyboard. Most of the time although the connection is open, it remains idle, with only data relevant to maintaining ssh service being exchanged.

The connection is encrypted and authentication handled using the exchange of private/public key pairs. For more details regarding ssh see

When EA are logged in (which we only do when requested to do something by our customers) there may be further outgoing connections, for example http get requests to download some new content from Whilst we could provide a log of data packets, you could sniff these yourselves using many available network analysis tools, but at the same time they would be of little use as they are encrypted. The unencrypted content of these packets would typically consist of the input of shell commands and the output of results, (all clear text), audio and sequence files (text file of robot axes movements)

EA can also manage the robot's content, perform diagnostics etc. A mix of xml based and standard http protocols are used for this (most our software is browser based), however these connections are always carried within the encrypted outgoing connection.

Current servers that the robot connects to:

  1. Our main server is at (
  2. The robot contacts the virtual robothespian website for generating animations and accessing animations (text files wrapped in .gz) and audio files (.ogg)
  3. The robot contacts for web based remote admin by yourselves and support by us.

Important note for customer support

In order to provide timely cost effective support to our customers EA need to be able to access the robot easily and reliably, if access is not possible, we cannot provide support.

LAN setup

For the robot IP - if you will be assigning IP by DHCP could you bind the IP to the robot's MAC address - giving it the same IP each time for your convenience.

Even better, if you are able to run local DNS then you can connect to the robot on your network via the robot's hostname e.g. for RoboThespian with serial 0103 simply use rt-0103 or for a SociBot with serial 21, simply sb-0021 - see Remote Connection