Network Applications: DNS Details; UDP Network App Programming

Slides:



Advertisements
Similar presentations
2: Application Layer1 Socket programming Socket API r introduced in BSD4.1 UNIX, 1981 r Sockets are explicitly created, used, released by applications.
Advertisements

Client-Server Paradigm and Performance L. Grewe. 2 Review: Basic Client-Server Request/Reply Paradigm Typical Internet app has two pieces: client and.
Network Programming and Java Sockets
Application Layer 2-1 Chapter 2 Application Layer Computer Networking: A Top Down Approach 6 th edition Jim Kurose, Keith Ross Application Layer – Lecture.
2: Application Layer 1 Socket programming Socket API r introduced in BSD4.1 UNIX, 1981 r explicitly created, used, released by apps r client/server paradigm.
9/23/2003-9/25/2003 Sockets & DNS September 23-25, 2003.
2: Application Layer1 Data Communication and Networks Lecture 12 Java Sockets November 30, 2006.
2: Application Layer1 Socket programming Socket API r introduced in BSD4.1 UNIX, 1981 r explicitly created, used, released by apps r client/server paradigm.
1 Overview r Socket programming with TCP r Socket programming with UDP r Building a Web server.
Internet and Intranet Protocols and Applications Lecture 4: Application Layer 3: Socket Programming February 8, 2005 Arthur Goldberg Computer Science Department.
2: Application Layer1 Chapter 2 (continued) Application Layer – part 2 Computer Networking: A Top Down Approach Featuring the Internet, 3 rd edition. Jim.
Lecture 11 Java Socket Programming CPE 401 / 601 Computer Network Systems slides are modified from Dave Hollinger and Joonbok Lee.
Socket programming with UDP and TCP. Socket Programming with TCP Connection oriented – Handshaking procedure Reliable byte-stream.
2: Application Layer1 Socket Programming. 2: Application Layer2 Socket-programming using TCP Socket: a door between application process and end- end-transport.
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 Network Layers Application Transport Network Data-Link Physical bits.
Protocols Rules for communicating between two entities (e.g., a client and a server) “A protocol definition specifies how distributed system elements interact.
2: Application Layer 1 Socket Programming Computer Networking: A Top Down Approach Featuring the Internet, 3 rd edition. Jim Kurose, Keith Ross Addison-Wesley,
2: Application Layer 1 Socket Programming TCP and UDP.
Network Applications: UDP and TCP Socket Programming Y. Richard Yang 9/17/2013.
JAVA Socket Programming Source: by Joonbok Lee, KAIST, 2003.
ECE5650: Network Programming
1 1 Socket programming Socket API r introduced in BSD4.1 UNIX, 1981 r explicitly created, used, released by apps r client/server paradigm r two types of.
2: Application Layer1 Chapter 2 Application Layer Computer Networking: A Top Down Approach Featuring the Internet, 2 nd edition. Jim Kurose, Keith Ross.
Network Applications: DNS, UDP Socket Y. Richard Yang 9/12/2013.
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,
2: Application Layer1 Socket programming Socket API r introduced in BSD4.1 UNIX, 1981 r explicitly created, used, released by apps r client/server paradigm.
CS 3830 Day 11 Introduction : Application Layer 2 Server-client vs. P2P: example Client upload rate = u, F/u = 1 hour, u s = 10u, d min ≥ u s.
1 9/18/2009 Network Applications and Network Programming: + DNS.
Chapter 2 Application Layer Computer Networking: A Top Down Approach, 5 th edition. Jim Kurose, Keith Ross Addison-Wesley, April A note on the use.
Winter 2002Suprakash Datta1 Socket programming Socket API introduced in BSD4.1 UNIX, 1981 explicitly created, used, released by apps client/server paradigm.
-1- Georgia State UniversitySensorweb Research Laboratory CSC4220/6220 Computer Networks Dr. WenZhan Song Associate Professor, Computer Science.
Socket Programming Lee, Sooyong
Network Programming and Sockets CPSC 363 Computer Networks Ellen Walker Hiram College (Includes figures from Computer Networking by Kurose & Ross, © Addison.
Socket Programming Tutorial. Socket programming Socket API introduced in BSD4.1 UNIX, 1981 explicitly created, used, released by apps client/server paradigm.
Java Socket programming. Socket programming with TCP.
L 2 - 1 3( 1/ 20) : Java Network Programming. The Socket API The previous contents describe client-server interaction that application programs use when.
NETWORK PROGRAMMING.
Socket-Programming.  Establish contact (connection).  Exchange information (bi-directional).  Terminate contact.
2: Application Layer1 Socket programming Socket API Explicitly created, used, released by apps Client/server paradigm Two types of transport service via.
1 CSCD 330 Network Programming Spring 2014 Some Material in these slides from J.F Kurose and K.W. Ross All material copyright Lecture 7 Application.
Network Applications: DNS, UDP Socket 1/24/ Outline  Recap r DNS r Network application programming: UDP.
1 Socket programming Socket API r introduced in BSD4.1 UNIX, 1981 r explicitly created, used, released by apps r client/server paradigm r two types of.
CSI 3125, Preliminaries, page 1 Networking. CSI 3125, Preliminaries, page 2 Inetaddress Class When establishing a connection across the Internet, addresses.
1 CSCD 330 Network Programming Fall 2013 Some Material in these slides from J.F Kurose and K.W. Ross All material copyright Lecture 8a Application.
Network Applications: Network App Programming: TCP FTP Y. Richard Yang 2/8/2016.
Data Communications and Computer Networks Chapter 2 CS 3830 Lecture 11 Omar Meqdadi Department of Computer Science and Software Engineering University.
1 All rights reserved to Chun-Chuan Yang Upon completion you will be able to: The OSI Model and the TCP/IP Protocol Suite Understand the architecture of.
2: Application Layer1 Network applications: some jargon Process: program running within a host. r within same host, two processes communicate using interprocess.
16-1 Last time □ Reliable Data Transfer with packet loss ♦ rdt3.0 □ Pipelining ♦ Problems with stop-and-wait ♦ Go-Back-N ♦ Selective-Repeat.
Socket Programming Socket Programming Overview
Transport layer (last part) Application layer
DNS: Domain Name System
Socket programming with TCP
Chapter 2: outline 2.1 principles of network applications
Socket programming - Java
CSCD 330 Network Programming
Socket Programming Socket Programming Overview
Socket Programming.
CSCD 330 Network Programming
Java Socket Programming
Socket Programming 2: Application Layer.
DNS: Domain Name System
CPSC 441 UDP Socket Programming
Chapter 2: Application layer
DNS: Domain Name System
Network Applications: DNS; Socket Programming
DNS: Domain Name System
Socket Programming with UDP
Presentation transcript:

Network Applications: DNS Details; UDP Network App Programming Y. Richard Yang http://zoo.cs.yale.edu/classes/cs433/ 2/3/2016

Outline Admin and recap Network app programming

Recap: Domain Name System (DNS) Function map between (domain name, service) to value, e.g., (www.cs.yale.edu, Addr) -> 128.36.229.30 (cs.yale.edu, Email) -> netra.cs.yale.edu clients DNS Hostname, Service Address routers Why name: easy to remember, one-level of indirection servers

Recap: DNS Key design features of DNS Hierarchical domain name space allowing delegation Recursive or iterative queries Why name: easy to remember, one-level of indirection

DNS Message Format? Basic encoding decisions: UDP/TCP, how to encode domain name, how to encode answers… IP Ethernet Cable/DSL Wireless TCP UDP DNS IP Ethernet Cable/DSL Wireless TCP UDP DNS Basic questions: how to encode domain name; how to do compression…

Observing DNS Messages Issue DNS query using the command dig: force iterated query to see the trace: %dig +trace www.cnn.com see the manual for more details Capture the messages DNS server is at port 53 Display and clear DNS cache https://support.apple.com/en-us/HT202516 (e.g., MAC) Try to load the dns-capture file from class Schedule page, if you do not want live capture

DNS Protocol, Messages https://www.ietf.org/rfc/rfc1035.txt DNS protocol : typically over UDP (can use TCP); query and reply messages, both with the same message format

DNS Details Header (Sec. 4.1.1 of https://www.ietf.org/rfc/rfc1035.txt) Encoding of questions (Sec. 4.1.2): [Label-length label-chars] Encoding of answers (Sec. 4.1.3) Pointer format (http://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml) See example DNS packets

Evaluation of DNS Key questions to ask about a C-S application - extensible? - scalable? - robust? - security?

What DNS did Right? Hierarchical delegation avoids central control, improving manageability and scalability Redundant servers improve robustness see http://www.internetnews.com/dev-news/article.php/1486981 for DDoS attack on root servers in Oct. 2002 (9 of the 13 root servers were crippled, but only slowed the network) Caching reduces workload and improves robustness

Problems of DNS Domain names may not be the best way to name other resources, e.g. files Simple query model makes it hard to implement advanced query Relatively static resource types make it hard to introduce new services or handle mobility Although theoretically you can update the values of the records, it is rarely enabled Early binding (separation of DNS query from application query) does not work well in mobile, dynamic environments e.g., load balancing, locate the nearest printer

Outline Recap Network app programming

Socket Programming Socket API introduced in BSD4.1 UNIX, 1981 Two types of sockets Connectionless (UDP) connection-oriented (TCP) an interface (a “door”) into which one application process can both send and receive messages to/from another (remote or local) application process socket

Services Provided by Transport User data protocol (UDP) multiplexing/demultiplexing Transmission control protocol (TCP) multiplexing/demultiplexing reliable data transfer rate control: flow control and congestion control Host A Host B Hello I am ready DATA ACK

Big Picture: Socket buffers, states buffers, states

Outline Recap Basic network application programming Overview UDP (Datagram Socket)

DatagramSocket(Java) (Basic) constructs a datagram socket and binds it to any available port on the local host DatagramSocket(int lport) constructs a datagram socket and binds it to the specified port on the local host machine.  DatagramPacket(byte[] buf, int length) constructs a DatagramPacket for receiving packets of length length. DatagramPacket(byte[] buf, int length, InetAddress address, int port) constructs a datagram packet for sending packets of length length to the specified port number on the specified host. receive(DatagramPacket p) receives a datagram packet from this socket.  send(DatagramPacket p) sends a datagram packet from this socket. close() closes this datagram socket.

Connectionless UDP: Big Picture (Java version) Server (running on serv) Client create socket, port=x, for incoming request: create socket, clientSocket = DatagramSocket() serverSocket = DatagramSocket( x ) Create datagram using (serv, x) as (dest addr. port), send request using clientSocket read request from serverSocket generate reply, create datagram using client host address, port number write reply to serverSocket read reply from clientSocket close clientSocket

Example: UDPServer.java A simple UDP server which changes any received sentence to upper case.

Java Server (UDP): Create Socket import java.io.*; import java.net.*; class UDPServer { public static void main(String args[]) throws Exception { DatagramSocket serverSocket = new DatagramSocket(9876); Create datagram socket bind at port 9876 Check socket state: %netstat –a –p udp –n

local address why shown as “*”? System State after the Call server 128.36.232.5 128.36.230.2 UDP socket space “*” indicates that the socket binds to all IP addresses of the machine: % ifconfig -a address: {*:9876} snd/recv buf: local port local address why shown as “*”? address: {128.36.232.5:53} snd/recv buf:

Binding to Specific IP Addresses server Public address: 128.36.59.2 Local address: 127.0.0.1 InetAddress sIP1 = InetAddress.getByName(“localhost”); DatagramSocket ssock1 = new DatagramSocket(9876, sIP1); InetAddress sIP2 = InetAddress.getByName(“128.36.59.2”); DatagramSocket ssock2 = new DatagramSocket(9876,sIP2); DatagramSocket serverSocket = new DatagramSocket(6789); UDP socket space address: {127.0.0.1:9876} snd/recv buf: address: {128.36.59.2:9876} address: {*:6789} snd/recv buf: address: {128.36.232.5:53} snd/recv buf:

UDP Demultiplexing server client on server client IP: B SP: x DP: 9876 S-IP: A D-IP: 127.0.0.1 Public address: 128.36.59.2 Local address: 127.0.0.1 UDP socket space address: {127.0.0.1:9876} snd/recv buf: address: {128.36.59.2:9876} P2 client IP: B SP: y DP: 9876 S-IP: B D-IP: 128.36.59.2 address: {128.36.232.5:53} snd/recv buf: UDP demutiplexing is based on matching (dst address, dst port)

UDP Demultiplexing server Client on server client IP: C SP: x DP: 9876 S-IP: A D-IP: 127.0.0.1 Public address: 128.36.59.2 Local address: 127.0.0.1 UDP socket space address: {127.0.0.1:9876} snd/recv buf: address: {128.36.59.2:9876} P3 client IP: C address: {*:6789} snd/recv buf: SP: y DP: 6789 S-IP: C D-IP: 128.36.59.2 address: {128.36.232.5:53} snd/recv buf: UDP demutiplexing is based on matching (dst address, dst port)

Per Socket State Each Datagram socket has a set of states: local address send buffer size receive buffer size timeout traffic class See http://download.java.net/jdk7/archive/b123/docs/api/java/net/DatagramSocket.html Example: socket state after clients sent msgs to the server

Java Server (UDP): Receiving import java.io.*; import java.net.*; class UDPServer { public static void main(String args[]) throws Exception { DatagramSocket serverSocket = new DatagramSocket(9876); byte[] receiveData = new byte[1024]; byte[] sendData = null; while(true) DatagramPacket receivePacket = new DatagramPacket(receiveData, receiveData.length); serverSocket.receive(receivePacket); Create space for received datagram Receive datagram

DatagramPacket Receiving Sending DatagramPacket(byte[] buf, int length) constructs a DatagramPacket for receiving packets of length length. DatagramPacket(byte[] buf, int offset, int length) constructs a DatagramPacket for receiving packets starting at offset, length length. Sending DatagramPacket(byte[] buf, int length, InetAddress address, int port) constructs a datagram packet for sending packets of length length to the specified port number on the specified host. DatagramPacket(byte[] buf, int offset, int length, InetAddress address, int port)

Java Server (UDP): Processing getData() returns a pointer to an underlying buffer array; for efficiency, don’t assume receive() will reset the rest of the array import java.io.*; import java.net.*; class UDPServer { public static void main(String args[]) throws Exception { … // process data String sentence = new String(receivePacket.getData(), 0, receivePacket.getLength()); String capitalizedSentence = sentence.toUpperCase(); sendData = capitalizedSentence.getBytes(); getLength() returns how much data is valid.

Java Server (UDP): Response Java DatagramPacket: getAddress()/getPort() returns the source address/port

Java server (UDP): Reply InetAddress IPAddress = receivePacket.getAddress(); int port = receivePacket.getPort(); DatagramPacket sendPacket = new DatagramPacket(sendData, sendData.length, IPAddress, port); serverSocket.send(sendPacket); } Get IP addr port #, of sender Create datagram to send to client Write out datagram to socket End of while loop, loop back and wait for another datagram

Example: UDPClient.java A simple UDP client which reads input from keyboard, sends the input to server, and reads the reply back from the server.

Example: Java client (UDP) import java.io.*; import java.net.*; class UDPClient { public static void main(String args[]) throws Exception { BufferedReader inFromUser = new BufferedReader(new InputStreamReader(System.in)); String sentence = inFromUser.readLine(); byte[] sendData = sentence.getBytes(); DatagramSocket clientSocket = new DatagramSocket(); InetAddress sIPAddress = InetAddress.getByName(“servname"); Create input stream Create client socket Translate hostname to IP address using DNS

Example: Java client (UDP), cont. Create datagram with data-to-send, length, IP addr, port DatagramPacket sendPacket = new DatagramPacket(sendData, sendData.length, sIPAddress, 9876); clientSocket.send(sendPacket); byte[] receiveData = new byte[1024]; DatagramPacket receivePacket = new DatagramPacket(receiveData, receiveData.length); clientSocket.receive(receivePacket); String modifiedSentence = new String(receivePacket.getData()); System.out.println("FROM SERVER:" + modifiedSentence); clientSocket.close(); } Send datagram to server Read datagram from server

Demo %mac: java UDPServer % netstat to see buffer %cicada: java UDPClient <server> % wireshark to capture traffic System.out.println(clientSocket.getLocalAddress()); System.out.println(clientSocket.getLocalPort()); System.out.println(clientSocket.getReceiveBufferSize()); System.out.println(clientSocket.getSendBufferSize()); System.out.println(clientSocket.getSoTimeout()); System.out.println( java.nio.charset.Charset.defaultCharset() );

Discussion on Example Code A simple upper-case UDP echo service is among the simplest network service. Are there any problems with the program? System.out.println(clientSocket.getLocalAddress()); System.out.println(clientSocket.getLocalPort()); System.out.println(clientSocket.getReceiveBufferSize()); System.out.println(clientSocket.getSendBufferSize()); System.out.println(clientSocket.getSoTimeout()); System.out.println( java.nio.charset.Charset.defaultCharset() );

Data Encoding/Decoding Pay attention to encoding/decoding of data: transport layer handles only a sequence of bytes if not careful, query sent != query received (how?) client server query result encoding decoding byte array

Example: Endianness of Numbers int var = 0x0A0B0C0D ARM, Power PC, Motorola 68k, IA-64 Intel x86

Example: String and Chars Will we always get back the same string? client server String String (UTF-16) (UTF-16) byte array String.getBytes() String(rcvPkt, 0, rcvPkt.getLength()); Depends on default local platform char set (why?) : java.nio.charset.Charset.defaultCharset()

Example: Charset Troubles Try java EncodingDecoding US-ASCII UTF-8 System.out.println(clientSocket.getLocalAddress()); System.out.println(clientSocket.getLocalPort()); System.out.println(clientSocket.getReceiveBufferSize()); System.out.println(clientSocket.getSendBufferSize()); System.out.println(clientSocket.getSoTimeout()); System.out.println( java.nio.charset.Charset.defaultCharset() );

Encoding/Decoding as a Common Source of Errors Please read chapter 4 of Java Network Programming for more details Common mistake even in many (textbook) examples: http://www.java2s.com/Code/Java/Network-Protocol/UseDatagramSockettosendoutandreceiveDatagramPacket.htm System.out.println(clientSocket.getLocalAddress()); System.out.println(clientSocket.getLocalPort()); System.out.println(clientSocket.getReceiveBufferSize()); System.out.println(clientSocket.getSendBufferSize()); System.out.println(clientSocket.getSoTimeout()); System.out.println( java.nio.charset.Charset.defaultCharset() );

DataStream