IPV4 RAW AF INET RAW server client program with Epoll system call ==================================================================== .. tab-set:: .. tab-item:: IPv4 RAW_AF_INET RAW * In this program, you are going to learn .. panels:: :container: container pb-4 :column: col-lg-12 p-2 :card: shadow * How to create a Socket ? .. panels:: :container: container pb-4 :column: col-lg-12 p-2 :card: shadow * How to send a data ? .. panels:: :container: container pb-4 :column: col-lg-12 p-2 :card: shadow * How to recv a data ? .. panels:: :container: container pb-4 :column: col-lg-12 p-2 :card: shadow * How to use socket APIs ? * `socket `_ * `epoll_create1 `_ * `epoll_ctl `_ * `epoll_wait `_ * `sendto `_ * `recvfrom `_ .. panels:: :container: container pb-4 :column: col-lg-12 p-2 :card: shadow Topics in this section, * :ref:`IPV4 RAW_AF_INET RAW SOCKET FAQs ` * :ref:`Step 1: Sequence Diagram for SERVER.c ` * :ref:`Step 2: Program for Server.c ` * :ref:`Step 3: Compile and Execute Server.c ` * :ref:`Step 4: Sequence Diagram for CLIENT.c ` * :ref:`Step 5: Program for Client.c ` * :ref:`Step 6: Compile and Execute Client.c ` * :ref:`Summary ` .. _epoll_ipv4_raw_af_inet_raw_socket: .. tab-set:: .. tab-item:: IPV4 RAW_AF_INET RAW SOCKET : FAQs .. panels:: :container: container pb-4 :column: col-lg-12 p-2 :card: shadow Let us answer few basic questions in this socket .. panels:: :container: container pb-4 :column: col-lg-12 p-2 :card: shadow What does ``socket(AF_INET, SOCK_RAW, IPPROTO_RAW)`` do? .. dropdown:: See Answer This call creates a raw socket in the IPv4 address family ``(AF_INET)`` that allows applications to send raw IP packets. .. panels:: :container: container pb-4 :column: col-lg-12 p-2 :card: shadow Why use ``AF_INET`` as the address family? .. dropdown:: See Answer ``AF_INET`` specifies that the socket will work with IPv4 addresses. .. panels:: :container: container pb-4 :column: col-lg-12 p-2 :card: shadow What is the purpose of ``SOCK_RAW`` in the socket type? .. dropdown:: See Answer ``SOCK_RAW`` allows the socket to operate at a lower level by providing direct access to the packet, including the IP header. .. panels:: :container: container pb-4 :column: col-lg-12 p-2 :card: shadow Why specify ``IPPROTO_RAW`` as the protocol? .. dropdown:: See Answer It indicates that the socket will be used to send raw IP packets without any specific transport layer protocol. .. panels:: :container: container pb-4 :column: col-lg-12 p-2 :card: shadow How does this socket differ from a standard UDP or TCP socket? .. dropdown:: See Answer Unlike UDP or TCP sockets, a raw socket with ``IPPROTO_RAW`` is intended specifically for sending raw IP packets. .. panels:: :container: container pb-4 :column: col-lg-12 p-2 :card: shadow Is error checking needed after creating the socket? .. dropdown:: See Answer Yes, checking for errors ensures that the socket is created successfully before proceeding with further operations. .. panels:: :container: container pb-4 :column: col-lg-12 p-2 :card: shadow Can this socket be used for other protocols besides IP? .. dropdown:: See Answer No, ``IPPROTO_RAW`` specifies that the socket is exclusively for sending raw IP packets. .. panels:: :container: container pb-4 :column: col-lg-12 p-2 :card: shadow How is the destination IP address specified for the packet? .. dropdown:: See Answer The destination IP address is set in the IP header of the packet created by the application. .. panels:: :container: container pb-4 :column: col-lg-12 p-2 :card: shadow How is the source IP address handled in the packet? .. dropdown:: See Answer The source IP address needs to be set in the IP header by the application. .. panels:: :container: container pb-4 :column: col-lg-12 p-2 :card: shadow Can this socket type be used with IPv6? .. dropdown:: See Answer For IPv6, the equivalent would be AF_INET6 with ``SOCK_RAW`` and ``IPPROTO_RAW``. .. panels:: :container: container pb-4 :column: col-lg-12 p-2 :card: shadow What is the primary purpose of the epoll system call? .. dropdown:: See Answer To efficiently monitor multiple file descriptors for I/O events .. panels:: :container: container pb-4 :column: col-lg-12 p-2 :card: shadow What types of file descriptors can be monitored using epoll? .. dropdown:: See Answer sockets, files, timerfd, socketpair, message_queue, Namedpipes and shared_memory. .. panels:: :container: container pb-4 :column: col-lg-12 p-2 :card: shadow What data structure is used by epoll to store events? .. dropdown:: See Answer Hash table .. panels:: :container: container pb-4 :column: col-lg-12 p-2 :card: shadow How do you handle errors when using the epoll system call? .. dropdown:: See Answer Check the return value for -1 to detect errors, Use perror to print error messages. .. panels:: :container: container pb-4 :column: col-lg-12 p-2 :card: shadow How does epoll handle a set of file descriptors with different states (e.g., reading, writing, exception)? .. dropdown:: See Answer Create the epoll Instance: Before monitoring file descriptors, the application creates an epoll instance using the epoll_create system call. .. code-block:: c int epoll_fd = epoll_create1(0); Register File Discriptors: The application registers file descriptors with the epoll instance using the epoll_ctl system call. It specifies the file descriptor, the events it is interested in (EPOLLIN for readability, EPOLLOUT for writability, etc.), and a user-defined data associated with the file descriptor. .. code-block:: c struct epoll_event event; event.events = EPOLLIN | EPOLLOUT; // Interested in readability and writability event.data.fd = my_file_descriptor; // File descriptor to monitor epoll_ctl(epoll_fd, EPOLL_CTL_ADD, my_file_descriptor, &event); Wait for Events: The application enters a loop where it calls epoll_wait to wait for events. This call blocks until one or more registered file descriptors become ready or until a timeout occurs. .. code-block:: c #define MAX_EVENTS 10 struct epoll_event events[MAX_EVENTS]; int num_events = epoll_wait(epoll_fd, events, MAX_EVENTS, timeout_ms); Modify or Remove File Descriptors: The application can dynamically modify or remove file descriptors from the epoll set using the epoll_ctl system call. For example, to modify events for an existing file descriptor: .. code-block:: c struct epoll_event new_event; new_event.events = EPOLLOUT; // Modify to be interested in writability epoll_ctl(epoll_fd, EPOLL_CTL_MOD, my_file_descriptor, &new_event); To remove a file descriptor from the epoll set: .. code-block:: c epoll_ctl(epoll_fd, EPOLL_CTL_DEL, my_file_descriptor, NULL); .. panels:: :container: container pb-4 :column: col-lg-12 p-2 :card: shadow How does epoll Checking Ready File Descriptors? .. dropdown:: See Answer After epoll_wait returns, the application iterates through the returned events to identify which file descriptors are ready and for what types of events. .. code-block:: c for (int i = 0; i < num_events; ++i) { if (events[i].events & EPOLLIN) { // File descriptor i is ready for reading } if (events[i].events & EPOLLOUT) { // File descriptor i is ready for writing } // Check other events if needed (e.g., EPOLLERR, EPOLLHUP) } .. panels:: :container: container pb-4 :column: col-lg-12 p-2 :card: shadow What does it mean if epoll returns 0? .. dropdown:: See Answer No file descriptors are ready within the specified timeout. .. _epoll_ipv4_raw_af_inet_raw_socket_server_sequence_diagram: .. tab-set:: .. tab-item:: Step 1: Sequence Diagram for SERVER.c .. plantuml:: @startuml !theme spacelab start :socket(AF_INET, SOCK_RAW, IPPROTO_RAW); :bind(sockfd, (struct sockaddr*)&server_addr, sizeof(server_addr)); :epoll_fd = epoll_create1(0); :epoll_ctl(epoll_fd, EPOLL_CTL_ADD, sockfd, &event); while (while(1)) is (yes) :epoll_wait(epoll_fd, events, MAX_EVENTS, -1); if (events[0].data.fd == sockfd) then (yes) :recvfrom(sockfd, buffer, sizeof(buffer), 0, (struct sockaddr*)&server_addr, &addr_len)); :sendto(sockfd, buffer, len, 0, (struct sockaddr*)&server_addr, addr_len); else (no) endif endwhile (CTRL+c) :(void)close(sockfd); stop @enduml .. _epoll_ipv4_raw_af_inet_raw_socket_server_code: .. tab-set:: .. tab-item:: Step 2: Program for Server.c * There are many functions used in socket. We can classify those functions based on functionalities. * Create Socket * Epoll create1 * Epoll_ctl * Epoll_wait * Recvfrom data_packet * Sendto data_packet * Close socket * ``socket()`` is used to create a new socket. For example, .. code-block:: c sockfd = socket(AF_INET, SOCK_RAW, IPPROTO_RAW); * ``epoll_create1()`` creating an epoll instance using epoll_create1, The size parameter is an advisory hint for the kernel regarding the number of file descriptors expected to be monitored, For example, .. code-block:: c epoll_fd = epoll_create1(0); * ``epoll_ctl()`` After creating an epoll instance, file descriptors are added to it using epoll_ctl, For example, .. code-block:: c ret = epoll_ctl(epoll_fd, EPOLL_CTL_ADD, sockfd, &event); * ``epoll_wait()`` The application then enters a loop where it waits for events using epoll_wait, For example, .. code-block:: c ready_fds = epoll_wait(epoll_fd, events, MAX_EVENTS, -1); * ``recvfrom`` is commonly used with sockets, where communication is connectionless. it provides information about the source (sender) of the data, including the sender's IP address and port number. For example, .. code-block:: c len = recvfrom(sockfd, buffer, sizeof(buffer), 0, (struct sockaddr*)&server_addr, &addr_len)); * ``sendto`` is used to send the encoded message to the specified server address and port using a socket. For example, .. code-block:: c ret = sendto(sockfd, buffer, len, 0, (struct sockaddr*)&server_addr, addr_len); * ``close`` is used to close the socket To free up system resources associated with the socket. For example, .. code-block:: c (void)close(sockfd); * See the full program below, .. literalinclude:: ipv4_raw_af_inet_raw/server/server.c :language: c :emphasize-lines: 60, 61, 62, 69, 70, 71, 81, 91, 92, 93, 104, 105, 114, 115, 116, 117, 133, 134, 135, 136, 145, 146 .. _epoll_ipv4_raw_af_inet_raw_socket_server_side_compile_and_execute: .. tab-set:: .. tab-item:: Step 3: Compile and Execute Server.c .. code-block:: c :emphasize-lines: 1, 3 $ gcc -o server server.c $ sudo ./server Server is waiting Received raw packet: 45 00 00 14 30 39 00 00 FF FF 8C AF 7F 00 00 01 7F 00 00 01 Received raw packet: 45 00 00 14 30 39 00 00 FF FF 8C AF 7F 00 00 01 7F 00 00 01 Received raw packet: 45 00 00 14 30 39 00 00 FF FF 8C AF 7F 00 00 01 7F 00 00 01 Received raw packet: 45 00 00 14 30 39 00 00 FF FF 8C AF 7F 00 00 01 7F 00 00 01 Received raw packet: 45 00 00 14 30 39 00 00 FF FF 8C AF 7F 00 00 01 7F 00 00 01 Received raw packet: 45 00 00 14 30 39 00 00 FF FF 8C AF 7F 00 00 01 7F 00 00 01 Received raw packet: 45 00 00 14 30 39 00 00 FF FF 8C AF 7F 00 00 01 7F 00 00 01 Received raw packet: 45 00 00 14 30 39 00 00 FF FF 8C AF 7F 00 00 01 7F 00 00 01 Received raw packet: 45 00 00 14 30 39 00 00 FF FF 8C AF 7F 00 00 01 7F 00 00 01 Received raw packet: 45 00 00 14 30 39 00 00 FF FF 8C AF 7F 00 00 01 7F 00 00 01 Received raw packet: 45 00 00 14 30 39 00 00 FF FF 8C AF 7F 00 00 01 7F 00 00 01 .. _epoll_ipv4_raw_af_inet_raw_socket_client_sequence_diagram: .. tab-set:: .. tab-item:: Step 4 : Sequence Diagram for CLIENT.c .. plantuml:: @startuml !theme spacelab start :socket(AF_INET, SOCK_RAW, IPPROTO_RAW); :epoll_fd = epoll_create1(0); :epoll_ctl(epoll_fd, EPOLL_CTL_ADD, sockfd, &event); while (while(1)) is (yes) :sendto(sockfd, buffer, IP_HEADER_SIZE, 0, (struct sockaddr*)&server_addr, sizeof(server_addr)); :epoll_wait(epoll_fd, events, MAX_EVENTS, -1); if (events[0].data.fd == sockfd) then (yes) :recvfrom(sockfd, buffer, sizeof(buffer), 0, NULL, NULL); else (no) endif endwhile (CTRL+c) :(void)close(sockfd); stop @enduml .. _epoll_ipv4_raw_af_inet_raw_socket_client_code: .. tab-set:: .. tab-item:: Step 5: program for client.c * There are many functions used in socket. We can classify those functions based on functionalities. * Create Socket * Epoll create1 * Epoll_ctl * Epoll_wait * Sendto data_packet * Recvfrom data_packet * Close socket * ``socket`` is used to create a new socket. For example, .. code-block:: c sockfd = socket(AF_INET, SOCK_RAW, IPPROTO_RAW); * ``epoll_create1()`` creating an epoll instance using epoll_create1, The size parameter is an advisory hint for the kernel regarding the number of file descriptors expected to be monitored, For example, .. code-block:: c epoll_fd = epoll_create1(0); * ``epoll_ctl()`` After creating an epoll instance, file descriptors are added to it using epoll_ctl, For example, .. code-block:: c ret = epoll_ctl(epoll_fd, EPOLL_CTL_ADD, sockfd, &event); * ``epoll_wait()`` The application then enters a loop where it waits for events using epoll_wait, For example, .. code-block:: c ready_fds = epoll_wait(epoll_fd, events, MAX_EVENTS, -1); * ``sendto`` is used to send the encoded message to the specified server address and port using a socket. For example, .. code-block:: c ret = sendto(sockfd, buffer, IP_HEADER_SIZE, 0, (struct sockaddr*)&server_addr, sizeof(server_addr)); * ``recvfrom`` is commonly used with sockets, where communication is connectionless. it provides information about the source (sender) of the data, including the sender's IP address and port number. For example, .. code-block:: c len = recvfrom(sockfd, buffer, sizeof(buffer), 0, NULL, NULL); * ``close`` is used to close the socket To free up system resources associated with the socket. For example, .. code-block:: c (void)close(sockfd); * See the full program below, .. literalinclude:: ipv4_raw_af_inet_raw/client/client.c :language: c :emphasize-lines: 66, 67, 68, 115, 116, 117, 137, 148, 149, 160, 161, 162, 163, 170, 171, 172, 186 .. _epoll_ipv4_raw_af_inet_raw_socket_client_side_compile_and_execute: .. tab-set:: .. tab-item:: Step 6: Compile and Execute client.c .. code-block:: c :emphasize-lines: 1, 3 $ gcc -o client client.c $ sudo ./client 127.0.0.1 IP Address: 127.0.0.1 Client is sending Received: 45 00 00 14 30 39 00 00 FF FF 8C AF 7F 00 00 01 7F 00 00 01 Client is sending Received: 45 00 00 14 30 39 00 00 FF FF 8C AF 7F 00 00 01 7F 00 00 01 Client is sending Received: 45 00 00 14 30 39 00 00 FF FF 8C AF 7F 00 00 01 7F 00 00 01 Client is sending Received: 45 00 00 14 30 39 00 00 FF FF 8C AF 7F 00 00 01 7F 00 00 01 Client is sending Received: 45 00 00 14 30 39 00 00 FF FF 8C AF 7F 00 00 01 7F 00 00 01 Client is sending Received: 45 00 00 14 30 39 00 00 FF FF 8C AF 7F 00 00 01 7F 00 00 01 Client is sending Received: 45 00 00 14 30 39 00 00 FF FF 8C AF 7F 00 00 01 7F 00 00 01 .. tab-set:: .. tab-item:: Enhanced Socket Flexibility with ``AF_INET`` and ``PF_INET`` Domains .. panels:: :container: container pb-4 :column: col-lg-12 p-2 :card: shadow **Default Domain:** By default, the socket is configured to work in the ``AF_INET`` domain, handling all types of network data. **Additional Domain Support:** We expand the socket's capabilities to also function in the ``PF_INET`` domain, allowing it to operate similarly to ``AF_INET``. **Socket Creation:** We set up a network connection point known as a socket using ``socket(PF_INET, SOCK_RAW, IPPROTO_RAW)``. **Working Scenario:** Despite the change in domain to ``PF_INET``, the socket continues to operate the same way, handling general network data. .. _epoll_ipv4_raw_af_inet_raw_Summary: .. tab-set:: .. tab-item:: Summary ============== ================================================================================================================== Socket API Learning ============== ================================================================================================================== socket Create a new socket epoll handles a set of file descriptors with different states, such as reading, writing, and exceptions, by using the struct epoll_event structure and the associated event flags.. recvfrom It provides information about the source (sender) of the data, including the sender's IP address and port number. sendto Send the encoded message to the specified server address and port using a socket. ============== ================================================================================================================== .. card:: See Also * Previous topic * :doc:`../../../sockets/ipv4_raw_af_inet_raw/poll/poll` * Current topic * :doc:`../../../sockets/ipv4_raw_af_inet_raw/epoll/epoll` * Next topic * :doc:`../../../sockets/ipv4_raw_af_inet_tcp` * Other sockets * :doc:`../../../sockets/ipv4_raw_af_inet_udp` * :doc:`../../../sockets/ipv6_af_inet6_tcp` * :doc:`../../../sockets/ipv6_af_inet6_udp` * :doc:`../../../sockets/ipv6_raw_af_inet6_icmp` * :doc:`../../../sockets/ipv6_raw_af_inet6_tcp` * :doc:`../../../sockets/ipv6_raw_af_inet6_udp` * :doc:`../../../sockets/ipv6_raw_af_inet6_raw` * :doc:`../../../sockets/raw_af_packet_raw_htons_ETH_P_ALL` * :doc:`../../../sockets/raw_af_packet_tcp_htons_ETH_P_ALL` * :doc:`../../../sockets/raw_af_packet_udp_htons_ETH_P_ALL` * Other IPCs * :doc:`../../../Message_queues/Message_queues` * :doc:`../../../NamedPipes/NamedPipes` * :doc:`../../../Netlink/Netlink` * :doc:`../../../Shared_Memory/Shared_Memory` * :doc:`../../../Shared_Memory_2_FDS/Shared_Memory_2_FDS` * :doc:`../../../SocketPair/SocketPair` * :doc:`../../../Timerfd/Timerfd`