15 213 The course that gives CMU its Zip Network Programming April 20 2004 Topics class26 ppt Programmer s view of the Internet review Sockets interface Writing clients and servers A Client Server Transaction Most network applications are based on the clientserver model A server process and one or more client processes Server manages some resource Server provides service by manipulating resource for clients 4 Client handles response Client process 1 Client sends request 3 Server sends response Server process Resource 2 Server handles request Note clients and servers are processes running on hosts can be the same or different hosts 2 15 213 S 04 A Programmer s View of the Internet 1 Hosts are mapped to a set of 32 bit IP addresses 128 2 203 179 In IP V6 Host addresses are 64 bit at some point in the future a transition from IP V4 to IP V6 will happen 2 The set of IP addresses is mapped to a set of identifiers called Internet domain names 128 2 203 179 is mapped to www cs cmu edu 3 A process on one Internet host can communicate with a process on another Internet host over a connection 3 15 213 S 04 1 IP Addresses 32 bit IP addresses are stored in an IP address struct IP addresses are always stored in memory in network byte order big endian byte order True in general for any integer transferred in a packet header from one machine to another E g the port number used to identify an Internet connection Internet address structure struct in addr unsigned int s addr network byte order big endian Handy network byte order conversion functions htonl convert long int from host to network byte order htons convert short int from host to network byte order ntohl convert long int from network to host byte order ntohs convert short int from network to host byte order 4 15 213 S 04 2 Domain Naming System DNS The Internet maintains a mapping between IP addresses and domain names in a huge worldwide distributed database called DNS Conceptually programmers can view the DNS database as a collection of millions of host entry structures DNS host entry structure struct hostent char h name char h aliases int h addrtype int h length char h addr list official domain name of host null terminated array of domain names host address type AF INET length of an address in bytes null terminated array of in addr structs Functions for retrieving host entries from DNS 5 gethostbyname query key is a DNS domain name gethostbyaddr query key is an IP address 15 213 S 04 3 Internet Connections Clients and servers communicate by sending streams of bytes over connections Connections are point to point full duplex 2 way communication and reliable Client socket address 128 2 194 242 51213 Client Server socket address 208 216 181 15 80 Connection socket pair 128 2 194 242 51213 208 216 181 15 80 Server port 80 Client host address 128 2 194 242 Server host address 208 216 181 15 Note 51213 is an ephemeral port allocated 6 by the kernel Note 80 is a well known port associated with Web servers 15 213 S 04 Clients Examples of client programs Web browsers ftp telnet ssh How does a client find the server The IP address in the server socket address identifies the host more precisely an adapter on the host The well known port in the server socket address identifies the service and thus implicitly identifies the server process that performs that service Examples of well know ports Port 7 Echo server Port 22 Secure Shell ssh server daemon Port 25 Mail server Port 80 Web server 7 15 213 S 04 Using Ports to Identify Services Server host 128 2 194 242 Client host Client Service request for 128 2 194 242 80 i e the Web server Web server port 80 Kernel Echo server port 7 Client Service request for 128 2 194 242 7 i e the echo server Web server port 80 Kernel Echo server port 7 8 15 213 S 04 Servers 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 Each server waits for requests to arrive on a well known port associated with a particular service Port 7 echo server Port 22 ssh server Port 25 mail server Port 80 HTTP server A machine that runs a server process is also often referred to as a server 9 15 213 S 04 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 depreciated Resource files Service stores and retrieve files SSH server 22 See etc services for a comprehensive list of the services available on a Linux machine Resource terminal Service proxies a terminal on the server machine over an excrypted and authenticated connection Also supports file transfers forwarding of ports and X11 sessions Mail server 25 10 Resource email spool file Service stores mail messages in spool file 15 213 S 04 Security Issues Don t run services that you do not really need Open port detection utility nmap see http www insecure org nmap Port knocking ports appear to be closed but open for a brief period if the kernel detects a specific sequence of connection attempts 11 15 213 S 04 Sockets Interface 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 most Internet applications Based on client server programming model 12 15 213 S 04 Overview of the Sockets Interface Client Server socket socket bind open listenfd open clientfd listen connect accept rio writen rio readlineb rio readlineb rio writen close 13 Connection request EOF Await connection request from next client rio readlineb close 15 213 S 04 Sockets What is a socket To the kernel a socket is an endpoint of communication To an application a socket is a file descriptor that lets the application read write from to the network Remember All Unix I O devices including networks are modeled as files Clients and servers communicate with each other by reading from and writing to socket descriptors The main distinction between regular file I O and socket I O is how the application opens the socket descriptors 14 15 213 S 04 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 char sa data 14 protocol family address data Internet specific socket address Must cast
View Full Document