Network Programming in Rust

#network #tcpip #go

The aim of this three part series is to help the reader, both tech and non-tech, to visualize as they read what happens in the world of networking. Rust is chosen as the language, but the concept is applicable to any language of the readers' choice.

Image source: Screenshot from https://www.rust-lang.org/what/networking

Simply put, networking refers to the process of connecting and communicating with others. What is a process? Process refers to a series of actions, steps, or operations that are followed in order to achieve a particular result or objective. Networking can be divided based on specific contexts i.e. social networking, professional networking, computer networking amongst others. Regardless of the context, the objective is to connect and communicate; to connect, there a process to be followed. In this article, I'll restrict the context to Computer Networking which involves connecting computers and devices to share resources and communicate to each other. The process of establishing computer networking includes protocols, infrastructure, security measures, and technologies like routers, switches, and firewalls.

In networking, people or devices must be READY/AVAILABLE for the connection. In Professional Networking: This can be done through events, conferences, social media platforms (like LinkedIn), and other personal connections. In an event, people have ways they can be identified with, whether name, email, company they are working for, or any other means. To complete the process of being ready and being ready for future communication, you take the contact/name or any means of reaching out to the intended party.

In computer networking, for a device to be ready/available, a lot goes into place. This a lot include: Network Design and Planning, which can be summarized as:

a. Design and Planning

Determine Requirements: Identify the needs of the network, such as bandwidth, security, and number of devices.
Select Network Topology: Decide on the layout of the network (e.g., star, bus, mesh).
Choose Hardware: Select routers, switches, access points, etc.

b. Physical Setup

Cable and Connect Devices: Set up physical connections between devices, including wiring, switches, and routers.
Wireless Setup: If it's a wireless network, set up wireless access points.

c. IP Addressing and Configuration

Assign IP Addresses: Assign static or dynamic IP addresses to devices in the network. (This is where the unique identity to each and every device is established. It is like a name/email/place of work. It must be UNIQUE)
Configure Routing: Set up routing protocols to ensure devices can communicate across different networks.

d. Network Protocol Configuration

Install Protocols: Set up protocols like TCP/IP (Transmission Control Protocol/Internet Protocol), DNS (Domain Name System), DHCP (Dynamic Host Configuration Protocol), etc., for communication.

e. Security Configuration

Firewall Setup: Configure firewalls to protect the network from unauthorized access.
Encryption: Ensure data is encrypted for confidentiality.
Access Control: Set up user permissions and roles to control who can access certain parts of the network.

f. Testing and Monitoring

Test Connectivity: Use tools like ping or traceroute to test device connections and network performance.
Monitor Network Traffic: Regularly monitor network traffic to ensure everything is running smoothly and troubleshoot any issues.

Once the Computer Networking Process is complete, the device(s), is/are now ready to connect and communicate.

The process of being ready is complete. The next step is to establish a connection for the communication to take place. Assume you want to get a resource (file, song, movie, web page etc.) from Device Z, located at Ondati Center, the process will be as follows:

You type a URL in their browser.
The browser sends a request to a DNS server to resolve the domain name
The request is passed to the transport layer to establish a connection.
Data is split into packets, and the network layer (IP) routes the packets to the server.
The server receives the packets, processes them, and sends the data back through the same layers in reverse order.
The client browser reconstructs the data and displays the web page.

In part two of this series, I'll deconstruct the above process, what happens under the hood, well.. at a molecular level.
Also watch out for part three on how you can use Rust in developing your next Networking Application.

#goForRust
Happy Coding