Socket Programming. Kameswari Chebrolu Dept. of Electrical Engineering, IIT Kanpur



Similar documents
Unix Network Programming

Socket Programming. Srinidhi Varadarajan

Tutorial on Socket Programming

ELEN 602: Computer Communications and Networking. Socket Programming Basics

ICT SEcurity BASICS. Course: Software Defined Radio. Angelo Liguori. SP4TE lab.

Introduction to Socket Programming Part I : TCP Clients, Servers; Host information

Socket Programming. Request. Reply. Figure 1. Client-Server paradigm

Communication Networks. Introduction & Socket Programming Yuval Rochman

Porting applications & DNS issues. socket interface extensions for IPv6. Eva M. Castro. ecastro@dit.upm.es. dit. Porting applications & DNS issues UPM

Introduction to Socket programming using C

Implementing Network Software

Lab 4: Socket Programming: netcat part

TCP/IP - Socket Programming

Socket Programming in C/C++

VMCI Sockets Programming Guide VMware ESX/ESXi 4.x VMware Workstation 7.x VMware Server 2.0

UNIX Sockets. COS 461 Precept 1

IT304 Experiment 2 To understand the concept of IPC, Pipes, Signals, Multi-Threading and Multiprocessing in the context of networking.

The POSIX Socket API

Programmation Systèmes Cours 9 UNIX Domain Sockets

Networks. Inter-process Communication. Pipes. Inter-process Communication

NS3 Lab 1 TCP/IP Network Programming in C

DESIGN AND IMPLEMENT AND ONLINE EXERCISE FOR TEACHING AND DEVELOPMENT OF A SERVER USING SOCKET PROGRAMMING IN C

Application Architecture

Network Programming with Sockets. Process Management in UNIX

Computer Networks Network architecture

INTRODUCTION UNIX NETWORK PROGRAMMING Vol 1, Third Edition by Richard Stevens

Lecture 7: Introduction to Sockets

BSD Sockets Interface Programmer s Guide

UNIX. Sockets. mgr inż. Marcin Borkowski

Overview. Socket Programming. Using Ports to Identify Services. UNIX Socket API. Knowing What Port Number To Use. Socket: End Point of Communication

Session NM059. TCP/IP Programming on VMS. Geoff Bryant Process Software

Concurrent Server Design Alternatives

Network Programming with Sockets. Anatomy of an Internet Connection

Client / Server Programming with TCP/IP Sockets

Hostnames. HOSTS.TXT was a bottleneck. Once there was HOSTS.TXT. CSCE515 Computer Network Programming. Hierarchical Organization of DNS

CSE 333 SECTION 6. Networking and sockets

Windows Socket Programming & IPv6 Translation Middleware

System calls. Problem: How to access resources other than CPU

Writing a C-based Client/Server

This tutorial has been designed for everyone interested in learning the data exchange features of Unix Sockets.

Elementary Name and Address. Conversions

Operating Systems Design 16. Networking: Sockets

Elementary Name and Address Conversions

A Client Server Transaction. Introduction to Computer Systems /18 243, fall th Lecture, Nov. 3 rd

Domain Name System (1)! gethostbyname (2)! gethostbyaddr (2)!

Networks class CS144 Introduction to Computer Networking Goal: Teach the concepts underlying networks Prerequisites:

Generalised Socket Addresses for Unix Squeak

IPv6 Enabling CIFS/SMB Applications

A Client-Server Transaction. Systemprogrammering 2006 Föreläsning 8 Network Programming. Hardware Org of a Network Host.

TCP/IP Sockets in C. Practical Guide for Programmers

Goal: learn how to build client/server application that communicate using sockets. An interface between application and network

Network Programming. Chapter The Client-Server Programming Model

Writing Client/Server Programs in C Using Sockets (A Tutorial) Part I. Session Greg Granger grgran@sas. sas.com. SAS/C & C++ Support

Limi Kalita / (IJCSIT) International Journal of Computer Science and Information Technologies, Vol. 5 (3), 2014, Socket Programming

Chapter 11. User Datagram Protocol (UDP)

Programming with TCP/IP Best Practices

Packet Sniffing and Spoofing Lab

VMCI Sockets Programming Guide VMware ESXi 5.5 VMware Workstation 9.x

Lecture 17. Process Management. Process Management. Process Management. Inter-Process Communication. Inter-Process Communication

Direct Sockets. Christian Leber Lehrstuhl Rechnerarchitektur Universität Mannheim

RPG Does TCP/IP (Socket Progamming in RPG IV)

IP Network Layer. Datagram ID FLAG Fragment Offset. IP Datagrams. IP Addresses. IP Addresses. CSCE 515: Computer Network Programming TCP/IP

What is CSG150 about? Fundamentals of Computer Networking. Course Outline. Lecture 1 Outline. Guevara Noubir noubir@ccs.neu.

Name and Address Conversions

SMTP-32 Library. Simple Mail Transfer Protocol Dynamic Link Library for Microsoft Windows. Version 5.2

TFTP Usage and Design. Diskless Workstation Booting 1. TFTP Usage and Design (cont.) CSCE 515: Computer Network Programming TFTP + Errors

KATRAGADDA INNOVATIVE TRUST FOR EDUCATION NETWORK PROGRAMMING. Notes prepared by D. Teja Santosh, Assistant Professor, KPES, Shabad, R.R. District.

IBM i Version 7.2. Programming Socket programming IBM

DNS Domain Name System

An Introductory 4.4BSD Interprocess Communication Tutorial

SSC - Communication and Networking Java Socket Programming (II)

Beej's Guide to Network Programming

Socket = an interface connection between two (dissimilar) pipes. OS provides this API to connect applications to networks. home.comcast.

Network Programming using sockets

Socket programming. Socket Programming. Languages and Platforms. Sockets. Rohan Murty Hitesh Ballani. Last Modified: 2/8/2004 8:30:45 AM

Programming With Sockets 2

Project 1: Implement a simple hosts framework using UNIX TCP Sockets to demonstrate the concept of Mobile Agents

Network Programming TDC 561

sys socketcall: Network systems calls on Linux

First Workshop on Open Source and Internet Technology for Scientific Environment: with case studies from Environmental Monitoring

Overview. Securing TCP/IP. Introduction to TCP/IP (cont d) Introduction to TCP/IP

An Advanced 4.4BSD Interprocess Communication Tutorial

The exam has 110 possible points, 10 of which are extra credit. There is a Word Bank on Page 8. Pages 7-8 can be removed from the exam.

Porting and Deploying VoIP to IPv6: Lessons Learned

3.5. cmsg Developer s Guide. Data Acquisition Group JEFFERSON LAB. Version

Implementing and testing tftp

Firewall Implementation

CS640: Computer Networks. Naming /ETC/HOSTS

Linux Kernel Architecture

CS 213, Fall 2000 Lab Assignment L5: Logging Web Proxy Assigned: Nov. 28, Due: Mon. Dec. 11, 11:59PM

Transcription:

Socket Programming Kameswari Chebrolu Dept. of Electrical Engineering, IIT Kanpur

Background

Demultiplexing Convert host-to-host packet delivery service into a process-to-process communication channel 0 16 31 Application process Application process Application process SrcPort DstPort Ports Length Checksum Data Queues Packets demultiplexed Transport Packets arrive

Byte Ordering Two types of Byte ordering Network Byte Order: High-order byte of the number is stored in memory at the lowest address Host Byte Order: Low-order byte of the number is stored in memory at the lowest address Network stack (TCP/IP) expects Network Byte Order Conversions: htons() - Host to Network Short htonl() - Host to Network Long ntohs() - Network to Host Short ntohl() - Network to Host Long

What is a socket? Socket: An interface between an application process and transport layer The application process can send/receive messages to/from another application process (local or remote)via a socket In Unix jargon, a socket is a file descriptor an integer associated with an open file Types of Sockets: Internet Sockets, unix sockets, X.25 sockets etc Internet sockets characterized by IP Address (4 bytes), port number (2 bytes)

Socket Description

Encapsulation

Types of Internet Sockets Stream Sockets (SOCK_STREAM) Connection oriented Rely on TCP to provide reliable two-way connected communication Datagram Sockets (SOCK_DGRAM) Rely on UDP Connection is unreliable

socket() -- Get the file descriptor int socket(int domain, int type, int protocol); domain should be set to PF_INET type can be SOCK_STREAM or SOCK_DGRAM set protocol to 0 to have socket choose the correct protocol based on type socket() returns a socket descriptor for use in later system calls or -1 on error int sockfd; sockfd = socket (PF_INET, SOCK_STREAM, 0);

Socket Structures struct sockaddr: Holds socket address information for many types of sockets struct sockaddr { unsigned short sa_family; //address family AF_xxx unsigned short sa_data[14]; //14 bytes of protocol addr } struct sockaddr_in: A parallel structure that makes it easy to reference elements of the socket address struct sockaddr_in { short int sin_family; // set to AF_INET unsigned short int sin_port; // Port number struct in_addr sin_addr; // Internet address unsigned char sin_zero[8]; //set to all zeros } sin_port and sin_addr must be in Network Byte Order

Dealing with IP Addresses struct in_addr { unsigned long s_addr; // that's a 32 bit long, or 4 bytes }; int inet_aton(const char *cp, struct in_addr *inp); struct sockaddr_in my_addr; my_addr.sin_family = AF_INET; my_addr.sin_port = htons(myport); inet_aton( 10.0.0.5,&(my_addr.sin_addr)); memset(&(my_addr.sin_zero),'\0',8); inet_aton() gives non-zero on success; zero on failure To convert binary IP to string: inet_noa() printf( %s,inet_ntoa(my_addr.sin_addr));

bind() - what port am I on? Used to associate a socket with a port on the local machine The port number is used by the kernel to match an incoming packet to a process int bind(int sockfd, struct sockaddr *my_addr, int addrlen) sockfd is the socket descriptor returned by socket() my_addr is pointer to struct sockaddr that contains information about your IP address and port addrlen is set to sizeof(struct sockaddr) returns -1 on error my_addr.sin_port = 0; //choose an unused port at random my_addr.sin_addr.s_addr = INADDR_ANY; //use my IP adr

int sockfd; struct sockaddr_in my_addr; Example sockfd = socket(pf_inet, SOCK_STREAM, 0); my_addr.sin_family = AF_INET; my_addr.sin_port = htons(myport); order // host byte order // short, network byte my_addr.sin_addr.s_addr = inet_addr("172.28.44.57"); memset(&(my_addr.sin_zero), '\0', 8); // zero the rest of the struct bind(sockfd, (struct sockaddr *)&my_addr, sizeof(struct sockaddr)); /****** Code needs error checking. Don't forget to do that ****** /

connect() - Hello! Connects to a remote host int connect(int sockfd, struct sockaddr *serv_addr, int addrlen) sockfd is the socket descriptor returned by socket() serv_addr is pointer to struct sockaddr that contains information on destination IP address and port addrlen is set to sizeof(struct sockaddr) returns -1 on error No need to bind(), kernel will choose a port

#define DEST_IP "172.28.44.57" #define DEST_PORT 5000 main(){ int sockfd; Example struct sockaddr_in dest_addr; // will hold the destination addr sockfd = socket(pf_inet, SOCK_STREAM, 0); dest_addr.sin_family = AF_INET; // host byte order dest_addr.sin_port = htons(dest_port); // network byte order dest_addr.sin_addr.s_addr = inet_addr(dest_ip); memset(&(dest_addr.sin_zero), '\0', 8); // zero the rest of the struct connect(sockfd, (struct sockaddr *)&dest_addr, sizeof(struct sockaddr)); /******* Don't forget error checking ********/

listen() - Call me please! Waits for incoming connections int listen(int sockfd, int backlog); sockfd is the socket file descriptor returned by socket() backlog is the number of connections allowed on the incoming queue listen() returns -1 on error Need to call bind() before you can listen() socket() bind() listen() accept()

accept() - Thank you for calling! accept() gets the pending connection on the port you are listen()ing on int accept(int sockfd, void *addr, int *addrlen); sockfd is the listening socket descriptor information about incoming connection is stored in addr which is a pointer to a local struct sockaddr_in addrlen is set to sizeof(struct sockaddr_in) accept returns a new socket file descriptor to use for this accepted connection and -1 on error

#include <string.h> #include <sys/types.h> #include <sys/socket.h> #include <netinet/in.h> #define MYPORT 3490 #define BACKLOG 10 main(){ Example // the port users will be connecting to // pending connections queue will hold int sockfd, new_fd; // listen on sock_fd, new connection on new_fd struct sockaddr_in my_addr; // my address information struct sockaddr_in their_addr; // connector's address information int sin_size; sockfd = socket(pf_inet, SOCK_STREAM, 0);

Cont... my_addr.sin_family = AF_INET; my_addr.sin_port = htons(myport); order // host byte order // short, network byte my_addr.sin_addr.s_addr = INADDR_ANY; // auto-fill with my IP memset(&(my_addr.sin_zero), '\0', 8); // zero the rest of the struct // don't forget your error checking for these calls: bind(sockfd, (struct sockaddr *)&my_addr, sizeof(struct sockaddr)); listen(sockfd, BACKLOG); sin_size = sizeof(struct sockaddr_in); new_fd = accept(sockfd, (struct sockaddr *)&their_addr, &sin_size);

send() and recv() - Let's talk! The two functions are for communicating over stream sockets or connected datagram sockets. int send(int sockfd, const void *msg, int len, int flags); sockfd is the socket descriptor you want to send data to (returned by socket() or got from accept()) msg is a pointer to the data you want to send len is the length of that data in bytes set flags to 0 for now sent() returns the number of bytes actually sent (may be less than the number you told it to send) or -1 on error

send() and recv() - Let's talk! int recv(int sockfd, void *buf, int len, int flags); sockfd is the socket descriptor to read from buf is the buffer to read the information into len is the maximum length of the buffer set flags to 0 for now recv() returns the number of bytes actually read into the buffer or -1 on error If recv() returns 0, the remote side has closed connection on you

sendto() and recvfrom() - DGRAM style int sendto(int sockfd, const void *msg, int len, int flags, const struct sockaddr *to, int tolen); to is a pointer to a struct sockaddr which contains the destination IP and port tolen is sizeof(struct sockaddr) int recvfrom(int sockfd, void *buf, int len, int flags, struct sockaddr *from, int *fromlen); from is a pointer to a local struct sockaddr that will be filled with IP address and port of the originating machine fromlen will contain length of address stored in from

close() - Bye Bye! int close(int sockfd); Closes connection corresponding to the socket descriptor and frees the socket descriptor Will prevent any more sends and recvs

Connection Oriented Protocol Server socket() Client bind() socket() listen() connect() accept() send() recv() recv() send() close() close()

Connectionless Protocol Server Client socket() bind() socket() bind() recvfrom() sendto() sendto() recvfrom() close() close()

Miscellaneous Routines int getpeername(int sockfd, struct sockaddr *addr, int *addrlen); Will tell who is at the other end of a connected stream socket and store that info in addr int gethostname(char *hostname, size_t size); Will get the name of the computer your program is running on and store that info in hostname

Miscellaneous Routines struct hostent *gethostbyname(const char *name); struct hostent { char *h_name; //official name of host char **h_aliases; //alternate names for the host int h_addrtype; //usually AF_NET int h_length; //length of the address in bytes char **h_addr_list; //array of network addresses for the host } #define h_addr h_addr_list[0] Example Usage: struct hostent *h; h = gethostbyname( www.iitk.ac.in ); printf( Host name : %s \n, h >h_name); printf( IP Address: %s\n,inet_ntoa(*((struct in_addr *)h >h_addr)));

Advanced Topics Blocking Select Handling partial sends Signal handlers Threading

Summary Sockets help application process to communicate with each other using standard Unix file descriptors Two types of Internet sockets: SOCK_STREAM and SOCK_DGRAM Many routines exist to help ease the process of communication

References Books: Unix Network Programming, volumes 1-2 by W. Richard Stevens. TCP/IP Illustrated, volumes 1-3 by W. Richard Stevens and Gary R. Wright Web Resources: Beej's Guide to Network Programming www.ecst.csuchico.edu/~beej/guide/net/