Examples of Ping

Windows
ping google.com

Pinging google.com [64.223.167.99] with 32 bytes of data:
Reply from 64.223.167.99: bytes=32 time=37ms TTL=57
Reply from 64.223.167.99: bytes=32 time=37ms TTL=57
Reply from 64.223.167.99: bytes=32 time=75ms TTL=57
Reply from 64.223.167.99: bytes=32 time=40ms TTL=57

Ping statistics for 64.223.167.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 37ms, Maximum = 75ms, Average = 47ms

Linux
ping -c 5 itresource.com.au

PING itresource.com.au(203.88.118.177) 56(84) bytes of data.
64 bytes from kookaburra.cbr.hosting-server.com.au (203.88.118.177): icmp_seq=1 ttl=57 time=36.6 ms
64 bytes from kookaburra.cbr.hosting-server.com.au (203.88.118.177): icmp_seq=2 ttl=57 time=36.5 ms
64 bytes from kookaburra.cbr.hosting-server.com.au (203.88.118.177): icmp_seq=3 ttl=57 time=37.0 ms
64 bytes from kookaburra.cbr.hosting-server.com.au (203.88.118.177): icmp_seq=4 ttl=57 time=36.9 ms
64 bytes from kookaburra.cbr.hosting-server.com.au (203.88.118.177): icmp_seq=5 ttl=57 time=36.6 ms

— itresource.com.au ping statistics —
5 packets transmitted, 5 received, 0% packet loss, time 9000ms
rtt min/avg/max/mdev = 35.918/36.638/37.106/0.400 ms

Mac OS X
ping -c 10 itresource.com.au

PING kookaburra.cbr.hosting-server.com.au (203.88.118.177): 56 data bytes
64 bytes from 203.88.118.177: icmp_seq=0 ttl=53 time=40.019 ms
64 bytes from 203.88.118.177: icmp_seq=1 ttl=53 time=47.502 ms
64 bytes from 203.88.118.177: icmp_seq=2 ttl=53 time=43.208 ms
64 bytes from 203.88.118.177: icmp_seq=3 ttl=53 time=50.851 ms
64 bytes from 203.88.118.177: icmp_seq=4 ttl=53 time=46.556 ms

— ping statistics —
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 40.019/45.575/50.851/3.588 ms

Useful links:
http://en.wikipedia.org/wiki/Ping

http://www.computerhope.com/jargon/p/ping.htm

The Sydney University based Centre for Ultra-high bandwidth Devices for Optical Systems (CUDOS) team, led by Ben Eggleton, has created a switch embedded in a silicon chip. The chip uses scratches on a glass surface to direct optical traffic at speeds of up to 640 gigabits per second.

Traditionally, switching network traffic means converting it from light into electrical signals and then back again. However, with the massive speeds now used in backbone networks, such an approach is becoming a bottleneck. The new switch opens up the prospect of multi terabit-per-second speeds.

Eggleton says “The switch chip essentially uses one beam of light to control another. The scratches create a photonic circuit that does the job traditionally done by electronics”. The circuit will guide data in much the same way as trains are guided from one track to another.

Just as potentially impressive as the operating speed is the simplicity and potential cheapness of the design. This should eventually allow it to be incorporated into a wide variety of equipment.

The CUDOS team has worked with other researchers at the Australian National University and the Technical University of Denmark on the project. A proof of concept chip is currently under evaluation in Europe.

Find CUDOS here

The model was developed by the International Organization for Standardization (ISO) in 1984, and it is now considered the primary architectural model for intercomputer communications. The OSI model divides the tasks involved with moving information between networked computers into seven smaller, more manageable task groups. A task or group of tasks is then assigned to each of the seven OSI layers. Each layer is reasonably self-contained so that the tasks assigned to each layer can be implemented independently. This enables the solutions offered by one layer to be updated without adversely affecting the other layers.

The seven layers of the OSI model are:

• Layer 7 – Application
• Layer 6 – Presentation
• Layer 5 – Session
• Layer 4 – Transport
• Layer 3 – Network
• Layer 2 – Data link
• Layer 1 – Physical

Layer 7 – Application Layer
This is the layer that interacts with the operating system and/or application whenever the user chooses to transfer files, e-mail, create terminal sessions or other network software services or related activities. Telnet and FTP are applications that exist entirely in the application level.

Layer 6 – Presentation Layer
Layer 6 takes the data provided by the Application layer and converts it into a standard format that the other layers can understand. Protocols at the presentation layer are part of the operating system and application the user runs on a workstation. Information is formatted for display or printing in this layer. Codes within the data, such as tabs or special graphics sequences, are interpreted. This layer also encrypts data to be sent across a network, as well as providing translation of other character sets.

Layer 5 – Session Layer
The session layer establishes, manages, and terminates communication sessions. Communication sessions consist of service requests and service responses that occur between applications located in different network devices. These requests and responses are coordinated by protocols implemented at the session layer. Some examples of session-layer implementations include Zone Information Protocol (ZIP), the AppleTalk protocol that coordinates the name binding process; and Session Control Protocol (SCP), the DECnet Phase IV session layer protocol.

Layer 4 – Transport Layer
The transport layer provides a high level of control for moving information between systems, including more sophisticated error handling, prioritization, and security features. The transport layer provides quality service and accurate delivery by providing connection oriented services between two end systems. It controls the sequence of packets, regulates traffic flow, and recognizes duplicate packets. The transport layer assigns packetized information a traffic number that is checked at the destination. If data is missing from the packet, the transport layer protocol at the receiving end arranges with the transport layer of the sending system to have packets re-transmitted. This layer ensures that all data is received and in the proper order.

Layer 3 – Network Layer
The network layer defines the network address, which differs from the MAC address. Some network layer implementations, such as the Internet Protocol (IP), define network addresses in a way that route selection can be determined systematically by comparing the source network address with the destination network address and applying the subnet mask. Because this layer defines the logical network layout, routers can use this layer to determine how to forward packets. Because of this, much of the design and configuration work for internetworks happens at Layer 3, the network layer.

Layer 2 – Data-Link Layer
The data link layer defines the rules for sending and receiving information across the physical connection between two systems. This layer encodes and frames data for transmission, in addition to providing error detection and control. Because the data link layer can provide error control, higher layers may not need to handle such services. However, when reliable media is used, there is a performance advantage by not handling error control in this layer, but in higher layers. Bridges operate at this layer in the protocol stack.

Layer 1 – Physical Layer
Physical layer specifications define characteristics such as voltage levels, timing of voltage changes, physical data rates, maximum transmission distances, and physical connectors for activating, maintaining, and deactivating the physical link between communicating network systems. Well-know physical layer interfaces for local area networks (LANs) include Ethernet, Token-Ring, and Fiber Distributed Data Interface (FDDI).