neutron ipsecvpn create step

admin · 发表于 2019-4-26 10:09:31

马上注册，结交更多好友，享用更多功能，让你轻松玩转社区。

您需要登录才可以下载或查看，没有账号？开始注册

x

以下为手动编写这个文件:
cd /usr/share/openstack-dashboard/openstack_dashboard/enabled/
touch _7100_project_vpn_panel.py
文件内容如下:
[root@localhost enabled]# vim _7100_project_vpn_panel.py
# Licensed under the Apache License, Version 2.0 (the "License"); you may
# not use this file except in compliance with the License. You may obtain
# a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
# License for the specific language governing permissions and limitations
# under the License.

# The slug of the panel to be added to HORIZON_CONFIG. Required.
PANEL = 'vpn'
# The slug of the dashboard the PANEL associated with. Required.
PANEL_DASHBOARD = 'project'
# The slug of the panel group the PANEL is associated with.
PANEL_GROUP = 'network'

# Python panel class of the PANEL to be added.
ADD_PANEL = 'neutron_vpnaas_dashboard.dashboards.project.vpn.panel.VPN'

ADD_INSTALLED_APPS = ["neutron_vpnaas_dashboard"]

4.1 vim /etc/neutron/neutron.conf
[DEFAULT]
service_plugins = router,vpnaas

4.2 vim  /etc/neutron/neutron_vpnaas.conf
[service_providers]
service_provider = VPN:strongswan:neutron_vpnaas.services.vpn.service_drivers.ipsec.IPsecVPNDriver:default

4.3 vim /etc/neutron/l3_agent.ini
[agent]
extensions = vpnaas
[vpnagent]
vpn_device_driver = neutron_vpnaas.services.vpn.device_drivers.strongswan_ipsec.StrongSwanDriver

4.4 执行 neutron-db-manage --subproject neutron-vpnaas upgrade head

5. 重启服务
systemctl restart neutron-server
systemctl restart neutron-l3-agent
systemctl restart apache2
---------------------

Virtual Private Network-as-a-Service (VPNaaS)

THIS PAGE LAST UPDATED:
Enabling VPNaaS¶
This section describes the setting for the reference implementation. Vendor plugins or drivers can have different setup procedure and perhaps they provide their version of manuals.
Enable the VPNaaS plug-in in the /etc/neutron/neutron.conf file by appending vpnaas to service_plugins in [DEFAULT]:
[DEFAULT]
# ...
service_plugins = vpnaas
Note
vpnaas is just example of reference implementation. It depends on a plugin that you are going to use. Consider to set suitable plugin for your own deployment.
Configure the VPNaaS service provider by creating the /etc/neutron/neutron_vpnaas.conf file as follows, strongswan used in Ubuntu distribution:
[service_providers]
service_provider = VPN:strongswan:neutron_vpnaas.services.vpn.service_drivers.ipsec.IPsecVPNDriver:default
Note
There are several kinds of service drivers. Depending upon the Linux distribution, you may need to override this value. Select libreswan for RHEL/CentOS, the config will like this: service_provider = VPN:openswan:neutron_vpnaas.services.vpn.service_drivers.ipsec.IPsecVPNDriver:default. Consider to use the appropriate one for your deployment.
Configure the VPNaaS plugin for the L3 agent by adding to /etc/neutron/l3_agent.ini the following section, StrongSwanDriver used in Ubuntu distribution:
[AGENT]
extensions = vpnaas
[vpnagent]
vpn_device_driver = neutron_vpnaas.services.vpn.device_drivers.strongswan_ipsec.StrongSwanDriver
Note
There are several kinds of device drivers. Depending upon the Linux distribution, you may need to override this value. Select LibreSwanDriver for RHEL/CentOS, the config will like this: vpn_device_driver = neutron_vpnaas.services.vpn.device_drivers.libreswan_ipsec.LibreSwanDriver. Consider to use the appropriate drivers for your deployment.
Create the required tables in the database:
# neutron-db-manage --subproject neutron-vpnaas upgrade head
Note
In order to run the above command, you need to have neutron-vpnaas package installed on controller node.
Restart the neutron-server in controller node to apply the settings.
Restart the neutron-l3-agent in network node to apply the settings.
Using VPNaaS with endpoint group (recommended)¶
IPsec site-to-site connections will support multiple local subnets, in addition to the current multiple peer CIDRs. The multiple local subnet feature is triggered by not specifying a local subnet, when creating a VPN service. Backwards compatibility is maintained with single local subnets, by providing the subnet in the VPN service creation.
To support multiple local subnets, a new capability called “End Point Groups” has been added. Each endpoint group will define one or more endpoints of a specific type, and can be used to specify both local and peer endpoints for IPsec connections. The endpoint groups separate the “what gets connected” from the “how to connect” for a VPN service, and can be used for different flavors of VPN, in the future.
Refer Multiple Local Subnets for more detail.
Create the IKE policy, IPsec policy, VPN service, local endpoint group and peer endpoint group. Then, create an IPsec site connection that applies the above policies and service.
Create an IKE policy:
$ openstack vpn ike policy create ikepolicy
  +-------------------------------+----------------------------------------+
  | Field                      | Value                               |
  +-------------------------------+----------------------------------------+
  | Authentication Algorithm    | sha1                                  |
  | Description                |                                     |
  | Encryption Algorithm       | aes-128                               |
  | ID                         | 735f4691-3670-43b2-b389-f4d81a60ed56 |
  | IKE Version                | v1                                  |
  | Lifetime                   | {u'units': u'seconds', u'value': 3600} |
  | Name                         | ikepolicy                            |
  | Perfect Forward Secrecy (PFS) | group5                               |
  | Phase1 Negotiation Mode    | main                                  |
  | Project                      | 095247cb2e22455b9850c6efff407584    |
  | project_id                   | 095247cb2e22455b9850c6efff407584    |
  +-------------------------------+----------------------------------------+
Create an IPsec policy:
$ openstack vpn ipsec policy create ipsecpolicy
  +-------------------------------+----------------------------------------+
  | Field                      | Value                               |
  +-------------------------------+----------------------------------------+
  | Authentication Algorithm    | sha1                                  |
  | Description                |                                     |
  | Encapsulation Mode          | tunnel                               |
  | Encryption Algorithm       | aes-128                               |
  | ID                         | 4f3f46fc-f2dc-4811-a642-9601ebae310f |
  | Lifetime                   | {u'units': u'seconds', u'value': 3600} |
  | Name                         | ipsecpolicy                         |
  | Perfect Forward Secrecy (PFS) | group5                               |
  | Project                      | 095247cb2e22455b9850c6efff407584    |
  | Transform Protocol          | esp                                  |
  | project_id                   | 095247cb2e22455b9850c6efff407584    |
  +-------------------------------+----------------------------------------+
Create a VPN service:
$ openstack vpn service create vpn \
  --router 9ff3f20c-314f-4dac-9392-defdbbb36a66
  +----------------+--------------------------------------+
  | Field       | Value                               |
  +----------------+--------------------------------------+
  | Description |                                     |
  | Flavor       | None                               |
  | ID          | 9f499f9f-f672-4ceb-be3c-d5ff3858c680 |
  | Name          | vpn                               |
  | Project       | 095247cb2e22455b9850c6efff407584    |
  | Router       | 9ff3f20c-314f-4dac-9392-defdbbb36a66 |
  | State       | True                               |
  | Status       | PENDING_CREATE                      |
  | Subnet       | None                               |
  | external_v4_ip | 192.168.20.7                      |
  | external_v6_ip | 2001:db8::7                         |
  | project_id    | 095247cb2e22455b9850c6efff407584    |
  +----------------+--------------------------------------+
Note
Please do not specify --subnet option in this case.
The Networking openstackclient requires a router (Name or ID) and name.
Create local endpoint group:
$ openstack vpn endpoint group create ep_subnet \
  --type subnet \
  --value 1f888dd0-2066-42a1-83d7-56518895e47d
  +-------------+-------------------------------------------+
  | Field    | Value                                  |
  +-------------+-------------------------------------------+
  | Description |                                        |
  | Endpoints | [u'1f888dd0-2066-42a1-83d7-56518895e47d'] |
  | ID       | 667296d0-67ca-4d0f-b676-7650cf96e7b1    |
  | Name       | ep_subnet                               |
  | Project    | 095247cb2e22455b9850c6efff407584       |
  | Type       | subnet                                  |
  | project_id  | 095247cb2e22455b9850c6efff407584       |
  +-------------+-------------------------------------------+
Note
The type of a local endpoint group must be subnet.
Create peer endpoint group:
$ openstack vpn endpoint group create ep_cidr \
  --type cidr \
  --value 192.168.1.0/24
  +-------------+--------------------------------------+
  | Field    | Value                               |
  +-------------+--------------------------------------+
  | Description |                                     |
  | Endpoints | [u'192.168.1.0/24']                |
  | ID       | 5c3d7f2a-4a2a-446b-9fcf-9a2557cfc641 |
  | Name       | ep_cidr                            |
  | Project    | 095247cb2e22455b9850c6efff407584    |
  | Type       | cidr                               |
  | project_id  | 095247cb2e22455b9850c6efff407584    |
  +-------------+--------------------------------------+
Note
The type of a peer endpoint group must be cidr.
Create an ipsec site connection:
$ openstack vpn ipsec site connection create conn \
  --vpnservice vpn \
  --ikepolicy ikepolicy \
  --ipsecpolicy ipsecpolicy \
  --peer-address 192.168.20.9 \
  --peer-id 192.168.20.9 \
  --psk secret \
  --local-endpoint-group ep_subnet \
  --peer-endpoint-group ep_cidr
  +--------------------------+--------------------------------------------------------+
  | Field                   | Value                                                 |
  +--------------------------+--------------------------------------------------------+
  | Authentication Algorithm | psk                                                 |
  | Description             |                                                       |
  | ID                      | 07e400b7-9de3-4ea3-a9d0-90a185e5b00d                |
  | IKE Policy             | 735f4691-3670-43b2-b389-f4d81a60ed56                |
  | IPSec Policy          | 4f3f46fc-f2dc-4811-a642-9601ebae310f                |
  | Initiator             | bi-directional                                        |
  | Local Endpoint Group ID  | 667296d0-67ca-4d0f-b676-7650cf96e7b1                |
  | Local ID                |                                                       |
  | MTU                   | 1500                                                 |
  | Name                   | conn                                                 |
  | Peer Address          | 192.168.20.9                                        |
  | Peer CIDRs             |                                                       |
  | Peer Endpoint Group ID | 5c3d7f2a-4a2a-446b-9fcf-9a2557cfc641                |
  | Peer ID                | 192.168.20.9                                        |
  | Pre-shared Key          | secret                                              |
  | Project                | 095247cb2e22455b9850c6efff407584                      |
  | Route Mode             | static                                              |
  | State                   | True                                                 |
  | Status                | PENDING_CREATE                                        |
  | VPN Service             | 9f499f9f-f672-4ceb-be3c-d5ff3858c680                |
  | dpd                   | {u'action': u'hold', u'interval': 30, u'timeout': 120} |
  | project_id             | 095247cb2e22455b9850c6efff407584                      |
  +--------------------------+--------------------------------------------------------+
Note
Please do not specify --peer-cidr option in this case. Peer CIDR(s) are provided by a peer endpoint group.
Configure VPNaaS without endpoint group (the legacy way)¶
Create the IKE policy, IPsec policy, VPN service. Then, create an ipsec site connection that applies the above policies and service.
Create an IKE policy:
$ openstack vpn ike policy create ikepolicy1
  +-------------------------------+----------------------------------------+
  | Field                      | Value                               |
  +-------------------------------+----------------------------------------+
  | Authentication Algorithm    | sha1                                  |
  | Description                |                                     |
  | Encryption Algorithm       | aes-128                               |
  | ID                         | 99e4345d-8674-4d73-acb4-0e2524425e34 |
  | IKE Version                | v1                                  |
  | Lifetime                   | {u'units': u'seconds', u'value': 3600} |
  | Name                         | ikepolicy1                            |
  | Perfect Forward Secrecy (PFS) | group5                               |
  | Phase1 Negotiation Mode    | main                                  |
  | Project                      | 095247cb2e22455b9850c6efff407584    |
  | project_id                   | 095247cb2e22455b9850c6efff407584    |
  +-------------------------------+----------------------------------------+
Create an IPsec policy:
$ openstack vpn ipsec policy create ipsecpolicy1
  +-------------------------------+----------------------------------------+
  | Field                      | Value                               |
  +-------------------------------+----------------------------------------+
  | Authentication Algorithm    | sha1                                  |
  | Description                |                                     |
  | Encapsulation Mode          | tunnel                               |
  | Encryption Algorithm       | aes-128                               |
  | ID                         | e6f547af-4a1d-4c28-b40b-b97cce746459 |
  | Lifetime                   | {u'units': u'seconds', u'value': 3600} |
  | Name                         | ipsecpolicy1                         |
  | Perfect Forward Secrecy (PFS) | group5                               |
  | Project                      | 095247cb2e22455b9850c6efff407584    |
  | Transform Protocol          | esp                                  |
  | project_id                   | 095247cb2e22455b9850c6efff407584    |
  +-------------------------------+----------------------------------------+
Create a VPN service:
$ openstack vpn service create vpn \
  --router 66ca673a-cbbd-48b7-9fb6-bfa7ee3ef724 \
  --subnet cdfb411e-e818-466a-837c-7f96fc41a6d9
  +----------------+--------------------------------------+
  | Field       | Value                               |
  +----------------+--------------------------------------+
  | Description |                                     |
  | Flavor       | None                               |
  | ID          | 79ef6250-ddc3-428f-88c2-0ec8084f4e9a |
  | Name          | vpn                               |
  | Project       | 095247cb2e22455b9850c6efff407584    |
  | Router       | 66ca673a-cbbd-48b7-9fb6-bfa7ee3ef724 |
  | State       | True                               |
  | Status       | PENDING_CREATE                      |
  | Subnet       | cdfb411e-e818-466a-837c-7f96fc41a6d9 |
  | external_v4_ip | 192.168.20.2                      |
  | external_v6_ip | 2001:db8::d                         |
  | project_id    | 095247cb2e22455b9850c6efff407584    |
  +----------------+--------------------------------------+
Note
The --subnet option is required in this scenario.
Create an ipsec site connection:
$ openstack vpn ipsec site connection create conn \
  --vpnservice vpn \
  --ikepolicy ikepolicy1 \
  --ipsecpolicy ipsecpolicy1 \
  --peer-address 192.168.20.11 \
  --peer-id 192.168.20.11 \
  --peer-cidr 192.168.1.0/24 \
  --psk secret
  +--------------------------+--------------------------------------------------------+
  | Field                   | Value                                                 |
  +--------------------------+--------------------------------------------------------+
  | Authentication Algorithm | psk                                                 |
  | Description             |                                                       |
  | ID                      | 5b2935e6-b2f0-423a-8156-07ed48703d13                |
  | IKE Policy             | 99e4345d-8674-4d73-acb4-0e2524425e34                |
  | IPSec Policy          | e6f547af-4a1d-4c28-b40b-b97cce746459                |
  | Initiator             | bi-directional                                        |
  | Local Endpoint Group ID  | None                                                 |
  | Local ID                |                                                       |
  | MTU                   | 1500                                                 |
  | Name                   | conn                                                 |
  | Peer Address          | 192.168.20.11                                        |
  | Peer CIDRs             | 192.168.1.0/24                                        |
  | Peer Endpoint Group ID | None                                                 |
  | Peer ID                | 192.168.20.11                                        |
  | Pre-shared Key          | secret                                              |
  | Project                | 095247cb2e22455b9850c6efff407584                      |
  | Route Mode             | static                                              |
  | State                   | True                                                 |
  | Status                | PENDING_CREATE                                        |
  | VPN Service             | 79ef6250-ddc3-428f-88c2-0ec8084f4e9a                |
  | dpd                   | {u'action': u'hold', u'interval': 30, u'timeout': 120} |
  | project_id             | 095247cb2e22455b9850c6efff407584                      |
  +--------------------------+--------------------------------------------------------+
Note
Please do not specify --local-endpoint-group and --peer-endpoint-group options in this case.

admin · 发表于 2019-4-26 10:17:48

Installation
In order to use Neutron-VPNaaS with devstack (http://devstack.org) a single node setup, you'll need the following settings in your local.conf (NEW: neutron-vpnaas plugin is added).

[[local|localrc]]

enable_plugin neutron-vpnaas https://git.openstack.org/openstack/neutron-vpnaas

disable_service n-net
enable_service q-svc
enable_service q-agt
enable_service q-dhcp
enable_service q-l3
enable_service q-meta
# Optional, to enable tempest configuration as part of devstack
enable_service tempest

# IPSec driver to use. Optional, defaults to OpenSwan.
IPSEC_PACKAGE="openswan"
Quick Test Script
http://paste.openstack.org/raw/44702/

This quick test script create two site with a router,a network and a subnet connected with public network. Then, connect both site via VPN.

Using Two DevStack Nodes for Testing
You can use two DevStack nodes connected by a common "public" network to test VPNaaS. The second node can be set up with the same public network as the first node, except it will use a different gateway IP (and hence router IP). In this example, we'll assume we have two DevStack nodes (East and West), each running on hardware (you can do the same thing with multiple VM guests, if desired). (Note: you can also create similar topology using two virtual routers with one devstack)

Example Topology

A dedicated physical port can be used for the "public" network connection (e.g. eth2) interconnected by a physical switch. You'll need to add the port to the OVS bridge on each DevStack node (e.g. sudo ovs-vsctl add-port br-ex eth2).

   (10.1.0.0/24 - DevStack East)
            |
            |  10.1.0.1
   [Neutron Router]
            |  172.24.4.226
            |
            |  172.24.4.225
   [Internet GW]
            |
            |
   [Internet GW]
            | 172.24.4.232
            |
            | 172.24.4.233
   [Neutron Router]
            |  10.2.0.1
            |
   (10.2.0.0/24 DevStack West)
DevStack Configuration

For East you can append these lines to the localrc, which will give you a private net of 10.1.0.0/24 and public network of 172.24.4.0/24

PUBLIC_SUBNET_NAME=yoursubnet
PRIVATE_SUBNET_NAME=mysubnet
FIXED_RANGE=10.1.0.0/24
NETWORK_GATEWAY=10.1.0.1
PUBLIC_NETWORK_GATEWAY=172.24.4.225
Q_FLOATING_ALLOCATION_POOL=start=172.24.4.226,end=172.24.4.231
For West you can add these lines to localrc to use a different local network, public GW (and implicitly router) IP:

PUBLIC_SUBNET_NAME=yoursubnet
PRIVATE_SUBNET_NAME=mysubnet
FIXED_RANGE=10.2.0.0/24
NETWORK_GATEWAY=10.2.0.1
PUBLIC_NETWORK_GATEWAY=172.24.4.232
Q_FLOATING_ALLOCATION_POOL=start=172.24.4.233,end=172.24.4.238
VPNaaS Configuration

With DevStack running on East and West and connectivity confirmed (make sure you can ping one router/GW from the other), you can perform these VPNaaS CLI commands.

On East

neutron vpn-ikepolicy-create ikepolicy1
neutron vpn-ipsecpolicy-create ipsecpolicy1
neutron vpn-service-create --name myvpn --description "My vpn service" router1 mysubnet
neutron ipsec-site-connection-create --name vpnconnection1 --vpnservice-id myvpn --ikepolicy-id ikepolicy1 --ipsecpolicy-id ipsecpolicy1 --peer-address 172.24.4.233 --peer-id 172.24.4.233 --peer-cidr 10.2.0.0/24 --psk secret
On West

neutron vpn-ikepolicy-create ikepolicy1
neutron vpn-ipsecpolicy-create ipsecpolicy1
neutron vpn-service-create --name myvpn --description "My vpn service" router1 mysubnet
neutron ipsec-site-connection-create --name vpnconnection1 --vpnservice-id myvpn --ikepolicy-id ikepolicy1 --ipsecpolicy-id ipsecpolicy1 --peer-address 172.24.4.226 --peer-id 172.24.4.226 --peer-cidr 10.1.0.0/24 --psk secret
Note: Please make sure setup security group (open icmp for vpn subnet etc)

Verification

You can spin up VMs on each node, and then from the VM ping the far end router's public IP. With tcpdump running on one of the nodes, you can see that pings appear as encrypted packets (ESP). Note that BOOTP, IGMP, and the keepalive packets between the two nodes are not encrypted (nor are pings between the two external IP addresses).

Kilo Update

For Kilo, the localrc contents was moved into local.conf. With (VirtualBox) VMs used as hosts, where eth0 was set up as NAT, and eth1 set up as Internal Network, the following configurations were used in local.conf:

OVS_PHYSICAL_BRIDGE=br-ex
PUBLIC_INTERFACE=eth1
Once stacked, VMs were created for testing, VPN IPSec commands used to establish connections between the nodes, and security group rules added to allow ICMP and SSH.

VPNaaS with Single DevStack and Two Routers
Simple instructions on how to setup a test environment where a VPNaaS IPSec connection can be established using the reference implementation (OpenSwan). This example uses VIrtualBox running on laptop to provide a VM for running DevStack. It assumes a Kilo release (post Juno).

The idea here is to have a single OpenStack cloud created using DevStack, two routers (one created automatically), two private networks (one created automatically) -10.1.0.0/24 and 10.2.0.0/24, a VM in each private network, and establish a VPN connection between the two private nets, using the public network (172.24.4.0/24).

Preparation
Create a VM (e.g. 7 GB RAM, 2 CPUs) running Ubuntu 14.04, with NAT I/F for access to the Internet. Clone a DevStack repo with latest (Kilo-1 used for this example).

DevStack Configuration
For this example, the following local.conf is used:

localrc
GIT_BASE=https://github.com
DEST=/opt/stack

disable_service n-net
enable_service q-svc
enable_service q-agt
enable_service q-dhcp
enable_service q-l3
enable_service q-meta
enable_service neutron
enable_plugin neutron-vpnaas https://git.openstack.org/openstack/neutron-vpnaas

FIXED_RANGE=10.1.0.0/24
FIXED_NETWORK_SIZE=256
NETWORK_GATEWAY=10.1.0.1
PRIVATE_SUBNET_NAME=privateA

PUBLIC_SUBNET_NAME=public-subnet
FLOATING_RANGE=172.24.4.0/24
PUBLIC_NETWORK_GATEWAY=172.24.4.10
Q_FLOATING_ALLOCATION_POOL="start=172.24.4.11,end=172.24.4.29"

LIBVIRT_TYPE=qemu

IMAGE_URLS="http://cloud-images.ubuntu.com/releases/14.04.1/release/ubuntu-14.04-server-cloudimg-amd64.tar.gz,http://download.cirros-cloud.net ... 3-x86_64-uec.tar.gz"

SCREEN_LOGDIR=/opt/stack/screen-logs
SYSLOG=True
LOGFILE=~/devstack/stack.sh.log

ADMIN_PASSWORD=password
MYSQL_PASSWORD=password
RABBIT_PASSWORD=password
SERVICE_PASSWORD=password
SERVICE_TOKEN=tokentoken

Q_USE_DEBUG_COMMAND=True

# RECLONE=No
RECLONE=yes
OFFLINE=False
Start up the cloud using ./stack.sh and ensure it completes successfully. Once stacked, you can change RECLONE to No.

Cloud Configuration
Once stacking is completed, you'll have a private network (10.1.0.0/24), and a router (router1). To prepare for establishing a VPN connection, a second network, subnet, and router needs to be created, and a VM spun up in each private network.

# Create second net, subnet, router
source ~/devstack/openrc admin demo
neutron net-create privateB
neutron subnet-create --name subB privateB 10.2.0.0/24 --gateway 10.2.0.1
neutron router-create router2
neutron router-interface-add router2 subB
neutron router-gateway-set router2 public

# Start up a VM in the privateA subnet.
PRIVATE_NET=`neutron net-list | grep 'private ' | cut -f 2 -d' '`
nova boot --flavor 1 --image cirros-0.3.3-x86_64-uec --nic net-id=$PRIVATE_NET peter

# Start up a VM in the privateB subnet
PRIVATE_NETB=`neutron net-list | grep privateB | cut -f 2 -d' '`
nova boot --flavor 1 --image cirros-0.3.3-x86_64-uec --nic net-id=$PRIVATE_NETB paul
At this point, you can verify that you have basic connectivity. Note, DevStack will create a static route that will allow you to ping the private I/F IP of router1 from privateB network. You can remove the route, if desired.

IPSec Site-to-site Connection Creation
The following commands will create the IPSec connection:

# Create VPN connections
neutron vpn-ikepolicy-create ikepolicy
neutron vpn-ipsecpolicy-create ipsecpolicy
neutron vpn-service-create --name myvpn --description "My vpn service" router1 privateA

neutron ipsec-site-connection-create --name vpnconnection1 --vpnservice-id myvpn \
--ikepolicy-id ikepolicy --ipsecpolicy-id ipsecpolicy --peer-address 172.24.4.13 \
--peer-id 172.24.4.13 --peer-cidr 10.2.0.0/24 --psk secret

neutron vpn-service-create --name myvpnB --description "My vpn serviceB" router2 subB

neutron ipsec-site-connection-create --name vpnconnection2 --vpnservice-id myvpnB \
--ikepolicy-id ikepolicy --ipsecpolicy-id ipsecpolicy --peer-address 172.24.4.11 \
--peer-id 172.24.4.11 --peer-cidr 10.1.0.0/24 --psk secret
At this point (once the connections become active - which can take up to 30 seconds or so), you should be able to ping from the VM in the privateA network, to the VM in the privateB network. You'll see encrypted packets, if you tcpdump using the qg-# interface from one of the router namespaces. If you delete one of the connections, you'll see that the pings fail (if all works out correctly :).

Multiple Local Subnets
Early in Mitaka, IPSec site-to-site connections will support multiple local subnets, in addition to the current multiple peer CIDRs. The multiple local subnet feature is triggered by not specifying a local subnet, when creating a VPN service. Backwards compatibility is maintained with single local subnets, by providing the subnet in the VPN service creation.

To support multiple local subnets, a new capability has been provided (in Liberty), called "Endpoint Groups". Each endpoint group will define one or more endpoints of a specific type, and can be used to specify both local and peer endpoints for IPSec Connections. The Endpoint Groups separate the "what gets connected" from the "how to connect" for a VPN service, and can be used for different flavors of VPN, in the future. An example:

# Create VPN connections
neutron vpn-ikepolicy-create ikepolicy
neutron vpn-ipsecpolicy-create ipsecpolicy
neutron vpn-service-create --name myvpnC --description "My vpn service" router1
To prepare for an IPSec site-to-site, one would create an endpoint group for the local subnets, and an endpoint group for the peer CIDRs, like so:

neutron vpn-endpoint-group-create --name my-locals --type subnet --value privateA --value privateA2
neutron vpn-endpoint-group-create --name my-peers --type cidr --value 10.2.0.0/24 --value 20.2.0.0/24
where privateA and privateA2 are two local (private) subnets, and 10.2.0.0/24 and 20.2.0.0/24 are two CIDRs representing peer (private) subnets that will be used by a connection. Then, when creating the IPSec site-to-site connection, these endpoint group IDs would be specified, instead of the peer-cidrs attribute:

neutron ipsec-site-connection-create --name vpnconnection3 --vpnservice-id myvpnC \
--ikepolicy-id ikepolicy --ipsecpolicy-id ipsecpolicy --peer-address 172.24.4.11 \
--peer-id 172.24.4.11 --local-ep-group my-locals --peer-ep-group my-peers --psk secret
Notes:

The validation logic makes sure that endpoint groups and peer CIDRs are not intermixed.
Endpoint group types are subnet, cidr, network, router, and vlan. However, only subnet and cidr are implemented (for IPSec use).
The endpoints in a group must be of the same type, although can mix IP versions.
For IPSec connections, validation currently enforces that the local and peer endpoints all use the same IP version.
IPSec connection validation requires that local endpoints are subnets, and peer endpoints are CIDRs.
Migration will convert information for any existing VPN services and connections to endpoint groups.
The original APIs will work for backward compatibility.
Horizon Support
Checkout Test branch
Horizon support has been merged.

Enable VPN section in Horizon
Note that ff q-vpn is enabled Horizon VPN support is enabled automatically.

Open
/opt/stack/horizon/openstack_dashboard/local/local_settings.py
and replace

OPENSTACK_NEUTRON_NETWORK = {
'enable_vpn': False,
}
with

OPENSTACK_NEUTRON_NETWORK = {
'enable_vpn': True,
}

账号		自动登录	找回密码
密码			开始注册

neutron ipsecvpn create step

马上注册，结交更多好友，享用更多功能，让你轻松玩转社区。

浏览过的版块

站长推荐 /4