18.07.2013 Views

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 14: Configuring Virtual Private Networks<br />

Understanding virtual burbs<br />

406<br />

Figure 174: Virtual burb<br />

vs. a non-virtual burb VPN<br />

implementation<br />

that allow you to control precisely what your VPN users can or cannot do.<br />

Figure 174 illustrates this concept.<br />

VPN without a virtual burb<br />

<strong>Sidewinder</strong> <strong>G2</strong><br />

Internal<br />

network<br />

Trusted Internet<br />

burb burb<br />

Proxies<br />

VPN with a virtual burb<br />

<strong>Sidewinder</strong> <strong>G2</strong><br />

Internal<br />

network<br />

Trusted<br />

burb<br />

Proxies<br />

Proxies<br />

Virtual<br />

burb<br />

= VPN tunnel<br />

= Data<br />

Internet<br />

burb<br />

Internet<br />

Internet<br />

Non-VPN<br />

Client<br />

VPN<br />

Client<br />

Non-VPN<br />

Client<br />

VPN<br />

Client<br />

Note: Both VPN implementations depicted in Figure 174 represent “proxied” VPNs<br />

because proxies must be used to move VPN data between burbs. The use <strong>of</strong><br />

proxies enables you to control the resources that a VPN client has access to on<br />

your internal network.<br />

A virtual burb can support all the same services as a normal burb. If traffic<br />

coming from the virtual burb is destined to the <strong>Sidewinder</strong> <strong>G2</strong> itself (for<br />

example, DNS or SSH) the rule that allows traffic across that burb must specify<br />

a NAT address <strong>of</strong> localhost. If localhost is not specified, the <strong>Sidewinder</strong> <strong>G2</strong> will<br />

not be able to route traffic back to the originator.<br />

You can define up to 64 physical and virtual burbs. For example, if you have<br />

two distinct types <strong>of</strong> VPN associations and you want to apply a different set <strong>of</strong><br />

rules to each type, create two virtual burbs, then configure the required proxies<br />

and rules for each virtual burb.<br />

One question that might come to mind when using a virtual burb is: “How does<br />

VPN traffic get to the virtual burb if it doesn’t have a network card?” All VPN<br />

traffic originating from the Internet initially arrives via the network interface card<br />

in the Internet burb. A VPN security association, however, can internally route<br />

and logically terminate VPN traffic in any burb on the <strong>Sidewinder</strong> <strong>G2</strong>. By<br />

defining a security association to terminate the VPN in a virtual burb, the VPN<br />

traffic is automatically routed to that virtual burb within the <strong>Sidewinder</strong> <strong>G2</strong>.<br />

Thus, the trusted network now recognizes the virtual burb as the source burb<br />

for your VPN traffic. From the virtual burb, a proxy and rule are needed to move<br />

the traffic to a trusted burb with network access.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!