1 Networking Programming. 2 Outline Connection & Socket Sockets Interface –Functions –Echo Client and Server Suggested Reading: –11.4.

Slides:



Advertisements
Similar presentations
Introduction to Sockets Jan Why do we need sockets? Provides an abstraction for interprocess communication.
Advertisements

Network Programming Topics Peeking at Internet traffic Programmer’s view of the Internet (review) Sockets interface Writing clients and servers Understanding.
Chris Riesbeck, Fall 2007 Network Programming Topics –Sockets interface –Writing clients and servers.
Socket Programming Application Programming Interface.
Sockets Programming CS144 Review Session 1 April 4, 2008 Ben Nham.
Carnegie Mellon 1 Network Programming : Introduction to Computer Systems 20 th Lecture, Nov. 2, 2010 Instructors: Randy Bryant and Dave O’Hallaron.
Network Programming Topics Sockets interface Writing clients and servers CS 105 “Tour of the Black Holes of Computing!”
Quick Overview. 2 ISO/OSI Reference Model Application Application Presentation Presentation Session Session Transport Transport Network Network Data Link.
Networks and Network Programming May 24, 2006 Topics Client-server programming model Networks A programmer’s view of the Internet Sockets interface Writing.
– 1 – CS213, S’08 Network Programming June 4, 2008 Topics Sockets interface Writing clients and servers.
תקשורת באינטרנט Tutorial 8. 2 n Socket programming u What is socket ? u Sockets architecture u Types of Sockets u The Socket system calls u Data Transfer.
Tutorial 8 Socket Programming
Network Programming November 19, 2007 Topics Peeking at Internet traffic Programmer’s view of the Internet (review) Sockets interface Writing clients and.
Network Programming Nov. 6, 2008 Topics Peeking at Internet traffic Programmer’s view of the Internet (review) Sockets interface Writing clients and servers.
Network Programming Nov 21, 2002 Topics Programmer’s view of the Internet (review) Sockets interface Writing clients and servers class26.ppt “The.
CS 311 – Lecture 18 Outline IPC via Sockets – Server side socket() bind() accept() listen() – Client side connect() Lecture 181CS Operating Systems.
Internetworking II: Network programming April 20, 2000 Topics client/server model Berkeley sockets –TCP client and server examples –UDP client and server.
UNIX Sockets COS 461 Precept 1. Clients and Servers Client program – Running on end host – Requests service – E.g., Web browser Server program – Running.
1 Tutorial on Socket Programming Computer Networks - CSC 458 Department of Computer Science Yukun Zhu (Slides are mainly from Monia Ghobadi, and Amin Tootoonchian,
Networking S04, Recitation, Section A
1. Networks and the Internet 2. Network programming.
Recitation 12: 11/25/02 Outline Socket Interface –Echo Client/Server Http Protocol Evaluation Annie Luo Office Hours: Thursday.
TCP/IP Protocol Stack IP Device Drivers TCPUDP Application Sockets (Gate to network) TCP: –Establish connection –Maintain connection during the communication.
CS- 492 : Distributed system & Parallel Processing Lecture 2: 9/4/1435 Sun  networking.  internetworking essentials.  overview of network programming.
University of Amsterdam Computer Systems – Iterative server Arnoud Visser 1 Computer Systems Iterative server.
Computer Systems II CSC 2405 Network Programming.
INTERNET L4: Internet. Last Lecture Re-cap: IP Internet  Based on the TCP/IP protocol family  IP (Internet protocol) : Provides basic naming scheme.
Network Programming Topics Programmer’s view of the Internet Sockets interface Writing clients and servers CS 105 “Tour of the Black Holes of Computing!”
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.
The Application Layer Application Services (Telnet, FTP, , WWW) Reliable Stream Transport (TCP) Connectionless Packet Delivery Service (IP) Unreliable.
 Wind River Systems, Inc Chapter - 13 Network Programming.
Recitation 12 (Nov. 29) Outline Socket programming Lab 7: part 1 Reminder Lab 7: Due next Thursday Minglong Shao Office hours: Thursdays.
Carnegie Mellon 1 Network Programming / : Introduction to Computer Systems 21 st Lecture, Nov. 7, 2013 Instructors: Randy Bryant, Dave O’Hallaron,
TELE202 Lecture 15 Socket programming 1 Lecturer Dr Z. Huang Overview ¥Last Lecture »TCP/UDP (2) »Source: chapter 17 ¥This Lecture »Socket programming.
Network programming Nov 16, 2000 Topics Client-server model Sockets interface Echo client and server class24.ppt “The course that gives CMU its.
Carnegie Mellon Introduction to Computer Systems /18-243, spring th Lecture, Nov. 5 th Instructors: Roger Dannenberg and Greg Ganger.
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.
Sockets Socket = abstraction of the port concept: –Application programs request that the operating system create a socket when one is needed –O.S. returns.
Carnegie Mellon 1 Network Programming / : Introduction to Computer Systems 21 st Lecture, Nov. 8, 2012 Instructors: Dave O’Hallaron, Greg.
Network Programming Topics Sockets interface Writing clients and servers CS 105 “Tour of the Black Holes of Computing!”
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,
– 1 – , Spring 2006 Network Programming Introduction Jan. 25, 2006 Topics Programmer's view of the Internet Sockets interface Writing clients and.
Intro to Socket Programming CS 360. Page 2 CS 360, WSU Vancouver Two views: Server vs. Client Servers LISTEN for a connection and respond when one is.
Carnegie Mellon Introduction to Computer Systems /18-243, spring rd Lecture, Apr. 14 th Instructors: Gregory Kesden and Markus Püschel.
CSCI 330 UNIX and Network Programming Unit XIV: User Datagram Protocol.
回到第一頁 Client/sever model n Client asks (request) – server provides (response) n Typically: single server - multiple clients n The server does not need.
1 Networking Programming (I). A Client-Server Transaction Client process Server process 1. Client sends request 2. Server handles request 3. Server sends.
1 Spring Semester 2008, Dept. of Computer Science, Technion Internet Networking recitation #7 Socket Programming.
Carnegie Mellon 1 Network Programming / : Introduction to Computer Systems 21 st Lecture, April 2, 2015 Instructors: Franz Franchetti, Seth.
– 1 – , Fall 2003 Network Programming Introduction Sept. 1, 2004 Topics Programmer's view of the Internet Sockets interface Writing clients and servers.
Extending echo server HTTP Broken pipe error Feedback and evaluation
Instructors: Anthony Rowe, Seth Goldstein and Greg Kesden
Network Programming /18-243: Introduction to Computer Systems
CS 105 “Tour of the Black Holes of Computing!”
Network Programming April 11, 2008
Internet Topics Client-server programming model Networks in general
Network programming Nov 27, 2001
Recitation 11 – 4/29/01 Outline Sockets Interface
Web Services Topics Proxies Sockets interface
Network Programming Chapter 12
Networking Programming
Network Programming: Part II CSCI 380: Operating Systems Lecture #13
Networking Programming
Network Programming: Part I CSCI 380: Operating Systems
Network Programming: Part II CSCI 380: Operating Systems
Network Programming November 3, 2008
Internet Networking recitation #8
Presentation transcript:

1 Networking Programming

2 Outline Connection & Socket Sockets Interface –Functions –Echo Client and Server Suggested Reading: –11.4

3 Internet connections Clients and servers communicate by sending streams of bytes of connections. –point-to-point, full-duplex, and reliable A connection is uniquely identified by the socket addresses of its endpoints (socket pair) –(cliaddr:cliport, servaddr:servport)

4 Internet connections A port is a 16-bit integer that identifies a process: –Ephemeral port : assigned automatically on client when client makes a connection request –Well-known port : associated with some service provided by a server (e.g., port 80 is associated with Web servers)

Putting it all Together: Anatomy of an Internet Connection Connection socket pair ( :51213, :80) Server (port 80) Client Client socket address :51213 Server socket address :80 Client host address Server host address is an ephemeral port allocated by the kernel 80 is a well-known port associated with Web servers 5

Using Ports to Identify Services Web server (port 80) Client host Server host Echo server (port 7) Service request for :80 (i.e., the Web server) Web server (port 80) Echo server (port 7) Service request for :7 (i.e., the echo server) Kernel Client 6

7 Clients How does the client find the server? –The address of the server process has two parts: IPaddress:port The port is positive integer associated with a service (and thus a server process) on that machine. –port 7: echo server –port 23: telnet server –port 25: mail server –port 80: web server

8 Servers are long-running processes (daemons) –Created at boot-time (typically) by the init process (process 1) –Run continuously until the machine is turned off. A machine that runs a server process is also often referred to as a “server”. Servers

9 Each server waits for requests to arrive on a well-known port associated with a particular service –Port 7: echo server –Port 23: telnet server –Port 25: mail server –Port 80: HTTP server Servers

Server Examples Web server (port 80) –Resource: files/compute cycles (CGI programs) –Service: retrieves files and runs CGI programs on behalf of the client FTP server (20, 21) –Resource: files –Service: stores and retrieve files Telnet server (23) –Resource: terminal –Service: proxies a terminal on the server machine Mail server (25) –Resource: “spool” file –Service: stores mail messages in spool file See /etc/services for a comprehensive list of the port mappings on a Linux machine 10

11 Created in the early 80’s as part of the original Berkeley distribution of Unix that contained an early version of the Internet protocols Provides a user-level interface to the network Underlying basis for all Internet applications Based on client/server programming model Berkeley Sockets Interface

12 To the kernel, a socket is an endpoint of communication To an application, a socket is a descriptor that lets an application read/write from/to the network. Remember: All Unix I/O devices, including networks, are modeled as files What is a socket?

13 Clients and servers communicate with each other by reading from and writing to socket descriptors –Using regular Unix read and write I/O functions What is a socket? Client clientfd Server serverfd

14 The main difference between file I/O and socket I/O is how the application “opens” the socket descriptors What is a socket?

15 Overview of the Sockets Interface Client / Server Session socket bind listen rio_readlineb rio_writenrio_readlineb rio_writen Connection request rio_readlineb close EOF Await connection request from next client open_listenfd open_clientfd acceptconnect ClientServer

16 Internet-style sockets are characterized by –a 32-bit IP address and a port Defined in /usr/include/netinet/in.h /* Internet address */ struct in_addr { unsigned int s_addr; /* 32-bit IP address */ }; Key data structures

17 Defined in /usr/include/netdb.h /* Domain Name Service (DNS) host entry */ struct hostent { char *h_name; /* official name of host */ char **h_aliases; /* alias list */ int h_addrtype; /* host address type */ int h_length; /* length of address */ char **h_addr_list;/*list of addresses */ } Key data structures

Socket Address Structures Generic socket address: –For address arguments to connect, bind, and accept –Necessary only because C did not have generic ( void * ) pointers when the sockets interface was designed struct sockaddr { unsigned short sa_family; /* protocol family */ char sa_data[14]; /* address data. */ }; sa_family Family Specific 18

Socket Address Structures Internet-specific socket address: –Must cast ( sockaddr_in * ) to ( sockaddr * ) for connect, bind, and accept sa_family Family Specific struct sockaddr_in { unsigned short sin_family; /* address family (always AF_INET) */ unsigned short sin_port; /* port num in network byte order */ struct in_addr sin_addr; /* IP addr in network byte order */ unsigned char sin_zero[8]; /* pad to sizeof(struct sockaddr) */ }; sin_port AF_INET sin_addr sin_family 19

Echo Client Main Routine #include "csapp.h" /* usage:./echoclient host port */ int main(int argc, char **argv) { int clientfd, port; char *host, buf[MAXLINE]; rio_t rio; host = argv[1]; port = atoi(argv[2]); clientfd = Open_clientfd(host, port); Rio_readinitb(&rio, clientfd); printf("type:"); fflush(stdout); while (Fgets(buf, MAXLINE, stdin) != NULL) { Rio_writen(clientfd, buf, strlen(buf)); Rio_readlineb(&rio, buf, MAXLINE); printf("echo:"); Fputs(buf, stdout); printf("type:"); fflush(stdout); } Close(clientfd); exit(0); } Send line to server Receive line from server Read input line Print server response 20

Overview of the Sockets Interface ClientServer socket bind listen Connection request open_listenfd open_clientfd acceptconnect 21

Echo Client: open_clientfd int open_clientfd(char *hostname, int port) { int clientfd; struct hostent *hp; struct sockaddr_in serveraddr; if ((clientfd = socket(AF_INET, SOCK_STREAM, 0)) < 0) return -1; /* check errno for cause of error */ /* Fill in the server's IP address and port */ if ((hp = gethostbyname(hostname)) == NULL) return -2; /* check h_errno for cause of error */ bzero((char *) &serveraddr, sizeof(serveraddr)); serveraddr.sin_family = AF_INET; bcopy((char *)hp->h_addr_list[0], (char *)&serveraddr.sin_addr.s_addr, hp->h_length); serveraddr.sin_port = htons(port); /* Establish a connection with the server */ if (connect(clientfd, (SA *) &serveraddr, sizeof(serveraddr)) < 0) return -1; return clientfd; } This function opens a connection from the client to the server at hostname:port Create socket Create address Establish connection 22

Echo Client: open_clientfd (socket) int clientfd; /* socket descriptor */ if ((clientfd = socket(AF_INET, SOCK_STREAM, 0)) < 0) return -1; /* check errno for cause of error */... creates a socket descriptor on the client –Just allocates & initializes some internal data structures –AF_INET: indicates that the socket is associated with Internet protocols –SOCK_STREAM: selects a reliable byte stream connection provided by TCP 23

24 The client builds the server’s Internet address. struct hostent *hp; /* DNS host entry */ struct sockaddr_in serveraddr; /* server’s IP address */ /* fill in the server's IP address and port */ hp = Gethostbyname(hostname); bzero((char *) &serveraddr, sizeof(serveraddr)); serveraddr.sin_family = AF_INET; bcopy((char *)hp->h_addr_list[0], (char *) &serveraddr.sin_addr.s_addr, hp->h_length); serveraddr.sin_port = htons(port); Echo client: open_clientfd()

A Careful Look at bcopy Arguments /* DNS host entry structure */ struct hostent {... int h_length; /* length of an address, in bytes */ char **h_addr_list; /* null-terminated array of in_addr structs */ }; struct hostent *hp; /* DNS host entry */ struct sockaddr_in serveraddr; /* server’s IP address */... bcopy((char *)hp->h_addr_list[0], /* src, dest */ (char *)&serveraddr.sin_addr.s_addr, hp->h_length); struct sockaddr_in {... struct in_addr sin_addr; /* IP addr in network byte order */... }; /* Internet address structure */ struct in_addr { unsigned int s_addr; /* network byte order (big-endian) */ }; 25

Bcopy Argument Data Structures sin_port AF_INET sin_addrsin_family struct sockaddr_in struct in_addr s_addr 0 h_lengthh_addr_list struct hostent struct in_addr s_addr... 26

27 Echo client: open_clientfd()(connect) int clientfd; /* socket descriptor */ struct sockaddr_in serveraddr; /* server address */ typedef struct sockaddr SA; /* generic sockaddr */... /* Establish a connection with the server */ if (connect(clientfd, (SA *)&serveraddr, sizeof(serveraddr))< 0) return -1; return clientfd; }

28 Then the client creates a connection with the server –The client process suspends (blocks) until the connection is created with the server. –At this point the client is ready to begin exchanging messages with the server via Unix I/O calls on the descriptor clientfd. Echo client: open_clientfd()(connect)

29 int main(int argc, char **argv) { int listenfd, connfd, port, clientlen; struct sockaddr_in clientaddr; struct hostent *hp; char *haddrp; port = atoi(argv[1]); /* the server listens on a port passed on the command line */ listenfd = open_listenfd(port); Echo server : Main Routine

30 while (1) { clientlen = sizeof(clientaddr); connfd = Accept(listenfd, (SA *)&clientaddr, &clientlen); hp = Gethostbyaddr((const char *)&clientaddr.sin_addr.s_addr, sizeof(clientaddr.sin_addr.s_addr), AF_INET); haddrp = inet_ntoa(clientaddr.sin_addr); client_port = ntohs(clientaddr.sin_port); printf("server connected to %s (%s), port %u\n", hp->h_name, haddrp, client_port); echo(connfd); Close(connfd); } Echo server

Overview of the Sockets Interface Office Telephone Analogy for Server –Socket: Buy a phone –Bind: Tell the local administrator what number you want to use –Listen: Plug the phone in –Accept: Answer the phone when it rings ClientServer socket bind listen Connection request open_listenfd open_clientfd acceptconnect 31

32 Echo server: open_listenfd() int open_listenfd(int port) { int listenfd, optval=1; struct sockaddr_in serveraddr; /* Create a socket descriptor */ if ((listenfd = socket(AF_INET, SOCK_STREAM, 0)) < 0) return -1; /* Eliminates "Address already in use" error from bind. */ if (setsockopt(listenfd, SOL_SOCKET, SO_REUSEADDR, (const void *)&optval, sizeof(int)) < 0) return -1;...

33 Echo server: open_listenfd() (cont)... /* Listenfd will be an endpoint for all requests to port on any IP address for this host */ bzero((char *) &serveraddr, sizeof(serveraddr)); serveraddr.sin_family = AF_INET; serveraddr.sin_addr.s_addr = htonl(INADDR_ANY); serveraddr.sin_port = htons((unsigned short)port); if (bind(listenfd, (SA *)&serveraddr, sizeof(serveraddr)) < 0) return -1; /* Make it a listening socket ready to accept connection requests */ if (listen(listenfd, LISTENQ) < 0) return -1; return listenfd; }

34 The socket can be given some attributes. Echo server: open_listenfd() (setsockopt)... /* Eliminates "Address already in use" error from bind(). */ if (setsockopt(listenfd, SOL_SOCKET, SO_REUSEADDR, (const void *)&optval, sizeof(int)) < 0) return -1;

35 Handy trick that allows us to rerun the server immediately after we kill it. –Otherwise we would have to wait about 15 secs. –Eliminates “Address already in use” error from bind(). Strongly suggest you do this for all your servers to simplify debugging. Echo server: open_listenfd()(setsockopt)

36 Initialize socket with server port number Accept connection from any IP address Echo server: open_listenfd() struct sockaddr_in serveraddr; /* server's socket addr */... /* listenfd will be an endpoint for all requests to port on any IP address for this host */ bzero((char *) &serveraddr, sizeof(serveraddr)); serveraddr.sin_family = AF_INET; serveraddr.sin_port = htons((unsigned short)port); serveraddr.sin_addr.s_addr = htonl(INADDR_ANY);

37 IP addr and port stored in network (big-endian) byte order –htonl() converts longs from host byte order to network byte order. –htons() convers shorts from host byte order to network byte order. Echo server: open_listenfd() (initialize socket address) sa_family sin_port AF_INET sin_addr INADDR_ANY sin_family

38 bind() associates the socket with the socket address we just created. Echo server: open_listenfd() (bind) int listenfd; /* listening socket */ struct sockaddr_in serveraddr; /* server’s socket addr */... /* listenfd will be an endpoint for all requests to port on any IP address for this host */ if (bind(listenfd, (SA *)&serveraddr, sizeof(serveraddr)) < 0) return -1;

39 listen() indicates that this socket will accept connection ( connect ) requests from clients. LISTENQ is constant indicating how many pending requests allowed We’re finally ready to enter the main server loop that accepts and processes client connection requests. Echo server: open_listenfd (listen) int listenfd; /* listening socket */... /* Make it a listening socket ready to accept connection requests */ if (listen(listenfd, LISTENQ) < 0) return -1; return listenfd; }

40 The server loops endlessly, waiting for connection requests, then reading input from the client, and echoing the input back to the client. main() { /* create and configure the listening socket */ while(1) { /* Accept(): wait for a connection request */ /* echo(): read and echo input line from client */ /* Close(): close the connection */ } Echo server: main loop

accept() blocks waiting for a connection request int listenfd; /* listening descriptor */ int connfd; /* connected descriptor */ struct sockaddr_in clientaddr; int clientlen; clientlen = sizeof(clientaddr); connfd = Accept(listenfd, (SA *)&clientaddr, &clientlen); 41 Echo server: accept()

42 accept() returns a connected socket descriptor ( connfd ) with the same properties as the listening descriptor ( listenfd) –Returns when connection between client and server is created and ready for I/O transfers. –All I/O with the client will be done via the connected socket. accept() also fills in client’s address. Echo server: accept()

Echo Server: accept Illustrated listenfd(3) Client 1. Server blocks in accept, waiting for connection request on listening descriptor listenfd clientfd Server listenfd(3) Client clientfd Server 2. Client makes connection request by calling and blocking in connect Connection request listenfd(3) Client clientfd Server 3. Server returns connfd from accept. Client returns from connect. Connection is now established between clientfd and connfd connfd(4) 43

Connected vs. Listening Descriptors Listening descriptor –End point for client connection requests –Created once and exists for lifetime of the server Connected descriptor –End point of the connection between client and server –A new descriptor is created each time the server accepts a connection request from a client –Exists only as long as it takes to service client Why the distinction? –Allows for concurrent servers that can communicate over many client connections simultaneously E.g., Each time we receive a new request, we fork a child to handle the request 44

45 The server can determine the domain name and IP address of the client. Echo server: identifying the client struct hostent *hp; /* pointer to DNS host entry */ char *haddrp; /* pointer to dotted decimal string */ unsigned short client_port; hp = Gethostbyaddr((const char *)&clientaddr.sin_addr.s_addr, sizeof(clientaddr.sin_addr.s_addr), AF_INET); haddrp = inet_ntoa(clientaddr.sin_addr); client_port = ntohs(clientaddr.sin_port); printf("server connected to %s (%s), port %u\n", hp->h_name, haddrp, client_port);

46 The server uses Unix I/O to read and echo text lines until EOF (end-of-file) is encountered. – EOF notification caused by client calling close(clientfd). –NOTE: EOF is a condition, not a data byte. Echo server: echo()

47 void echo(int connfd) { size_t n; char buf[MAXLINE]; rio_t rio Rio_readinitb(&rio, connfd) while((n = Rio_readlineb(&rio, buf, MAXLINE))!=0){ printf("server received %d bytes\n", n); Rio_writen(connfd, buf, n); } Echo server: echo()

Testing Servers Using telnet The telnet program is invaluable for testing servers that transmit ASCII strings over Internet connections –Our simple echo server –Web servers –Mail servers Usage: –unix> telnet –Creates a connection with a server running on and listening on port 48

Testing the Echo Server With telnet greatwhite> echoserver linux> telnet greatwhite.ics.cs.cmu.edu Trying Connected to greatwhite.ics.cs.cmu.edu. Escape character is '^]'. hi there HI THERE 49

Watching Network Packet Sniffer –Program that records network traffic visible at node –Promiscuous mode: Record traffic that does not have this host as source or destination 50

Watching Echo Client / Server 51

For More Information W. Richard Stevens, “Unix Network Programming: Networking APIs: The Sockets Networking API”, Volume 1, Third Edition, Prentice Hall, 2003 –THE network programming bible Unix Man Pages –Good for detailed information about specific functions Complete versions of the echo client and server are developed in the text –Updated versions linked to course website –Feel free to use this code in your assignments 52

Next Web servers –HTTP Protocol –Web Content –CGI The Tiny Web Server Suggested Reading: –11.5~