TCP/IP Sockets in C: Practical Guide for Programmers

Slides:



Advertisements
Similar presentations
Network Programming Week #1 J.P. Yoo
Advertisements

Socket Programming 101 Vivek Ramachandran.
Transmission Control Protocol (TCP). TCP: Overview RFCs: 793, 1122, 1323, 2018, 2581 r reliable, in-order byte steam: m no “message boundaries” r send.
Elementary TCP Sockets Computer Networks Computer Networks Term B10 UNIX Network Programming Vol. 1, Second Ed. Stevens Chapter 4.
Networks: TCP/IP Socket Calls1 Elementary TCP Sockets Chapter 4 UNIX Network Programming Vol. 1, Second Ed. Stevens.
Quick Overview. 2 ISO/OSI Reference Model Application Application Presentation Presentation Session Session Transport Transport Network Network Data Link.
Socket Programming: a Primer Socket to me!. Feb. 23, 2001EE122, UCB2 Why does one need sockets? application network protocol sockets network.
1 Socket Interfaces Professor Jinhua Guo CIS527 Fall 2003.
Tutorial 8 Socket Programming
UDP: User Datagram Protocol. UDP: User Datagram Protocol [RFC 768] r “bare bones”, “best effort” transport protocol r connectionless: m no handshaking.
Socket Addresses. Domains Internet domains –familiar with these Unix domains –for processes communicating on the same hosts –not sure of widespread use.
TCP/IP Sockets in C: Practical Guide for Programmers Michael J. Donahoo Kenneth L. Calvert.
ISP – 9 th Recitation Socket programming – Client side.
1 Tutorial on Socket Programming Computer Networks - CSC 458 Department of Computer Science Yukun Zhu (Slides are mainly from Monia Ghobadi, and Amin Tootoonchian,
TCP/IP Sockets in Java: Practical Guide for Programmers Kenneth L. Calvert Michael J. Donahoo.
Basic Socket Programming TCP/IP overview. TCP interface Reference: –UNIX Network Programming, by Richard Stevens. –UNIX man page.
Ashutosh Shukla Lecture 3 Network Programming CS 640: Computer Networking.
TCP Socket Programming. r An abstract interface provided to the application programmer  File descriptor, allows apps to read/write to the network r Allows.
Socket Programming References: redKlyde ’ s tutorial set Winsock2 for games (gamedev.net)
Operating Systems Chapter 9 Distributed Communication.
Sirak Kaewjamnong Computer Network Systems
Server Sockets: A server socket listens on a given port Many different clients may be connecting to that port Ideally, you would like a separate file descriptor.
1 CS: 4244 Internet Programming Sockets Programming Dr. Eli Tilevich January 29, 2007.
 Wind River Systems, Inc Chapter - 13 Network Programming.
1 Writing Network Applications using the TCP/IP Protocol Stack: Socket Programming.
The Pocket Guide to TCP/IP Sockets: C Version Michael J. Donahoo Kenneth L. Calvert.
Outline Socket programming with Windows OSSocket programming with Windows OS C++ UDPSocket classC++ UDPSocket class Socket programming with Windows OSSocket.
Networking Tutorial Special Interest Group for Software Engineering Luke Rajlich.
TELE202 Lecture 15 Socket programming 1 Lecturer Dr Z. Huang Overview ¥Last Lecture »TCP/UDP (2) »Source: chapter 17 ¥This Lecture »Socket programming.
University of Calgary – CPSC 441.  A socket is an interface between the application and the network (the lower levels of the protocol stack)  The application.
Elementary TCP Sockets UNIX Network Programming Vol. 1, Second Ed. Stevens Chapter 4.
UNIX Sockets COS 461 Precept 1. Socket and Process Communication The interface that the OS provides to its networking subsystem application layer transport.
Introduction to Socket
Socket Programming Tutorial Department of Computer Science Southern Illinois University Edwardsville Fall, 2015 Dr. Hiroshi Fujinoki
Socket Programming Lab 1 1CS Computer Networks.
1 Sockets Programming Socket to me!. 2 Network Application Programming Interface (API) The services provided by the operating system that provide the.
Project 2: Socket Programming. Overview Sockets Working with sockets Client-Server example Project 1 Hints.
Socket Programming Introduction. Socket Definition A network socket is one endpoint in a two-way communication flow between two programs running over.
2: Application Layer1 Chapter 2: Application layer r 2.1 Principles of network applications r 2.2 Web and HTTP r 2.3 FTP r 2.4 Electronic Mail  SMTP,
CSCI 330 UNIX and Network Programming Unit XIV: User Datagram Protocol.
1 Spring Semester 2008, Dept. of Computer Science, Technion Internet Networking recitation #7 Socket Programming.
Lecture 15 Socket Programming CPE 401 / 601 Computer Network Systems slides are modified from Dave Hollinger.
Lecture 3 TCP and UDP Sockets CPE 401 / 601 Computer Network Systems slides are modified from Dave Hollinger.
Berkeley Sockets. Client-server model Sockets interface: Address structure, byte ordering, port no Socket primitives: socket, bind,listen… Example code.
Socket Programming in C CS587x Lecture 3 Department of Computer Science Iowa State University.
Socket Programming(1/2). Outline  1. Introduction to Network Programming  2. Network Architecture – Client/Server Model  3. TCP Socket Programming.
Jim Fawcett CSE 681 – Software Modeling & Analysis Fall 2002
UNIX Sockets COS 461 Precept 1.
Sockets TCP/IP Sockets in C: Practical Guide for Programmers (we are covering all chapters of Part 1; Part 2 is a good sockets API reference) Sockets.
Socket Programming (Cont.)
Jim Fawcett CSE 687-OnLine – Object Oriented Design Summer 2017
The Pocket Guide to TCP/IP Sockets: C Version
Jim Fawcett CSE 775 – Distributed Objects Spring 2007
TCP/IP Sockets in C: Practical Guide for Programmers
Network Programming with Sockets
Socket Interface 1 Introduction 11 Socket address formats 2 API 12 13
Tutorial on Socket Programming
Transport layer API: Socket Programming
Socket Programming in C
TCP/IP Sockets in C: Practical Guide for Programmers
Socket 程式設計.
Tutorial on Socket Programming
Socket Programming(1/2)
Sockets Programming Socket to me!.
Sockets Programming Socket to me!.
Internet Networking recitation #8
TCP/IP Sockets in C: Practical Guide for Programmers
Outline Communications in Distributed Systems Socket Programming
TCP/IP Sockets in Java: Practical Guide for Programmers
Jim Fawcett CSE 681 – Software Modeling & Analysis Summer 2003
Presentation transcript:

TCP/IP Sockets in C: Practical Guide for Programmers Michael J. Donahoo Kenneth L. Calvert

Computer Chat How do we make computers talk? How are they interconnected? Internet Protocol (IP)

Internet Protocol (IP) Datagram (packet) protocol Best-effort service Loss Reordering Duplication Delay Host-to-host delivery (not application-to-application) Host-to-host delivery means that IP takes packets from one host to another host. Datagram service analogy to the post office.

IP Address 32-bit identifier Dotted-quad: 192.118.56.25 www.mkp.com -> 167.208.101.28 Identifies a host interface (not a host) We need some way to identify computers on an internetwork The “dotted-quad” representation is just a more readable version of a real 32-bit number 192.18.22.13 209.134.16.123

Transport Protocols Best-effort not sufficient! Add services on top of IP User Datagram Protocol (UDP) Data checksum Best-effort Transmission Control Protocol (TCP) Reliable byte-stream delivery Flow and congestion control

Ports Identifying the ultimate destination IP addresses identify hosts Host has many applications Ports (16-bit identifier) Ports are analogous to phone extensions from main switchboard Application WWW E-mail Telnet Port 80 25 23 192.18.22.13

Socket How does one speak TCP/IP? Sockets provides interface to TCP/IP Generic interface for many protocols

Sockets Identified by protocol and local/remote address/port Applications may refer to many sockets Sockets accessed by many applications

TCP/IP Sockets mySock = socket(family, type, protocol); TCP/IP-specific sockets Socket reference File (socket) descriptor in UNIX Socket handle in WinSock Family Type Protocol TCP PF_INET SOCK_STREAM IPPROTO_TCP UDP SOCK_DGRAM IPPROTO_UDP Socket descriptors can be used just like file descriptors in UNIX. In WinSock, Socket handles and file handles are not the same thing.

Generic IP Specific struct sockaddr { unsigned short sa_family; /* Address family (e.g., AF_INET) */ char sa_data[14]; /* Protocol-specific address information */ }; struct sockaddr_in unsigned short sin_family; /* Internet protocol (AF_INET) */ unsigned short sin_port; /* Port (16-bits) */ struct in_addr sin_addr; /* Internet address (32-bits) */ char sin_zero[8]; /* Not used */ struct in_addr unsigned long s_addr; /* Internet address (32-bits) */ Generic IP Specific sockaddr Family Blob 2 bytes 2 bytes 4 bytes 8 bytes sockaddr_in Family Port Internet address Not used

Clients and Servers Client: Initiates the connection Server: Passively waits to respond Server: Jane Client: Bob “Hi, Bob. I’m Jane” “Hi. I’m Bob.” “Nice to meet you, Jane.”

TCP Client/Server Interaction Server starts by getting ready to receive client connections… Server Create a TCP socket Assign a port to socket Set socket to listen Repeatedly: Accept new connection Communicate Close the connection Client Create a TCP socket Establish connection Communicate Close the connection Students should follow along with source code in the book

TCP Client/Server Interaction /* Create socket for incoming connections */ if ((servSock = socket(PF_INET, SOCK_STREAM, IPPROTO_TCP)) < 0) DieWithError("socket() failed"); Server Create a TCP socket Bind socket to a port Set socket to listen Repeatedly: Accept new connection Communicate Close the connection Client Create a TCP socket Establish connection Communicate Close the connection Students should follow along with source code in the book

TCP Client/Server Interaction echoServAddr.sin_family = AF_INET; /* Internet address family */ echoServAddr.sin_addr.s_addr = htonl(INADDR_ANY);/* Any incoming interface */ echoServAddr.sin_port = htons(echoServPort); /* Local port */ if (bind(servSock, (struct sockaddr *) &echoServAddr, sizeof(echoServAddr)) < 0) DieWithError("bind() failed"); Server Create a TCP socket Bind socket to a port Set socket to listen Repeatedly: Accept new connection Communicate Close the connection Client Create a TCP socket Establish connection Communicate Close the connection Students should follow along with source code in the book

TCP Client/Server Interaction /* Mark the socket so it will listen for incoming connections */ if (listen(servSock, MAXPENDING) < 0) DieWithError("listen() failed"); Server Create a TCP socket Bind socket to a port Set socket to listen Repeatedly: Accept new connection Communicate Close the connection Client Create a TCP socket Establish connection Communicate Close the connection Students should follow along with source code in the book

TCP Client/Server Interaction for (;;) /* Run forever */ { clntLen = sizeof(echoClntAddr); if ((clntSock=accept(servSock,(struct sockaddr *)&echoClntAddr,&clntLen)) < 0) DieWithError("accept() failed"); Server Create a TCP socket Bind socket to a port Set socket to listen Repeatedly: Accept new connection Communicate Close the connection Client Create a TCP socket Establish connection Communicate Close the connection Students should follow along with source code in the book

TCP Client/Server Interaction Server is now blocked waiting for connection from a client Later, a client decides to talk to the server… Server Create a TCP socket Bind socket to a port Set socket to listen Repeatedly: Accept new connection Communicate Close the connection Client Create a TCP socket Establish connection Communicate Close the connection Students should follow along with source code in the book

TCP Client/Server Interaction /* Create a reliable, stream socket using TCP */ if ((sock = socket(PF_INET, SOCK_STREAM, IPPROTO_TCP)) < 0) DieWithError("socket() failed"); Server Create a TCP socket Bind socket to a port Set socket to listen Repeatedly: Accept new connection Communicate Close the connection Client Create a TCP socket Establish connection Communicate Close the connection Students should follow along with source code in the book

TCP Client/Server Interaction echoServAddr.sin_family = AF_INET; /* Internet address family */ echoServAddr.sin_addr.s_addr = inet_addr(servIP); /* Server IP address */ echoServAddr.sin_port = htons(echoServPort); /* Server port */ if (connect(sock, (struct sockaddr *) &echoServAddr, sizeof(echoServAddr)) < 0) DieWithError("connect() failed"); Server Create a TCP socket Bind socket to a port Set socket to listen Repeatedly: Accept new connection Communicate Close the connection Client Create a TCP socket Establish connection Communicate Close the connection Students should follow along with source code in the book A new socket is created on the server that is connected to the client socket

TCP Client/Server Interaction if ((clntSock=accept(servSock,(struct sockaddr *)&echoClntAddr,&clntLen)) < 0) DieWithError("accept() failed"); Server Create a TCP socket Bind socket to a port Set socket to listen Repeatedly: Accept new connection Communicate Close the connection Client Create a TCP socket Establish connection Communicate Close the connection Students should follow along with source code in the book

TCP Client/Server Interaction echoStringLen = strlen(echoString); /* Determine input length */ /* Send the string to the server */ if (send(sock, echoString, echoStringLen, 0) != echoStringLen) DieWithError("send() sent a different number of bytes than expected"); Server Create a TCP socket Bind socket to a port Set socket to listen Repeatedly: Accept new connection Communicate Close the connection Client Create a TCP socket Establish connection Communicate Close the connection Students should follow along with source code in the book

TCP Client/Server Interaction /* Receive message from client */ if ((recvMsgSize = recv(clntSocket, echoBuffer, RCVBUFSIZE, 0)) < 0) DieWithError("recv() failed"); Server Create a TCP socket Bind socket to a port Set socket to listen Repeatedly: Accept new connection Communicate Close the connection Client Create a TCP socket Establish connection Communicate Close the connection Students should follow along with source code in the book

TCP Client/Server Interaction close(sock); close(clntSocket) Server Create a TCP socket Bind socket to a port Set socket to listen Repeatedly: Accept new connection Communicate Close the connection Client Create a TCP socket Establish connection Communicate Close the connection Students should follow along with source code in the book Note that server closes connection socket, not listening socket

TCP Tidbits Client Server Client must know the server’s address and port Server only needs to know its own port No correlation between send() and recv() Client send(“Hello Bob”) recv() -> “Hi Jane” Server recv() -> “Hello ” recv() -> “Bob” send(“Hi ”) send(“Jane”) The client must know the server address and port The server discovers the client’s address and port at connection

Closing a Connection Echo Client Echo Server close() used to delimit communication Analogous to EOF Echo Client send(string) while (not received entire string) recv(buffer) print(buffer) close(socket) Echo Server recv(buffer) while(client has not closed connection) send(buffer) close(client socket) In echo application, how does server know when client is done considering it doesn’t know echo string length? Role of closer can (and is in HTTP) be reversed

Constructing Messages …beyond simple strings

TCP/IP Byte Transport TCP/IP protocols transports bytes Application protocol provides semantics Application Application byte stream byte stream Here are some bytes. I don’t know what they mean. I’ll pass these to the app. It knows what to do. TCP/IP TCP/IP TCP does not examine or modify the bytes

Application Protocol Encode information in bytes Sender and receiver must agree on semantics Data encoding Primitive types: strings, integers, and etc. Composed types: message with fields

Primitive Types String Character encoding: ASCII, Unicode, UTF Delimit: length vs. termination character 0 77 0 111 0 109 0 10 M o m \n 3 77 111 109

Primitive Types Integer Strings of character encoded decimal digits Advantage: 1. Human readable 2. Arbitrary size Disadvantage: 1. Inefficient 2. Arithmetic manipulation 49 55 57 57 56 55 48 10 ‘1’ ‘7’ ‘9’ ‘9’ ‘8’ ‘7’ ‘0’ \n Inefficient: Need only 4 bits to represent values 0-9 Arithmetic manipulation: Cannot add and subtract strings. Must convert to primitive type. If you must convert then you lose arbitrary size advantage.

Primitive Types Integer Native representation Network byte order (Big-Endian) Use for multi-byte, binary data exchange htonl(), htons(), ntohl(), ntohs() Little-Endian 0 0 92 246 4-byte two’s-complement integer 23,798 Big-Endian If the byte order is already big-endian, then the [hn]to[ns][sl]( ) functions are no-ops. 246 92 0 0

Message Composition Message composed of fields Fixed-length fields Variable-length fields integer short M i k e 1 2 \n

“Beware the bytes of padding” -- Julius Caesar, Shakespeare Architecture alignment restrictions Compiler pads structs to accommodate Problem: Alignment restrictions vary Solution: 1) Rearrange struct members 2) Serialize struct by-member struct tst { short x; int y; short z; }; x [pad] y z [pad] Rip off of quote from Shakesphere’s Julius Caesar “Beware the Ides of March” spoken by a soothsayer. Caesar replies, “He is a dreamer, let us leave him. Pass.” The warning turned out to be a harbinger of Caesar’s assassination by his most trusted aids.