Документация по NETSHe

Эта страница только для чтения. Вы можете посмотреть её исходный текст, но не можете его изменить. Сообщите администратору, если считаете, что это неправильно.
====== DMVPN ======
<sub>{{DMVPN.odt|Original file}}</sub>

**NETSHe firmware user guide**

**DM VPN implementation**

2018 © NETSHe Lab Ltd.

====== DM VPN overview ======

======  ======

DM VPN is a technology to establish secured VPN over public IP networks such as Internet.

**DM VPN op****erates with two types of nodes:**

  * HUB which represent central office or cloud service and control all VPN connections;
  * SPOKE which represent branch office and establish connection to central office and (may be) another branches.
DM VPN implements star (all traffic in VPN goes through HUB) or full mesh (traffic goes between branches) topologies.

It is possible to prohibit spoke-to-spoke communications by firewall or advanced routing rules in star topology. This case may be useful to meet different enterprise requirements.

I other way, mesh topology allows to unload hub channels, to reduce hub load (and hub hardware requirements), to reduce spoke-to-spoke delay.

Spokes may have static or dynamically assigned IP address, may be behind NAT (*).

Hub must have static IP address and must not be behind NAT (**).

Hub may be addressed through FQDN (Full Qualified Domain Name). In case of FQDN addressing, using of dynamically assigned IP addresses is allowed with understanding and agreement about service interruption when Hub address is changing.

* Some types of NAT or NAT settings may prohibit DM VPN Spoke functionality. 

** Hub may be behind properly configured NAT with multi-point GRE and IPSec bypassing.

Typical DM VPN application is shown below.



**Hub**



{{настройка_dm_vpn_Image_0.png?101}}

{{настройка_dm_vpn_Image_1.png?292}}**VPN**

{{настройка_dm_vpn_Image_2.png?112}}**Spoke n**

{{настройка_dm_vpn_Image_2.png?112}}**Spoke 1**

{{настройка_dm_vpn_Image_2.png?112}}**Spoke 2**



******DMVPN Tunnels btween Spokes**

******Traditional Static Tunnels and DM VPN tunnels which match traditional**

******Static and known IP Addresses**

******Dynamically assigned IP Addresses**



====== DM VPN basics ======

======  ======

DM VPN relies on three proven technologies:

  - Next Hop Resolution Protocol (NHRP): Creates a distributed (NHRP) mapping database of all the spoke tunnels to real (public interface) addresses.
  - Multi-point GRE Tunnel Interface: Single GRE interface to support multiple GRE tunnels.
  - IPSec: Secures data through GRE tunnels.
To simplify and automate routing management, DM VPN also uses dynamic routing service like OSPF or BGP.

===== DM VPN components. NHRP. =====

=====  =====

Provides registration, resolution and redirect services.

NHRP registration:

  * Spoke dynamically registers its mapping with NHS
  * Supports spokes with dynamic NBMA addresses or NAT
 NHRP resolutions and redirects

  * Supports building dynamic spoke-to-hub and spoke-to-spoke tunnels
  * Creates star or full-mesh overlay network topology
===== DM VPN components. Multipoint GRE tunnel =====

=====  =====

Provides single tunnel interface and NHRP source.

Single tunnel interface (multi-point)

  * Non-Broadcast Multi-Access (NBMA) network
  * Smaller hub configuration
  * Multicast and broadcast support
  * Dynamic tunnel destination
Next Hop Resolution Protocol (NHRP)

  * VPN IP-to-NBMA IP address mapping
  * Short-cut forwarding
  * Direct support for dynamic addresses and NAT
===== DM VPN components. IPSec =====

=====  =====

DM VPN builds out a dynamic tunnel overlay network.

IPSec is triggered through “tunnel protection” and works with NHRP together:

  * NHRP triggers IPsec before installing new mappings.
  * IPSec notifies NHRP when encryption is ready.
  * NHRP installs mappings, and sends registration if needed.
  * NHRP and IPSec notify each other when a mapping or service assurance is cleared.
===== DM VPN components. Dynamic routing =====

=====  =====

Dynamic routing service such as BGP or OSPF is used to establich right routing rules to Hub and every Spoke automatically.

Each available routing services have own advantages:

  * OSPF requires less configuration.
  * BGP provides less delay for overlay network reconfiguration and routing exchange.
====== Major features ======

======  ======

  - DM VPN offers configuration reduction and no-touch deployment
  - Supports IP Unicast, IP Multicast, and dynamic routing protocols
  - Supports remote peers with dynamically assigned addresses
  - Supports spoke routers behind dynamic NAT and hub routers behind static NAT
  - Dynamic spoke-to-spoke tunnels for scaling partial- or full-mesh VPNs
  - Uses IPsec encryption to secure data
====== Typical use cases ======

======  ======

===== Controlled corporate extra-net network =====

=====  =====

Star topology. Spoke-to-spoke communications are prohibited (or controlled) by firewall or routing rules.



===== Meshed corporate network =====

=====  =====

Meshed topology. Spoke-to-spoke communications are allowed to reduce latency and hub load.

===== DM VPN as backup for MPLS network =====

=====  =====

Meshed topology. Spoke-to-spoke communications are allowed to reduce latency and hub load. DM VPN is used only when primary MPLS network is down.

==== DM VPN implementation details and limitations ====

====  ====

NETSHe firmware provides:

  * Simple configuration in a few steps
  * Hub and Spoke functionality out of the box.
  * PSK protected IPSec tunnels
  * OSPF or BGP routing over the overlay network. Routing does not require any additional configuration.
  * CISCO Hub and Spoke compatibility with BGP and OSPF routing over the overlay network.
Limitations:

  * Single or twoHub(s) in the network.
  * One device can act as one HUB only.
  * SPOKE can have no more than two configured tunnel to HUBs.
  * Requires to have default-route through main WAN interface for HUB and first/single SPOKE tunnels functionality.
  * Another vendor Hub and Spoke compatibility with OSPF is not tested yet. (*)
* - Work is in progress.

====== How to configure ======

======  ======

===== Typical supported topology =====

=====  =====

Current implementation supports next DM VPN topology:

  - Single HUB and single tunnel from SPOKE thorugh main (or single) WAN interface.
  - Single HUB and single tunnel from SPOKE through main WAN interface. Second WAN interface may be used as backup link for single tunnel.
  - Two HUBs (primary and backup) with two different concurrent tunnels through single WAN interface.
  - Two HUBs (primary and backup) with two different concurrent tunnels through main WAN interface and second WAN interface.
This topologies will be adressed below.

===== Spoke configuration =====

=====  =====

Spoke can be configured in two ways:

==== Through setup wizard or simple web-interface ====

====  ====

This way allow to configure SPOKE with single tunnel to single HUB in the network (topology 1) or primary tunnel for SPOKE for topologies 2,3 and 4 (second tunnel configuration will require to access full web-interface).

Please keep in mind that this way allows to configure cellular connection as backup or second WAN link for topologies 2 and 4.

To configure spoke, go through setup wizard till DM VPN configuration question as shown below.

{{настройка_dm_vpn_Image_5.png?642}}

Choose „Yes. I want to setup DM VPN spoke» option then fill DM VPN Hub address, Spoke private address, passphrase for IPSec, AS number if you want to use BGP routing and mandatory tunnel key.

Please keep in mind that Hub address may be FQDN as show below or

{{настройка_dm_vpn_Image_6.png?642}}

static IP address as shown below

{{настройка_dm_vpn_Image_7.png?642}}The last setup will use OSPF routing (AS number is zero).

Some optional parameters can be configured here like authentication secret and hold time for NHRP, tunnel cost, area, hello and dead time for OSPF, metric for BGP.

Complete setup wizard and reboot device. Enjoy running DM VPN spoke.

==== Through full web-interface ====

====  ====

This way allows to configure SPOKE to any available topologies.

To configure DM VPN Spoke through expert web-interface, please select menu „Services→Access concentrator→DM VPN» as shown below.

{{настройка_dm_vpn_Image_8.png?642}}

Tick „Enable SPOKE“ checkbox and fill related fields as shown below.

{{настройка_dm_vpn_Image_9.png?642}}

To configure second tunnel to another HUB, please select second tab.

It should be noted! Second tunnel can be configured through the same WAN interface as primary tunnel or through another WAN interface.

If system does not see second WAN interface, it will not offer to select source interface for second tunnel and will use primary WAN interface automatically.



It should be noted! Configuring DM VPN SPOKE with two concurrent tunnels through two WAN interfaces (topology 4) with concurrent default-routes will provide non predicable result.

We offer to implement topology 4 in next manner:

  * Configure primary WAN interface with default route (wire or cellular)
  * Configure second WAN interface without default route (wire or cellular). Use option ‘Do not replace exsiting default route’ when configure this interface.
  * Configure static route to second HUB through second WAN interface.
  * Configure second SPOKE tunnel to second HUB and select second WAN interface as tunnel source.
{{настройка_dm_vpn_Image_10.png?642}}

{{настройка_dm_vpn_Image_11.png?642}}

{{настройка_dm_vpn_Image_12.png?642}}

Press «Save» button. If you will tick «Restart service..» checkbox, you will be prompted to reboot device.

===== Hub configuration =====

=====  =====

Hub configuration is available in full web-interface only.

To configure DM VPN Hub, select menu «Services→Access concentrator→DM VPN». Tick «Enable HUB» checkbox and fill related fields as shown below.

{{настройка_dm_vpn_Image_13.png?642}}

Please keep in mind that when you used BGP routing (AS number is not zero), you must specify every SPOKE address. Of course, when you use OSPF routing (AS number is zero), you may not specify any SPOKE addresses.

Please keep inf mind that you must specify private network netmask for HUB setup. Any SPOKE addresses must be from network which is specified by HUB private address and netmask.

Another field which is specific for HUB setup is «Does HUB act as VPN node?». When this field is ticked, networks behind HUB LAN interfaces will be introduced to overlay network.

{{настройка_dm_vpn_Image_14.png?642}}

===== Why so few setup options are here? =====

=====  =====

We tried to simplify DM VPN setup process as possible:

  * We announce LAN side networks to the HUB by default.
  * We discover external WAN interface and WAN address automatically.
  * We create and setup all parts of DM VPN automatically.
  * We switch mGRE tunnel to another WAN interface and back in a backup process automatically.
====== Conclusion ======

======  ======

The security has never been so affordable!
Документация по NETSHe

Инструменты пользователя

Инструменты сайта

Инструменты страницы
