The SockServer is an application providing a set of services used by the WiFi CMSIS-Driver Validation suite to test the Socket interface of the WiFi driver. It is located in the <pack installation root>/Tools/SockServer subdirectory of the pack root directory. The SockServer is available for different target systems. It runs several standard network services.

The SockServer is available for Personal Computer running Microsoft Windows (executable located in <pack installation root>/Tools/SockServer/PC/Win).

The following services are available by SockServer:

Echo service on port 7, TCP and UDP
(two instances of TCP service, one instance of UDP service)
Discard service on port 9, TCP and UDP
(one instance of TCP service, one instance of UDP service)
Chargen service on port 19, TCP and UDP
(two instances of TCP service, one instance of UDP service)
Assistant service on port 5000
(helper service used to test WiFi sockets in server mode (socket accept functionality))
Telnet service on port 23
(SockServer status monitoring service)

SockServer for PC running Microsoft Windows

Requirements:

Personal Computer running Microsoft Windows
PC connection to local network

SockServer is already built and can be executed by running the SockServer.exe file in <pack installation root>/Tools/SockServer/PC/Win.

If you need to change the functionality of SockServer, source files and a batch script for building the executable are available in <pack installation root>/Tools/SockServer/PC/Win.

Note

SockServer build process requires Minimalist GNU for Windows (MinGW).
To build the SockServer executable for Windows, follow these steps:
- Download and install MinGW from https://winlibs.com/
- Set environment path in Microsoft Windows as explained under Usage heading on https://winlibs.com/#usage
- Run Build.bat located in <pack installation root>/Tools/SockServer/PC/Win which will result in an executable that is located in <pack installation root>/Tools/SockServer/PC/Win

Troubleshooting

Problems and solutions:

SockServer not responding to requests
- Open Windows firewall -> Advanced settings
  - select inbound rules
- create a new custom rule (New Rule...)
  - Rule type: Program
  - Program: This program path (select path to SockServer.exe)
  - Action: Allow the connection
  - Profile: Domain, Private (Public not advised)
  - Name: SockServer
Test computer not responding to ping
- Open Windows firewall -> Advanced settings
  - select inbound rules, enable rule File and Printer sharing (Echo request - ICMPv4-In)
- If rule does not exist, create a new custom rule (New Rule...)
  - Rule type: Custom
  - Program: All programs
  - Protocol type: ICMPv4
  - ICMP Settings: Customize - Specific ICMP types: Echo Request
  - Scope: Any IP address
  - Action: Allow the connection
  - Profile: Domain, Private (Public not advised)
  - Name: Ping Echo