Project Overview

<aside> A technical deep-dive into implementing native TCP sockets with demonstrations and results

</aside>

Problem Statement

As part of my assignments repository, I needed to implement a native socket server, aesdsocket, that adhered to strict requirements. The server had to bind to port 9000, accept client connections, log connection details, receive data, store it in a file, and return the file contents upon receiving complete packets. Additionally, it had to handle signals gracefully, support daemon mode, and pass validation using an automated test script (full-test.sh). Ensuring robustness, proper error handling, and compliance with these specifications was a significant challenge.

Action Taken

Technical Implementation

• Socket Architecture Design:
  • Developed a socket-based server that binds to port 9000 and listens for incoming client connections.
  • Implemented socket handling for connection acceptance, data reception, and response transmission.
• Key Code Components:
  • Implemented functions to handle client connections, receive and append data, and respond with file content.
  • Utilized syslog for logging connection and error messages.
  • Implemented proper error handling for socket failures and memory allocation errors.
• Implementation Challenges Overcome:
  • Managed newline-separated packet processing efficiently.
  • Handled large file sizes and ensured memory management was efficient.
  • Implemented graceful termination using signal handlers.
• Testing Strategies:
  • Installed netcat for manual testing of the socket server.
  • Validated functionality using sockettest.sh, ensuring correct data storage and retrieval.
  • Successfully executed full-test.sh to verify compliance with specifications.

Results & Demo

Terminating aesdsocket process

aesdsocketterm.mp4

aesdsocket after integration into QEMU

Key Learnings

Document the insights gained from this project:

• Technical discoveries
• Best practices identified