Académique Documents
Professionnel Documents
Culture Documents
The Embedded Virtual Private Network (eVPN) proiect describes the design and
implementation issues in developing an Embedded Virtual Network (eVPN) System.
The entire proiect is split into 3 parts The Architecture oI eVPN by Chun Ko. Key
Management oI eVPN by Jerome Lau and PerIormance and Scalability oI eVPN by Eric
Chan.
This thesis outlines the requirements. design and implementation issues oI Embedded
Virtual Private Network (eVPN). It describes the PerIormance and Scalability issues oI
eVPN: research. analysis and evaluation on existing VPN protocols were perIormed.
The goal oI this thesis is to analyze and evaluate existing technologies oI VPN. as well
as oIIering a solution to the design and implementation oI an embedded VPN System. A
compact prototype system is developed Ior testing and analysis purpose.
The prototype system is implemented under Linux platIorm. The overall system is
implemented with 3 workstations 1 workstation acts as the central management
system. network traIIic monitor and providing key management services. while the 2
gateways` on either side oI the network will act as an eVPN device. A secure channel
was setup between the two gateways using OpenVPN to provide secure
communications over the Internet`. Streaming and non-streaming data packets can be
transIerred across the network with the conIidentiality. availability and integrity oI
inIormation ensured. More resources can be integrated into the system to provide a
better model Ior the testing and development oI the eVPN system. Further work will
evolve Irom this prototype system.
Embedded Virtual Private Network: PerIormance and Scalability
iii
Table of Contents
1.0 Introduction------------------------------------------------------------------ 1
1.1 Background---------------------------------------------------------- 1
1.2 Information Security Hacker's point of view--------------- 1
1.2.1 Threats to computer resources---------------------- 2
1.2.2 How they do it-------------------------------------------- 3
1.2.2.1 Brute-force Attack--------------------------- 3
1.2.2.2 Trojan Horse Attack------------------------- 3
1.2.2.3 IP Spoofing------------------------------------ 4
1.2.2.4 Man in the middle Attack------------------ 4
1.2.2.5 Other Attacks--------------------------------- 4
1.3 What is Virtual Private Networks (VPN)---------------------- 5
1.3.1 Private Network----------------------------------------- 5
1.3.2 Internet---------------------------------------------------- 6
1.3.3 Virtual Private Network-------------------------------- 8
1.3.3.1 Topologies------------------------------------ 11
1.3.3.1.1 Host-to-Host----------------------- 11
1.3.3.1.2 Host-to-Network------------------ 12
1.3.3.1.3 Network-to-Network------------- 13
1.4 What is Embedded Virtual Private Networks (eVPN)----- 14
1.5 eVPN Goals--------------------------------------------------------- 15
1.6 Thesis Goals-------------------------------------------------------- 16
1.7 Thesis Overview--------------------------------------------------- 18
1.7.1 Literature Review-------------------------------------- 18
1.7.2 Design and Architecture of eVPN------------------ 18
1.7.3 Implementation----------------------------------------- 18
1.7.4 Analysis and Recommendations------------------- 18
1.7.5 Evaluation------------------------------------------------ 19
1.7.6 Future Work--------------------------------------------- 19
1.7.7 Conclusion----------------------------------------------- 19
2.0 Literature Review--------------------------------------------------------- 20
2.1 Transport Layer Protocols-------------------------------------- 20
2.1.1 TCP------------------------------------------------------- 20
2.1.2 UDP------------------------------------------------------- 22
2.1.3 TCP vs UDP-------------------------------------------- 23
2.2 Tunneling Protocols---------------------------------------------- 25
2.2.1 Standard Tunneling Protocols---------------------- 25
2.2.1.1 PPTP------------------------------------------ 25
2.2.1.2 L2F--------------------------------------------- 26
2.2.1.3 L2TP------------------------------------------- 27
2.2.1.4 IPSec------------------------------------------ 29
2.2.1.5 MPLS------------------------------------------ 31
2.2.2 Non-Standard Tunneling Protocols---------------- 32
2.2.2.1 OpenVPN------------------------------------- 32
Embedded Virtual Private Network: PerIormance and Scalability
iv
2.2.2.2 cIPE-------------------------------------------- 33
2.2.3 Comparisons-------------------------------------------- 33
2.3 Key Management-------------------------------------------------- 35
3.0 Design and Architecture of eVPN------------------------------------ 36
3.1 Specification of eVPN--------------------------------------------- 37
3.1.1 eVPN Device--------------------------------------------- 38
3.1.1.1 Authentication Scheme-------------------- 38
3.1.1.2 Configuration and Services--------------- 39
3.1.2 eVPN Central Server---------------------------------- 40
3.1.2.1 Authentication-------------------------------- 40
3.1.2.2 Access Control------------------------------- 40
3.1.2.3 Session Tracking---------------------------- 41
4.0 Implementation------------------------------------------------------------- 42
4.1 System Architecutre----------------------------------------------- 42
4.2 System Requirements--------------------------------------------- 43
4.3 Setting Up the System-------------------------------------------- 44
6.0 Evaluation-------------------------------------------------------------------- 54
6.1 Project Evaluation-------------------------------------------------- 54
6.2 System Evaluation------------------------------------------------- 54
6.3 Thesis Evaluation-------------------------------------------------- 55
6.4 Personal Evaluation----------------------------------------------- 55
6.5 Summary------------------------------------------------------------- 56
7.0 Future Work----------------------------------------------------------------- 57
8.0 Conclusion------------------------------------------------------------------ 58
Authentication VeriIy the identity oI the entity to give appropriate access rights
CA CertiIication Authority. issue certiIicates and maintain CRL
CertiIicate Public-key signed by a CA
cIPE Crypto IP Encapsulation
Digital Signatures Encryption with private-key. acting as a signature
eVPN Embedded Virtual Private Network
Eavesdropping Reading public network packets to obtain sensitive data
Hacker Computer proIessionals or cracker
IPSec Internet Protocol Security
IP SpooIing Creation oI TCP/IP packets using somebody else's IP address
L2F Layer 2 Forwarding
L2TP Layer 2 Tunneling Protocol
MPLS Multi-Protocol Label Switching
PPTP Point-to-Point Tunneling Protocol
TCP Transmission Control Protocol
UDP User Datagram Protocol
VPN Virtual Private Network
VPN Topology VPN architecture to support diIIerent applications
Embedded Virtual Private Network: PerIormance and Scalability
1
1.0 Introduction
1.1 Background
The Internet has changed the world undoubtedly. It is a rapidly growing global
phenomenon that has grown Iaster than any innovation in the industrial and inIormation
ages. Ranging Irom small-sized businesses to giant corporations. legitimate users to
national deIense. almost every person/organization in the world makes use oI the
Internet in one way or another.
The Internet`s greatest attractions openness and ubiquity. are also its greatness
weakness. In the absence oI security mechanisms. using the Internet to communicate
private and sensitive inIormation is an extremely dangerous practice it can easily lead
to numerous and unpredictable impacts with the presence oI hackers and
eavesdroppers hence. inIormation must be protected.
Virtual Private Network. or simply VPN. is an evolutionary invention that would
change the world oI computer security Iorever. It oIIers and ensures every single aspect
oI computer security with non-complex design and algorithms. and will surely be the
maior technology that will be employed in the coming decades.
1.2 Information Security - Hacker's point of view
Computers connected to the Internet are always under attack hackers are
causing damages everywhere all the time. So. why do they hack? What do they have to
gain? ProIessional hackers are not iust computer nerds they are extremely intelligent.
prepared and organized personnels they can cause serious damages to any
organization easily without anyone noticing their existence. Their motivation is not
solely Ior money. most oI them hack iust because oI the challenge oI it they tend to
believe that iI a system can be broken. regardless oI the eIIort it takes to perpetrate an
attack. the responsibility rests with the system owner Ior not protecting it well enough.
Embedded Virtual Private Network: PerIormance and Scalability
2
1.2.1 Threats to computer resources
Hackers can perIorm numerous threats to computer resources. below is a list oI
basic threats to organizations that use the Internet Ior corporate data communications:
Accidental Use: The inadvertent misuse oI a Web site or Internet service by a
legitimate user.
Data destruction: The accidental or malicious loss oI data on a web site (or other
Internet-based service and the interception oI data Ilowing to or Irom the
service) whether encrypted or not.
Interference: The derailing oI web sites or Internet services by rerouting data
intended Ior them or by overloading them with data. thus crippling the server.
Misrepresentation: Electronic posturing. where the perpetrator hands out Ialse
credentials. perhaps creating a counterIeit Web site to siphon oII traIIic intended
Ior legitimate destination.
Modification: The altering oI incoming or outgoing data that belongs to a
particular Web site or service whether intentional or not. A particularly
dreadIul hazard. since modiIication is diIIicult to detect in large transmissions.
Repudiation: The denial (on the part oI a consumer or customer) that an online
order was ever placed or the goods ever received.
Unauthorized altering or downloading: The inappropriate use oI data. whether
copying or updating. by someone without the proper security rights.
Unauthorized disclosure: The viewing oI data without the appropriate
permissions.
Unauthorized transactions: Any use oI a Web site or Internet service by
someone without the approval oI the site`s owner.
These threats become more pervasive as the quantity and value oI the data and
services are increased.
Embedded Virtual Private Network: PerIormance and Scalability
3
1.2.2 How they do it
Countless attacks methods exist in the world oI computer security. They are
employed to attack on the conIidentiality. integrity and availability oI inIormation and
services. Some Iundamental and popular attack methods are described in the Iollowing
sub-sections.
1.2.2.1 Brute-force Attack
Troian horse attacks pose one oI the most serious threats to computer security. A
Troian horse is a destructive program that masquerades as a benign application. Unlike
viruses. Troian horses do not replicate themselves but they can be iust as destructive.
Here is an example oI Troian horse attacks: hackers attach malicious code to email such
that when the network operating system processes it to determine the destination oI the
email. the errant code instructs the operating system to perIorm unauthorized operation
such as creating a new user and user password. AIterwards. the hacker is able to access
the network at any time.
Embedded Virtual Private Network: PerIormance and Scalability
4
1.2.2.3 IP Spoofing
IP spooIing a technique used to gain unauthorized access to computers. whereby
the intruder sends messages to a computer with an IP address indicating that the
message is coming Irom a trusted host. To engage in IP spooIing. a hacker must Iirst use
a variety oI techniques to Iind an IP address oI a trusted host and then modiIy the packet
headers so that it appears that the packets are coming Irom that host.
1.2.2.4 Man in the middle Attack
Man in the middle attack is where the user`s outgoing packets are going not to
the intended destination. but rather to someone who has severed the communication
path between the user and the intended recipient and pretends to be the recipient to the
user and pretends to be the user to the recipient. The man in the middle` will be able to
read. modiIy and delete the packets going into him/her. and thus causing extremely
dangerous security problem.
1.2.2.5 Other Attacks
Brute-Iorce attack. Troian horse attack. IP spooIing and Man in the middle
attack are iust Iew examples out oI the world oI hackers. Other attacks such as Denial oI
Service (DoS) Attack. Rootkit Attack. Flooding. Ping oI Death are also extremely
common and used all over the world. To protect against these attacks. security measures
must be employed. Virtual Private Network (VPN) is one oI the most powerIul and
secure algorithms developed to counter this security crisis.
Embedded Virtual Private Network: PerIormance and Scalability
5
1.3 What is Virtual Private Network (VPN)
To understand what a Virtual Private Network is. one must understand the
meanings oI Private Network and Public Network (or commonly reIerred as Internet)
Iirst.
1.3.1 Private Network
Private networks are wide area networks that connect geographically dispersed
LANs. usually between oIIice and branch oIIices and/or remote PC clients. The
connection is usually a main telecommunication line or a backbone consisting oI leased
lines or dedicated Iiber. LAN-to-LAN or point-to-point connections are sometimes
handled by Irame relay. Ironically. private networks share the sane telecommunications
inIrastructure as the Internet. However. private network lines cost considerably more
than standard telephone lines because they are conIigured Ior higher speeds and greater
bandwidth. Private networks also require another crucial inIrastructure component
called private dial-in access system. which resides at the central site. Access systems
include communication servers. modem banks and toll-Iree telephone numbers. Access
to the private network Irom remote-locations can be accommodated by standard dial-up
or digital telephone lines such as ISDN (Integrated Services Digital Network) or DSL
(Digital Subscriber Line) lines. An illustration oI private network is shown in .
Higher perIormance. speed and security are obvious advantages oI a private
network. Private networks also support a variety oI protocols such as Irame relay.
Asynchronous Transmission Mode (ATM) and TCP/IP as well. However. private
networks can be incredibly expensive. A large enterprise planning to connect many
oIIices located globally via a Iiber-optic telecommunications backbone can literally
spend hundreds oI million oI dollars on the resulting network.
Embedded Virtual Private Network: PerIormance and Scalability
6
Figure 1. Private Aetworking
1.3.2 Internet
Every computer connected to the Internet is part oI a network. even the one in
your home. For example. you may use a modem and dial a local number to connect to
an Internet Service Provider (ISP). At work. you may be part oI a local area network
(LAN). but you most likely still connect to the Internet using an ISP that your company
has contracted with. When you connect to your ISP. you become part oI their network.
The ISP may then connect to a larger network and become part oI their network. The
Internet is simply a network oI networks.
Most large communications companies have their own dedicated backbones
connecting various regions. In each region. the company has a Point oI Presence (POP).
The POP is a place Ior local users to access the company's network. oIten through a
local phone number or dedicated line. The amazing thing here is that there is no overall
controlling network. Instead. there are several high-level networks connecting to each
other through Network Access Points or NAPs. Dozens oI large Internet providers
Embedded Virtual Private Network: PerIormance and Scalability
7
interconnect at NAPs in various cities. and trillions oI bytes oI data Ilow between the
individual networks at these points. The Internet is a collection oI huge corporate
networks that agree to all intercommunicate with each other at the NAPs. In this way.
every computer on the Internet connects to every other (as shown in Figure 2).
With such openness and Ilexibility. Internet introduces many new possibilities.
as well as threats. Since security was not take into account during the design oI the
underlining protocol oI Internet. TCP/IP. thus without security measures implemented.
communications on Internet is not secure at all it`s possible that somebody is
viewing/intercepting/modiIying/Iorging you and your inIormation at anytime anywhere
in the world. Comparing to the private network and Internet. private network use and
deployment is expensive; the Internet is not. Private networks are secure. while the
Internet is notoriously insecure. Private networks guarantee perIormance and a level oI
reliability; the Internet guarantee redundancy and availability. Private networks support
multiple WAN protocols; the Internet supports only TCP/IP. Private networks are
exclusive. rigid. and not easily scalable; the Internet is ubiquitous. Ilexible. and easily
scalable. with virtually unlimited potentials.
Figure 2. Internet Infrastructure - when vou connect to the Internet, vour computer
becomes part of the Aetwork. [33]
Embedded Virtual Private Network: PerIormance and Scalability
8
1.3.3 Virtual Private Network
A Virtual Private Network (VPN) is a private data network that makes use oI the
public telecommunication inIrastructure. maintaining privacy through the use oI a
tunneling protocol and security procedures. To understand Virtual Private Network Iully.
each oI the words in the name must be looked separately. Jirtual. in this case. means
dynamic and possibly changing. as opposed to the static hardwired network that we
normally would think oI. The idea oI a VPN is to make it appear to the hosts on each
end oI the connection. that they are part oI the same network. connected by a traditional
hardwired network. even though they are communicating over the public Internet. The
word Private in Virtual Private Network is a little harder to accurately deIine. Its
general meaning is that communications Irom each oI the endpoints to the other is
encrypted and is thereIore protected Irom snooping and tampering. Other deIinitions oI
a VPN are 'a communications environment in which access is controlled to permit peer
connections only within a deIined community oI interest. and is constructed though
some Iorm oI partitioning oI a common underlying communications medium. where this
underlying communications medium provides services to the network on a non-
exclusive basis. and 'a private network constructed within a public network
inIrastructure. such as the global Internet.
Figure 3. Jirtual Private Aetworks [34]
Embedded Virtual Private Network: PerIormance and Scalability
9
There are two common VPN types:
Remote-access - Also called a Virtual Private Dial-up Network (VPDN). this is a user-
to-LAN connection used by a company that has employees who need to connect to the
private network Irom various remote locations. Typically. a corporation that wishes to
set up a large remote-access VPN will outsource to an Enterprise Service Provider
(ESP). The ESP sets up a network access server (NAS) and provides the remote users
with desktop client soItware Ior their computers. The telecommuters can then dial a toll-
Iree number to reach the NAS and use their VPN client soItware to access the corporate
network.
A good example oI a company that needs a remote-access VPN would be a large
Iirm with hundreds oI sales people in the Iield. Remote-access VPNs permit secure.
encrypted connections between a company's private network and remote users through a
third-party service provider.
Site-to-site - Through the use oI dedicated equipment and large-scale encryption. a
company can connect multiple Iixed sites over a public network such as the Internet.
Site-to-site VPNs can be either:
Intranet-based - II a company has one or more remote locations that they wish to
ioin in a single private network. they can create an intranet VPN to connect LAN
to LAN.
Extranet-based - When a company has a close relationship with another
company (Ior example. a partner. supplier or customer). they can build an
extranet VPN that connects LAN to LAN. and that allows all oI the various
companies to work in a shared environment.
Embedded Virtual Private Network: PerIormance and Scalability
10
OI these 2 common types oI VPNs. there are 4 important VPN technologies exist:
Trusted VPNs
Secure VPNs
Hybrid VPNs
Provider-provisioned VPNs
Trusted VPNs
A VPN customer trusting the VPN provider to maintain the integrity oI circuits
and to use the best available business practices to avoid snooping oI the network traIIic.
It oIIers no real security.
Secure VPNs
VPNs that are constructed using encryption are called Secure VPNs. Encrypted
traIIic acts like it is in a tunnel between the two networks: even iI an attacker can see the
traIIic. they cannot read it. and they cannot change the traIIic without the changes being
seen by the receiving party and thereIore reiected.
Hybrid VPNs
A Secure VPN can be run as part oI a Trusted VPN. thus creating the third type
oI VPN: Hybrid VPNs. The secure parts oI a hybrid VPN might be controlled by the
customer (such as by using secure VPN equipment on their sites) or by the same
provider that provides the trusted part oI the hybrid VPN. Sometimes an entire hybrid
VPN is secured with the secure VPN. but more commonly. only a part oI a hybrid VPN
is secure.
Provider-Provisioned VPNs
VPNs that are administered by a service provider are called Provider-
Provisioned VPNs. All initiations and maintenances oI a Provider-Provisioned VPN are
done by someone other than the user oI the VPN.
Embedded Virtual Private Network: PerIormance and Scalability
11
1.3.3.1 Topologies
There are diIIerent topologies oI VPN depending on the application. Below
illustrates three basic varieties oI VPN topologies.
1.3.3.1.1 Host-to-Host
Host-to-Host VPN topology is the simplest implementation involving only two
end point computers. Figure 4 illustrates this setup - 2 hosts connected together via the
Internet thru their Local Area Network.
Figure 4: Host-to-Host JPA
Embedded Virtual Private Network: PerIormance and Scalability
14
1.4 What is Embedded Virtual Private Network (eVPN)
With the availability oI the broadband networks into general public usage and
the local residences. it is expected that embedded systems will soon be widely in use. In
the public Internet. security issues will become a bottleneck Ior such applications. The
Embedded Virtual Private Network (eVPN) is a solution Ior such dilemma.
Embedded Virtual Private Network is not a standard it is a proposed design
and architecture oI integrating the concept oI embedded systems with Virtual Private
Network (VPN). It oIIers numerous advantages over the existing conventional VPN
technologies:
Multi-platIorms eVPN supports multi-platIorms deployment. making
interoperability possible
Multiple-protocols eVPN supports almost every single VPN/tunneling
protocols. solving the problem oI interoperability with ease
Remote conIigurations eVPN can be conIigured anywhere in the world by
the user. with simple procedures via web browsers
Plug-n-Play eVPN is a selI-conIigurable device. take the conIiguration
problems away Irom the user
Embedded Virtual Private Network: PerIormance and Scalability
15
1.5 eVPN Goals
The eVPN proiect outlines the requirements. design and implementation issues
oI an Embedded Virtual Private Network (eVPN) system. and attempts to oIIer a
comprehensive design. architecture and implementation Ior sych system.
This proiect is undertaken by 3 soItware engineering students. Eric Chan. Chun
Ko and Jerome Lau under the supervision oI Dr. Xue Li. Although it is only in its Iirst
year oI running. but the development this interesting and yet challenging proiect will
surely be continued by other students in the Iuture.
The goals oI the eVPN proiect are used as the guidelines Ior each participating
student`s thesis. At such an early stage oI the proiect. it is divided into 3 maior sections:
PerIormance and Scalability oI eVPN
Architecture oI eVPN
Key Management oI eVPN
These areas are being researched and analyzed by students Eric Chan. Chun Ko
and Jerome Lau respectively. Each participating student is to apply the proiect goals to
their own subsection. and oIIer a comprehensive design oI eVPN system by integrating
them together.
Another important goal Ior this proiect is the development oI a prototype system
Ior eVPN.This model will Iorm the basis oI the eVPN system and Iurther development
will evolve Irom it.
Embedded Virtual Private Network: PerIormance and Scalability
16
1.6 Thesis Goal
The goal oI my thesis is to research and analyze the perIormance and scalability
issues oI eVPN. This includes an in-depth investigation on all existing VPN
technologies and protocols.
PerIormance and scalability are the maior concerns Ior the design oI eVPN. For
perIormance. 3 requirements are particularly Iocused:
Speed
Security Level
Quality oI Service
Speed
Speed is the most primary concern Ior eVPN it is the easiest Iorm oI
perIormance that an user can detect and notice. Finding a solution Ior constructing the
eVPN system in order to provide Iast connections to end users is the goal oI this area.
Notice that the speed` and scalability oI the system are deeply related to each other.
Security Level
The degree oI security is another maior design issue Ior eVPN. All security
requirements such as authentication. cryptography must be considered careIully and
thoroughly in order to provide saIe and secure eVPN services to the users.
Quality oI Service
The quality oI service Iocuses on the reliability and connectivity oI eVPN
system. How the eVPN system should be designed and implemented to minimize the
loss oI data and connections is the task Ior this section.
Embedded Virtual Private Network: PerIormance and Scalability
17
On the other hand. the scalability oI eVPN mainly Iocuses on 2 areas:
Scalability oI eVPN architecture
Scalability oI eVPN under operation
Scalability oI eVPN architecture
II new VPN protocols and services are invented or developed. how should they
be appended into the existing eVPN system? Devising suitable algorithms Ior the
scaling oI eVPN system is the goal Ior this section.
Scalability oI eVPN under operation
How the eVPN system should be designed in order to accommodate large
number oI users without compromising the perIormance is the main Iocus oI this
section.
PerIormance and Scalability are the two maior design issues oI eVPN they are
deeply related and must not be separated Irom each other. Analysis and evaluation oI
this 2 issues must be carried out careIully and thoroughly in order to provide a complete
and ideal design Ior eVPN.
Embedded Virtual Private Network: PerIormance and Scalability
18
1.7 Thesis Overview
The remainder oI this thesis explores the Iollowing areas in more detail.
1.7.1 Literature Review
This section outlines the existing VPN technologies developed. Details and
characteristics oI each technology will be discussed thoroughly. It also describes the use
oI the technologies and ways in which they are related to the eVPN proiect.
1.7.2 Design and Architecture of eVPN
This section outlines the design and architecture oI the eVPN system proposed
by the eVPN proiect members. It will be discussed comprehensively to provide an
insight view oI the system.
1.7.3 Implementation
This section outlines how the eVPN prototype system was implemented. All
instructions and procedures that are necessary Ior redeveloping the system will be
included.
1.7.4 Analysis and Recommendations
This section describes the recommend solutions to the PerIormance and
Scalability issues oI the eVPN design. It also relates to the architecture and key
management issues oI eVPN which are described by other two participating members.
Embedded Virtual Private Network: PerIormance and Scalability
19
1.7.5 Evaluation
This section outlines how much oI a success the proiect is. It discusses the
proiect and thesis goals and relates these to the implementation.
1.7.6 Future Work
This section describes what possible Iuture work that can be implemented to the
existing proiect and system.
1.7.7 Conclusion
This section summarizes the eVPN proiect.
Detail background discussions on intro and background can be found in.
[1]. [2]. [3]. [4]. [5]. [6]. [7]. [26]. [28]. [29]. [30]. [33]. [34]
Embedded Virtual Private Network: PerIormance and Scalability
20
2. Literature Review
Although both TCP and UDP are transport layer protocols. but there are many
diIIerences exist between them:
UDP is a connectionless protocol. This means it does not perIorm retransmission
oI data and thereIore provides very Iew error recovery services. UDP instead
oIIers a direct way to send and receive datagrams (packets) over the network; it
is more suitable Ior broadcasting messages. multi-media data
TCP. on the other hand. provides a connection-based. reliable data stream.
(Whereas the IP protocol deals only with packets. TCP enables two hosts to
establish a connection and exchange streams oI data.) TCP guarantees delivery
oI data and also guarantees that packets will be delivered in the same order in
which they were sent.
Embedded Virtual Private Network: PerIormance and Scalability
24
A table summarizing the similarities and diIIerences between TCP and UDP is shown
below:
TCP UDP
Connection-oriented Connectionless
Checks Ior error No error checking
Guarantee Delivery Does not Guarantee Delivery
Maintain order oI delivery
Packets may arrive out oI
order
High reliability Low reliability
Retransmit packet oI errors
occur
No resending oI packets
Stream-oriented Packets-oriented
Has Ilow-control No Ilow control
Suitable Ior non-streaming
data transIer (e.g. File
TransIer)
Suitable Ior streaming data
transIer
(e.g. Online video streams)
Not suitable Ior multicasting Suitable Ior multicasting
Duplex Duplex
Not as Iast as UDP Faster than TCP
Large overheads Minimal overheads
1able 1. 1CP vs UDP
-
As opposed to PPTP. L2F (Layer 2 Forwarding) is the tunneling solution
developed by Cisco is 1996. As its name suggested. L2F protocol permits the tunneling
oI the link layer (layer 2 in the OSI model) oI higher-level protocols. Using such
tunnels. it is possible to divorce the location oI the initial dial-up server Irom the
location at which the dial-up protocol connection is terminated and access to the
network provided.
Embedded Virtual Private Network: PerIormance and Scalability
27
L2F`s essential diIIerence Irom PPTP is the ability to use protocols at layer 2 oI
the network protocol stack Ior tunneling purpose. including ATM (Asynchronous
TransIer Mode) and Frame Relay. In the basic setup. the user makes a PPP or similar
connection to a local ISP. At the request oI the user. the NAS. using the L2F soItware.
initiates a tunnel to the user`s destination. The end point that is. the corporate router
running L2F strips oII the tunneling headers. logs the traIIic and allows
communication to take place.
Although L2F oIIers many beneIits such as:
Protocol Independence (e.g. IPX. SNA)
Media Independence (e.g. ATM. X.25. Frame Relay)
Accounting
However. there are also some maior Ilaws exist. Since L2F`s intended usage is Ior
hardware switches and routers. the authentication and encryption schemes are not
implemented as well as it should be. And that`s the reason why L2TP and IPSec comes
into play.
$
IPSec stands Ior IP security. perhaps it is the most widely recognizable and
employed tunneling protocols exist currently. IPSec is a Iramework oI open standards
that provides data conIidentiality. data integrity. and data authentication between
participating peers.
IPSec provides its service at the network layer. and uses several technologies Ior
establishing a VPN. such as:
DiIIie-Hellman key exchange
Digital Signatures
DES encryption
Keyed hash algorithm
Basically. IPSec provides security with 2 steps:
1. Encapsulate an IP packet by wrapping another packet around it
2. Encrypt the result
And the IP packets are encrypted through the Iollowing steps:
1. Original packet includes unencrypted header and data
2. The original packet is encapsulated with another header and space Ior
a message digest to serve as checksum
3. The checksum is created by Iollowing a message-digest Iormula
4. The entire packet is encrypted and transIerred to the destination
Embedded Virtual Private Network: PerIormance and Scalability
30
IPSec has two modes oI operation transport mode and tunnel mode:
Transport Mode
The transport mode oI IPSec can be used only when security is desired end to
end. When security is not enabled. transport layer packets such as TCP and UDP Ilow
into the network layer. IP. which adds the IP header and calls into the data link layer.
When security in transport layer is enabled. the transport layer packets Ilow into the
IPSec component. The IPSec component is implemented as part oI the network layer
(when integrated with OS). The IPSec component adds the AH. ESP. or both headers.
and invokes the part oI the network layer that adds the network layer header.
Tunnel Mode
IPSec in tunnel mode is normally used when the ultimate destination oI the
packet is diIIerent Irom the security termination point. The tunnel mode is used in cases
when security is provided by a device that did not originate packets - as in the case oI
VPNs. or when the packet needs to be secured to a destination that is diIIerent Irom the
actual destination.
IPSec established its outstanding position as the best tunneling protocol when it
was integrated as part oI the MicrosoIt Windows 2000 release and included as a
mandatory part oI the Ipv6 implementation. Because oI its growing popularity and
usage. many open source IPSec implementation Ior operating systems other than
MicrosoIt are emerged. One oI the most successIul implementation is the FreeS/WAN
VPN Ior Linux.
Although IPSec is such a widely recognizable and employed tunneling protocol.
but does this mean it has no weakness at all? In paper Cryptographic Evaluation oI
IPSec` # by Niel Ferguson and Bruce Schneier. IPSec is criticized to be too complex.
IPsec contains too many options and too much exibility; there are oIten several ways oI
doing the same or similar things - the complexity has lead to a large number oI
Embedded Virtual Private Network: PerIormance and Scalability
31
ambiguities. contradictions. ineIIiciencies. and weaknesses. Another disadvantages oI
IPSec is the interoperability currently. only MicrosoIt`s operating systems have
included IPSec along their release; iI users want to employ IPSec on other operating
systems. it can be an annoying and complex procedure (e.g. compiling Linux Kernel).
Figure 9. IPSec in 1unnel Mode
2.2.1.5 MPLS
Multiple Protocol Layer Switching (MPLS) is an IETF (Internet Engineering
Task Force) standardized label distribution protocol proposed by Cisco in 2001.
Basically. MPLS is a packet-Iorwarding technology which uses labels to make data
Iorwarding decisions. With MPLS. the Layer 3 header analysis is done iust once (when
the packet enters the MPLS domain). Label inspection drives subsequent packet
Iorwarding. Additionally. it decreases the Iorwarding overhead on the core routers.
MPLS technologies are applicable to any network layer protocol.
By providing better perIormance and scalability over all existing VPN
technologies. MPLS is regarded as the replacement and standard oI VPN applications in
the Iuture.
Embedded Virtual Private Network: PerIormance and Scalability
32
2.2.2 Non-Standard Tunneling Protocols
Non-standard Tunneling Protocols Protocols that are developed by small
companies/individuals. usually not widely used by the public.
2.2.2.1 OpenVPN
OpenVPN is an open source proiect developed by networking expert James
Yonan this implementation was the winner oI openChallenge in 2001. Fundamentally.
OpenVPN is a conIigurable VPN (Virtual Private Network) daemon which can be used
to securely link two or more private networks using an encrypted tunnel over the
Internet.
There are many distinguishable Ieatures implemented in OpenVPN:
OS independent it can be run on Linux. Solaris. OpenBSD.
FreeBSD. and MAC OS X
It uses industrial-strength security model designed to protect against
both active and passive attacks. OpenVPN's security model is similar
to that oI IPSec but with a much lighter Iootprint and no kernel or IP
stack modiIication requirements.
OpenVPN uses OpenSSL PKI Ior session authentication. the TLS
protocol Ior key exchange and the HMAC algorithm Ior
authenticating tunnel data
However. there are also disadvantages associated with OpenVPN since
OpenVPN operates in a high layer oI session layer. it adds a Iair amount oI overheads to
the packets and hence seriously reducing the network throughput. in other words.
downgrading the perIormance oI the network.
Embedded Virtual Private Network: PerIormance and Scalability
33
2.2.2.2 cIPE
Crypto IP Encapsulation (cIPE) is a simple. lightweight package that provides
Ior tunneling oI encrypted IP packets over UDP. At present. CIPE can be run on both
Linux and MicrosoIt Windows. making interoperability possible. Features oI CIPE
include:
Supports dynamic addresses
NAT Network Address Translation
SOCKS proxies
Similar to OpenVPN. CIPE provides its services in session layer Iair amount
oI overheads exist and hence degrading the network perIormance.
2.2.3 Comparisons
There are many tunneling protocols exist they can be categorized into two
categories: Standard Tunneling Protocols and Non-Standard Protocols. The 2 tables
shown below summarizes all tunneling protocols (except MPLS it is not part oI the
scope Ior the eVPN design) discussed in previous sections:
Layer NAT
Behind
Firewall
Multiple
Protocols
SOCK
PPTP Link
Not
Supported
Not
Supported
Not
Supported
Not
Supported
L2F Link
Not
Supported
Not
Supported
Supported
Not
Supported
L2TP Link
Not
Supported
Not
Supported
Supported
Not
Supported
IPSec Network
Not
Supported
Not
Supported
Not
Supported
Not
Supported
OpenVPN Session Supported Supported Supported Supported
CIPE Session Supported Supported Supported Supported
1able 2a. 1unneling Protocols
Embedded Virtual Private Network: PerIormance and Scalability
34
Overhead Encryption Authentication
PPTP Small Weak Weak
L2F Small Weak Weak
L2TP Small Medium Medium
IPSec Medium Strong Strong
OpenVPN High Strong Strong
CIPE High Strong Strong
1able 2b. 1unneling Protocols
Embedded Virtual Private Network: PerIormance and Scalability
35
2.3 Key Management
The proposed eVPN device should be compact and portable. It should only
contains minimal amount oI system resource such as memory. and all eVPN services
can be achieved by allowing the device to dynamically download and update protocols
and other related inIormation Irom the Internet. It can be actively controlled by a user.
or passively iust providing end services to authenticated users. Ior example. a web-
enabled camera Ior traIIic monitoring system.
To protect against unauthorized usage. each eVPN device is associated with a
unique serial number - this serial number is used in the authentication scheme.
3.1.1.1 Authentication Scheme
Authentication is the key requirement Ior every security system. Authentication
scheme must be designed and implemented cautiously and entirely to ensure the
conIidentiality. integrity and availability oI inIormation and services. Since eVPN is
such an open and scalable system. authentication scheme must be employed.
Each eVPN device contains a unique identiIier - serial number. Along with
public key and digital certiIicate. the three oI them Iorm the basis oI the components
used in the authentication scheme. The authentication scheme is described below:
1. On initialization. each eVPN device will generate two keys automatically:
i. Private key must be kept secret and must not be unveiled in
any circumstances
Embedded Virtual Private Network: PerIormance and Scalability
39
ii. Public key can be sent across network Ior authentication
purpose. open to everybody
2. eVPN device sends its public key to CertiIicate Authority to obtain a Digital
CertiIicate
3. eVPN device connects to the eVPN Central Server through predeIined login
module
4. Establish VPN connection with the desired device
(Step 1 will only be perIormed on its Iirst connection/when the digital certiIicate has
expired)
This authentication scheme Iollows the Public Key InIrastructure (PKI). Please
reIer to paper Embedded Virtual Private Network Key Management` by Jerome Lau
Ior a more detailed version.
3.1.1.2 Configuration and Services
Once the eVPN device has been authenticated. it will be able to perIorm its
desired operation. Depending on its nature. conIiguration may be required.
The proposed eVPN device is intelligent - aIter analyzing the setup and
connection. it will be able to make all the necessary conIigurations automatically. For
example. iI the desired tunneling protocol Ior the connection is not supported. the eVPN
device will download all mandatory Iiles and packages. and perIorm the installation
automatically. AIter Iinishing this automated procedure. the eVPN device can perIorm
the desired operation with maximum eIIiciencies and perIormance with the established
connection.
Recommendations to the choice oI tunneling protocol Ior eVPN connection are
presented in the section 5 oI this paper. Please reIer to paper Embedded Virtual Private
Embedded Virtual Private Network: PerIormance and Scalability
40
Network Architecture` by Chun Ko Ior a in-depth discussion on the conIiguration oI
eVPN device.
3.1.2 eVPN Central Server
The eVPN Central Server is responsible Ior several tasks in the system. They are
described in the Iollowing pages.
3.1.2.1 Authentication
The eVPN Central Server must be able to authenticate multiple eVPN devices.
Device`s public key. password (generated using eVPN device`s serial-number) and
digital certiIicate must be veriIied iI any oI them Iails during the authentication
process. its request will be reiected; iI the device is successIully authenticated. the
request will be recorded.
3.1.2.2 Access Control
Access control is also one oI the many tasks that the eVPN Central Server
perIorms. Access control is probably the central Iunction oI computer security
conIidentiality. integrity and availability all concern the prevention oI certain types oI
access.
In eVPN system. once an eVPN device is authenticated. its request will be
checked against the ACL (Access Control List) stored in the central server. An ACL
describes which obiects have access to which obiects/subiects. and what sort oI access
privileges. II the request is valid. the eVPN Central Server will connect to the target
eVPN device - note that the automated conIiguration. authentication scheme and access
control validation must also be perIormed on the target device.
Embedded Virtual Private Network: PerIormance and Scalability
41
3.1.2.3 Session Tracking
Session tracking is yet another duty responsible Ior eVPN Central Server. Once
the automated conIiguration. authentication scheme and access control validation has
been perIormed on both parties. a VPN connection can be established.
All VPN connections are recorded by the eVPN Central Server by tracking all
existing sessions. the central server can utilizes this inIormation to enhance the overall
perIormance and scalability oI the system. as well as perIorming actions such as port
conIigurations. At the end oI the each VPN connection. the eVPN Central Server will
update its database with the new inIormation oI the eVPN devices.
Embedded Virtual Private Network: PerIormance and Scalability
42
4.0 Implementation
A prototype eVPN system is implemented by eVPN proiect team. This section
describes all relevant details regarding system.
4.1 System Architecture
The eVPN prototype is implemented under Linux operating platIorm. A
minimum oI 3 computers are required Ior the setup - 1 workstation will act as the
central management system. network traIIic monitor and providing key management
services. while the other 2 gateway machines on either side oI the network will act as an
eVPN device; additional computers can be integrated into the system by placing them
behind the gateways (act as host machine).
A tunnel is setup between the two gateways using OpenVPN (or FreeS/WAN
IPSec) to provide secure communications over an insecure channel. Streaming and non-
streaming data packets can be transIerred across the network with the conIidentiality.
availability and integrity ensured. The system layout is illustrated in Figure 11:
Workstation Embedded VPN #2
Monitor/Centre Server
Embedded VPN #1 Workstation
192.168.1.0/24
192.168.0.0/24
10.0.0.0/24 10.0.1.0/24
Video
.1.2
1.1. .0.1
.0.2
.0.254 .0.1 .1.254 .1.1
Figure 11. Architecture of eJPA prototvpe svstem
Embedded Virtual Private Network: PerIormance and Scalability
43
The middle computer (reIerred to as the Internet machine. with IP 192.168.0.1
and 192.168.1.1) has two network interIaces and is acting as an Internet router. It also
served as the CertiIication Authority to sign certiIicates Ior the VPN computers/devices.
Since this machine behaves as the public Internet. it will also perIorm traIIic monitoring
and 'packet sniIIing. This computer has been implemented using Linux platIorm.
Embedded VPN#1 and Embedded VPN#2 are two VPN gateways that provide
all necessary security support to the two 10.0.X.X internal networks. Both FreeS/Wan
IPsec and OpenVPN are enabled to provide host-host. host-network and network-
network topology VPN systems.
4.2 System Requirements
The hardware and soItware requirements Ior the eVPN prototype system is listed
in the Iollowing table:
CPU Pentium III or equivalent class
RAM 256 mb
Hardrive Space 4 GigaBytes
Others 2 Network InterIace Card
1able 3. Hardware Requirements for eJPA prototvpe svstem
OS Linux Redhat 7.2
SoItware Packages OpenSSL http://www.openssl.org
OpenSSH http://www.openssh.org
FreeS/WAN IPSec http://www.Ireeswan.org
PHP http://www.php.net
Apache Web Server http://www.apache.org
OpenVPN http://openvpn.sourceIorge.net
MPEG4IP Video Streaming Package
http://mpeg4ip.sourceIorge.net/
IPGrab http://ipgrab.sourceIorge.net
1able 4. Software Requirements for eJPA prototvpe svstem
Embedded Virtual Private Network: PerIormance and Scalability
44
4.3 Setting up the System
In order Ior the eVPN prototype system to Iunction Ilawlessly. all hardware and
soItware requirements described in the previous section must be IulIilled. With the
diIIerent Iunctionalities provided by the monitoring machine and the 2 VPN gateways.
diIIerent setups are applied to them.
On all machines. install:
openSSL provides security modules
openSSH provides security modules
On the monitoring machine. install:
IPGrab provides all monitoring Iunctions
Apache provides web services
PHP provides dynamic web page generation
On the VPN gateways. install:
OpenVPN provides tunneling in session layer
FreeS/WAN provides tunneling in network layer
MPEG4IP provides video streaming modules
Detail descriptions oI the installation procedure are attached to the Appendices section.
Embedded Virtual Private Network: PerIormance and Scalability
45
5.0 Analysis and Recommendations
This section outlines the analysis perIormed using the results obtained Irom tests
carried out on the prototype system described in Section 4. Recommendations to
perIormance and scalability issues oI the eVPN design are also described in this section.
5.1 Performance Test
Similar to IPSec. the perIormance oI OpenVPN goes downhill as the packet size
grows. but in a much more dramatic scale. The time required Ior transmission grows
wildly aIter the packet size reaches 8192 bytes only two out oI thirty packets sent
were received when the packet is set to 16384 bytes. and the time required Ior those
transmissions are around 2 seconds; the remaining 28 packets are regarded as loss since
they took much longer than the speciIied interval oI ping` command to transmit. The
100 loss oI packets with packet size 32768 and 65507 can be explained with the
same reason they iust took too long to transmit even the ping` command stopped
waiting Ior them. This occurrence is totally unacceptable Ior eVPN as the overall
system perIormance will suIIer heavily undoubtedly.
Embedded Virtual Private Network: PerIormance and Scalability
49
5.2.3 Summary
Although the perIormance oI both IPSec and OpenVPN suIIer greatly as the
transmit packet size grows. but it is not diIIicult to see that which one has the more
catastrophic eIIect. The primary cause to such occurrence is the diIIerence in the layers
that the two protocols Iunction in: IPSec works in Network Layer whereas OpenVPN
works in Session Layer. IPSec perIorms its routines in a very deep level (kernel level)
oI the system the time required Ior operations such as encryption is kept as minimal as
possible; OpenVPN operates in a much higher level the need to call external soItware
packages (e.g. openSSL) Ior the necessary operations makes the perIormance suIIer
deeply. let alone the signiIicant amount oI overheads generated. Overall. IPSec is
absolutely the more preIerable choice oI tunneling protocol over OpenVPN.
5.3 Recommendations
This section describes the recommendations to the eVPN design and architecture
with the limitations to time and resources. the accuracy oI these recommendations
may be aIIected due to the assumptions and lack oI experimentations made during the
implementation.
5.3.1 Performance
Recommendations to the perIormance oI eVPN system are presented in this
section.
5.3.1.1 Transport Layer Protocols
Which one is better? TCP or UDP? With diIIerent Ieatures oIIered by the two
protocols. it`s an extremely diIIicult task to draw an absolute answer so generally
speaking. the answer is it depends`.
Embedded Virtual Private Network: PerIormance and Scalability
50
In eVPN. TCP and UDP can be employed Ior diIIerent purposes - when dealing
with applications that require high reliability and control. TCP will be the preIerable
choice; when dealing with applications where speed preIerred rather than reliability.
UDP is the more preIerable choice. Below is a list oI recommended applications Ior the
usage oI the two protocols:
TCP UDP
File TransIer. Online Transactions Streaming Audio/Video. Monitoring
Systems
1able 5. Recommended usages of 1CP and UDP
5.3.1.2 Tunneling Protocols
The results and analysis presented in section 5.1 and 5.2 have shown that
standard tunneling protocols are a much more preIerable choice Ior eVPN than non-
standard tunneling protocols.
PPTP. L2F. L2TP and IPSec are the primary considerations Ior eVPN. and out
oI these protocols. IPSec has proven to be the best solution. Although IPSec is criticized
to be too complex. but it oIIers by Iar the best security compare to other tunneling
protocols. One minor concern oI IPSec is the interoperability problem at present. only
MicrosoIt Windows have included IPSec as part oI their operating system release the
need Ior installation and compilation may prove to be a signiIicant issue to the eVPN
system. Nonetheless. enabling IPSec is strongly recommended to every eVPN device
and component in the eVPN architecture.
5.3.1.3 Key Management
Please reIer to paper Embedded Virtual Private Network Key Management`
Ior recommendations regarding key management issues.
Embedded Virtual Private Network: PerIormance and Scalability
51
5.3.2 Scalability
This section outlines the overall evaluation oI the eVPN proiect. The entire
evaluation is divided into 4 distinctive segments proiect evaluation. system evaluation
thesis evaluation and personal evaluation.
6.1 Project Evaluation
Did all eVPN proiect goals have been achieved? The answer is no but with
some partial successes. Although a generic design and architecture oI eVPN has been
proposed by the eVPN proiect team. but with the lack oI experimentations and
implementations. it is diIIicult to iudge rather it is successIul or not. The limitations to
time and resources can be concluded as the contributing Iactors oI such happening. as
they restrict the possibility oI Iurther developments. However. this proiect should be
served as the guidelines and basis oI any evolutions oI eVPN.
6.2 System Evaluation
The development oI an eVPN prototype system is one oI the maior goals oI the
proiect. As stated previously. the lack oI time and resources restricts the possibility oI
any advanced development oI the system. Because oI eVPN`s special requirements.
University oI Queensland had not been able to oIIer any resources at all throughout the
proiect.
The current state oI the eVPN prototype system is very generic a minimum oI
3 computers is required Ior such implementation no eVPN device and eVPN Central
Server are implemented in place. let alone the proposed eVPN Ieatures. Given more
time and resources. the overall system state should be much more advanced compare to
the present status. The recommended Iurther developments are discussed in Section 7 oI
this document.
Embedded Virtual Private Network: PerIormance and Scalability
55
6.3 Thesis Evaluation
This thesis is partially successIul the obiectives have only partially achieved.
The goal oI this thesis is the research and analysis oI the PerIormance and
Scalability issues oI eVPN as the consequences oI the limitations mentioned. only the
perIormance issues were being successIully researched and analyzed.
The study oI perIormance oI transport layer protocols and tunneling Protocols is
the one oI the primary obiectives Ior this thesis. and it had been successIully carried out
through researching and testing - results and analysis oI the perIormance are used to
draw out the recommendations presented.
On the other hand. the study oI scalability is rather a disappointing area to this
thesis no physical tests and implementations regarding this area were actually
developed. and again. due to the limitations oI the eVPN proiect. All recommendations
presented are only based on assumptions and theoretical analysis.
6.4 Personal Evaluation
Insecure Channel
PING 192.168.1.2 (192.168.1.2) from 192.168.0.2 : 8(36) bytes of data.
16 bytes from 192.168.1.2: icmp_seq=0 ttl=254 time=334 usec
16 bytes from 192.168.1.2: icmp_seq=1 ttl=254 time=241 usec
16 bytes from 192.168.1.2: icmp_seq=2 ttl=254 time=249 usec
16 bytes from 192.168.1.2: icmp_seq=3 ttl=254 time=262 usec
16 bytes from 192.168.1.2: icmp_seq=4 ttl=254 time=248 usec
16 bytes from 192.168.1.2: icmp_seq=5 ttl=254 time=195 usec
16 bytes from 192.168.1.2: icmp_seq=6 ttl=254 time=230 usec
16 bytes from 192.168.1.2: icmp_seq=7 ttl=254 time=243 usec
16 bytes from 192.168.1.2: icmp_seq=8 ttl=254 time=267 usec
16 bytes from 192.168.1.2: icmp_seq=9 ttl=254 time=235 usec
16 bytes from 192.168.1.2: icmp_seq=10 ttl=254 time=237 usec
16 bytes from 192.168.1.2: icmp_seq=11 ttl=254 time=232 usec
16 bytes from 192.168.1.2: icmp_seq=12 ttl=254 time=235 usec
16 bytes from 192.168.1.2: icmp_seq=13 ttl=254 time=250 usec
16 bytes from 192.168.1.2: icmp_seq=14 ttl=254 time=230 usec
16 bytes from 192.168.1.2: icmp_seq=15 ttl=254 time=234 usec
16 bytes from 192.168.1.2: icmp_seq=16 ttl=254 time=229 usec
16 bytes from 192.168.1.2: icmp_seq=17 ttl=254 time=236 usec
16 bytes from 192.168.1.2: icmp_seq=18 ttl=254 time=251 usec
16 bytes from 192.168.1.2: icmp_seq=19 ttl=254 time=234 usec
16 bytes from 192.168.1.2: icmp_seq=20 ttl=254 time=240 usec
16 bytes from 192.168.1.2: icmp_seq=21 ttl=254 time=249 usec
16 bytes from 192.168.1.2: icmp_seq=22 ttl=254 time=235 usec
16 bytes from 192.168.1.2: icmp_seq=23 ttl=254 time=251 usec
16 bytes from 192.168.1.2: icmp_seq=24 ttl=254 time=231 usec
16 bytes from 192.168.1.2: icmp_seq=25 ttl=254 time=237 usec
16 bytes from 192.168.1.2: icmp_seq=26 ttl=254 time=229 usec
16 bytes from 192.168.1.2: icmp_seq=27 ttl=254 time=238 usec
16 bytes from 192.168.1.2: icmp_seq=28 ttl=254 time=251 usec
16 bytes from 192.168.1.2: icmp_seq=29 ttl=254 time=232 usec
--- 192.168.1.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 0.195/0.242/0.334/0.023 ms
PING 192.168.1.2 (192.168.1.2) from 192.168.0.2 : 64(92) bytes of data.
72 bytes from 192.168.1.2: icmp_seq=0 ttl=254 time=238 usec
72 bytes from 192.168.1.2: icmp_seq=1 ttl=254 time=262 usec
72 bytes from 192.168.1.2: icmp_seq=2 ttl=254 time=258 usec
72 bytes from 192.168.1.2: icmp_seq=3 ttl=254 time=264 usec
72 bytes from 192.168.1.2: icmp_seq=4 ttl=254 time=278 usec
72 bytes from 192.168.1.2: icmp_seq=5 ttl=254 time=256 usec
72 bytes from 192.168.1.2: icmp_seq=6 ttl=254 time=263 usec
72 bytes from 192.168.1.2: icmp_seq=7 ttl=254 time=255 usec
72 bytes from 192.168.1.2: icmp_seq=8 ttl=254 time=269 usec
72 bytes from 192.168.1.2: icmp_seq=9 ttl=254 time=285 usec
72 bytes from 192.168.1.2: icmp_seq=10 ttl=254 time=229 usec
72 bytes from 192.168.1.2: icmp_seq=11 ttl=254 time=272 usec
72 bytes from 192.168.1.2: icmp_seq=12 ttl=254 time=267 usec
72 bytes from 192.168.1.2: icmp_seq=13 ttl=254 time=274 usec
72 bytes from 192.168.1.2: icmp_seq=14 ttl=254 time=285 usec
72 bytes from 192.168.1.2: icmp_seq=15 ttl=254 time=231 usec
72 bytes from 192.168.1.2: icmp_seq=16 ttl=254 time=264 usec
72 bytes from 192.168.1.2: icmp_seq=17 ttl=254 time=261 usec
72 bytes from 192.168.1.2: icmp_seq=18 ttl=254 time=266 usec
72 bytes from 192.168.1.2: icmp_seq=19 ttl=254 time=278 usec
72 bytes from 192.168.1.2: icmp_seq=20 ttl=254 time=259 usec
72 bytes from 192.168.1.2: icmp_seq=21 ttl=254 time=263 usec
72 bytes from 192.168.1.2: icmp_seq=22 ttl=254 time=260 usec
72 bytes from 192.168.1.2: icmp_seq=23 ttl=254 time=264 usec
72 bytes from 192.168.1.2: icmp_seq=24 ttl=254 time=277 usec
72 bytes from 192.168.1.2: icmp_seq=25 ttl=254 time=258 usec
72 bytes from 192.168.1.2: icmp_seq=26 ttl=254 time=267 usec
72 bytes from 192.168.1.2: icmp_seq=27 ttl=254 time=259 usec
72 bytes from 192.168.1.2: icmp_seq=28 ttl=254 time=268 usec
Embedded Virtual Private Network: PerIormance and Scalability
78
72 bytes from 192.168.1.2: icmp_seq=29 ttl=254 time=280 usec
--- 192.168.1.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 0.229/0.263/0.285/0.022 ms
PING 192.168.1.2 (192.168.1.2) from 192.168.0.2 : 128(156) bytes of data.
136 bytes from 192.168.1.2: icmp_seq=0 ttl=254 time=272 usec
136 bytes from 192.168.1.2: icmp_seq=1 ttl=254 time=297 usec
136 bytes from 192.168.1.2: icmp_seq=2 ttl=254 time=301 usec
136 bytes from 192.168.1.2: icmp_seq=3 ttl=254 time=296 usec
136 bytes from 192.168.1.2: icmp_seq=4 ttl=254 time=307 usec
136 bytes from 192.168.1.2: icmp_seq=5 ttl=254 time=323 usec
136 bytes from 192.168.1.2: icmp_seq=6 ttl=254 time=312 usec
136 bytes from 192.168.1.2: icmp_seq=7 ttl=254 time=307 usec
136 bytes from 192.168.1.2: icmp_seq=8 ttl=254 time=300 usec
136 bytes from 192.168.1.2: icmp_seq=9 ttl=254 time=307 usec
136 bytes from 192.168.1.2: icmp_seq=10 ttl=254 time=321 usec
136 bytes from 192.168.1.2: icmp_seq=11 ttl=254 time=267 usec
136 bytes from 192.168.1.2: icmp_seq=12 ttl=254 time=300 usec
136 bytes from 192.168.1.2: icmp_seq=13 ttl=254 time=300 usec
136 bytes from 192.168.1.2: icmp_seq=14 ttl=254 time=300 usec
136 bytes from 192.168.1.2: icmp_seq=15 ttl=254 time=317 usec
136 bytes from 192.168.1.2: icmp_seq=16 ttl=254 time=299 usec
136 bytes from 192.168.1.2: icmp_seq=17 ttl=254 time=303 usec
136 bytes from 192.168.1.2: icmp_seq=18 ttl=254 time=302 usec
136 bytes from 192.168.1.2: icmp_seq=19 ttl=254 time=309 usec
136 bytes from 192.168.1.2: icmp_seq=20 ttl=254 time=326 usec
136 bytes from 192.168.1.2: icmp_seq=21 ttl=254 time=301 usec
136 bytes from 192.168.1.2: icmp_seq=22 ttl=254 time=307 usec
136 bytes from 192.168.1.2: icmp_seq=23 ttl=254 time=271 usec
136 bytes from 192.168.1.2: icmp_seq=24 ttl=254 time=300 usec
136 bytes from 192.168.1.2: icmp_seq=25 ttl=254 time=314 usec
136 bytes from 192.168.1.2: icmp_seq=26 ttl=254 time=301 usec
136 bytes from 192.168.1.2: icmp_seq=27 ttl=254 time=321 usec
136 bytes from 192.168.1.2: icmp_seq=28 ttl=254 time=305 usec
136 bytes from 192.168.1.2: icmp_seq=29 ttl=254 time=301 usec
--- 192.168.1.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 0.267/0.302/0.326/0.027 ms
PING 192.168.1.2 (192.168.1.2) from 192.168.0.2 : 256(284) bytes of data.
264 bytes from 192.168.1.2: icmp_seq=0 ttl=254 time=349 usec
264 bytes from 192.168.1.2: icmp_seq=1 ttl=254 time=390 usec
264 bytes from 192.168.1.2: icmp_seq=2 ttl=254 time=375 usec
264 bytes from 192.168.1.2: icmp_seq=3 ttl=254 time=371 usec
264 bytes from 192.168.1.2: icmp_seq=4 ttl=254 time=373 usec
264 bytes from 192.168.1.2: icmp_seq=5 ttl=254 time=376 usec
264 bytes from 192.168.1.2: icmp_seq=6 ttl=254 time=388 usec
264 bytes from 192.168.1.2: icmp_seq=7 ttl=254 time=380 usec
264 bytes from 192.168.1.2: icmp_seq=8 ttl=254 time=373 usec
264 bytes from 192.168.1.2: icmp_seq=9 ttl=254 time=373 usec
264 bytes from 192.168.1.2: icmp_seq=10 ttl=254 time=380 usec
264 bytes from 192.168.1.2: icmp_seq=11 ttl=254 time=391 usec
264 bytes from 192.168.1.2: icmp_seq=12 ttl=254 time=339 usec
264 bytes from 192.168.1.2: icmp_seq=13 ttl=254 time=372 usec
264 bytes from 192.168.1.2: icmp_seq=14 ttl=254 time=374 usec
264 bytes from 192.168.1.2: icmp_seq=15 ttl=254 time=376 usec
264 bytes from 192.168.1.2: icmp_seq=16 ttl=254 time=387 usec
264 bytes from 192.168.1.2: icmp_seq=17 ttl=254 time=374 usec
264 bytes from 192.168.1.2: icmp_seq=18 ttl=254 time=379 usec
264 bytes from 192.168.1.2: icmp_seq=19 ttl=254 time=378 usec
264 bytes from 192.168.1.2: icmp_seq=20 ttl=254 time=383 usec
264 bytes from 192.168.1.2: icmp_seq=21 ttl=254 time=387 usec
264 bytes from 192.168.1.2: icmp_seq=22 ttl=254 time=373 usec
264 bytes from 192.168.1.2: icmp_seq=23 ttl=254 time=373 usec
264 bytes from 192.168.1.2: icmp_seq=24 ttl=254 time=371 usec
264 bytes from 192.168.1.2: icmp_seq=25 ttl=254 time=376 usec
264 bytes from 192.168.1.2: icmp_seq=26 ttl=254 time=386 usec
264 bytes from 192.168.1.2: icmp_seq=27 ttl=254 time=374 usec
264 bytes from 192.168.1.2: icmp_seq=28 ttl=254 time=374 usec
264 bytes from 192.168.1.2: icmp_seq=29 ttl=254 time=372 usec
Embedded Virtual Private Network: PerIormance and Scalability
79
--- 192.168.1.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 0.339/0.375/0.391/0.023 ms
PING 192.168.1.2 (192.168.1.2) from 192.168.0.2 : 512(540) bytes of data.
520 bytes from 192.168.1.2: icmp_seq=0 ttl=254 time=483 usec
520 bytes from 192.168.1.2: icmp_seq=1 ttl=254 time=517 usec
520 bytes from 192.168.1.2: icmp_seq=2 ttl=254 time=529 usec
520 bytes from 192.168.1.2: icmp_seq=3 ttl=254 time=510 usec
520 bytes from 192.168.1.2: icmp_seq=4 ttl=254 time=509 usec
520 bytes from 192.168.1.2: icmp_seq=5 ttl=254 time=512 usec
520 bytes from 192.168.1.2: icmp_seq=6 ttl=254 time=523 usec
520 bytes from 192.168.1.2: icmp_seq=7 ttl=254 time=529 usec
520 bytes from 192.168.1.2: icmp_seq=8 ttl=254 time=517 usec
520 bytes from 192.168.1.2: icmp_seq=9 ttl=254 time=514 usec
520 bytes from 192.168.1.2: icmp_seq=10 ttl=254 time=520 usec
520 bytes from 192.168.1.2: icmp_seq=11 ttl=254 time=526 usec
520 bytes from 192.168.1.2: icmp_seq=12 ttl=254 time=531 usec
520 bytes from 192.168.1.2: icmp_seq=13 ttl=254 time=472 usec
520 bytes from 192.168.1.2: icmp_seq=14 ttl=254 time=514 usec
520 bytes from 192.168.1.2: icmp_seq=15 ttl=254 time=516 usec
520 bytes from 192.168.1.2: icmp_seq=16 ttl=254 time=519 usec
520 bytes from 192.168.1.2: icmp_seq=17 ttl=254 time=532 usec
520 bytes from 192.168.1.2: icmp_seq=18 ttl=254 time=483 usec
520 bytes from 192.168.1.2: icmp_seq=19 ttl=254 time=519 usec
520 bytes from 192.168.1.2: icmp_seq=20 ttl=254 time=510 usec
520 bytes from 192.168.1.2: icmp_seq=21 ttl=254 time=515 usec
520 bytes from 192.168.1.2: icmp_seq=22 ttl=254 time=528 usec
520 bytes from 192.168.1.2: icmp_seq=23 ttl=254 time=508 usec
520 bytes from 192.168.1.2: icmp_seq=24 ttl=254 time=512 usec
520 bytes from 192.168.1.2: icmp_seq=25 ttl=254 time=519 usec
520 bytes from 192.168.1.2: icmp_seq=26 ttl=254 time=513 usec
520 bytes from 192.168.1.2: icmp_seq=27 ttl=254 time=530 usec
520 bytes from 192.168.1.2: icmp_seq=28 ttl=254 time=514 usec
520 bytes from 192.168.1.2: icmp_seq=29 ttl=254 time=513 usec
--- 192.168.1.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 0.472/0.514/0.532/0.027 ms
PING 192.168.1.2 (192.168.1.2) from 192.168.0.2 : 1024(1052) bytes of data.
1032 bytes from 192.168.1.2: icmp_seq=0 ttl=254 time=763 usec
1032 bytes from 192.168.1.2: icmp_seq=1 ttl=254 time=802 usec
1032 bytes from 192.168.1.2: icmp_seq=2 ttl=254 time=802 usec
1032 bytes from 192.168.1.2: icmp_seq=3 ttl=254 time=816 usec
1032 bytes from 192.168.1.2: icmp_seq=4 ttl=254 time=794 usec
1032 bytes from 192.168.1.2: icmp_seq=5 ttl=254 time=797 usec
1032 bytes from 192.168.1.2: icmp_seq=6 ttl=254 time=797 usec
1032 bytes from 192.168.1.2: icmp_seq=7 ttl=254 time=801 usec
1032 bytes from 192.168.1.2: icmp_seq=8 ttl=254 time=812 usec
1032 bytes from 192.168.1.2: icmp_seq=9 ttl=254 time=804 usec
1032 bytes from 192.168.1.2: icmp_seq=10 ttl=254 time=798 usec
1032 bytes from 192.168.1.2: icmp_seq=11 ttl=254 time=794 usec
1032 bytes from 192.168.1.2: icmp_seq=12 ttl=254 time=798 usec
1032 bytes from 192.168.1.2: icmp_seq=13 ttl=254 time=817 usec
1032 bytes from 192.168.1.2: icmp_seq=14 ttl=254 time=767 usec
1032 bytes from 192.168.1.2: icmp_seq=15 ttl=254 time=808 usec
1032 bytes from 192.168.1.2: icmp_seq=16 ttl=254 time=798 usec
1032 bytes from 192.168.1.2: icmp_seq=17 ttl=254 time=802 usec
1032 bytes from 192.168.1.2: icmp_seq=18 ttl=254 time=812 usec
1032 bytes from 192.168.1.2: icmp_seq=19 ttl=254 time=795 usec
1032 bytes from 192.168.1.2: icmp_seq=20 ttl=254 time=807 usec
1032 bytes from 192.168.1.2: icmp_seq=21 ttl=254 time=800 usec
1032 bytes from 192.168.1.2: icmp_seq=22 ttl=254 time=807 usec
1032 bytes from 192.168.1.2: icmp_seq=23 ttl=254 time=819 usec
1032 bytes from 192.168.1.2: icmp_seq=24 ttl=254 time=802 usec
1032 bytes from 192.168.1.2: icmp_seq=25 ttl=254 time=803 usec
1032 bytes from 192.168.1.2: icmp_seq=26 ttl=254 time=761 usec
1032 bytes from 192.168.1.2: icmp_seq=27 ttl=254 time=796 usec
1032 bytes from 192.168.1.2: icmp_seq=28 ttl=254 time=812 usec
1032 bytes from 192.168.1.2: icmp_seq=29 ttl=254 time=794 usec
--- 192.168.1.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
Embedded Virtual Private Network: PerIormance and Scalability
80
round-trip min/avg/max/mdev = 0.761/0.799/0.819/0.024 ms
PING 192.168.1.2 (192.168.1.2) from 192.168.0.2 : 2048(2076) bytes of data.
2056 bytes from 192.168.1.2: icmp_seq=0 ttl=254 time=1.107 msec
2056 bytes from 192.168.1.2: icmp_seq=1 ttl=254 time=1.116 msec
2056 bytes from 192.168.1.2: icmp_seq=2 ttl=254 time=1.111 msec
2056 bytes from 192.168.1.2: icmp_seq=3 ttl=254 time=1.196 msec
2056 bytes from 192.168.1.2: icmp_seq=4 ttl=254 time=1.112 msec
2056 bytes from 192.168.1.2: icmp_seq=5 ttl=254 time=1.110 msec
2056 bytes from 192.168.1.2: icmp_seq=6 ttl=254 time=1.114 msec
2056 bytes from 192.168.1.2: icmp_seq=7 ttl=254 time=1.115 msec
2056 bytes from 192.168.1.2: icmp_seq=8 ttl=254 time=1.117 msec
2056 bytes from 192.168.1.2: icmp_seq=9 ttl=254 time=1.113 msec
2056 bytes from 192.168.1.2: icmp_seq=10 ttl=254 time=1.122 msec
2056 bytes from 192.168.1.2: icmp_seq=11 ttl=254 time=1.117 msec
2056 bytes from 192.168.1.2: icmp_seq=12 ttl=254 time=1.113 msec
2056 bytes from 192.168.1.2: icmp_seq=13 ttl=254 time=1.109 msec
2056 bytes from 192.168.1.2: icmp_seq=14 ttl=254 time=1.115 msec
2056 bytes from 192.168.1.2: icmp_seq=15 ttl=254 time=1.096 msec
2056 bytes from 192.168.1.2: icmp_seq=16 ttl=254 time=1.124 msec
2056 bytes from 192.168.1.2: icmp_seq=17 ttl=254 time=1.115 msec
2056 bytes from 192.168.1.2: icmp_seq=18 ttl=254 time=1.108 msec
2056 bytes from 192.168.1.2: icmp_seq=19 ttl=254 time=1.115 msec
2056 bytes from 192.168.1.2: icmp_seq=20 ttl=254 time=1.107 msec
2056 bytes from 192.168.1.2: icmp_seq=21 ttl=254 time=1.117 msec
2056 bytes from 192.168.1.2: icmp_seq=22 ttl=254 time=1.115 msec
2056 bytes from 192.168.1.2: icmp_seq=23 ttl=254 time=1.112 msec
2056 bytes from 192.168.1.2: icmp_seq=24 ttl=254 time=1.115 msec
2056 bytes from 192.168.1.2: icmp_seq=25 ttl=254 time=1.107 msec
2056 bytes from 192.168.1.2: icmp_seq=26 ttl=254 time=1.109 msec
2056 bytes from 192.168.1.2: icmp_seq=27 ttl=254 time=1.117 msec
2056 bytes from 192.168.1.2: icmp_seq=28 ttl=254 time=1.108 msec
2056 bytes from 192.168.1.2: icmp_seq=29 ttl=254 time=1.112 msec
--- 192.168.1.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 1.096/1.115/1.196/0.035 ms
PING 192.168.1.2 (192.168.1.2) from 192.168.0.2 : 4096(4124) bytes of data.
4104 bytes from 192.168.1.2: icmp_seq=0 ttl=254 time=1.478 msec
4104 bytes from 192.168.1.2: icmp_seq=1 ttl=254 time=1.491 msec
4104 bytes from 192.168.1.2: icmp_seq=2 ttl=254 time=1.496 msec
4104 bytes from 192.168.1.2: icmp_seq=3 ttl=254 time=1.501 msec
4104 bytes from 192.168.1.2: icmp_seq=4 ttl=254 time=1.496 msec
4104 bytes from 192.168.1.2: icmp_seq=5 ttl=254 time=1.507 msec
4104 bytes from 192.168.1.2: icmp_seq=6 ttl=254 time=1.495 msec
4104 bytes from 192.168.1.2: icmp_seq=7 ttl=254 time=1.498 msec
4104 bytes from 192.168.1.2: icmp_seq=8 ttl=254 time=1.496 msec
4104 bytes from 192.168.1.2: icmp_seq=9 ttl=254 time=1.503 msec
4104 bytes from 192.168.1.2: icmp_seq=10 ttl=254 time=1.502 msec
4104 bytes from 192.168.1.2: icmp_seq=11 ttl=254 time=1.504 msec
4104 bytes from 192.168.1.2: icmp_seq=12 ttl=254 time=1.500 msec
4104 bytes from 192.168.1.2: icmp_seq=13 ttl=254 time=1.490 msec
4104 bytes from 192.168.1.2: icmp_seq=14 ttl=254 time=1.505 msec
4104 bytes from 192.168.1.2: icmp_seq=15 ttl=254 time=1.506 msec
4104 bytes from 192.168.1.2: icmp_seq=16 ttl=254 time=1.495 msec
4104 bytes from 192.168.1.2: icmp_seq=17 ttl=254 time=1.510 msec
4104 bytes from 192.168.1.2: icmp_seq=18 ttl=254 time=1.506 msec
4104 bytes from 192.168.1.2: icmp_seq=19 ttl=254 time=1.505 msec
4104 bytes from 192.168.1.2: icmp_seq=20 ttl=254 time=1.519 msec
4104 bytes from 192.168.1.2: icmp_seq=21 ttl=254 time=1.493 msec
4104 bytes from 192.168.1.2: icmp_seq=22 ttl=254 time=1.506 msec
4104 bytes from 192.168.1.2: icmp_seq=23 ttl=254 time=1.492 msec
4104 bytes from 192.168.1.2: icmp_seq=24 ttl=254 time=1.505 msec
4104 bytes from 192.168.1.2: icmp_seq=25 ttl=254 time=1.504 msec
4104 bytes from 192.168.1.2: icmp_seq=26 ttl=254 time=1.502 msec
4104 bytes from 192.168.1.2: icmp_seq=27 ttl=254 time=1.495 msec
4104 bytes from 192.168.1.2: icmp_seq=28 ttl=254 time=1.497 msec
4104 bytes from 192.168.1.2: icmp_seq=29 ttl=254 time=1.495 msec
--- 192.168.1.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 1.478/1.499/1.519/0.047 ms
PING 192.168.1.2 (192.168.1.2) from 192.168.0.2 : 8192(8220) bytes of data.
Embedded Virtual Private Network: PerIormance and Scalability
81
8200 bytes from 192.168.1.2: icmp_seq=0 ttl=254 time=2.191 msec
8200 bytes from 192.168.1.2: icmp_seq=1 ttl=254 time=2.215 msec
8200 bytes from 192.168.1.2: icmp_seq=2 ttl=254 time=2.207 msec
8200 bytes from 192.168.1.2: icmp_seq=3 ttl=254 time=2.215 msec
8200 bytes from 192.168.1.2: icmp_seq=4 ttl=254 time=2.252 msec
8200 bytes from 192.168.1.2: icmp_seq=5 ttl=254 time=2.225 msec
8200 bytes from 192.168.1.2: icmp_seq=6 ttl=254 time=2.223 msec
8200 bytes from 192.168.1.2: icmp_seq=7 ttl=254 time=2.225 msec
8200 bytes from 192.168.1.2: icmp_seq=8 ttl=254 time=2.212 msec
8200 bytes from 192.168.1.2: icmp_seq=9 ttl=254 time=2.226 msec
8200 bytes from 192.168.1.2: icmp_seq=10 ttl=254 time=2.203 msec
8200 bytes from 192.168.1.2: icmp_seq=11 ttl=254 time=2.237 msec
8200 bytes from 192.168.1.2: icmp_seq=12 ttl=254 time=2.213 msec
8200 bytes from 192.168.1.2: icmp_seq=13 ttl=254 time=2.221 msec
8200 bytes from 192.168.1.2: icmp_seq=14 ttl=254 time=2.202 msec
8200 bytes from 192.168.1.2: icmp_seq=15 ttl=254 time=2.203 msec
8200 bytes from 192.168.1.2: icmp_seq=16 ttl=254 time=2.210 msec
8200 bytes from 192.168.1.2: icmp_seq=17 ttl=254 time=2.205 msec
8200 bytes from 192.168.1.2: icmp_seq=18 ttl=254 time=2.214 msec
8200 bytes from 192.168.1.2: icmp_seq=19 ttl=254 time=2.213 msec
8200 bytes from 192.168.1.2: icmp_seq=20 ttl=254 time=2.203 msec
8200 bytes from 192.168.1.2: icmp_seq=21 ttl=254 time=2.230 msec
8200 bytes from 192.168.1.2: icmp_seq=22 ttl=254 time=2.217 msec
8200 bytes from 192.168.1.2: icmp_seq=23 ttl=254 time=2.220 msec
8200 bytes from 192.168.1.2: icmp_seq=24 ttl=254 time=2.218 msec
8200 bytes from 192.168.1.2: icmp_seq=25 ttl=254 time=2.211 msec
8200 bytes from 192.168.1.2: icmp_seq=26 ttl=254 time=2.230 msec
8200 bytes from 192.168.1.2: icmp_seq=27 ttl=254 time=2.220 msec
8200 bytes from 192.168.1.2: icmp_seq=28 ttl=254 time=2.222 msec
8200 bytes from 192.168.1.2: icmp_seq=29 ttl=254 time=2.208 msec
--- 192.168.1.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 2.191/2.216/2.252/0.042 ms
PING 192.168.1.2 (192.168.1.2) from 192.168.0.2 : 16384(16412) bytes of data.
16392 bytes from 192.168.1.2: icmp_seq=0 ttl=254 time=3.714 msec
16392 bytes from 192.168.1.2: icmp_seq=1 ttl=254 time=3.702 msec
16392 bytes from 192.168.1.2: icmp_seq=2 ttl=254 time=3.698 msec
16392 bytes from 192.168.1.2: icmp_seq=3 ttl=254 time=3.692 msec
16392 bytes from 192.168.1.2: icmp_seq=4 ttl=254 time=3.708 msec
16392 bytes from 192.168.1.2: icmp_seq=5 ttl=254 time=3.689 msec
16392 bytes from 192.168.1.2: icmp_seq=6 ttl=254 time=3.693 msec
16392 bytes from 192.168.1.2: icmp_seq=7 ttl=254 time=3.694 msec
16392 bytes from 192.168.1.2: icmp_seq=8 ttl=254 time=3.692 msec
16392 bytes from 192.168.1.2: icmp_seq=9 ttl=254 time=3.686 msec
16392 bytes from 192.168.1.2: icmp_seq=10 ttl=254 time=3.705 msec
16392 bytes from 192.168.1.2: icmp_seq=11 ttl=254 time=3.684 msec
16392 bytes from 192.168.1.2: icmp_seq=12 ttl=254 time=3.696 msec
16392 bytes from 192.168.1.2: icmp_seq=13 ttl=254 time=3.694 msec
16392 bytes from 192.168.1.2: icmp_seq=14 ttl=254 time=3.705 msec
16392 bytes from 192.168.1.2: icmp_seq=15 ttl=254 time=3.692 msec
16392 bytes from 192.168.1.2: icmp_seq=16 ttl=254 time=3.701 msec
16392 bytes from 192.168.1.2: icmp_seq=17 ttl=254 time=3.710 msec
16392 bytes from 192.168.1.2: icmp_seq=18 ttl=254 time=3.702 msec
16392 bytes from 192.168.1.2: icmp_seq=19 ttl=254 time=3.699 msec
16392 bytes from 192.168.1.2: icmp_seq=20 ttl=254 time=3.701 msec
16392 bytes from 192.168.1.2: icmp_seq=21 ttl=254 time=3.687 msec
16392 bytes from 192.168.1.2: icmp_seq=22 ttl=254 time=3.710 msec
16392 bytes from 192.168.1.2: icmp_seq=23 ttl=254 time=3.688 msec
16392 bytes from 192.168.1.2: icmp_seq=24 ttl=254 time=3.712 msec
16392 bytes from 192.168.1.2: icmp_seq=25 ttl=254 time=3.696 msec
16392 bytes from 192.168.1.2: icmp_seq=26 ttl=254 time=3.699 msec
16392 bytes from 192.168.1.2: icmp_seq=27 ttl=254 time=3.712 msec
16392 bytes from 192.168.1.2: icmp_seq=28 ttl=254 time=3.689 msec
16392 bytes from 192.168.1.2: icmp_seq=29 ttl=254 time=3.690 msec
--- 192.168.1.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 3.684/3.698/3.714/0.008 ms
PING 192.168.1.2 (192.168.1.2) from 192.168.0.2 : 32768(32796) bytes of data.
32776 bytes from 192.168.1.2: icmp_seq=0 ttl=254 time=3.079 msec
32776 bytes from 192.168.1.2: icmp_seq=1 ttl=254 time=6.652 msec
Embedded Virtual Private Network: PerIormance and Scalability
82
32776 bytes from 192.168.1.2: icmp_seq=2 ttl=254 time=6.632 msec
32776 bytes from 192.168.1.2: icmp_seq=3 ttl=254 time=6.691 msec
32776 bytes from 192.168.1.2: icmp_seq=4 ttl=254 time=6.648 msec
32776 bytes from 192.168.1.2: icmp_seq=5 ttl=254 time=6.642 msec
32776 bytes from 192.168.1.2: icmp_seq=6 ttl=254 time=6.645 msec
32776 bytes from 192.168.1.2: icmp_seq=7 ttl=254 time=6.663 msec
32776 bytes from 192.168.1.2: icmp_seq=8 ttl=254 time=6.658 msec
32776 bytes from 192.168.1.2: icmp_seq=9 ttl=254 time=6.657 msec
32776 bytes from 192.168.1.2: icmp_seq=10 ttl=254 time=6.645 msec
32776 bytes from 192.168.1.2: icmp_seq=11 ttl=254 time=6.648 msec
32776 bytes from 192.168.1.2: icmp_seq=12 ttl=254 time=6.661 msec
32776 bytes from 192.168.1.2: icmp_seq=13 ttl=254 time=6.671 msec
32776 bytes from 192.168.1.2: icmp_seq=14 ttl=254 time=6.621 msec
32776 bytes from 192.168.1.2: icmp_seq=15 ttl=254 time=6.674 msec
32776 bytes from 192.168.1.2: icmp_seq=16 ttl=254 time=6.641 msec
32776 bytes from 192.168.1.2: icmp_seq=17 ttl=254 time=6.658 msec
32776 bytes from 192.168.1.2: icmp_seq=18 ttl=254 time=6.660 msec
32776 bytes from 192.168.1.2: icmp_seq=19 ttl=254 time=6.644 msec
32776 bytes from 192.168.1.2: icmp_seq=20 ttl=254 time=6.648 msec
32776 bytes from 192.168.1.2: icmp_seq=21 ttl=254 time=6.684 msec
32776 bytes from 192.168.1.2: icmp_seq=22 ttl=254 time=6.626 msec
32776 bytes from 192.168.1.2: icmp_seq=23 ttl=254 time=6.681 msec
32776 bytes from 192.168.1.2: icmp_seq=24 ttl=254 time=6.639 msec
32776 bytes from 192.168.1.2: icmp_seq=25 ttl=254 time=6.688 msec
32776 bytes from 192.168.1.2: icmp_seq=26 ttl=254 time=6.655 msec
32776 bytes from 192.168.1.2: icmp_seq=27 ttl=254 time=6.661 msec
32776 bytes from 192.168.1.2: icmp_seq=28 ttl=254 time=6.664 msec
32776 bytes from 192.168.1.2: icmp_seq=29 ttl=254 time=6.656 msec
--- 192.168.1.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 3.079/6.536/6.691/0.646 ms
PING 192.168.1.2 (192.168.1.2) from 192.168.0.2 : 65507(65535) bytes of data.
65515 bytes from 192.168.1.2: icmp_seq=0 ttl=254 time=9.623 msec
65515 bytes from 192.168.1.2: icmp_seq=1 ttl=254 time=9.633 msec
65515 bytes from 192.168.1.2: icmp_seq=2 ttl=254 time=9.637 msec
65515 bytes from 192.168.1.2: icmp_seq=3 ttl=254 time=9.632 msec
65515 bytes from 192.168.1.2: icmp_seq=4 ttl=254 time=9.638 msec
65515 bytes from 192.168.1.2: icmp_seq=5 ttl=254 time=9.633 msec
65515 bytes from 192.168.1.2: icmp_seq=6 ttl=254 time=9.629 msec
65515 bytes from 192.168.1.2: icmp_seq=7 ttl=254 time=9.631 msec
65515 bytes from 192.168.1.2: icmp_seq=8 ttl=254 time=9.638 msec
65515 bytes from 192.168.1.2: icmp_seq=9 ttl=254 time=9.654 msec
65515 bytes from 192.168.1.2: icmp_seq=10 ttl=254 time=9.660 msec
65515 bytes from 192.168.1.2: icmp_seq=11 ttl=254 time=9.652 msec
65515 bytes from 192.168.1.2: icmp_seq=12 ttl=254 time=9.657 msec
65515 bytes from 192.168.1.2: icmp_seq=13 ttl=254 time=9.650 msec
65515 bytes from 192.168.1.2: icmp_seq=14 ttl=254 time=9.653 msec
65515 bytes from 192.168.1.2: icmp_seq=15 ttl=254 time=9.652 msec
65515 bytes from 192.168.1.2: icmp_seq=16 ttl=254 time=9.658 msec
65515 bytes from 192.168.1.2: icmp_seq=17 ttl=254 time=9.635 msec
65515 bytes from 192.168.1.2: icmp_seq=18 ttl=254 time=9.638 msec
65515 bytes from 192.168.1.2: icmp_seq=19 ttl=254 time=9.631 msec
65515 bytes from 192.168.1.2: icmp_seq=20 ttl=254 time=9.638 msec
65515 bytes from 192.168.1.2: icmp_seq=21 ttl=254 time=9.635 msec
65515 bytes from 192.168.1.2: icmp_seq=22 ttl=254 time=9.633 msec
65515 bytes from 192.168.1.2: icmp_seq=23 ttl=254 time=9.631 msec
65515 bytes from 192.168.1.2: icmp_seq=24 ttl=254 time=9.637 msec
65515 bytes from 192.168.1.2: icmp_seq=25 ttl=254 time=9.617 msec
65515 bytes from 192.168.1.2: icmp_seq=26 ttl=254 time=9.654 msec
65515 bytes from 192.168.1.2: icmp_seq=27 ttl=254 time=9.654 msec
65515 bytes from 192.168.1.2: icmp_seq=28 ttl=254 time=9.653 msec
65515 bytes from 192.168.1.2: icmp_seq=29 ttl=254 time=9.660 msec
--- 192.168.1.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 9.617/9.641/9.660/0.102 ms
Embedded Virtual Private Network: PerIormance and Scalability
83
$
PING 192.168.1.2 (192.168.1.2) from 192.168.0.2 : 8(36) bytes of data.
16 bytes from 192.168.1.2: icmp_seq=0 ttl=255 time=1.516 msec
16 bytes from 192.168.1.2: icmp_seq=1 ttl=255 time=673 usec
16 bytes from 192.168.1.2: icmp_seq=2 ttl=255 time=691 usec
16 bytes from 192.168.1.2: icmp_seq=3 ttl=255 time=676 usec
16 bytes from 192.168.1.2: icmp_seq=4 ttl=255 time=684 usec
16 bytes from 192.168.1.2: icmp_seq=5 ttl=255 time=609 usec
16 bytes from 192.168.1.2: icmp_seq=6 ttl=255 time=671 usec
16 bytes from 192.168.1.2: icmp_seq=7 ttl=255 time=666 usec
16 bytes from 192.168.1.2: icmp_seq=8 ttl=255 time=695 usec
16 bytes from 192.168.1.2: icmp_seq=9 ttl=255 time=666 usec
16 bytes from 192.168.1.2: icmp_seq=10 ttl=255 time=645 usec
16 bytes from 192.168.1.2: icmp_seq=11 ttl=255 time=667 usec
16 bytes from 192.168.1.2: icmp_seq=12 ttl=255 time=673 usec
16 bytes from 192.168.1.2: icmp_seq=13 ttl=255 time=668 usec
16 bytes from 192.168.1.2: icmp_seq=14 ttl=255 time=682 usec
16 bytes from 192.168.1.2: icmp_seq=15 ttl=255 time=682 usec
16 bytes from 192.168.1.2: icmp_seq=16 ttl=255 time=685 usec
16 bytes from 192.168.1.2: icmp_seq=17 ttl=255 time=669 usec
16 bytes from 192.168.1.2: icmp_seq=18 ttl=255 time=684 usec
16 bytes from 192.168.1.2: icmp_seq=19 ttl=255 time=670 usec
16 bytes from 192.168.1.2: icmp_seq=20 ttl=255 time=693 usec
16 bytes from 192.168.1.2: icmp_seq=21 ttl=255 time=673 usec
16 bytes from 192.168.1.2: icmp_seq=22 ttl=255 time=684 usec
16 bytes from 192.168.1.2: icmp_seq=23 ttl=255 time=670 usec
16 bytes from 192.168.1.2: icmp_seq=24 ttl=255 time=677 usec
16 bytes from 192.168.1.2: icmp_seq=25 ttl=255 time=671 usec
16 bytes from 192.168.1.2: icmp_seq=26 ttl=255 time=677 usec
16 bytes from 192.168.1.2: icmp_seq=27 ttl=255 time=659 usec
16 bytes from 192.168.1.2: icmp_seq=28 ttl=255 time=676 usec
16 bytes from 192.168.1.2: icmp_seq=29 ttl=255 time=662 usec
--- 192.168.1.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 0.609/0.700/1.516/0.154 ms
PING 192.168.1.2 (192.168.1.2) from 192.168.0.2 : 64(92) bytes of data.
72 bytes from 192.168.1.2: icmp_seq=0 ttl=255 time=1.255 msec
72 bytes from 192.168.1.2: icmp_seq=1 ttl=255 time=761 usec
72 bytes from 192.168.1.2: icmp_seq=2 ttl=255 time=731 usec
72 bytes from 192.168.1.2: icmp_seq=3 ttl=255 time=751 usec
72 bytes from 192.168.1.2: icmp_seq=4 ttl=255 time=729 usec
72 bytes from 192.168.1.2: icmp_seq=5 ttl=255 time=748 usec
72 bytes from 192.168.1.2: icmp_seq=6 ttl=255 time=740 usec
72 bytes from 192.168.1.2: icmp_seq=7 ttl=255 time=745 usec
72 bytes from 192.168.1.2: icmp_seq=8 ttl=255 time=730 usec
72 bytes from 192.168.1.2: icmp_seq=9 ttl=255 time=756 usec
72 bytes from 192.168.1.2: icmp_seq=10 ttl=255 time=734 usec
72 bytes from 192.168.1.2: icmp_seq=11 ttl=255 time=767 usec
72 bytes from 192.168.1.2: icmp_seq=12 ttl=255 time=737 usec
72 bytes from 192.168.1.2: icmp_seq=13 ttl=255 time=743 usec
72 bytes from 192.168.1.2: icmp_seq=14 ttl=255 time=743 usec
72 bytes from 192.168.1.2: icmp_seq=15 ttl=255 time=743 usec
72 bytes from 192.168.1.2: icmp_seq=16 ttl=255 time=740 usec
72 bytes from 192.168.1.2: icmp_seq=17 ttl=255 time=755 usec
72 bytes from 192.168.1.2: icmp_seq=18 ttl=255 time=731 usec
72 bytes from 192.168.1.2: icmp_seq=19 ttl=255 time=750 usec
72 bytes from 192.168.1.2: icmp_seq=20 ttl=255 time=729 usec
72 bytes from 192.168.1.2: icmp_seq=21 ttl=255 time=753 usec
72 bytes from 192.168.1.2: icmp_seq=22 ttl=255 time=687 usec
72 bytes from 192.168.1.2: icmp_seq=23 ttl=255 time=747 usec
72 bytes from 192.168.1.2: icmp_seq=24 ttl=255 time=736 usec
72 bytes from 192.168.1.2: icmp_seq=25 ttl=255 time=751 usec
72 bytes from 192.168.1.2: icmp_seq=26 ttl=255 time=739 usec
72 bytes from 192.168.1.2: icmp_seq=27 ttl=255 time=714 usec
72 bytes from 192.168.1.2: icmp_seq=28 ttl=255 time=728 usec
72 bytes from 192.168.1.2: icmp_seq=29 ttl=255 time=765 usec
--- 192.168.1.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
Embedded Virtual Private Network: PerIormance and Scalability
84
round-trip min/avg/max/mdev = 0.687/0.757/1.255/0.100 ms
PING 192.168.1.2 (192.168.1.2) from 192.168.0.2 : 128(156) bytes of data.
136 bytes from 192.168.1.2: icmp_seq=0 ttl=255 time=1.338 msec
136 bytes from 192.168.1.2: icmp_seq=1 ttl=255 time=836 usec
136 bytes from 192.168.1.2: icmp_seq=2 ttl=255 time=859 usec
136 bytes from 192.168.1.2: icmp_seq=3 ttl=255 time=807 usec
136 bytes from 192.168.1.2: icmp_seq=4 ttl=255 time=826 usec
136 bytes from 192.168.1.2: icmp_seq=5 ttl=255 time=814 usec
136 bytes from 192.168.1.2: icmp_seq=6 ttl=255 time=833 usec
136 bytes from 192.168.1.2: icmp_seq=7 ttl=255 time=817 usec
136 bytes from 192.168.1.2: icmp_seq=8 ttl=255 time=813 usec
136 bytes from 192.168.1.2: icmp_seq=9 ttl=255 time=805 usec
136 bytes from 192.168.1.2: icmp_seq=10 ttl=255 time=815 usec
136 bytes from 192.168.1.2: icmp_seq=11 ttl=255 time=804 usec
136 bytes from 192.168.1.2: icmp_seq=12 ttl=255 time=831 usec
136 bytes from 192.168.1.2: icmp_seq=13 ttl=255 time=803 usec
136 bytes from 192.168.1.2: icmp_seq=14 ttl=255 time=817 usec
136 bytes from 192.168.1.2: icmp_seq=15 ttl=255 time=804 usec
136 bytes from 192.168.1.2: icmp_seq=16 ttl=255 time=826 usec
136 bytes from 192.168.1.2: icmp_seq=17 ttl=255 time=814 usec
136 bytes from 192.168.1.2: icmp_seq=18 ttl=255 time=822 usec
136 bytes from 192.168.1.2: icmp_seq=19 ttl=255 time=799 usec
136 bytes from 192.168.1.2: icmp_seq=20 ttl=255 time=825 usec
136 bytes from 192.168.1.2: icmp_seq=21 ttl=255 time=805 usec
136 bytes from 192.168.1.2: icmp_seq=22 ttl=255 time=839 usec
136 bytes from 192.168.1.2: icmp_seq=23 ttl=255 time=810 usec
136 bytes from 192.168.1.2: icmp_seq=24 ttl=255 time=824 usec
136 bytes from 192.168.1.2: icmp_seq=25 ttl=255 time=812 usec
136 bytes from 192.168.1.2: icmp_seq=26 ttl=255 time=838 usec
136 bytes from 192.168.1.2: icmp_seq=27 ttl=255 time=823 usec
136 bytes from 192.168.1.2: icmp_seq=28 ttl=255 time=829 usec
136 bytes from 192.168.1.2: icmp_seq=29 ttl=255 time=807 usec
--- 192.168.1.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 0.799/0.836/1.338/0.098 ms
PING 192.168.1.2 (192.168.1.2) from 192.168.0.2 : 256(284) bytes of data.
264 bytes from 192.168.1.2: icmp_seq=0 ttl=255 time=1.508 msec
264 bytes from 192.168.1.2: icmp_seq=1 ttl=255 time=979 usec
264 bytes from 192.168.1.2: icmp_seq=2 ttl=255 time=961 usec
264 bytes from 192.168.1.2: icmp_seq=3 ttl=255 time=993 usec
264 bytes from 192.168.1.2: icmp_seq=4 ttl=255 time=959 usec
264 bytes from 192.168.1.2: icmp_seq=5 ttl=255 time=969 usec
264 bytes from 192.168.1.2: icmp_seq=6 ttl=255 time=922 usec
264 bytes from 192.168.1.2: icmp_seq=7 ttl=255 time=979 usec
264 bytes from 192.168.1.2: icmp_seq=8 ttl=255 time=969 usec
264 bytes from 192.168.1.2: icmp_seq=9 ttl=255 time=972 usec
264 bytes from 192.168.1.2: icmp_seq=10 ttl=255 time=952 usec
264 bytes from 192.168.1.2: icmp_seq=11 ttl=255 time=926 usec
264 bytes from 192.168.1.2: icmp_seq=12 ttl=255 time=956 usec
264 bytes from 192.168.1.2: icmp_seq=13 ttl=255 time=991 usec
264 bytes from 192.168.1.2: icmp_seq=14 ttl=255 time=957 usec
264 bytes from 192.168.1.2: icmp_seq=15 ttl=255 time=969 usec
264 bytes from 192.168.1.2: icmp_seq=16 ttl=255 time=958 usec
264 bytes from 192.168.1.2: icmp_seq=17 ttl=255 time=981 usec
264 bytes from 192.168.1.2: icmp_seq=18 ttl=255 time=971 usec
264 bytes from 192.168.1.2: icmp_seq=19 ttl=255 time=984 usec
264 bytes from 192.168.1.2: icmp_seq=20 ttl=255 time=959 usec
264 bytes from 192.168.1.2: icmp_seq=21 ttl=255 time=977 usec
264 bytes from 192.168.1.2: icmp_seq=22 ttl=255 time=949 usec
264 bytes from 192.168.1.2: icmp_seq=23 ttl=255 time=981 usec
264 bytes from 192.168.1.2: icmp_seq=24 ttl=255 time=951 usec
264 bytes from 192.168.1.2: icmp_seq=25 ttl=255 time=963 usec
264 bytes from 192.168.1.2: icmp_seq=26 ttl=255 time=956 usec
264 bytes from 192.168.1.2: icmp_seq=27 ttl=255 time=982 usec
264 bytes from 192.168.1.2: icmp_seq=28 ttl=255 time=971 usec
264 bytes from 192.168.1.2: icmp_seq=29 ttl=255 time=968 usec
--- 192.168.1.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 0.922/0.983/1.508/0.106 ms
PING 192.168.1.2 (192.168.1.2) from 192.168.0.2 : 512(540) bytes of data.
Embedded Virtual Private Network: PerIormance and Scalability
85
520 bytes from 192.168.1.2: icmp_seq=0 ttl=255 time=1.801 msec
520 bytes from 192.168.1.2: icmp_seq=1 ttl=255 time=1.247 msec
520 bytes from 192.168.1.2: icmp_seq=2 ttl=255 time=1.287 msec
520 bytes from 192.168.1.2: icmp_seq=3 ttl=255 time=1.262 msec
520 bytes from 192.168.1.2: icmp_seq=4 ttl=255 time=1.294 msec
520 bytes from 192.168.1.2: icmp_seq=5 ttl=255 time=1.255 msec
520 bytes from 192.168.1.2: icmp_seq=6 ttl=255 time=1.275 msec
520 bytes from 192.168.1.2: icmp_seq=7 ttl=255 time=1.214 msec
520 bytes from 192.168.1.2: icmp_seq=8 ttl=255 time=1.282 msec
520 bytes from 192.168.1.2: icmp_seq=9 ttl=255 time=1.268 msec
520 bytes from 192.168.1.2: icmp_seq=10 ttl=255 time=1.276 msec
520 bytes from 192.168.1.2: icmp_seq=11 ttl=255 time=1.250 msec
520 bytes from 192.168.1.2: icmp_seq=12 ttl=255 time=1.273 msec
520 bytes from 192.168.1.2: icmp_seq=13 ttl=255 time=1.247 msec
520 bytes from 192.168.1.2: icmp_seq=14 ttl=255 time=1.284 msec
520 bytes from 192.168.1.2: icmp_seq=15 ttl=255 time=1.245 msec
520 bytes from 192.168.1.2: icmp_seq=16 ttl=255 time=1.280 msec
520 bytes from 192.168.1.2: icmp_seq=17 ttl=255 time=1.270 msec
520 bytes from 192.168.1.2: icmp_seq=18 ttl=255 time=1.291 msec
520 bytes from 192.168.1.2: icmp_seq=19 ttl=255 time=1.280 msec
520 bytes from 192.168.1.2: icmp_seq=20 ttl=255 time=1.285 msec
520 bytes from 192.168.1.2: icmp_seq=21 ttl=255 time=1.252 msec
520 bytes from 192.168.1.2: icmp_seq=22 ttl=255 time=1.274 msec
520 bytes from 192.168.1.2: icmp_seq=23 ttl=255 time=1.252 msec
520 bytes from 192.168.1.2: icmp_seq=24 ttl=255 time=1.296 msec
520 bytes from 192.168.1.2: icmp_seq=25 ttl=255 time=1.210 msec
520 bytes from 192.168.1.2: icmp_seq=26 ttl=255 time=1.280 msec
520 bytes from 192.168.1.2: icmp_seq=27 ttl=255 time=1.257 msec
520 bytes from 192.168.1.2: icmp_seq=28 ttl=255 time=1.281 msec
520 bytes from 192.168.1.2: icmp_seq=29 ttl=255 time=1.267 msec
--- 192.168.1.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 1.210/1.284/1.801/0.104 ms
PING 192.168.1.2 (192.168.1.2) from 192.168.0.2 : 1024(1052) bytes of data.
1032 bytes from 192.168.1.2: icmp_seq=0 ttl=255 time=2.407 msec
1032 bytes from 192.168.1.2: icmp_seq=1 ttl=255 time=1.883 msec
1032 bytes from 192.168.1.2: icmp_seq=2 ttl=255 time=1.853 msec
1032 bytes from 192.168.1.2: icmp_seq=3 ttl=255 time=1.874 msec
1032 bytes from 192.168.1.2: icmp_seq=4 ttl=255 time=1.864 msec
1032 bytes from 192.168.1.2: icmp_seq=5 ttl=255 time=1.895 msec
1032 bytes from 192.168.1.2: icmp_seq=6 ttl=255 time=1.859 msec
1032 bytes from 192.168.1.2: icmp_seq=7 ttl=255 time=1.874 msec
1032 bytes from 192.168.1.2: icmp_seq=8 ttl=255 time=1.820 msec
1032 bytes from 192.168.1.2: icmp_seq=9 ttl=255 time=1.877 msec
1032 bytes from 192.168.1.2: icmp_seq=10 ttl=255 time=1.875 msec
1032 bytes from 192.168.1.2: icmp_seq=11 ttl=255 time=1.879 msec
1032 bytes from 192.168.1.2: icmp_seq=12 ttl=255 time=1.862 msec
1032 bytes from 192.168.1.2: icmp_seq=13 ttl=255 time=1.873 msec
1032 bytes from 192.168.1.2: icmp_seq=14 ttl=255 time=1.857 msec
1032 bytes from 192.168.1.2: icmp_seq=15 ttl=255 time=1.894 msec
1032 bytes from 192.168.1.2: icmp_seq=16 ttl=255 time=1.858 msec
1032 bytes from 192.168.1.2: icmp_seq=17 ttl=255 time=1.879 msec
1032 bytes from 192.168.1.2: icmp_seq=18 ttl=255 time=1.869 msec
1032 bytes from 192.168.1.2: icmp_seq=19 ttl=255 time=1.882 msec
1032 bytes from 192.168.1.2: icmp_seq=20 ttl=255 time=1.871 msec
1032 bytes from 192.168.1.2: icmp_seq=21 ttl=255 time=1.876 msec
1032 bytes from 192.168.1.2: icmp_seq=22 ttl=255 time=1.851 msec
1032 bytes from 192.168.1.2: icmp_seq=23 ttl=255 time=1.891 msec
1032 bytes from 192.168.1.2: icmp_seq=24 ttl=255 time=1.849 msec
1032 bytes from 192.168.1.2: icmp_seq=25 ttl=255 time=1.882 msec
1032 bytes from 192.168.1.2: icmp_seq=26 ttl=255 time=1.851 msec
1032 bytes from 192.168.1.2: icmp_seq=27 ttl=255 time=1.870 msec
1032 bytes from 192.168.1.2: icmp_seq=28 ttl=255 time=1.859 msec
1032 bytes from 192.168.1.2: icmp_seq=29 ttl=255 time=1.877 msec
--- 192.168.1.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 1.820/1.887/2.407/0.098 ms
PING 192.168.1.2 (192.168.1.2) from 192.168.0.2 : 2048(2076) bytes of data.
2056 bytes from 192.168.1.2: icmp_seq=0 ttl=255 time=3.485 msec
2056 bytes from 192.168.1.2: icmp_seq=1 ttl=255 time=2.913 msec
Embedded Virtual Private Network: PerIormance and Scalability
86
2056 bytes from 192.168.1.2: icmp_seq=2 ttl=255 time=2.904 msec
2056 bytes from 192.168.1.2: icmp_seq=3 ttl=255 time=2.901 msec
2056 bytes from 192.168.1.2: icmp_seq=4 ttl=255 time=2.937 msec
2056 bytes from 192.168.1.2: icmp_seq=5 ttl=255 time=2.908 msec
2056 bytes from 192.168.1.2: icmp_seq=6 ttl=255 time=2.935 msec
2056 bytes from 192.168.1.2: icmp_seq=7 ttl=255 time=2.891 msec
2056 bytes from 192.168.1.2: icmp_seq=8 ttl=255 time=2.908 msec
2056 bytes from 192.168.1.2: icmp_seq=9 ttl=255 time=2.875 msec
2056 bytes from 192.168.1.2: icmp_seq=10 ttl=255 time=2.925 msec
2056 bytes from 192.168.1.2: icmp_seq=11 ttl=255 time=2.902 msec
2056 bytes from 192.168.1.2: icmp_seq=12 ttl=255 time=2.917 msec
2056 bytes from 192.168.1.2: icmp_seq=13 ttl=255 time=2.880 msec
2056 bytes from 192.168.1.2: icmp_seq=14 ttl=255 time=2.883 msec
2056 bytes from 192.168.1.2: icmp_seq=15 ttl=255 time=2.893 msec
2056 bytes from 192.168.1.2: icmp_seq=16 ttl=255 time=2.924 msec
2056 bytes from 192.168.1.2: icmp_seq=17 ttl=255 time=2.882 msec
2056 bytes from 192.168.1.2: icmp_seq=18 ttl=255 time=2.907 msec
2056 bytes from 192.168.1.2: icmp_seq=19 ttl=255 time=2.893 msec
2056 bytes from 192.168.1.2: icmp_seq=20 ttl=255 time=2.906 msec
2056 bytes from 192.168.1.2: icmp_seq=21 ttl=255 time=2.889 msec
2056 bytes from 192.168.1.2: icmp_seq=22 ttl=255 time=2.910 msec
2056 bytes from 192.168.1.2: icmp_seq=23 ttl=255 time=2.886 msec
2056 bytes from 192.168.1.2: icmp_seq=24 ttl=255 time=2.918 msec
2056 bytes from 192.168.1.2: icmp_seq=25 ttl=255 time=2.888 msec
2056 bytes from 192.168.1.2: icmp_seq=26 ttl=255 time=2.939 msec
2056 bytes from 192.168.1.2: icmp_seq=27 ttl=255 time=2.896 msec
2056 bytes from 192.168.1.2: icmp_seq=28 ttl=255 time=2.918 msec
2056 bytes from 192.168.1.2: icmp_seq=29 ttl=255 time=2.887 msec
--- 192.168.1.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 2.875/2.923/3.485/0.114 ms
PING 192.168.1.2 (192.168.1.2) from 192.168.0.2 : 4096(4124) bytes of data.
4104 bytes from 192.168.1.2: icmp_seq=0 ttl=255 time=5.146 msec
4104 bytes from 192.168.1.2: icmp_seq=1 ttl=255 time=4.531 msec
4104 bytes from 192.168.1.2: icmp_seq=2 ttl=255 time=4.521 msec
4104 bytes from 192.168.1.2: icmp_seq=3 ttl=255 time=4.521 msec
4104 bytes from 192.168.1.2: icmp_seq=4 ttl=255 time=4.505 msec
4104 bytes from 192.168.1.2: icmp_seq=5 ttl=255 time=4.541 msec
4104 bytes from 192.168.1.2: icmp_seq=6 ttl=255 time=4.498 msec
4104 bytes from 192.168.1.2: icmp_seq=7 ttl=255 time=4.558 msec
4104 bytes from 192.168.1.2: icmp_seq=8 ttl=255 time=4.502 msec
4104 bytes from 192.168.1.2: icmp_seq=9 ttl=255 time=4.552 msec
4104 bytes from 192.168.1.2: icmp_seq=10 ttl=255 time=4.575 msec
4104 bytes from 192.168.1.2: icmp_seq=11 ttl=255 time=4.548 msec
4104 bytes from 192.168.1.2: icmp_seq=12 ttl=255 time=4.540 msec
4104 bytes from 192.168.1.2: icmp_seq=13 ttl=255 time=4.545 msec
4104 bytes from 192.168.1.2: icmp_seq=14 ttl=255 time=4.517 msec
4104 bytes from 192.168.1.2: icmp_seq=15 ttl=255 time=4.547 msec
4104 bytes from 192.168.1.2: icmp_seq=16 ttl=255 time=4.530 msec
4104 bytes from 192.168.1.2: icmp_seq=17 ttl=255 time=4.624 msec
4104 bytes from 192.168.1.2: icmp_seq=18 ttl=255 time=4.515 msec
4104 bytes from 192.168.1.2: icmp_seq=19 ttl=255 time=4.556 msec
4104 bytes from 192.168.1.2: icmp_seq=20 ttl=255 time=4.521 msec
4104 bytes from 192.168.1.2: icmp_seq=21 ttl=255 time=4.554 msec
4104 bytes from 192.168.1.2: icmp_seq=22 ttl=255 time=4.539 msec
4104 bytes from 192.168.1.2: icmp_seq=23 ttl=255 time=4.547 msec
4104 bytes from 192.168.1.2: icmp_seq=24 ttl=255 time=4.488 msec
4104 bytes from 192.168.1.2: icmp_seq=25 ttl=255 time=4.534 msec
4104 bytes from 192.168.1.2: icmp_seq=26 ttl=255 time=4.499 msec
4104 bytes from 192.168.1.2: icmp_seq=27 ttl=255 time=4.543 msec
4104 bytes from 192.168.1.2: icmp_seq=28 ttl=255 time=4.474 msec
4104 bytes from 192.168.1.2: icmp_seq=29 ttl=255 time=4.536 msec
--- 192.168.1.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 4.474/4.553/5.146/0.134 ms
PING 192.168.1.2 (192.168.1.2) from 192.168.0.2 : 8192(8220) bytes of data.
8200 bytes from 192.168.1.2: icmp_seq=0 ttl=255 time=2.585 msec
8200 bytes from 192.168.1.2: icmp_seq=1 ttl=255 time=8.700 msec
8200 bytes from 192.168.1.2: icmp_seq=2 ttl=255 time=7.970 msec
8200 bytes from 192.168.1.2: icmp_seq=3 ttl=255 time=7.960 msec
Embedded Virtual Private Network: PerIormance and Scalability
87
8200 bytes from 192.168.1.2: icmp_seq=4 ttl=255 time=7.999 msec
8200 bytes from 192.168.1.2: icmp_seq=5 ttl=255 time=7.940 msec
8200 bytes from 192.168.1.2: icmp_seq=6 ttl=255 time=7.965 msec
8200 bytes from 192.168.1.2: icmp_seq=7 ttl=255 time=7.934 msec
8200 bytes from 192.168.1.2: icmp_seq=8 ttl=255 time=7.995 msec
8200 bytes from 192.168.1.2: icmp_seq=9 ttl=255 time=7.934 msec
8200 bytes from 192.168.1.2: icmp_seq=10 ttl=255 time=7.974 msec
8200 bytes from 192.168.1.2: icmp_seq=11 ttl=255 time=7.927 msec
8200 bytes from 192.168.1.2: icmp_seq=12 ttl=255 time=7.964 msec
8200 bytes from 192.168.1.2: icmp_seq=13 ttl=255 time=7.944 msec
8200 bytes from 192.168.1.2: icmp_seq=14 ttl=255 time=7.948 msec
8200 bytes from 192.168.1.2: icmp_seq=15 ttl=255 time=7.938 msec
8200 bytes from 192.168.1.2: icmp_seq=16 ttl=255 time=7.939 msec
8200 bytes from 192.168.1.2: icmp_seq=17 ttl=255 time=7.903 msec
8200 bytes from 192.168.1.2: icmp_seq=18 ttl=255 time=7.980 msec
8200 bytes from 192.168.1.2: icmp_seq=19 ttl=255 time=7.934 msec
8200 bytes from 192.168.1.2: icmp_seq=20 ttl=255 time=7.955 msec
8200 bytes from 192.168.1.2: icmp_seq=21 ttl=255 time=7.908 msec
8200 bytes from 192.168.1.2: icmp_seq=22 ttl=255 time=7.957 msec
8200 bytes from 192.168.1.2: icmp_seq=23 ttl=255 time=7.940 msec
8200 bytes from 192.168.1.2: icmp_seq=24 ttl=255 time=7.949 msec
8200 bytes from 192.168.1.2: icmp_seq=25 ttl=255 time=7.893 msec
8200 bytes from 192.168.1.2: icmp_seq=26 ttl=255 time=7.941 msec
8200 bytes from 192.168.1.2: icmp_seq=27 ttl=255 time=7.905 msec
8200 bytes from 192.168.1.2: icmp_seq=28 ttl=255 time=7.944 msec
8200 bytes from 192.168.1.2: icmp_seq=29 ttl=255 time=7.899 msec
--- 192.168.1.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 2.585/7.790/8.700/0.982 ms
PING 192.168.1.2 (192.168.1.2) from 192.168.0.2 : 16384(16412) bytes of data.
16392 bytes from 192.168.1.2: icmp_seq=0 ttl=255 time=9.154 msec
16392 bytes from 192.168.1.2: icmp_seq=1 ttl=255 time=9.899 msec
16392 bytes from 192.168.1.2: icmp_seq=2 ttl=255 time=9.898 msec
16392 bytes from 192.168.1.2: icmp_seq=3 ttl=255 time=9.899 msec
16392 bytes from 192.168.1.2: icmp_seq=4 ttl=255 time=9.899 msec
16392 bytes from 192.168.1.2: icmp_seq=5 ttl=255 time=9.899 msec
16392 bytes from 192.168.1.2: icmp_seq=6 ttl=255 time=9.848 msec
16392 bytes from 192.168.1.2: icmp_seq=7 ttl=255 time=9.897 msec
16392 bytes from 192.168.1.2: icmp_seq=8 ttl=255 time=9.899 msec
16392 bytes from 192.168.1.2: icmp_seq=9 ttl=255 time=9.899 msec
16392 bytes from 192.168.1.2: icmp_seq=10 ttl=255 time=9.899 msec
16392 bytes from 192.168.1.2: icmp_seq=11 ttl=255 time=9.899 msec
16392 bytes from 192.168.1.2: icmp_seq=12 ttl=255 time=9.898 msec
16392 bytes from 192.168.1.2: icmp_seq=13 ttl=255 time=9.899 msec
16392 bytes from 192.168.1.2: icmp_seq=14 ttl=255 time=9.900 msec
16392 bytes from 192.168.1.2: icmp_seq=15 ttl=255 time=9.899 msec
16392 bytes from 192.168.1.2: icmp_seq=16 ttl=255 time=9.899 msec
16392 bytes from 192.168.1.2: icmp_seq=17 ttl=255 time=9.898 msec
16392 bytes from 192.168.1.2: icmp_seq=18 ttl=255 time=9.899 msec
16392 bytes from 192.168.1.2: icmp_seq=19 ttl=255 time=9.900 msec
16392 bytes from 192.168.1.2: icmp_seq=20 ttl=255 time=9.899 msec
16392 bytes from 192.168.1.2: icmp_seq=21 ttl=255 time=9.899 msec
16392 bytes from 192.168.1.2: icmp_seq=22 ttl=255 time=9.898 msec
16392 bytes from 192.168.1.2: icmp_seq=23 ttl=255 time=9.899 msec
16392 bytes from 192.168.1.2: icmp_seq=24 ttl=255 time=9.899 msec
16392 bytes from 192.168.1.2: icmp_seq=25 ttl=255 time=9.899 msec
16392 bytes from 192.168.1.2: icmp_seq=26 ttl=255 time=9.899 msec
16392 bytes from 192.168.1.2: icmp_seq=27 ttl=255 time=9.898 msec
16392 bytes from 192.168.1.2: icmp_seq=28 ttl=255 time=9.899 msec
16392 bytes from 192.168.1.2: icmp_seq=29 ttl=255 time=9.899 msec
--- 192.168.1.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 9.154/9.872/9.900/0.154 ms
PING 192.168.1.2 (192.168.1.2) from 192.168.0.2 : 32768(32796) bytes of data.
32776 bytes from 192.168.1.2: icmp_seq=0 ttl=255 time=12.136 msec
32776 bytes from 192.168.1.2: icmp_seq=1 ttl=255 time=9.822 msec
32776 bytes from 192.168.1.2: icmp_seq=2 ttl=255 time=9.822 msec
32776 bytes from 192.168.1.2: icmp_seq=3 ttl=255 time=9.818 msec
32776 bytes from 192.168.1.2: icmp_seq=4 ttl=255 time=9.822 msec
32776 bytes from 192.168.1.2: icmp_seq=5 ttl=255 time=9.821 msec
Embedded Virtual Private Network: PerIormance and Scalability
88
32776 bytes from 192.168.1.2: icmp_seq=6 ttl=255 time=9.822 msec
32776 bytes from 192.168.1.2: icmp_seq=7 ttl=255 time=9.770 msec
32776 bytes from 192.168.1.2: icmp_seq=8 ttl=255 time=9.820 msec
32776 bytes from 192.168.1.2: icmp_seq=9 ttl=255 time=9.822 msec
32776 bytes from 192.168.1.2: icmp_seq=10 ttl=255 time=9.821 msec
32776 bytes from 192.168.1.2: icmp_seq=11 ttl=255 time=9.821 msec
32776 bytes from 192.168.1.2: icmp_seq=12 ttl=255 time=9.822 msec
32776 bytes from 192.168.1.2: icmp_seq=13 ttl=255 time=9.818 msec
32776 bytes from 192.168.1.2: icmp_seq=14 ttl=255 time=9.822 msec
32776 bytes from 192.168.1.2: icmp_seq=15 ttl=255 time=9.822 msec
32776 bytes from 192.168.1.2: icmp_seq=16 ttl=255 time=9.821 msec
32776 bytes from 192.168.1.2: icmp_seq=17 ttl=255 time=9.822 msec
32776 bytes from 192.168.1.2: icmp_seq=18 ttl=255 time=9.820 msec
32776 bytes from 192.168.1.2: icmp_seq=19 ttl=255 time=9.822 msec
32776 bytes from 192.168.1.2: icmp_seq=20 ttl=255 time=9.822 msec
32776 bytes from 192.168.1.2: icmp_seq=21 ttl=255 time=9.821 msec
32776 bytes from 192.168.1.2: icmp_seq=22 ttl=255 time=9.822 msec
32776 bytes from 192.168.1.2: icmp_seq=23 ttl=255 time=9.819 msec
32776 bytes from 192.168.1.2: icmp_seq=24 ttl=255 time=9.822 msec
32776 bytes from 192.168.1.2: icmp_seq=25 ttl=255 time=9.822 msec
32776 bytes from 192.168.1.2: icmp_seq=26 ttl=255 time=9.822 msec
32776 bytes from 192.168.1.2: icmp_seq=27 ttl=255 time=9.821 msec
32776 bytes from 192.168.1.2: icmp_seq=28 ttl=255 time=9.819 msec
32776 bytes from 192.168.1.2: icmp_seq=29 ttl=255 time=9.821 msec
--- 192.168.1.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 9.770/9.896/12.136/0.429 ms
PING 192.168.1.2 (192.168.1.2) from 192.168.0.2 : 65507(65535) bytes of data.
65515 bytes from 192.168.1.2: icmp_seq=0 ttl=255 time=23.219 msec
65515 bytes from 192.168.1.2: icmp_seq=1 ttl=255 time=29.662 msec
65515 bytes from 192.168.1.2: icmp_seq=2 ttl=255 time=29.663 msec
65515 bytes from 192.168.1.2: icmp_seq=3 ttl=255 time=29.662 msec
65515 bytes from 192.168.1.2: icmp_seq=4 ttl=255 time=29.658 msec
65515 bytes from 192.168.1.2: icmp_seq=5 ttl=255 time=29.662 msec
65515 bytes from 192.168.1.2: icmp_seq=6 ttl=255 time=29.664 msec
65515 bytes from 192.168.1.2: icmp_seq=7 ttl=255 time=29.662 msec
65515 bytes from 192.168.1.2: icmp_seq=8 ttl=255 time=29.663 msec
65515 bytes from 192.168.1.2: icmp_seq=9 ttl=255 time=29.657 msec
65515 bytes from 192.168.1.2: icmp_seq=10 ttl=255 time=29.662 msec
65515 bytes from 192.168.1.2: icmp_seq=11 ttl=255 time=29.663 msec
65515 bytes from 192.168.1.2: icmp_seq=12 ttl=255 time=29.662 msec
65515 bytes from 192.168.1.2: icmp_seq=13 ttl=255 time=29.662 msec
65515 bytes from 192.168.1.2: icmp_seq=14 ttl=255 time=29.657 msec
65515 bytes from 192.168.1.2: icmp_seq=15 ttl=255 time=29.663 msec
65515 bytes from 192.168.1.2: icmp_seq=16 ttl=255 time=29.663 msec
65515 bytes from 192.168.1.2: icmp_seq=17 ttl=255 time=29.661 msec
65515 bytes from 192.168.1.2: icmp_seq=18 ttl=255 time=29.663 msec
65515 bytes from 192.168.1.2: icmp_seq=19 ttl=255 time=29.657 msec
65515 bytes from 192.168.1.2: icmp_seq=20 ttl=255 time=29.652 msec
65515 bytes from 192.168.1.2: icmp_seq=21 ttl=255 time=29.663 msec
65515 bytes from 192.168.1.2: icmp_seq=22 ttl=255 time=29.663 msec
65515 bytes from 192.168.1.2: icmp_seq=23 ttl=255 time=29.664 msec
65515 bytes from 192.168.1.2: icmp_seq=24 ttl=255 time=29.659 msec
65515 bytes from 192.168.1.2: icmp_seq=25 ttl=255 time=29.663 msec
65515 bytes from 192.168.1.2: icmp_seq=26 ttl=255 time=29.663 msec
65515 bytes from 192.168.1.2: icmp_seq=27 ttl=255 time=29.542 msec
65515 bytes from 192.168.1.2: icmp_seq=28 ttl=255 time=29.659 msec
65515 bytes from 192.168.1.2: icmp_seq=29 ttl=255 time=29.631 msec
--- 192.168.1.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 23.219/29.441/29.664/1.167 ms
Embedded Virtual Private Network: PerIormance and Scalability
89
7
PING 10.4.0.2 (10.4.0.2) from 10.4.0.1 : 8(36) bytes of data.
16 bytes from 10.4.0.2: icmp_seq=0 ttl=255 time=1.187 msec
16 bytes from 10.4.0.2: icmp_seq=1 ttl=255 time=824 usec
16 bytes from 10.4.0.2: icmp_seq=2 ttl=255 time=835 usec
16 bytes from 10.4.0.2: icmp_seq=3 ttl=255 time=830 usec
16 bytes from 10.4.0.2: icmp_seq=4 ttl=255 time=841 usec
16 bytes from 10.4.0.2: icmp_seq=5 ttl=255 time=775 usec
16 bytes from 10.4.0.2: icmp_seq=6 ttl=255 time=822 usec
16 bytes from 10.4.0.2: icmp_seq=7 ttl=255 time=819 usec
16 bytes from 10.4.0.2: icmp_seq=8 ttl=255 time=830 usec
16 bytes from 10.4.0.2: icmp_seq=9 ttl=255 time=835 usec
16 bytes from 10.4.0.2: icmp_seq=10 ttl=255 time=793 usec
16 bytes from 10.4.0.2: icmp_seq=11 ttl=255 time=809 usec
16 bytes from 10.4.0.2: icmp_seq=12 ttl=255 time=819 usec
16 bytes from 10.4.0.2: icmp_seq=13 ttl=255 time=813 usec
16 bytes from 10.4.0.2: icmp_seq=14 ttl=255 time=829 usec
16 bytes from 10.4.0.2: icmp_seq=15 ttl=255 time=826 usec
16 bytes from 10.4.0.2: icmp_seq=16 ttl=255 time=820 usec
16 bytes from 10.4.0.2: icmp_seq=17 ttl=255 time=813 usec
16 bytes from 10.4.0.2: icmp_seq=18 ttl=255 time=827 usec
16 bytes from 10.4.0.2: icmp_seq=19 ttl=255 time=829 usec
16 bytes from 10.4.0.2: icmp_seq=20 ttl=255 time=841 usec
16 bytes from 10.4.0.2: icmp_seq=21 ttl=255 time=815 usec
16 bytes from 10.4.0.2: icmp_seq=22 ttl=255 time=820 usec
16 bytes from 10.4.0.2: icmp_seq=23 ttl=255 time=993 usec
16 bytes from 10.4.0.2: icmp_seq=24 ttl=255 time=836 usec
16 bytes from 10.4.0.2: icmp_seq=25 ttl=255 time=833 usec
16 bytes from 10.4.0.2: icmp_seq=26 ttl=255 time=791 usec
16 bytes from 10.4.0.2: icmp_seq=27 ttl=255 time=799 usec
16 bytes from 10.4.0.2: icmp_seq=28 ttl=255 time=805 usec
16 bytes from 10.4.0.2: icmp_seq=29 ttl=255 time=800 usec
--- 10.4.0.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 0.775/0.836/1.187/0.083 ms
PING 10.4.0.2 (10.4.0.2) from 10.4.0.1 : 64(92) bytes of data.
72 bytes from 10.4.0.2: icmp_seq=0 ttl=255 time=663 usec
72 bytes from 10.4.0.2: icmp_seq=1 ttl=255 time=903 usec
72 bytes from 10.4.0.2: icmp_seq=2 ttl=255 time=888 usec
72 bytes from 10.4.0.2: icmp_seq=3 ttl=255 time=891 usec
72 bytes from 10.4.0.2: icmp_seq=4 ttl=255 time=886 usec
72 bytes from 10.4.0.2: icmp_seq=5 ttl=255 time=903 usec
72 bytes from 10.4.0.2: icmp_seq=6 ttl=255 time=898 usec
72 bytes from 10.4.0.2: icmp_seq=7 ttl=255 time=902 usec
72 bytes from 10.4.0.2: icmp_seq=8 ttl=255 time=891 usec
72 bytes from 10.4.0.2: icmp_seq=9 ttl=255 time=897 usec
72 bytes from 10.4.0.2: icmp_seq=10 ttl=255 time=921 usec
72 bytes from 10.4.0.2: icmp_seq=11 ttl=255 time=912 usec
72 bytes from 10.4.0.2: icmp_seq=12 ttl=255 time=907 usec
72 bytes from 10.4.0.2: icmp_seq=13 ttl=255 time=898 usec
72 bytes from 10.4.0.2: icmp_seq=14 ttl=255 time=892 usec
72 bytes from 10.4.0.2: icmp_seq=15 ttl=255 time=1.051 msec
72 bytes from 10.4.0.2: icmp_seq=16 ttl=255 time=901 usec
72 bytes from 10.4.0.2: icmp_seq=17 ttl=255 time=880 usec
72 bytes from 10.4.0.2: icmp_seq=18 ttl=255 time=878 usec
72 bytes from 10.4.0.2: icmp_seq=19 ttl=255 time=895 usec
72 bytes from 10.4.0.2: icmp_seq=20 ttl=255 time=1.472 msec
72 bytes from 10.4.0.2: icmp_seq=21 ttl=255 time=907 usec
72 bytes from 10.4.0.2: icmp_seq=22 ttl=255 time=857 usec
72 bytes from 10.4.0.2: icmp_seq=23 ttl=255 time=871 usec
72 bytes from 10.4.0.2: icmp_seq=24 ttl=255 time=871 usec
72 bytes from 10.4.0.2: icmp_seq=25 ttl=255 time=881 usec
72 bytes from 10.4.0.2: icmp_seq=26 ttl=255 time=886 usec
72 bytes from 10.4.0.2: icmp_seq=27 ttl=255 time=877 usec
72 bytes from 10.4.0.2: icmp_seq=28 ttl=255 time=888 usec
72 bytes from 10.4.0.2: icmp_seq=29 ttl=255 time=873 usec
--- 10.4.0.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 0.663/0.908/1.472/0.117 ms
Embedded Virtual Private Network: PerIormance and Scalability
90
PING 10.4.0.2 (10.4.0.2) from 10.4.0.1 : 128(156) bytes of data.
136 bytes from 10.4.0.2: icmp_seq=0 ttl=255 time=701 usec
136 bytes from 10.4.0.2: icmp_seq=1 ttl=255 time=926 usec
136 bytes from 10.4.0.2: icmp_seq=2 ttl=255 time=944 usec
136 bytes from 10.4.0.2: icmp_seq=3 ttl=255 time=927 usec
136 bytes from 10.4.0.2: icmp_seq=4 ttl=255 time=936 usec
136 bytes from 10.4.0.2: icmp_seq=5 ttl=255 time=930 usec
136 bytes from 10.4.0.2: icmp_seq=6 ttl=255 time=940 usec
136 bytes from 10.4.0.2: icmp_seq=7 ttl=255 time=944 usec
136 bytes from 10.4.0.2: icmp_seq=8 ttl=255 time=937 usec
136 bytes from 10.4.0.2: icmp_seq=9 ttl=255 time=926 usec
136 bytes from 10.4.0.2: icmp_seq=10 ttl=255 time=935 usec
136 bytes from 10.4.0.2: icmp_seq=11 ttl=255 time=923 usec
136 bytes from 10.4.0.2: icmp_seq=12 ttl=255 time=947 usec
136 bytes from 10.4.0.2: icmp_seq=13 ttl=255 time=927 usec
136 bytes from 10.4.0.2: icmp_seq=14 ttl=255 time=935 usec
136 bytes from 10.4.0.2: icmp_seq=15 ttl=255 time=947 usec
136 bytes from 10.4.0.2: icmp_seq=16 ttl=255 time=941 usec
136 bytes from 10.4.0.2: icmp_seq=17 ttl=255 time=906 usec
136 bytes from 10.4.0.2: icmp_seq=18 ttl=255 time=930 usec
136 bytes from 10.4.0.2: icmp_seq=19 ttl=255 time=921 usec
136 bytes from 10.4.0.2: icmp_seq=20 ttl=255 time=944 usec
136 bytes from 10.4.0.2: icmp_seq=21 ttl=255 time=924 usec
136 bytes from 10.4.0.2: icmp_seq=22 ttl=255 time=907 usec
136 bytes from 10.4.0.2: icmp_seq=23 ttl=255 time=929 usec
136 bytes from 10.4.0.2: icmp_seq=24 ttl=255 time=926 usec
136 bytes from 10.4.0.2: icmp_seq=25 ttl=255 time=919 usec
136 bytes from 10.4.0.2: icmp_seq=26 ttl=255 time=927 usec
136 bytes from 10.4.0.2: icmp_seq=27 ttl=255 time=937 usec
136 bytes from 10.4.0.2: icmp_seq=28 ttl=255 time=926 usec
136 bytes from 10.4.0.2: icmp_seq=29 ttl=255 time=923 usec
--- 10.4.0.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 0.701/0.922/0.947/0.057 ms
PING 10.4.0.2 (10.4.0.2) from 10.4.0.1 : 256(284) bytes of data.
264 bytes from 10.4.0.2: icmp_seq=0 ttl=255 time=778 usec
264 bytes from 10.4.0.2: icmp_seq=1 ttl=255 time=1.029 msec
264 bytes from 10.4.0.2: icmp_seq=2 ttl=255 time=1.041 msec
264 bytes from 10.4.0.2: icmp_seq=3 ttl=255 time=1.035 msec
264 bytes from 10.4.0.2: icmp_seq=4 ttl=255 time=1.020 msec
264 bytes from 10.4.0.2: icmp_seq=5 ttl=255 time=1.019 msec
264 bytes from 10.4.0.2: icmp_seq=6 ttl=255 time=1.016 msec
264 bytes from 10.4.0.2: icmp_seq=7 ttl=255 time=1.032 msec
264 bytes from 10.4.0.2: icmp_seq=8 ttl=255 time=1.039 msec
264 bytes from 10.4.0.2: icmp_seq=9 ttl=255 time=1.027 msec
264 bytes from 10.4.0.2: icmp_seq=10 ttl=255 time=1.029 msec
264 bytes from 10.4.0.2: icmp_seq=11 ttl=255 time=1.025 msec
264 bytes from 10.4.0.2: icmp_seq=12 ttl=255 time=1.043 msec
264 bytes from 10.4.0.2: icmp_seq=13 ttl=255 time=1.041 msec
264 bytes from 10.4.0.2: icmp_seq=14 ttl=255 time=1.026 msec
264 bytes from 10.4.0.2: icmp_seq=15 ttl=255 time=1.025 msec
264 bytes from 10.4.0.2: icmp_seq=16 ttl=255 time=1.022 msec
264 bytes from 10.4.0.2: icmp_seq=17 ttl=255 time=1.020 msec
264 bytes from 10.4.0.2: icmp_seq=18 ttl=255 time=1.053 msec
264 bytes from 10.4.0.2: icmp_seq=19 ttl=255 time=1.029 msec
264 bytes from 10.4.0.2: icmp_seq=20 ttl=255 time=1.024 msec
264 bytes from 10.4.0.2: icmp_seq=21 ttl=255 time=1.027 msec
264 bytes from 10.4.0.2: icmp_seq=22 ttl=255 time=1.022 msec
264 bytes from 10.4.0.2: icmp_seq=23 ttl=255 time=1.035 msec
264 bytes from 10.4.0.2: icmp_seq=24 ttl=255 time=1.023 msec
264 bytes from 10.4.0.2: icmp_seq=25 ttl=255 time=1.021 msec
264 bytes from 10.4.0.2: icmp_seq=26 ttl=255 time=1.024 msec
264 bytes from 10.4.0.2: icmp_seq=27 ttl=255 time=1.031 msec
264 bytes from 10.4.0.2: icmp_seq=28 ttl=255 time=1.031 msec
264 bytes from 10.4.0.2: icmp_seq=29 ttl=255 time=1.022 msec
--- 10.4.0.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 0.778/1.020/1.053/0.052 ms
PING 10.4.0.2 (10.4.0.2) from 10.4.0.1 : 512(540) bytes of data.
520 bytes from 10.4.0.2: icmp_seq=0 ttl=255 time=1.000 msec
Embedded Virtual Private Network: PerIormance and Scalability
91
520 bytes from 10.4.0.2: icmp_seq=1 ttl=255 time=1.227 msec
520 bytes from 10.4.0.2: icmp_seq=2 ttl=255 time=1.232 msec
520 bytes from 10.4.0.2: icmp_seq=3 ttl=255 time=1.227 msec
520 bytes from 10.4.0.2: icmp_seq=4 ttl=255 time=1.249 msec
520 bytes from 10.4.0.2: icmp_seq=5 ttl=255 time=1.241 msec
520 bytes from 10.4.0.2: icmp_seq=6 ttl=255 time=1.289 msec
520 bytes from 10.4.0.2: icmp_seq=7 ttl=255 time=1.256 msec
520 bytes from 10.4.0.2: icmp_seq=8 ttl=255 time=1.268 msec
520 bytes from 10.4.0.2: icmp_seq=9 ttl=255 time=1.286 msec
520 bytes from 10.4.0.2: icmp_seq=10 ttl=255 time=1.246 msec
520 bytes from 10.4.0.2: icmp_seq=11 ttl=255 time=1.234 msec
520 bytes from 10.4.0.2: icmp_seq=12 ttl=255 time=1.247 msec
520 bytes from 10.4.0.2: icmp_seq=13 ttl=255 time=1.238 msec
520 bytes from 10.4.0.2: icmp_seq=14 ttl=255 time=1.260 msec
520 bytes from 10.4.0.2: icmp_seq=15 ttl=255 time=1.237 msec
520 bytes from 10.4.0.2: icmp_seq=16 ttl=255 time=1.238 msec
520 bytes from 10.4.0.2: icmp_seq=17 ttl=255 time=1.234 msec
520 bytes from 10.4.0.2: icmp_seq=18 ttl=255 time=1.242 msec
520 bytes from 10.4.0.2: icmp_seq=19 ttl=255 time=1.207 msec
520 bytes from 10.4.0.2: icmp_seq=20 ttl=255 time=1.236 msec
520 bytes from 10.4.0.2: icmp_seq=21 ttl=255 time=1.241 msec
520 bytes from 10.4.0.2: icmp_seq=22 ttl=255 time=1.230 msec
520 bytes from 10.4.0.2: icmp_seq=23 ttl=255 time=1.228 msec
520 bytes from 10.4.0.2: icmp_seq=24 ttl=255 time=1.206 msec
520 bytes from 10.4.0.2: icmp_seq=25 ttl=255 time=1.232 msec
520 bytes from 10.4.0.2: icmp_seq=26 ttl=255 time=1.233 msec
520 bytes from 10.4.0.2: icmp_seq=27 ttl=255 time=1.231 msec
520 bytes from 10.4.0.2: icmp_seq=28 ttl=255 time=1.240 msec
520 bytes from 10.4.0.2: icmp_seq=29 ttl=255 time=1.255 msec
--- 10.4.0.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 1.000/1.233/1.289/0.046 ms
PING 10.4.0.2 (10.4.0.2) from 10.4.0.1 : 1024(1052) bytes of data.
1032 bytes from 10.4.0.2: icmp_seq=0 ttl=255 time=1.455 msec
1032 bytes from 10.4.0.2: icmp_seq=1 ttl=255 time=1.679 msec
1032 bytes from 10.4.0.2: icmp_seq=2 ttl=255 time=1.676 msec
1032 bytes from 10.4.0.2: icmp_seq=3 ttl=255 time=1.685 msec
1032 bytes from 10.4.0.2: icmp_seq=4 ttl=255 time=1.678 msec
1032 bytes from 10.4.0.2: icmp_seq=5 ttl=255 time=1.684 msec
1032 bytes from 10.4.0.2: icmp_seq=6 ttl=255 time=1.668 msec
1032 bytes from 10.4.0.2: icmp_seq=7 ttl=255 time=1.666 msec
1032 bytes from 10.4.0.2: icmp_seq=8 ttl=255 time=1.686 msec
1032 bytes from 10.4.0.2: icmp_seq=9 ttl=255 time=1.677 msec
1032 bytes from 10.4.0.2: icmp_seq=10 ttl=255 time=1.687 msec
1032 bytes from 10.4.0.2: icmp_seq=11 ttl=255 time=1.678 msec
1032 bytes from 10.4.0.2: icmp_seq=12 ttl=255 time=1.675 msec
1032 bytes from 10.4.0.2: icmp_seq=13 ttl=255 time=1.678 msec
1032 bytes from 10.4.0.2: icmp_seq=14 ttl=255 time=1.700 msec
1032 bytes from 10.4.0.2: icmp_seq=15 ttl=255 time=1.691 msec
1032 bytes from 10.4.0.2: icmp_seq=16 ttl=255 time=1.685 msec
1032 bytes from 10.4.0.2: icmp_seq=17 ttl=255 time=1.680 msec
1032 bytes from 10.4.0.2: icmp_seq=18 ttl=255 time=1.681 msec
1032 bytes from 10.4.0.2: icmp_seq=19 ttl=255 time=1.665 msec
1032 bytes from 10.4.0.2: icmp_seq=20 ttl=255 time=1.687 msec
1032 bytes from 10.4.0.2: icmp_seq=21 ttl=255 time=1.686 msec
1032 bytes from 10.4.0.2: icmp_seq=22 ttl=255 time=1.675 msec
1032 bytes from 10.4.0.2: icmp_seq=23 ttl=255 time=1.681 msec
1032 bytes from 10.4.0.2: icmp_seq=24 ttl=255 time=1.692 msec
1032 bytes from 10.4.0.2: icmp_seq=25 ttl=255 time=1.686 msec
1032 bytes from 10.4.0.2: icmp_seq=26 ttl=255 time=1.645 msec
1032 bytes from 10.4.0.2: icmp_seq=27 ttl=255 time=1.682 msec
1032 bytes from 10.4.0.2: icmp_seq=28 ttl=255 time=1.679 msec
1032 bytes from 10.4.0.2: icmp_seq=29 ttl=255 time=1.678 msec
--- 10.4.0.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 1.455/1.672/1.700/0.047 ms
PING 10.4.0.2 (10.4.0.2) from 10.4.0.1 : 2048(2076) bytes of data.
2056 bytes from 10.4.0.2: icmp_seq=0 ttl=255 time=1.872 msec
2056 bytes from 10.4.0.2: icmp_seq=1 ttl=255 time=2.017 msec
2056 bytes from 10.4.0.2: icmp_seq=2 ttl=255 time=1.988 msec
Embedded Virtual Private Network: PerIormance and Scalability
92
2056 bytes from 10.4.0.2: icmp_seq=3 ttl=255 time=2.006 msec
2056 bytes from 10.4.0.2: icmp_seq=4 ttl=255 time=2.017 msec
2056 bytes from 10.4.0.2: icmp_seq=5 ttl=255 time=1.996 msec
2056 bytes from 10.4.0.2: icmp_seq=6 ttl=255 time=2.021 msec
2056 bytes from 10.4.0.2: icmp_seq=7 ttl=255 time=2.000 msec
2056 bytes from 10.4.0.2: icmp_seq=8 ttl=255 time=2.010 msec
2056 bytes from 10.4.0.2: icmp_seq=9 ttl=255 time=1.991 msec
2056 bytes from 10.4.0.2: icmp_seq=10 ttl=255 time=2.015 msec
2056 bytes from 10.4.0.2: icmp_seq=11 ttl=255 time=2.030 msec
2056 bytes from 10.4.0.2: icmp_seq=12 ttl=255 time=2.004 msec
2056 bytes from 10.4.0.2: icmp_seq=13 ttl=255 time=1.999 msec
2056 bytes from 10.4.0.2: icmp_seq=14 ttl=255 time=2.018 msec
2056 bytes from 10.4.0.2: icmp_seq=15 ttl=255 time=2.006 msec
2056 bytes from 10.4.0.2: icmp_seq=16 ttl=255 time=2.019 msec
2056 bytes from 10.4.0.2: icmp_seq=17 ttl=255 time=1.996 msec
2056 bytes from 10.4.0.2: icmp_seq=18 ttl=255 time=2.006 msec
2056 bytes from 10.4.0.2: icmp_seq=19 ttl=255 time=2.002 msec
2056 bytes from 10.4.0.2: icmp_seq=20 ttl=255 time=2.002 msec
2056 bytes from 10.4.0.2: icmp_seq=21 ttl=255 time=2.019 msec
2056 bytes from 10.4.0.2: icmp_seq=22 ttl=255 time=2.029 msec
2056 bytes from 10.4.0.2: icmp_seq=23 ttl=255 time=2.011 msec
2056 bytes from 10.4.0.2: icmp_seq=24 ttl=255 time=2.068 msec
2056 bytes from 10.4.0.2: icmp_seq=25 ttl=255 time=2.034 msec
2056 bytes from 10.4.0.2: icmp_seq=26 ttl=255 time=2.046 msec
2056 bytes from 10.4.0.2: icmp_seq=27 ttl=255 time=2.009 msec
2056 bytes from 10.4.0.2: icmp_seq=28 ttl=255 time=2.032 msec
2056 bytes from 10.4.0.2: icmp_seq=29 ttl=255 time=1.999 msec
--- 10.4.0.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 1.872/2.008/2.068/0.062 ms
PING 10.4.0.2 (10.4.0.2) from 10.4.0.1 : 4096(4124) bytes of data.
4104 bytes from 10.4.0.2: icmp_seq=0 ttl=255 time=2.521 msec
4104 bytes from 10.4.0.2: icmp_seq=1 ttl=255 time=2.566 msec
4104 bytes from 10.4.0.2: icmp_seq=2 ttl=255 time=2.607 msec
4104 bytes from 10.4.0.2: icmp_seq=3 ttl=255 time=2.555 msec
4104 bytes from 10.4.0.2: icmp_seq=4 ttl=255 time=2.533 msec
4104 bytes from 10.4.0.2: icmp_seq=5 ttl=255 time=2.526 msec
4104 bytes from 10.4.0.2: icmp_seq=6 ttl=255 time=2.539 msec
4104 bytes from 10.4.0.2: icmp_seq=7 ttl=255 time=2.520 msec
4104 bytes from 10.4.0.2: icmp_seq=8 ttl=255 time=2.526 msec
4104 bytes from 10.4.0.2: icmp_seq=9 ttl=255 time=2.516 msec
4104 bytes from 10.4.0.2: icmp_seq=10 ttl=255 time=2.533 msec
4104 bytes from 10.4.0.2: icmp_seq=11 ttl=255 time=2.534 msec
4104 bytes from 10.4.0.2: icmp_seq=12 ttl=255 time=2.569 msec
4104 bytes from 10.4.0.2: icmp_seq=13 ttl=255 time=2.522 msec
4104 bytes from 10.4.0.2: icmp_seq=14 ttl=255 time=2.553 msec
4104 bytes from 10.4.0.2: icmp_seq=15 ttl=255 time=2.521 msec
4104 bytes from 10.4.0.2: icmp_seq=16 ttl=255 time=2.550 msec
4104 bytes from 10.4.0.2: icmp_seq=17 ttl=255 time=2.550 msec
4104 bytes from 10.4.0.2: icmp_seq=18 ttl=255 time=2.540 msec
4104 bytes from 10.4.0.2: icmp_seq=19 ttl=255 time=2.540 msec
4104 bytes from 10.4.0.2: icmp_seq=20 ttl=255 time=2.551 msec
4104 bytes from 10.4.0.2: icmp_seq=21 ttl=255 time=2.542 msec
4104 bytes from 10.4.0.2: icmp_seq=22 ttl=255 time=2.530 msec
4104 bytes from 10.4.0.2: icmp_seq=23 ttl=255 time=2.556 msec
4104 bytes from 10.4.0.2: icmp_seq=24 ttl=255 time=2.536 msec
4104 bytes from 10.4.0.2: icmp_seq=25 ttl=255 time=2.546 msec
4104 bytes from 10.4.0.2: icmp_seq=26 ttl=255 time=2.567 msec
4104 bytes from 10.4.0.2: icmp_seq=27 ttl=255 time=2.512 msec
4104 bytes from 10.4.0.2: icmp_seq=28 ttl=255 time=2.551 msec
4104 bytes from 10.4.0.2: icmp_seq=29 ttl=255 time=2.535 msec
--- 10.4.0.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 2.512/2.541/2.607/0.057 ms
PING 10.4.0.2 (10.4.0.2) from 10.4.0.1 : 8192(8220) bytes of data.
8200 bytes from 10.4.0.2: icmp_seq=0 ttl=255 time=3.682 msec
8200 bytes from 10.4.0.2: icmp_seq=1 ttl=255 time=3.867 msec
8200 bytes from 10.4.0.2: icmp_seq=2 ttl=255 time=3.848 msec
8200 bytes from 10.4.0.2: icmp_seq=3 ttl=255 time=3.870 msec
8200 bytes from 10.4.0.2: icmp_seq=4 ttl=255 time=3.848 msec
Embedded Virtual Private Network: PerIormance and Scalability
93
8200 bytes from 10.4.0.2: icmp_seq=5 ttl=255 time=3.862 msec
8200 bytes from 10.4.0.2: icmp_seq=6 ttl=255 time=3.853 msec
8200 bytes from 10.4.0.2: icmp_seq=7 ttl=255 time=3.869 msec
8200 bytes from 10.4.0.2: icmp_seq=8 ttl=255 time=3.881 msec
8200 bytes from 10.4.0.2: icmp_seq=9 ttl=255 time=3.858 msec
8200 bytes from 10.4.0.2: icmp_seq=10 ttl=255 time=3.856 msec
8200 bytes from 10.4.0.2: icmp_seq=11 ttl=255 time=3.858 msec
8200 bytes from 10.4.0.2: icmp_seq=12 ttl=255 time=3.893 msec
8200 bytes from 10.4.0.2: icmp_seq=13 ttl=255 time=3.861 msec
8200 bytes from 10.4.0.2: icmp_seq=14 ttl=255 time=3.850 msec
8200 bytes from 10.4.0.2: icmp_seq=15 ttl=255 time=3.846 msec
8200 bytes from 10.4.0.2: icmp_seq=16 ttl=255 time=3.905 msec
8200 bytes from 10.4.0.2: icmp_seq=17 ttl=255 time=3.884 msec
8200 bytes from 10.4.0.2: icmp_seq=18 ttl=255 time=3.881 msec
8200 bytes from 10.4.0.2: icmp_seq=19 ttl=255 time=3.844 msec
8200 bytes from 10.4.0.2: icmp_seq=20 ttl=255 time=3.837 msec
8200 bytes from 10.4.0.2: icmp_seq=21 ttl=255 time=3.834 msec
8200 bytes from 10.4.0.2: icmp_seq=22 ttl=255 time=3.885 msec
8200 bytes from 10.4.0.2: icmp_seq=23 ttl=255 time=3.893 msec
8200 bytes from 10.4.0.2: icmp_seq=24 ttl=255 time=3.854 msec
8200 bytes from 10.4.0.2: icmp_seq=25 ttl=255 time=3.854 msec
8200 bytes from 10.4.0.2: icmp_seq=26 ttl=255 time=3.883 msec
8200 bytes from 10.4.0.2: icmp_seq=27 ttl=255 time=3.849 msec
8200 bytes from 10.4.0.2: icmp_seq=28 ttl=255 time=3.849 msec
8200 bytes from 10.4.0.2: icmp_seq=29 ttl=255 time=3.845 msec
--- 10.4.0.2 ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss
round-trip min/avg/max/mdev = 3.682/3.856/3.905/0.079 ms
PING 10.4.0.2 (10.4.0.2) from 10.4.0.1 : 16384(16412) bytes of data.
16392 bytes from 10.4.0.2: icmp_seq=0 ttl=255 time=1.993 sec
16392 bytes from 10.4.0.2: icmp_seq=1 ttl=255 time=1.999 sec
--- 10.4.0.2 ping statistics ---
30 packets transmitted, 2 packets received, 93% packet loss
round-trip min/avg/max/mdev = 1993.215/1996.557/1999.899/3.342 ms
PING 10.4.0.2 (10.4.0.2) from 10.4.0.1 : 32768(32796) bytes of data.
--- 10.4.0.2 ping statistics ---
30 packets transmitted, 0 packets received, 100% packet loss
PING 10.4.0.2 (10.4.0.2) from 10.4.0.1 : 65507(65535) bytes of data.
--- 10.4.0.2 ping statistics ---
30 packets transmitted, 0 packets received, 100% packet loss