VPN Site-to-Site networking - Revision history

Horemu at 10:54, 24 April 2011

2011-04-24T10:54:06Z

Horemu at 18:39, 15 March 2007

2007-03-15T18:39:23Z

Horemu: heading 1 removed

2007-03-15T18:37:30Z

heading 1 removed

Davide.poletto: /* VPN without normal Internet traffic */ (Text modification)

2006-11-23T21:11:29Z

‎VPN without normal Internet traffic: (Text modification)

Davide.poletto: /* Overview */

2006-11-19T13:53:33Z

‎Overview

Davide.poletto: /* Important informations */

2006-11-19T11:57:32Z

‎Important informations

Davide.poletto: /* Important informations */

2006-11-18T14:30:35Z

‎Important informations

Davide.poletto at 14:28, 18 November 2006

2006-11-18T14:28:59Z

Davide.poletto: /* Important informations */

2006-11-18T14:26:15Z

‎Important informations

Davide.poletto at 14:24, 18 November 2006

2006-11-18T14:24:51Z

← Older revision		Revision as of 10:54, 24 April 2011
Line 1:		Line 1:
−	~~<div class="breadcrumb">~~	+	{{Breadcrumb\|0\|0\|Communications Systems}}
−	{{up}} ~~[[Platforms]]~~
−	~~</div>~~

	== VPN without normal Internet traffic ==		== VPN without normal Internet traffic ==

@@ Line 2: / Line 2: @@
 {{up}} [[Platforms]]
 </div>
 == VPN without normal Internet traffic ==

← Older revision		Revision as of 18:37, 15 March 2007
Line 4:		Line 4:

	__TOC__		__TOC__
−	~~= VPN Site-to-Site networking =~~

	== VPN without normal Internet traffic ==		== VPN without normal Internet traffic ==

@@ Line 8: / Line 8: @@
 == VPN without normal Internet traffic ==
-This Site-to-Site networking scenario lets an enterprises to use:
+This Site-to-Site networking scenario lets enterprises to use:
-* HiPath 2000 as [[VPN]] Site-to-Site gateway both for Voice and Data traffic.
+* HiPath 2000 as Site-to-Site [[VPN]] gateway both for Voice and Data traffic.
-* HiPath 2000 as a cost-effective gateway to route [[VoIP]] traffic by performing [[CorNet]]-IP trunking between sites over [[VPN]] trunk.
+* HiPath 2000 as a cost-effective gateway to route [[VoIP]] traffic by performing SIP and [[CorNet]]-IP IP trunking between sites over [[VPN]] trunk.
 * HiPath 2000 as gateway to access enterprise resources and applications available on the company’s [[VPN]] networked sites.

@@ Line 16: / Line 16: @@
 === Overview ===
-VPN Site-to-Site networking ''without'' normal Internet traffic '''Overview''' ''here''
+[[Image:H2k_VPN_StS_Networking_1.png|HiPath 2000 VPN Site-to-Site networking scenario without normal Internet traffic]]
 === Important informations ===

@@ Line 43: / Line 43: @@
 ** HiPath 2000 can manage [[VPN]] Bandwidth entirely (No Bandwith share with normal Internet traffic).
 ** HiPath 2000 lightweight processing power requirements handling and routing only Voice traffic over [[VPN]] Trunk.
-* Routing/Security policies demanded at additional Proxy/Firewall devices for normal unencrypted Internet traffic handling.
+* Routing/Security policies demanded to external Proxy/Firewall devices for normal unencrypted Internet traffic handling.
 == VPN with normal Internet traffic and QoS support ==

@@ Line 27: / Line 27: @@
 ** Customer need to ensure itself with additional ISP connection to Internet.
 ** Customer need to ensure additional devices/services like:
-*** Router, necessary to route LAN hosts normal data traffic to Internet.
+*** Router, necessary to route LAN hosts normal traffic to Internet.
 *** Firewall, necessary to protect LAN hosts and implement [[DMZ]] at site.
 *** Proxy, necessary to implement Internet traffic policies.

@@ Line 11: / Line 11: @@
 * HiPath 2000 as [[VPN]] Site-to-Site gateway both for Voice and Data traffic.
-* HiPath 2000 as a cost-effective gateway to route [[VoIP]] traffic by performing [[CorNet]]-IP trunking between sites over VPN trunk.
+* HiPath 2000 as a cost-effective gateway to route [[VoIP]] traffic by performing [[CorNet]]-IP trunking between sites over [[VPN]] trunk.
-* HiPath 2000 as gateway to access enterprise resources and applications available on the company’s VPN networked sites.
+* HiPath 2000 as gateway to access enterprise resources and applications available on the company’s [[VPN]] networked sites.
 === Overview ===
@@ Line 40: / Line 40: @@
 * Normal Internet traffic completely separated from Voice traffic by means of second Internet connection to ISP:
-** Voice quality over VPN is preserved from normal Internet traffic side effects (No Voice/Date traffic congestion, no burstly data traffic or high downstream can jam Voice connections).
+** Voice quality over [[VPN]] is preserved from normal Internet traffic side effects (No Voice/Date traffic congestion, no burstly data traffic or high downstream can jam Voice connections).
-** HiPath 2000 can manage VPN Bandwidth entirely (No Bandwith share with normal Internet traffic).
+** HiPath 2000 can manage [[VPN]] Bandwidth entirely (No Bandwith share with normal Internet traffic).
-** HiPath 2000 lightweight processing power requirements handling and routing only Voice traffic over VPN Trunk.
+** HiPath 2000 lightweight processing power requirements handling and routing only Voice traffic over [[VPN]] Trunk.
 * Routing/Security policies demanded at additional Proxy/Firewall devices for normal unencrypted Internet traffic handling.
@@ Line 53: / Line 53: @@
 === Important informations ===
-* The ISP must support [[QoS]] to ensure sufficient voice packet quality (According to specific [[SLA]])
+* The [[ISP]] must support [[QoS]] to ensure sufficient voice packet quality (According to specific [[SLA]])
 * HiPath 2000 as [[VPN]] Site-to-Site gateway to a single ISP access, used for both:
 ** Voice and Data traffic.
@@ Line 60: / Line 60: @@
 ** [[VoIP]] traffic by performing [[CorNet]]-IP trunking between sites over VPN trunk.
 ** normal Internet traffic to ISP.
-** traffic to DMZ at site.
+** traffic to [[DMZ]] at site.
 * External additional Proxy/Firewall:
-** must be capable to handle traffic carried by [VPN] transparently.
+** must be capable to handle traffic carried by [[VPN]] transparently.
 ** offer high level of Security for normal unencrypted Internet traffic
 * HiPath 2000 as gateway to access enterprise resources and applications available on the company’s [[VPN]] networked sites.
 * The ISP access can be overloaded (Available bandwidth could be used by massive or bursty downloads) affecting Voice quality first (Bursty data traffic, high downstream can jam Voice connections).
-* Operation of public servers on ([[DMZ]]) is only recommended QoS can be provided by ISP and access Router is able to support bandwidth control for both Voice and Data traffic.
+* Operation of public servers on ([[DMZ]]) is only recommended QoS can be provided by [[ISP]] and access Router is able to support bandwidth control for both Voice and Data traffic.
-* Not all ISPs are able nor have a suitable infrastructure ready to offer adequate QoS policies (Or QoS at all) on their Internet access.
+* Not all ISPs are able nor have a suitable infrastructure ready to offer adequate/any [[QoS]] features on their Internet access.