Firmware/Remote: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
No edit summary
Line 60: Line 60:


== Combining with serial terminal ==
== Combining with serial terminal ==
[[Image:Ofw-net2ser.png|right|0px]]

Use of rdc, rdcd, telnet and telnetd are ineffective if the problem being diagnosed is networking. In that case, the target firmware system must be accessed via serial.
Use of <code>rdc</code>, <code>rdcd</code>, <code>telnet</code> and <code>telnetd</code> on the target should be avoided if the problem being diagnosed is networking. In that case, the target firmware system must be accessed via serial.


Therefore, use another system as a relay, and start the <code>serial</code> program.
Therefore, use another system as a relay, and start the <code>serial</code> program.

The diagram on the right shows the relay connected to the target by back to back serial port. The setup sequence is:
* start <code>telnetd</code> on the relay,
* start <code>telnet</code> on the host,
* start <code>serial</code> on the relay,
* connect or power up the target.

Start the <code>serial</code> program before making the electrical connection or powering the target, so as to avoid a data loop.

The disconnection sequence is:
* power down or disconnect the target,
* exit <code>serial</code> using <code>^a^k</code>,
* exit <code>telnet</code> using <code>^]</code>.


= Internals =
= Internals =

Revision as of 03:42, 26 February 2013

Firmware Remote Diagnosis

Using telnetd

0px

On the target system:

  • start the telnet server:
ok telnetd
  • note the IP address shown,
  • wait for connection to arrive.

On the host system:

  • start the telnet client and connect to the IP address,
ok telnet IP

Once connected, the host keyboard and display will be using the command interpreter of the target.

To disconnect, type exit-telnet in the target command interpreter, or use ^] to exit the telnet client.

This method is ineffective if the target system is behind a NAT router with respect to the host, since the IP address is not routable.

Using rdc via a relay

0px

Scenario: need to connect to a user laptop that is behind a NAT router. You are at the host.

On a relay server that is accessible to the user over the internet:

  • set up a TCP relay that listens on ports 8024 and 8023:
% socat \
  TCP-LISTEN:8024,fork,reuseaddr,nodelay,bind=127.0.0.1 \
  TCP-LISTEN:8023,reuseaddr,nodelay

On the host system:

  • start a telnet client and connect to port 8024 on the relay server:
ok telnet IP 8024
(or, on a Linux client, type:
% telnet -- 127.0.0.1 -8024
the odd arguments are to force automatic initiation of TELNET options which would otherwise be omitted due to the non-standard port number).

On the target system, ask the user to start rdc:

ok rdc IP
where IP is the IP address of the relay server.

Once connected, the host keyboard and display will be using the command interpreter of the target.

To disconnect, type exit-rdc in the target command interpreter, or use ^] to exit the telnet program on the host.

The port number can be changed by mutual agreement. The default is 8023. For instance, to use port 9023 you must (a) change the socat command from 8023 to 9023, and (b) add 9023 to the end of the rdc command:

ok rdc IP 9023

Using rdc on a local area network

0px

On the host system:

  • start rdcd to listen for connections, and note the IP address shown,
ok rdcd

On the target system:

  • type rdc IP,
ok rdc IP

Once connected, the host keyboard and display will be using the command interpreter of the target.

To disconnect, type exit-rdc in the target command interpreter, or use ^] to exit the rdcd program on the host.

This method is ineffective if the host system is behind a NAT router with respect to the target, since the IP address is not routable.

Combining with serial terminal

0px

Use of rdc, rdcd, telnet and telnetd on the target should be avoided if the problem being diagnosed is networking. In that case, the target firmware system must be accessed via serial.

Therefore, use another system as a relay, and start the serial program.

The diagram on the right shows the relay connected to the target by back to back serial port. The setup sequence is:

  • start telnetd on the relay,
  • start telnet on the host,
  • start serial on the relay,
  • connect or power up the target.

Start the serial program before making the electrical connection or powering the target, so as to avoid a data loop.

The disconnection sequence is:

  • power down or disconnect the target,
  • exit serial using ^a^k,
  • exit telnet using ^].

Internals

  • telnet - a plain telnet client,
  • telnetd - a telnet server that binds the console to the accepted connection,
  • rdc - a telnetd that makes rather than accepting a connection.
  • rdcd - a telnet that accepts rather than making a connection.