04 Elementary. Client/Server. CEN 463 Network Programming. Dr. Mostafa Hassan Dahshan. King Saud University
|
|
- Ferdinand Evans
- 6 years ago
- Views:
Transcription
1 CEN 463 Network Programming 04 Elementary TCP Sockets Dr. Mostafa Hassan Dahshan College of Computer and Information Sciences King Saud University Elementary TCP Client/Server 2
2 socket Function First function process must call to perform network I/O #include <sys/socket.h> int socket (int family, int type,, int protocol); ) Returns: non-negative descriptor if OK, -1 on error family AF_INET AF_INET6 AF_LOCAL AF_ROUTE Description IPv4 protocols IPv6 protocols Unix domain protocols Routing sockets type SOCK_STREAM SOCK_DGRAM SOCK_SEQPACKET Description stream socket datagram socket sequenced packet socket AF_KEY Key socket kt SOCK_RAW raw socket protocol IPPROTO_TCP IPPROTO_UDP IPPROTO_SCTP Description TCP transport protocol UDP transport protocol SCTP transport protocol 3 socket Function Allowed combinations shown in table Other values/names used in some systems On success, socket returns positive int Called socket descriptor (sockfd) AF_INET AF_INET6 AF_LOCAL AF_ROUTE AF_KEY SOCK_STREAM TCP, SCTP TCP, SCTP Yes SOCK_DGRAM UDP UDP Yes SOCK_SEQPACKET SCTP SCTP Yes SOCK_RAW IPv4 IPv6 Yes Yes 4
3 connect Function Used by TCP client to establish connection with TCP server #include <sys/socket.h> int connect(int sockfd, const struct sockaddr *servaddr, socklen_ t addrlen); Returns: 0 if OK, -1 on error sockfd is socket ktdescriptor returned dby socket servaddr is a pointer to sockaddr structure addrlen is length of servaddr (since its by ref) servaddr must include server s IP and port 5 connect Function For TCP, connect initiates 3 way handshake h Move from CLOSED to SYN_SENT state Returns only if connection is established (ESTABLISHED state) error occurs (must go back to CLOSED state) Error code Reason Possible cause ETIMEOUT No response to SYN segment Server offline or turned off ECONNREFUSED server responds with RST EHOSTUNREACH ENETUNREACH ICMP "destination unreachable from intermediate router after multiple SYN requests server process not running no route to server machine, should not fail due to transient errors 6
4 bind Function Assigns a local lprotocol address to a socket kt #include <sys/socket.h> int bind (int sockfd, const struct sockaddr *myaddr, socklen_t addrlen); Returns: 0 if OK,-1 on error For IP, protocol potocoaddress is IP address + port Server have to call bind, clients don t Servers bind to their well known ports on start If not called, kernel choose ephemeral port when calling connect or listen 7 bind Function Process can bind specific IP client: assign source IP used for sent datagrams server: restrict incoming connections to that IP TCPclients normally don t bind specific IP kernel decides interface based on route If TCP server doesn t bind an IP address kernel uses dest IP in client SYN as server ss src IP Common error (errno == EADDRINUSE) address (IP + port) already in use 8
5 IP and Port Specification for bind Process Specifies IP address Port Result Wildcard (any) 0 Kernel chooses IP address and port Wildcard (any) nonzero Kernel chooses IP address, process specifies port Local IP address 0 Process specifies IP address, kernel chooses port Local IP address nonzero Process specifies IP address and port 9 Virtual Hosting one.com two.com three.com All IP addresses aliases to same interface using alias option in ifconfig command IP layer will accept datagrams to all IP addresses Each copy of HTTP server e binds to different e IP demultplexing of datagrams done by kernel Another approach, bind to wildcard address demultiplexing done by process (web server) 10
6 listen Function Converts an unconnected socket into a passive socket #include <sys/socket.h> int listen (int sockfd, int backlog); Returns: 0 if OK, -1 onerror Indicate that kernel should accept incoming connection requests to socket sockfd Move socket from CLOSED to LISTEN state Called after socket, bind and before accept backlog is max number of connections kernel can queue for this socket 11 Listening Socket Connection Queues backlog = sum of the lengths of these two queues Incomplete connection queue received SYN, awaiting completion of 3 way HS when ACK received, move to complete connection queue Complete connection queue entry for each client in ESTABLISHED state when server call accept, remove from queue 12
7 Listening Socket Connection Queues What value to choose for backlog? old applications used 5, now inadequate instead of fixed value, can be set by env variable don t set backlog to 0 If queue is full and SYN arrives server ignores, doesn t send RST char* ptr; if ( (ptr = getenv("listenq"))!= NULL) backlog = atoi (ptr); client will retransmit, hopefully finding room when is RST sent? 13 accept Function Rt Return the next connection from the front of the completed ltdconnection queue #include <sys/socket.h> int accept (int sockfd, struct sockaddr *cliaddr, socklen_t *addrlen); Returns: non-negative descriptor if OK, -1 on error Called by TCP server to return next connection If connection queue empty, sleep (blocking) cliaddr used to return client protocol address addrlen is value result argument passed as sizeof(cliaddr), returns actual length 14
8 accept Function On success, accept returns socket descriptor new, created by kernel (TCP connection w/ client) called connected socket (one for each connection) different from listening socket (one per process) If we don t want client address pass cliaddr and addrlen as null pointers (NULL) 15 close Function Close socket and terminate TCP connection #include <unistd.h> int close (int sockfd); Returns: 0 if OK, -1 on error Normal Unix close function Mark socket as closed, returns immediately sockfd can no longer be used for read/write TCP will attempt to send unsent queued data After this, normal TCP connection termination ti 16
9 Example 1 Simple client/server Server code ex1_srv.c c Client code ex1_cli.c Look at execution result 17 Notes Have not checked for errors (serious flaw) No concurrent server No data transfer, just connect Hard coded port numbers Address structs better zero filled before using 18
10 Reading from TCP Socket #include <sys/socket.h> ssize_t recv(int socket, void *buffer, size_t length, int flags); Return: on success, number of bytes received, 0 if no data, -1 onerror #include <unistd.h> ssize_t read(int fildes, void *buf, size_t nbyte); Return: on success, number of bytes read, -1 on error 19 Reading from TCP Socket recv used with sockets, read both files, sockets When used with SOCK_STREAMSTREAM both will block until data is available (blocking socket) return whatever data is available (even 1 byte) not guarantee to return requested length not preserve message boundaries eg e.g. you send 1000 then 1000 you may receive 200, then 600 then 400 read socket ktsame as recv with flags set to 0 20
11 size_t and ssize_t int, long, short different among platforms size_t (size type) unsigned integer suitable for sizes e.g. malloc, memcpy, memset ssize_t (signed size type) same as size_ t but signed used in read/recv and write/send 21 Writing to TCP Socket #include <sys/socket.h> ssize_t send(int socket, void *buffer, size_t length, int flags); Return: on success, number of bytes sent, -1 onerror(errno set) #include <unistd.h> ssize_t write(int fildes, void *buf, size_t nbyte); Return: on success, number of written bytes, -1 on error 22
12 Writing to TCP Socket send used with sockets, write both files, sockets write socket same as send with flags set to 0 If socket has no space to hold all data will block until space if available (blocking socket) Successful return doesn t guarantee delivery only indicates no local error 23 Example 2 Add send and receive functionality Server code ex2_srv.c c Client code ex2_cli.c 24
13 Notes recv should check if there is more data Server closes after handling one client Server can t handle simultaneous connections We ll study these other issues, next 25 fork Function #include <unistd.h> pid_t fork(void); Returns: 0 in child, process ID of child in parent, -1 on error The only way to create new process in Unix Called once, returns twice once in parent process once in child process Child can get parent proces ID: call getppid() Parent can record each child pid from fork return 26
14 fork Function Descriptors (sockets) open by parent before calling fork are shared with child after fork Parent call accept then fork Connected socket shared between parent, child Child read/write connected socket Parent close connected socket 27 fork Uses Process make copy of itself one copy can handle one operation (conn socket) other copy handles another task (listen socket) typical for network servers Execute another program use exec functions process copy replace itself with new program used with shells, inted 28
15 Example fork1.c 29 fork1: Execution Result <main>this is main process (pid = 9079) before fork <main>i have x= 10, y = 10 <common>this part executed in all copies... <child>this a child process (pid = 9080) <child>my parent process (pid = 9079) <child>i have changed x to 15, y to 12 <child>sleeping... <common>this part executed in all copies... <parent>this the parent process (pid = 9079) <parent>i got child with (pid = 9080) <parent>i have x= 10, y = 10 <parent>waiting for child to finish... <child>waking up, finishing... <parent>child finished (returned 0), bye. 30
16 Concurrent Servers Iterative server: handle one client at a time Acceptable for simple daytime server Long service time: can t tie server to one client Concurrent server handle multiple clients at same time use fork, create child process for each client 31 client connect() server listen_fd client connect() server listen_fd conn_fd 32
17 client connect() server(parent) listen_fd conn_fd fork() server (child) listen_fd conn_fd client connect() server(parent) listen_fd server (child) conn_fd 33 pid_t pid; int listen_fd, conn_fd; Concurrent Server Outline listen_fd = socket(... ); /* fill in sockaddr_in{} with server's well-known port */ bind(listen_fd,... ); listen(listen_fd, LISTENQ); for ( ; ; ) { conn_fd = accept (listen_fd,... ); /* probably blocks */ if( (pid = fork()) == 0) { close(listen_fd); /* child closes listening socket */ doit(conn_fd); /* process the request */ close(conn_fd); /* done with this client */ exit(0); /* child terminates */ } } close(conn_ fd); /* parent closes connected socket */ 34
18 Concurrent Server Outline Connection established, accept returns Server call fork Child service client (conn _ fd) ) Parent wait for new connection (listen_fd) Parent close connected socket (conn_fd) why doesn t parent close send FIN to client? socket descriptors duplicated, reference count Child close listening socket (listen_fd) 35 getsockname Function #include <sys/socket.h> int getsockname(int sockfd, struct sockaddr *localaddr, socklen_t *addrlen); Return: 0 if OK, -1 onerror Return protocol address of local socket Usedby client after connect to get assigned IP, port after bind with port 0, get assigned port Used by server after bind, client connect, get local address must use connected, not listening socket for sockfd 36
19 getpeername Function #include <sys/socket.h> int getpeername(int sockfd, struct sockaddr *localaddr, socklen_t *addrlen); Return: 0 if OK, -1 onerror Return protocol address of remote socket Used by server execed by another process that uses accept inetd fork, then exec another server 37 Example: inetd Spawning Telnet Server inetd peer s address fork() inetd(child) peer s address conn_fd =accept( ) conn_fd exec() telnetd calls getpeername() using conn_fd to get peer s address conn_fd telnetd 38
20 Additional References Virtual Hosting p// p p / / / Why size_t matters no=1 read, recv, write and send specifications from Open Group org/onlinepubs/ /functions/recv fork, wait specifications from Open Group
21 File: /home/mostafa/netprog/sockets/ex1_cli.c Page 1 of 1 /* Client that connects and prints a message, no data transfer */ #include <stdio.h> /* printf */ #include <sys/socket.h> /* socket, connect, socklen_t */ #include <arpa/inet.h> /* sockaddr_in, inet_aton */ #define SRV_PORT 2000 /* port number of the server */ int main(int argc, char* argv[]) { int sock_fd; /* client need only one socket */ struct sockaddr_in srv_addr; /* server address structure */ } if (argc < 2) /* user entered no arguments */ { printf("usage: %s <IP address>\n", argv[0]); return -1; } /* create a client socket */ sock_fd = socket(af_inet, SOCK_STREAM, IPPROTO_TCP); srv_addr.sin_family = AF_INET; /* Internet address family */ /* convert command line argument to numeric IP */ inet_aton(argv[1], &srv_addr.sin_addr); srv_addr.sin_port = htons(srv_port); /* TCP server port*/ /* connect to server */ connect(sock_fd, (struct sockaddr*) &srv_addr, sizeof(srv_addr)); printf("connected to:%s:%d..\n",argv[1],srv_port); /* server should perform active close */ return 0;
22 File: /home/mostafa/netprog/sockets/ex1_srv.c Page 1 of 1 /* Server that accepts a single connection and prints a message */ #include <stdio.h> /* printf */ #include <sys/socket.h> /* socket, bind, listen, accept, socklen_t */ #include <arpa/inet.h> /* sockaddr_in, inet_aton */ #include <unistd.h> /* close */ #define SRV_PORT 2000 /* port number for the server */ #define LISTEN_ENQ 5 /* for listen backlog */ int main(int argc, char* argv[]) { int listen_fd, /* listening socket file descriptor*/ conn_fd; /* connected socket file descriptor*/ struct sockaddr_in srv_addr, /* server address structure */ cli_addr; /* client address structure */ socklen_t cli_len; /* to hold the length of cli_addr*/ srv_addr.sin_family = AF_INET; /* Internet address family */ /* listen on all interface (note the htonl) */ srv_addr.sin_addr.s_addr = htonl(inaddr_any); srv_addr.sin_port = htons(srv_port); /* specify TCP port */ /* attempt to open a socket (didn't check for error in this ex) */ listen_fd = socket(af_inet, SOCK_STREAM, IPPROTO_TCP); /* bind to created socket (serv_addr should contain all info) */ bind(listen_fd, (struct sockaddr*) &srv_addr, sizeof(srv_addr)); /* listen on the socket */ listen(listen_fd, LISTEN_ENQ); cli_len = sizeof(cli_addr); printf ("Waiting for a client to connect...\n"); /* block until some client connects */ conn_fd = accept( listen_fd, (struct sockaddr*) &cli_addr, &cli_len); /* display message when client connects */ printf("client connected from %s:%d\n", inet_ntoa(cli_addr.sin_addr), ntohs(cli_addr.sin_port)); close(conn_fd); /* close connected socket*/ close(listen_fd); /* close listening socket*/ } return 0;
23 File: /home/mostafa/netprog/sockets/ex2_cli.c Page 1 of 1 /* Client that connects, sends a constant message, recive response and quits */ #include <stdio.h> /* printf */ #include <sys/socket.h> /* socket, connect, socklen_t */ #include <arpa/inet.h> /* sockaddr_in, inet_aton */ #include <string.h> /* strlen */ #define SRV_PORT 2000 /* port number of the server */ #define MAX_RECV_BUF 256 int main(int argc, char* argv[]) { int sock_fd; /* client need only one socket */ struct sockaddr_in srv_addr; /* server address structure */ ssize_t sent_bytes, rcvd_bytes; char recv_str[max_recv_buf]; } if (argc < 2) { printf("usage: %s <IP address>\n", argv[0]); return -1; } /* create a client socket */ sock_fd = socket(af_inet, SOCK_STREAM, IPPROTO_TCP); srv_addr.sin_family = AF_INET; /* Internet address family */ /* convert command line argument to numeric IP */ inet_aton(argv[1], &srv_addr.sin_addr); srv_addr.sin_port = htons(srv_port); /* TCP server port*/ /* connect to server */ connect(sock_fd, (struct sockaddr*) &srv_addr, sizeof(srv_addr)); printf("connected to:%s:%d..\n",argv[1],srv_port); /* prepare data to be sent */ char* send_str = "This is a message from Client"; /* send the contents of send_str to server socket */ sent_bytes = send(sock_fd, send_str, strlen(send_str), 0); printf("client sent: %s (%d bytes)\n",send_str, sent_bytes); /* expect to receive one message from server */ rcvd_bytes = recv(sock_fd, recv_str, MAX_RECV_BUF, 0); printf("client received: %s (%d bytes)\n", recv_str, rcvd_bytes); /* server should perform active close */ return 0;
24 File: /home/mostafa/netprog/sockets/ex2_srv.c Page 1 of 2 /* Server that receives a message from a single clinet and sends it back */ #include <stdio.h> /* printf */ #include <sys/socket.h> /* socket, bind, listen, accept, socklen_t */ #include <arpa/inet.h> /* sockaddr_in, inet_aton */ #include <string.h> /* strlen */ #include <unistd.h> /* close */ #define SRV_PORT 2000 /* port number for the server */ #define LISTEN_ENQ 5 /* for listen backlog */ #define MAX_RECV_BUF 256 int main(int argc, char* argv[]) { int listen_fd, /* listening socket file descriptor*/ conn_fd; /* connected socket file descriptor*/ struct sockaddr_in srv_addr, /* server address structure */ cli_addr; /* client address structure */ socklen_t cli_len; /* to hold the length of cli_addr*/ ssize_t sent_bytes, rcvd_bytes; char recv_str[max_recv_buf]; srv_addr.sin_family = AF_INET; /* Internet address family */ /* listen on all interface (note the htonl) */ srv_addr.sin_addr.s_addr = htonl(inaddr_any); srv_addr.sin_port = htons(srv_port); /* specify TCP port */ /* attempt to open a socket (didn't check for error in this ex) */ listen_fd = socket(af_inet, SOCK_STREAM, IPPROTO_TCP); /* bind to created socket (serv_addr should contain all info) */ bind(listen_fd, (struct sockaddr*) &srv_addr, sizeof(srv_addr)); /* listen on the socket */ listen(listen_fd, LISTEN_ENQ); cli_len = sizeof(cli_addr); printf ("Waiting for a client to connect...\n"); /* block until some client connects */ conn_fd = accept( listen_fd, (struct sockaddr*) &cli_addr, &cli_len); /* display message when client connects */ printf("client connected from %s:%d\n", inet_ntoa(cli_addr.sin_addr), ntohs(cli_addr.sin_port)); /* prepare data to be sent */ char* send_str = "This is a message from Server"; /* expect to receive one message from server */ rcvd_bytes = recv(conn_fd, recv_str, MAX_RECV_BUF, 0); printf("server received: %s (%d bytes)\n", recv_str, rcvd_bytes); /* send the contents of send_str to connected socket */
25 File: /home/mostafa/netprog/sockets/ex2_srv.c Page 2 of 2 sent_bytes = send(conn_fd, send_str, strlen(send_str), 0); printf("server sent: %s (%d bytes)\n",send_str, sent_bytes); close(conn_fd); /* close connected socket*/ close(listen_fd); /* close listening socket*/ return 0; }
26 File: /home/mostafa/netprog/sockets/fork1.c Page 1 of 1 /* Simple fork demo */ #include <stdio.h> /* printf */ #include <unistd.h> /* fork */ #include <sys/wait.h> /* wait */ #include <stdlib.h> /* exit */ int main(void) { pid_t fork_pid; int x=10, y=10; /* to demonstrate that variables are copied to child */ int child_rv; /* child return value */ printf("<main>this is main process (pid = %d) before fork\n", getpid()); printf("<main>i have x= %d, y = %d\n", x, y); } fork_pid = fork(); if(fork_pid < 0) /* fork() failed */ { printf("fork() failed!\n"); return -1; } /* common part */ printf("<common>this part executed in all copies...\n"); /* Now begin the split */ if(fork_pid == 0) /* child part*/ { x += 5; y += 2; printf("<child>this a child process (pid = %d)\n", getpid()); printf("<child>my parent process (pid = %d)\n", getppid()); printf("<child>i have changed x to %d, y to %d\n", x, y); printf("<child>sleeping...\n"); sleep(5); /* let parent do something, to show parallel execution */ printf("<child>waking up, finishing...\n"); child_rv = 0; exit(child_rv); } else /* fork > 0 : parent part*/ { printf("<parent>this the parent process (pid = %d)\n", getpid()); printf("<parent>i got child with (pid = %d)\n", fork_pid ); printf("<parent>i have x= %d, y = %d\n", x, y); printf("<parent>waiting for child to finish...\n"); wait(&child_rv); printf("<parent>child finished (returned %d), bye.\n", child_rv); } return 0;
Unix Network Programming Chapter 4. Elementary TCP Sockets 광운대학교컴퓨터과학과 정보통신연구실 석사과정안중현
Unix Network Programming Chapter 4. Elementary TCP Sockets 광운대학교컴퓨터과학과 정보통신연구실 석사과정안중현 4.1 Introduction A Time line of the typical scenario that takes place between a TCP client and server. Describes the
More informationReview. Preview. Closing a TCP Connection. Closing a TCP Connection. Port Numbers 11/27/2017. Packet Exchange for TCP Connection
Review Preview Algorithms and Issues in Client Software Design Client Architecture Identifying the Location of a Parsing an Address Argument Looking Up a Domain Name Looking Up a Well-Known Port by Name
More informationLecture 3 Overview! Last Lecture! TCP/UDP and Sockets introduction!
Lecture 3 Overview! Last Lecture! TCP/UDP and Sockets introduction! This Lecture! Elementary TCP sockets! TCP Client-Server example! Source: Stevens book(chapters 4,5), Comer s book (Chapters 20, 21)!
More informationHyo-bong Son Computer Systems Laboratory Sungkyunkwan University
Sockets Hyo-bong Son (proshb@csl.skku.edu) Computer Systems Laboratory Sungkyunkwan University http://csl.skku.edu Client-Server Model Most network application is based on the client-server model: A server
More informationSockets. Jin-Soo Kim Computer Systems Laboratory Sungkyunkwan University
Sockets Jin-Soo Kim (jinsookim@skku.edu) Computer Systems Laboratory Sungkyunkwan University http://csl.skku.edu Internet Connections (1) Connection Clients and servers communicate by sending streams of
More informationPA #2 Reviews. set_name, get_name, del_name. Questions? Will be modified after PA #4 ~
Sockets Prof. Jin-Soo Kim( jinsookim@skku.edu) TA Dong-Yun Lee(dylee@csl.skku.edu) Computer Systems Laboratory Sungkyunkwan University http://csl.skku.edu PA #2 Reviews set_name, get_name, del_name Will
More informationOral. Total. Dated Sign (2) (5) (3) (2)
R N Oral Total Dated Sign (2) (5) (3) (2) Assignment Group- A_07 Problem Definition Write a program using TCP socket for wired network for following Say Hello to Each other ( For all students) File transfer
More informationSockets. Dong-kun Shin Embedded Software Laboratory Sungkyunkwan University Embedded Software Lab.
1 Sockets Dong-kun Shin Embedded Software Laboratory Sungkyunkwan University http://nyx.skku.ac.kr Echo Client (1) 2 #include #include #include #include
More informationElementary TCP Sockets
Elementary TCP Sockets Chapter 4 UNIX Network Programming Vol. 1, Second Ed. Stevens Distributed Computer Systems 1 socket interface Application 1 Application 2 socket interface user kernel user kernel
More informationIntroduction to Client-Server Model
Preview Introduction to Client-Server Model Motivation of Client-Server Model Terminologies and Concepts in Client-Server Model Connectionless vs. Connection-Oriented Stateless vs. Stateful Server Identify
More informationNETWORK PROGRAMMING. Instructor: Junaid Tariq, Lecturer, Department of Computer Science
NETWORK PROGRAMMING CSC- 341 25 Instructor: Junaid Tariq, Lecturer, Department of Computer Science 26 9 Lecture Sockets as means for inter-process communication (IPC) application layer Client Process Socket
More informationGroup-A Assignment No. 6
Group-A Assignment No. 6 R N Oral Total Dated Sign (2) (5) (3) (10) Title : File Transfer using TCP Socket Problem Definition: Use Python for Socket Programming to connect two or more PCs to share a text
More informationOutline. Distributed Computer Systems. Socket Basics An end-point for a IP network connection. Ports. Sockets and the OS. Transport Layer.
Outline Distributed Computer Systems Socket basics Socket details (TCP and UDP) Socket options Final notes Sockets Socket Basics An end-point for a IP network connection what the application layer plugs
More informationSTUDY OF SOCKET PROGRAMMING
STUDY OF SOCKET PROGRAMMING Sockets : An application programming interface(api) used for inter process communication. Sockets allow communication between two different processes on the same or different
More informationOutline. Operating Systems. Socket Basics An end-point for a IP network connection. Ports. Network Communication. Sockets and the OS
Outline Operating Systems Socket basics Socket details Socket options Final notes Project 3 Sockets Socket Basics An end-point for a IP network connection what the application layer plugs into programmer
More informationCS 3516: Computer Networks
Welcome to CS 3516: Prof. Yanhua Li Time: 9:00am 9:50am M, T, R, and F Location: AK219 Fall 2018 A-term 1 Some slides are originally from the course materials of the textbook Computer Networking: A Top
More informationCSE 333 Section 8 - Client-Side Networking
CSE 333 Section 8 - Client-Side Networking Welcome back to section! We re glad that you re here :) Networking Quick Review What are the following protocols used for? (bonus: what layer of the networking
More informationIntroduction to Socket Programming
UNIT II - ELEMENTARY TCP SOCKETS Introduction to Socket Programming Introduction to Sockets Socket address Structures Byte ordering functions address conversion functions Elementary TCP Sockets socket,
More informationOutline. Distributed Computing Systems. Socket Basics (1 of 2) Socket Basics (2 of 2) 3/28/2014
Outline Distributed Computing Systems Sockets Socket basics Socket details (TCP and UDP) Socket options Final notes Socket Basics (1 of 2) An end-point for an Internet network connection what application
More informationUNIT IV- SOCKETS Part A
1. Define sockets - SOCKETS Part A A socket is a construct to provide a communication between computers. It hides the underlying networking concepts and provides us with an interface to communicate between
More informationPiotr Mielecki Ph. D.
Piotr Mielecki Ph. D. http://mielecki.ristel.pl/ piotr.mielecki@pwr.edu.pl pmielecki@gmail.com Building blocks of client-server applications: Client, Server, Middleware. Simple client-server application:
More informationCSC209H Lecture 9. Dan Zingaro. March 11, 2015
CSC209H Lecture 9 Dan Zingaro March 11, 2015 Socket Programming (Kerrisk Ch 56, 57, 59) Pipes and signals are only useful for processes communicating on the same machine Sockets are a general interprocess
More informationTCP: Three-way handshake
Sockets in C 1 Sockets in C The slides by themselves will not be sufficient to learn how to write socket code. If you did not attend class, then you will want to review the relevant chapters in Kerrisk
More informationMSc Integrated Electronics Networks Assignment. Investigation of TCP/IP Sockets and Ports. Gavin Cameron
MSc Integrated Electronics Networks Assignment Investigation of TCP/IP Sockets and Ports Gavin Cameron Introduction TCP and IP (Transmission Control Protocol / Internet Protocol) are two protocols from
More informationTutorial on Socket Programming
Tutorial on Socket Programming Computer Networks - CSC 458 Department of Computer Science Hao Wang (Slides are mainly from Seyed Hossein Mortazavi, Monia Ghobadi, and Amin Tootoonchian, ) 1 Outline Client-server
More informationSocket Programming TCP UDP
Socket Programming TCP UDP Introduction Computer Network hosts, routers, communication channels Hosts run applications Routers forward information Packets: sequence of bytes contain control information
More informationCS321: Computer Networks Introduction to Application Layer
CS321: Computer Networks Introduction to Application Layer Dr. Manas Khatua Assistant Professor Dept. of CSE IIT Jodhpur E-mail: manaskhatua@iitj.ac.in Basic Application layer provides services to the
More informationCSE 124 Discussion Section Sockets Programming 10/10/17
CSE 124 Discussion Section Sockets Programming 10/10/17 Topics What s a socket? Creating a socket Connecting a socket Sending data Receiving data Resolving URLs to IPs Advanced socket options Live code
More informationSocket Programming. CSIS0234A Computer and Communication Networks. Socket Programming in C
1 CSIS0234A Computer and Communication Networks Socket Programming in C References Beej's Guide to Network Programming Official homepage: http://beej.us/guide/bgnet/ Local mirror http://www.cs.hku.hk/~c0234a/bgnet/
More informationCS321: Computer Networks Socket Programming
CS321: Computer Networks Socket Programming Dr. Manas Khatua Assistant Professor Dept. of CSE IIT Jodhpur E-mail: manaskhatua@iitj.ac.in Socket Programming It shows how the network application programs
More informationCS 640: Computer Networking
CS 640: Computer Networking Yu-Chi Lai Lecture 3 Network Programming Topics Client-server model Sockets interface Socket primitives Example code for echoclient and echoserver Debugging With GDB Programming
More informationUNIX Sockets. Developed for the Azera Group By: Joseph D. Fournier B.Sc.E.E., M.Sc.E.E.
UNIX Sockets Developed for the Azera Group By: Joseph D. Fournier B.Sc.E.E., M.Sc.E.E. Socket and Process Communication application layer User Process Socket transport layer (TCP/UDP) network layer (IP)
More informationProcesses communicating. Network Communication. Sockets. Addressing processes 4/15/2013
Processes communicating Network Communication Process: program running within a host. within same host, two processes communicate using inter-process communication (defined by OS). processes in different
More informationNetwork Socket Programming - 3 BUPT/QMUL
Network Socket Programming - 3 BUPT/QMUL 2018-04-02 Agenda Basic concepts in NP Introduction to IP & TCP/UDP Introduction to Sockets 2 Introduction to Sockets Reviews of some helpful points Sockets interface
More informationNetwork Socket Programming - 3 BUPT/QMUL
Network Socket Programming - 3 BUPT/QMUL 2017-3-27 Agenda Basic concepts in NP Introduction to IP & TCP/UDP Introduction to Sockets 2 Introduction to Sockets Reviews of some helpful points Sockets interface
More informationThe Berkeley Sockets API. Networked Systems Architecture 3 Lecture 4
The Berkeley Sockets API Networked Systems Architecture 3 Lecture 4 The Berkeley Sockets API Widely used low-level C networking API First introduced in 4.3BSD Unix Now available on most platforms: Linux,
More informationLecture 24. Thursday, November 19 CS 375 UNIX System Programming - Lecture 24 1
Lecture 24 Log into Linux. Copy directory /home/hwang/cs375/lecture24 Final project posted. Due during finals week. Reminder: No class next Tuesday (11/24) Questions? Thursday, November 19 CS 375 UNIX
More informationSockets. Dong-kun Shin Embedded Software Laboratory Sungkyunkwan University Embedded Software Lab.
1 Sockets Dong-kun Shin Embedded Software Laboratory Sungkyunkwan University http://nyx.skku.ac.kr Internet Connections (1) 2 Connection Clients and servers communicate by sending streams of bytes over
More informationNetworks. Practical Investigation of TCP/IP Ports and Sockets. Gavin Cameron
Networks Practical Investigation of TCP/IP Ports and Sockets Gavin Cameron MSc/PGD Networks and Data Communication May 9, 1999 TABLE OF CONTENTS TABLE OF CONTENTS.........................................................
More informationA Socket Example. Haris Andrianakis & Angelos Stavrou George Mason University
A Socket Example & George Mason University Everything is a file descriptor Most socket system calls operate on file descriptors Server - Quick view socket() bind() listen() accept() send(), recv() close()
More informationsottotitolo Socket Programming Milano, XX mese 20XX A.A. 2016/17 Federico Reghenzani
Titolo presentazione Piattaforme Software per la Rete sottotitolo Socket Programming Milano, XX mese 20XX A.A. 2016/17 Outline 1) Introduction to Sockets 2) UDP communication 3) TCP communication 4) RAW
More informationExperiential Learning Workshop on Basics of Socket Programming
Experiential Learning Workshop on Basics of Socket June 28, 2018 Dr. Ram P Rustagi Professor, CSE Dept KSIT, Bangalore rprustagi@ksit.edu.in Resources https://rprustagi.com/elnt/experiential- Learning.html
More informationUnix Network Programming
Introduction to Computer Networks Polly Huang EE NTU Unix Network Programming The socket struct and data handling System calls Based on Beej's Guide to Network Programming 1 The Unix Socket A file descriptor
More informationHybrid of client-server and P2P. Pure P2P Architecture. App-layer Protocols. Communicating Processes. Transport Service Requirements
Announcements CS 5565 Network Architecture and Protocols Lecture 5 Godmar Back Problem Set 1 due Feb 17 Project 1 handed out shortly 2 Layer The Layer Let s look at some s (in keeping with top-down) architectures:
More informationChristian Tschudin (basierend auf einem Foliensatz von C. Jelger und T. Meyer) Departement Mathematik und Informatik, Universität Basel
Internettechnologien (CS262) Socket Programming in C 4. März 2015 Christian Tschudin (basierend auf einem Foliensatz von C. Jelger und T. Meyer) Departement Mathematik und Informatik, Universität Basel
More informationLecture 7. Followup. Review. Communication Interface. Socket Communication. Client-Server Model. Socket Programming January 28, 2005
Followup symbolic link (soft link): pathname, can be across file systems, replacement of file will be active on all symbolic links, consumes at least an inode. hard link: pointers to an inode, only in
More informationNetwork Communication
Network Communication Processes communicating Process: program running within a host. q within same host, two processes communicate using inter- process communica6on (defined by OS). q processes in different
More informationSocket Programming for TCP and UDP
CSCI4430 Data Communication and Computer Networks Socket Programming for TCP and UDP ZHANG, Mi Jan. 19, 2017 Outline Socket Programming for TCP Introduction What is TCP What is socket TCP socket programming
More informationProgramming with TCP/IP. Ram Dantu
1 Programming with TCP/IP Ram Dantu 2 Client Server Computing Although the Internet provides a basic communication service, the protocol software cannot initiate contact with, or accept contact from, a
More informationNetwork Programming Worksheet 2. Simple TCP Clients and Servers on *nix with C.
Simple TCP Clients and Servers on *nix with C. Aims. This worksheet introduces a simple client and a simple server to experiment with a daytime service. It shows how telnet can be used to test the server.
More informationEEC-484/584 Computer Networks
EEC-484/584 Computer Networks Lecture 15 wenbing@ieee.org (Lecture nodes are based on materials supplied by Dr. Louise Moser at UCSB and Prentice-Hall) Outline 2 Review of last lecture The network layer
More informationChapter 6. The Transport Layer. Transport Layer 3-1
Chapter 6 The Transport Layer Transport Layer 3-1 Transport services and protocols provide logical communication between app processes running on different hosts transport protocols run in end systems
More informationPorts under 1024 are often considered special, and usually require special OS privileges to use.
1 2 Turns out that besides an IP address (used by the IP layer), there is another address that is used by TCP (stream sockets) and, coincidentally, by UDP (datagram sockets). It is the port number. It's
More informationNetwork Programming in C: The Berkeley Sockets API. Networked Systems 3 Laboratory Sessions
Network Programming in C: The Berkeley Sockets API Networked Systems 3 Laboratory Sessions The Berkeley Sockets API Widely used low-level C networking API First introduced in 4.3BSD Unix Now available
More informationNetworked Applications: Sockets. End System: Computer on the Net
Networked Applications: Sockets Topics Programmer s view of the Internet Sockets interface End System: Computer on the Net Internet Also known as a host 2 Page 1 Clients and Servers Client program Running
More informationSocket Programming. #In the name of Allah. Computer Engineering Department Sharif University of Technology CE443- Computer Networks
#In the name of Allah Computer Engineering Department Sharif University of Technology CE443- Computer Networks Socket Programming Acknowledgments: Lecture slides are from Computer networks course thought
More informationNetwork Programming in C. Networked Systems 3 Laboratory Sessions and Problem Sets
Network Programming in C Networked Systems 3 Laboratory Sessions and Problem Sets Lab Timetable, Aims, and Objectives Teaching Week Activity 14 Introduction 15 Warm-up exercise 16 17 Web client 18 19 20
More informationΕργαστήριο 9 I/O Multiplexing
Εργαστήριο 9 I/O Multiplexing Στοεργαστήριοθαμελετηθούν: Server High Level View I/O Multiplexing Solutions for Concurrency nonblocking I/O Use alarm and signal handler to interrupt slow system calls. Use
More informationCS307 Operating Systems Processes
CS307 Processes Fan Wu Department of Computer Science and Engineering Shanghai Jiao Tong University Spring 2018 Process Concept Process a program in execution An operating system executes a variety of
More informationProcesses. Process Concept. The Process. The Process (Cont.) Process Control Block (PCB) Process State
CS307 Process Concept Process a program in execution Processes An operating system executes a variety of programs: Batch system jobs Time-shared systems user programs or tasks All these activities are
More informationHow do we Communicate? Introduction to Unix Network Programming. What does Alice do? What does Bob do? Two simplest networking programs
Introduction to Unix Network Programming Reference: Stevens Unix Network Programming How do we Communicate? Send a mail from Alice to Bob Bob Alice in Champaign, Bob in Hollywood Example: US Postal Service
More informationProgramming Internet with Socket API. Hui Chen, Ph.D. Dept. of Engineering & Computer Science Virginia State University Petersburg, VA 23806
Programming Internet with Socket API Hui Chen, Ph.D. Dept. of Engineering & Computer Science Virginia State University Petersburg, VA 23806 10/19/2015 CSCI 445 - Fall 2015 1 Acknowledgements Some pictures
More informationUNIX Network Programming. Overview of Socket API Network Programming Basics
UNIX Network Programming Overview of Socket API Network Programming Basics 1 Client-Server Model Client Machine A Network Server Machine B Web browser and server FTP client and server Telnet client and
More informationCSE/EE 461 Lecture 14. Connections. Last Time. This Time. We began on the Transport layer. Focus How do we send information reliably?
CSE/EE 461 Lecture 14 Connections Last Time We began on the Transport layer Focus How do we send information reliably? Topics ARQ and sliding windows Application Presentation Session Transport Network
More informationECE 650 Systems Programming & Engineering. Spring 2018
ECE 650 Systems Programming & Engineering Spring 2018 Programming with Network Sockets Tyler Bletsch Duke University Slides are adapted from Brian Rogers (Duke) Sockets We ve looked at shared memory vs.
More informationCSE 333 SECTION 8. Sockets, Network Programming
CSE 333 SECTION 8 Sockets, Network Programming Overview Domain Name Service (DNS) Client side network programming steps and calls Server side network programming steps and calls dig and ncat tools Network
More informationLecture 5 Overview! Last Lecture! This Lecture! Next Lecture! I/O multiplexing! Source: Chapter 6 of Stevens book!
Lecture 5 Overview! Last Lecture! I/O multiplexing! Source: Chapter 6 of Stevens book! This Lecture! Socket options! Source: Chapter 7 of Stevens book! Elementary UDP sockets! Source: Chapter 8 of Stevens
More informationSockets 15H2. Inshik Song
Sockets 15H2 Inshik Song Internet CAU www server (www.cau.ac.kr) Your web browser (Internet Explorer/Safari) Sockets 2 How do we find the server? Every computer on the Internet has an Internet address.
More informationNetwork programming(i) Lenuta Alboaie
Network programming(i) Lenuta Alboaie adria@info.uaic.ro 2017 2018 Computer Network http://www.info.uaic.ro/~computernetworks 1 Content Client/server paradigm API for network programming BSD Socket Characteristics
More informationSocket Programming(2/2)
Socket Programming(2/2) 1 Outline 1. Introduction to Network Programming 2. Network Architecture Client/Server Model 3. TCP Socket Programming 4. UDP Socket Programming 5. IPv4/IPv6 Programming Migration
More informationInter-Process Communication. Disclaimer: some slides are adopted from the book authors slides with permission 1
Inter-Process Communication Disclaimer: some slides are adopted from the book authors slides with permission 1 Today Inter-Process Communication (IPC) What is it? What IPC mechanisms are available? 2 Inter-Process
More informationIntroduction to Socket Programming
Introduction to Socket Programming (Advanced Computer Networks) By Priyank Shah NET ID : pss160530 A Simple Question What are Sockets? Sockets are communication points on the same or different computers
More informationNetworked Applications: Sockets. Goals of Todayʼs Lecture. End System: Computer on the ʻNet. Client-server paradigm End systems Clients and servers
Networked Applications: Sockets CS 375: Computer Networks Spring 2009 Thomas Bressoud 1 Goals of Todayʼs Lecture Client-server paradigm End systems Clients and servers Sockets and Network Programming Socket
More informationNETWORK AND SYSTEM PROGRAMMING. I/O Multiplexing: select and poll function
NETWORK AND SYSTEM PROGRAMMING LAB 15 I/O Multiplexing: select and poll function 15.1 objectives What is a Concurrent server Use of Select System call Use of Poll System call 15.2 What is concurrent server?
More informationClient-server model The course that gives CMU its Zip! Network programming Nov 27, Using ports to identify services.
15-213 The course that gives CMU its Zip! Network programming Nov 27, 2001 Topics Client- model Sockets interface Echo and Client- model Every network application is based on the - model: Application is
More informationSemester 2, Computer Communication 352 Module 4
Page 4.1; CRICOS Number: 00301J MODULE 4 References: 1. Stevens, Fenner, Rudoff, UNIX Network Programming, vol. 1, Chapter 5. OBJECTIVE Provide detail description on TCP Client-Server Example. Discuss
More informationSystems software design NETWORK COMMUNICATIONS & RPC SYSTEMS
Systems software design NETWORK COMMUNICATIONS & RPC SYSTEMS outline network programming BSD/POSIX Socket API RPC systems object-oriented bridges CORBA DCOM RMI WebServices WSDL/SOAP XML-RPC REST network
More informationCLIENT-SIDE PROGRAMMING
CLIENT-SIDE PROGRAMMING George Porter Apr 11, 2018 ATTRIBUTION These slides are released under an Attribution-NonCommercial-ShareAlike 3.0 Unported (CC BY-NC-SA 3.0) Creative Commons license These slides
More informationClient Server Computing
Client Server Computing Although the Internet provides a basic communication service, the protocol software cannot initiate contact with, or accept contact from, a remote computer. Instead, two application
More informationCSMC 412. Computer Networks Prof. Ashok K Agrawala Ashok Agrawala Set 2. September 15 CMSC417 Set 2 1
CSMC 412 Computer Networks Prof. Ashok K Agrawala 2015 Ashok Agrawala Set 2 September 15 CMSC417 Set 2 1 Contents Client-server paradigm End systems Clients and servers Sockets Socket abstraction Socket
More informationCS4700/CS5700 Fundamentals of Computer Networking
CS4700/CS5700 Fundamentals of Computer Networking Prof. Alan Mislove Lecture 3: Crash course in socket programming September 10th, 2009 Project 0 Goal: Familiarize you with socket programming in C Implement
More informationLecture 2. Outline. Layering and Protocols. Network Architecture. Layering and Protocols. Layering and Protocols. Chapter 1 - Foundation
Lecture 2 Outline Wireshark Project 1 posted, due in a week Lab from a different textbook Work through the lab and answer questions at the end Chapter 1 - Foundation 1.1 Applications 1.2 Requirements 1.3
More informationTCP/IP Sockets in C: Practical Guide for Programmers. Computer Chat. Internet Protocol (IP) IP Address. Transport Protocols. Ports
TCP/IP Sockets in C: Practical Guide for Programmers Computer Chat! How do we make computers talk? Michael J. Donahoo Kenneth L. Calvert Morgan Kaufmann Publisher $14.95 Paperback! How are they interconnected?
More informationAnnouncement (1) Due date for PA3 is changed (~ next week) PA4 will also be started in the next class. Not submitted. Not scored
Announcement (1) Due date for PA3 is changed (~ next week) PA4 will also be started in the next class Not submitted Not scored 1 Concurrent Programming Prof. Jin-Soo Kim( jinsookim@skku.edu) TA Sanghoon
More informationCSE 333 SECTION 7. C++ Virtual Functions and Client-Side Network Programming
CSE 333 SECTION 7 C++ Virtual Functions and Client-Side Network Programming Overview Virtual functions summary and worksheet Domain Name Service (DNS) Client side network programming steps and calls dig
More informationSocket Programming. Dr. -Ing. Abdalkarim Awad. Informatik 7 Rechnernetze und Kommunikationssysteme
Socket Programming Dr. -Ing. Abdalkarim Awad Informatik 7 Rechnernetze und Kommunikationssysteme Before we start Can you find the ip address of an interface? Can you find the mac address of an interface?
More informationCSE 333 SECTION 7. Client-Side Network Programming
CSE 333 SECTION 7 Client-Side Network Programming Overview Domain Name Service (DNS) Client side network programming steps and calls dig and ncat tools Network programming for the client side Recall the
More informationSocket Programming. Sungkyunkwan University. Hyunseung Choo Copyright Networking Laboratory
Socket Programming Sungkyunkwan University Hyunseung Choo choo@skku.edu Copyright 2000-2019 Networking Laboratory Contents Goals Client-Server mechanism Introduction to socket Programming with socket on
More informationCSE 333 Lecture 16 - network programming intro
CSE 333 Lecture 16 - network programming intro Hal Perkins Department of Computer Science & Engineering University of Washington Today Network programming - dive into the Berkeley / POSIX sockets API -
More informationComputer Network Lab, SS Fachgebiet Technische Informatik, Joachim Zumbrägel. Overview. Sockets. Sockets in C.
Computer Network Lab 2016 Fachgebiet Technische Informatik, Joachim Zumbrägel Overview Sockets Sockets in C Sockets in Delphi 1 Inter process communication There are two possibilities when two processes
More informationCommunication. Sockets (Haviland Ch. 10)
Communication Sockets (Haviland Ch. 10) 1 Simple Web Request 5LFKDUG V+RPH3DJH &RXUVHV 5HVHDUFK 2 How do we find the server? Every computer on the Internet has an Internet address. Called an IP address
More informationComputer Networks Prof. Ashok K. Agrawala
CMSC417 Computer Networks Prof. Ashok K. Agrawala 2018Ashok Agrawala September 6, 2018 Fall 2018 Sept 6, 2018 1 Overview Client-server paradigm End systems Clients and servers Sockets Socket abstraction
More informationECE 435 Network Engineering Lecture 2
ECE 435 Network Engineering Lecture 2 Vince Weaver http://web.eece.maine.edu/~vweaver vincent.weaver@maine.edu 6 September 2018 Announcements Homework 1 will be posted. Will be on website, will announce
More informationECE 435 Network Engineering Lecture 2
ECE 435 Network Engineering Lecture 2 Vince Weaver http://web.eece.maine.edu/~vweaver vincent.weaver@maine.edu 31 August 2017 Announcements Homework 1 will be posted. Will be on website, will announce
More informationCS 43: Computer Networks. 05: Socket Programming September 12-14, 2018
CS 43: Computer Networks 05: Socket Programming September 12-14, 2018 Reading Quiz Lecture 5/6 - Slide 2 Socket Programming Adapted from: Donahoo, Michael J., and Kenneth L. Calvert. TCP/IP sockets in
More informationNetwork Programming November 3, 2008
15-213 Network Programming November 3, 2008 Topics Programmer s view of the Internet (review) Sockets interface Writing clients and servers class20.ppt A Client-Server Transaction Most network applications
More informationClient-side Networking
Client-side Networking CSE 333 Autumn 2018 Instructor: Hal Perkins Teaching Assistants: Tarkan Al-Kazily Renshu Gu Trais McGaha Harshita Neti Thai Pham Forrest Timour Soumya Vasisht Yifan Xu Administriia
More informationThe BSD UNIX Socket Interface (CS 640 Lecture) Assignment 1. Interprocess Communication (IPC) Work Individually (no groups)
The BSD UNIX Socket Interface (CS 640 Lecture) Assignment 1 Work Individually (no groups) Due Date: in class, Monday, September 19 Robert T Olsen olsen@cswiscedu 7390CS Office Hours: 3-5T, 11-12F - exception
More informationGood Luck! Marking Guide. APRIL 2014 Final Exam CSC 209H5S
APRIL 2014 Final Exam CSC 209H5S Last Name: Student #: First Name: Signature: UNIVERSITY OF TORONTO MISSISSAUGA APRIL 2014 FINAL EXAMINATION CSC209H5S System Programming Daniel Zingaro Duration - 3 hours
More informationA Client-Server Exchange
Socket programming A Client-Server Exchange A server process and one or more client processes Server manages some resource. Server provides service by manipulating resource for clients. 1. Client sends
More information