This documents the procedures for executing the tests in this collection on both Linux and RTEMS. Some tests can run without intervention or special setup. Others are manual. Some require special services to be available.
A subset of the networking tests may be executed without manual interactive actions. The command make runtests or make CONFIG_INC=@CONFIG_FILE@ runtests will execute them on the native host or a simulator. If the target is an embedded board without a runner script, it may be necessary to run them one at a time manually.
The following tests may be executed with no manual actions required.
- devctl_socket
- fcntl_socket
- getaddrinfo01
- getnameinfo01
- ioctl_socket
- send_recv
- sockopt01
The 'send_recv' test attempts to perform at http "get" transaction with devel.rtems.org by IP address. The target board
- tcp_echo_client
- tcp_echo_server
- udp_echo_server
- mcast_listener
- mcast_writer
- select01
These are discussed in the following subsections.
tcp_echo_client and tcp_echo_server are a mated pair. One is run on the target system and the other on the system under test. For complete testing, the client and server should be run on the target. tcp_echo_server should be invoked first as in the following example specifying the number of times to echo and the port to listen on:
tcp_echo_server 5 22001
tcp_client_client is interactive and is invoked with the port to connect to as shown below:
tcp_echo_client 22001
udp_echo_server is executed on the system under test. Use a program such as netcat to interact with it.
mcast_server and mcast_client are a mated pair. One is run on the target system and the other on the system under test. It will be necessary to address routing and firewall configuration for the two systems to communicate multicast.
select01 waits for connections. telnet from the host system to the system under test. There can be multiple telnet sessions.