CN107517129A - A kind of method and apparatus based on OpenStack configuration equipment upstream Interfaces - Google Patents
A kind of method and apparatus based on OpenStack configuration equipment upstream Interfaces Download PDFInfo
- Publication number
- CN107517129A CN107517129A CN201710740862.1A CN201710740862A CN107517129A CN 107517129 A CN107517129 A CN 107517129A CN 201710740862 A CN201710740862 A CN 201710740862A CN 107517129 A CN107517129 A CN 107517129A
- Authority
- CN
- China
- Prior art keywords
- vlan
- address
- target
- binding relationship
- openstack
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
- H04L63/0272—Virtual private networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Small-Scale Networks (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application provides a kind of method and apparatus based on OpenStack configuration equipment upstream Interfaces, and methods described includes：When receiving the request of establishment virtual firewall of subscriber's main station transmission, the order for creating virtual firewall is sent to the firewall box, and send the VLAN ID in the binding relationship pre-established to firewall box, so that the firewall box creates virtual firewall and target VLAN ID is obtained from the VLAN ID；The target VLAN ID that the firewall box returns are received, and according to the binding relationship, obtain the target ip address with target VLAN ID bindings；The target ip address is sent to the firewall box, so that the firewall box configures the upstream Interface of the virtual firewall so that the target ip address and the target VLAN ID respectively become the IP address and VLAN ID of the upstream Interface.The technical method proposed using the application, realize the upstream Interface for automatically configuring equipment.
Description
Technical field
The application is related to network communication technology field, more particularly to a kind of based on OpenStack configuration equipment upstream Interfaces
Method and apparatus.
Background technology
OpenStack is that an implementation is simple, can on a large scale extend, enrich, the cloud computing management platform that standard is unified, several
Support all types of cloud environments.OpenStack service end is the service being made up of the various websites for providing different services
Cluster, is provided the foundation the solution that facility services by various complementary services, and each service provides API to be collected
Into.
OpenStack covers the various aspects such as network, virtualization, operating system, server.Wherein, OpenStack bags
Include the core project of multiple different service types, such as calculating, object storage, mirroring service, identity service, network ＆ addresses pipe
Manage (Neutron) etc..
Neutron provides the network virtualization technology of cloud computing, is the other service providing network connection clothes of OpenStack
Business, provides the user interface, can define Network, Subnet, Router, configuration DHCP, DNS, load balancing, L3 services,
Network support GRE, VLAN, FWaaS (FireWall as a Service, fire wall service) etc..
Wherein, the FWaaS realizes the function of fire wall by software.Due to realizing function by software, not as passing through
Hardware device realizes that function is powerful like that, thus it is common to use hardware device realizes the function of fire wall to replace FWaaS.Its
In, firewall box is generally deployed in network egress position.
Fig. 1 is referred to, Fig. 1 is a kind of network that virtual firewall is created based on OpenStack shown in the prior art
Connection diagram.In the prior art, when user, which operates OpenStack, creates virtual network, because the virtual network can not
Outer net is directly accessed, it is necessary to which outer net could be accessed by the physical equipment being connected with outer net.Meanwhile in order to safeguard network security,
Need to carry out Network Isolation by firewall box.Therefore, using firewall box as the virtual network and the bridge of outer net.For
The connection of the virtual network and firewall box is established, firewall box needs to fictionalize virtual fire prevention by virtualization technology
Wall, by establishing the connection of the virtual network and the virtual firewall, realize the communication of the virtual network and firewall box.
Formed because the virtual network is created by OpenStack, therefore the configuration data of the virtual network is stored in
OpenStack service ends.When subscriber's main station in the virtual network needs to receive and dispatch message, the message is intended to by OpenStack
Service end.
Further, since when creating virtual network by OpenSatck, the virtual firewall is only configured on firewall box
Downstream interface, wherein, the downstream interface refers to the virtual interface that the virtual network is communicated with the virtual protecting wall, because
This can only realize the communication of the virtual network and the virtual firewall equipment, can not realize the logical of the virtual network and outer net
Letter.In order to realize the communication of the virtual network and outer net, in the prior art, firewall box keeper needs preventing fires manually
It is the virtual network configuration upstream Interface on wall equipment, wherein, the upstream Interface refers to that the virtual firewall is carried out with outer net
The virtual interface of communication.
, it is necessary to specifying the IP of the upstream Interface when firewall box keeper is the virtual network configuration upstream Interface
Location, VLAN ID, default route etc., wherein, the next-hop device in default route is the upstream equipment of the firewall box.For
The communication of upstream equipment and the virtual firewall is realized, the keeper of upstream equipment is with being also required to the IP according to the upstream Interface
The information such as location, VLAN ID, interface corresponding with the upstream Interface is configured on the upstream equipment manually, including specify the interface
IP address, VLAN ID, backhaul route etc..
In the prior art, a virtual firewall is often created, is required for the keeper of firewall box to be set in fire wall
Standby manual collocating uplink interface, and need the keeper of upstream equipment manual configuration and the upstream Interface on upstream equipment
Corresponding interface.
The content of the invention
In view of this, the application provides a kind of method and apparatus based on OpenStack configuration equipment upstream Interfaces, realizes
The automatic configuration of equipment upstream Interface.
Specifically, the application is achieved by the following technical solution：
A kind of method based on OpenStack collocating uplink interfaces, it is described applied to OpenStack service ends
OpenStack service ends have been pre-configured with IP address range and VLAN scopes, including：
When receiving the request of establishment virtual firewall of subscriber's main station transmission, send and create to the firewall box
The order of virtual firewall, and the VLAN ID in the binding relationship pre-established are sent to firewall box, so that described
Firewall box creates virtual firewall and target VLAN ID is obtained from the VLAN ID；Wherein, the binding relationship
For the binding relationship between the VLAN ID in valid ip address and VLAN scopes；The valid ip address is to be had based on default
Effect IP computational algorithms are calculated from the IP address range；The target VLAN ID are the VLAN in the binding relationship
Any VLAN ID being not used by ID；
Receive the target VLAN ID that the firewall box returns, and according to the binding relationship, obtain with it is described
The target ip address of target VLAN ID bindings；
The target ip address is sent to the firewall box, so that firewall box configuration is described virtual anti-
The upstream Interface of wall with flues so that the target ip address and the target VLAN ID are with respectively becoming the IP of the upstream Interface
Location and VLAN ID.
A kind of method based on OpenStack configuration equipment upstream Interfaces, applied to firewall box, including：
Receive what OpenStack service ends were sent when receiving the request of establishment virtual firewall of subscriber's main station transmission
Create order and the VLAN ID of virtual firewall；Wherein, the VlAN ID that the OpenStack service ends are sent are described
VLAN ID in the binding relationship that OpenStack service ends pre-establish；Wherein, the binding relationship is valid ip address, with
The binding relationship of VLAN ID in the VLAN scopes being pre-configured with；The valid ip address is that the OpenStack services end group
It is calculated in default effectively IP computational algorithms from the IP address range；
Virtual firewall is created based on the order, and, in the binding relationship sent from OpenStack service ends
VLAN ID in select any VLAN ID being not used by as target VLAN ID, and by the target VLAN ID send to
The OpenStack service ends, so that the Openstack service ends obtain and the target VLAN from the binding relationship
The target ip address of ID bindings；
The target ip address that the OpenStack service ends are sent is received, and configures the upper of the virtual firewall
Line interface so that the target ip address and the target VLAN ID respectively become the IP address and VLAN of the upstream Interface
ID。
A kind of device based on OpenStack collocating uplink interfaces, it is described applied to OpenStack service ends
OpenStack service ends have been pre-configured with IP address range and VLAN scopes, including：
First transmitting element, for when receiving the request of establishment virtual firewall of subscriber's main station transmission, to described
Firewall box send create virtual firewall order, and by the VLAN ID in the binding relationship pre-established send to
Firewall box, so that the firewall box creates virtual firewall and target VLAN is obtained from the VLAN ID
ID；Wherein, the binding relationship is the binding relationship between the VLAN ID in valid ip address and VLAN scopes；It is described effective
IP address is to be calculated based on default effectively IP computational algorithms from the IP address range；The target VLAN ID are
Any VLAN ID being not used by VLAN ID in the binding relationship；
Acquiring unit, the target VLAN ID returned for receiving the firewall box, and closed according to the binding
System, obtain the target ip address with target VLAN ID bindings；
Second transmitting element, for the target ip address to be sent to the firewall box, so that the fire wall
The upstream Interface of virtual firewall described in device configuration so that the target ip address and the target VLAN ID respectively become
The IP address and VLAN ID of the upstream Interface.
A kind of device based on OpenStack configuration equipment upstream Interfaces, applied to firewall box, including：
Receiving unit, the establishment virtual firewall of subscriber's main station transmission is being received for receiving OpenStack service ends
Request when send establishment virtual firewall order and VLAN ID；Wherein, the OpenStack service ends are sent
VlAN ID are the VLAN ID in the binding relationship that the OpenStack service ends pre-establish；Wherein, the binding relationship is
Valid ip address, the binding relationship with the VLAN ID in the VLAN scopes that are pre-configured with；The valid ip address is described
OpenStack service ends are based on default effectively IP computational algorithms and are calculated from the IP address range；
Creating unit, for creating virtual firewall based on the order；
Selecting unit, it is any for being selected in the VLAN ID in the binding relationship that is sent from OpenStack service ends
The VLAN ID being not used by are as target VLAN ID；
Transmitting element, for the target VLAN ID to be sent to the OpenStack service ends, so that described
Openstack service ends obtain the target ip address with target VLAN ID bindings from the binding relationship；
Dispensing unit, the target ip address sent for receiving the OpenStack service ends, and configure the void
Intend the upstream Interface of fire wall so that the target ip address and the target VLAN ID respectively become the upstream Interface
IP address and VLAN ID.
Due to being configured with IP address range and VLAN scopes in OpenStack service ends in advance, and calculated based on effective IP
Valid ip address is calculated in algorithm secondary IP address scope, and has pre-established in valid ip address and VLAN scopes
Binding relationship between VLAN ID, therefore, when needing to create virtual firewall, OpenStack service ends will create virtual anti-
VLAN ID in the order of wall with flues and binding relationship are transmitted to firewall box.Firewall box creates virtual firewall, and
Any VLAN ID being not used by are selected to send target VLAN ID as target VLAN ID from the binding relationship
To OpenStack service ends.OpenStack service ends obtain the Target IP with target VLAN ID bindings from binding relationship
Address, and the target ip address is sent to firewall box.Firewall box collocating uplink interface, by the target ip address and
Target VLAN ID are automatically based on OpenStack so as to realize respectively as the IP address and VLAN ID of the upstream Interface
Virtual firewall collocating uplink interface.
Brief description of the drawings
Fig. 1 is a kind of network connection schematic diagram that virtual firewall is created based on OpenStack shown in the prior art；
Fig. 2 is a kind of method flow that equipment upstream Interface is configured based on OpenStack shown in the embodiment of the present application one
Figure；
Fig. 3 is a kind of device place that equipment upstream Interface is configured based on OpenStack of the embodiment of the present application two
A kind of hardware structure diagram of OpenStack service ends；
Fig. 4 is a kind of device that equipment upstream Interface is configured based on OpenStack shown in the embodiment of the present application two；
Fig. 5 is a kind of device place fire wall that equipment upstream Interface is configured based on OpenStack of the embodiment of the present application three
A kind of hardware structure diagram of equipment；
Fig. 6 is a kind of device that equipment upstream Interface is configured based on OpenStack shown in the embodiment of the present application three.
Embodiment
Here exemplary embodiment will be illustrated in detail, its example is illustrated in the accompanying drawings.Following description is related to
During accompanying drawing, unless otherwise indicated, the same numbers in different accompanying drawings represent same or analogous key element.Following exemplary embodiment
Described in embodiment do not represent all embodiments consistent with the application.On the contrary, they be only with it is such as appended
The example of the consistent apparatus and method of some aspects be described in detail in claims, the application.
It is only merely for the purpose of description specific embodiment in term used in this application, and is not intended to be limiting the application.
" one kind " of singulative used in the application and appended claims, " described " and "the" are also intended to including majority
Form, unless context clearly shows that other implications.It is also understood that term "and/or" used herein refers to and wrapped
Containing the associated list items purpose of one or more, any or all may be combined.
It will be appreciated that though various information, but this may be described using term first, second, third, etc. in the application
A little information should not necessarily be limited by these terms.These terms are only used for same type of information being distinguished from each other out.For example, do not departing from
In the case of the application scope, the first information can also be referred to as the second information, and similarly, the second information can also be referred to as
One information.Depending on linguistic context, word as used in this " if " can be construed to " ... when " or " when ...
When " or " in response to determining ".
Embodiment one
In order to realize the automatic configuration of equipment upstream Interface, the embodiment of the present application one provides one kind and is based on
The method that OpenStack configures equipment upstream Interface, refers to Fig. 2, and Fig. 2 is that one kind shown in the embodiment of the present application one is based on
OpenStack configures the method flow diagram of equipment upstream Interface.It is specific to perform following steps：
Step 201：OpenStack service ends initialize, and establish in valid ip address and the VLAN scopes that are pre-configured with
Binding relationship between VLAN ID；
In the present embodiment, OpenStack service ends have been pre-configured with IP address range and VLAN scopes.Wherein, it is described
IP address range belongs to outer net IP address range, IP address range can be expanded and changed according to actual demand.
When OpenStack service ends initialize, default effectively IP computational algorithms can be based on, to the IP that is pre-configured with
Location scope is calculated, and valid ip address is obtained from the IP address range.Wherein, the valid ip address is to distribute to
The IP address that virtual firewall upstream Interface uses.
In the present embodiment, the IP address used due to distributing to the upstream Interface of virtual firewall, and distribute to and void
Intending the IP address that the upstream equipment interface that fire wall is communicated uses must must belong in same network, therefore, it is necessary to extremely
The IP address that an IP address used with distributing to virtual firewall upstream Interface belongs to consolidated network less be present.Wherein, by
The two reserved IP address of reservation networks address and broadcast address are needed in any network, distribute to that virtual firewall is up to be connect
The IP address and distribute to the IP address that the upstream equipment interface to be communicated with virtual firewall uses that mouth uses, for network
The legitimate ip address distributed to main frame and used beyond location and broadcast address, therefore, distributes to virtual firewall upstream Interface
Comprised at least in network where the legitimate ip address used two reserved addresses and two can distribute to main frame use it is legal
IP address.
Wherein, effective IP computational algorithms are that OpenStack service ends obtain from the IP address range being pre-configured with can be with
The legitimate ip address set that main frame uses is distributed to, then determines to distribute on virtual firewall from the legitimate ip address set
The valid ip address set that line interface uses.
For example, it is 10.1.1.0/30~10.1.2.0/30 in the IP address range that OpenStack service ends are pre-configured with.
Because the subnet mask of the IP address in the IP address range is 30, then the network of each IP address in the IP address range
Position is first 30 in 32 IP address, and main frame position is latter two, wherein, main frame position full 0 and complete 1 IP address are backup land
Location, it is impossible to distribute to main frame use, therefore only two legitimate ip address can distribute in the IP address of two main frame positions compositions
Used to main frame.In other words, the IP address range can be divided into it is multiple only two can distribute to main frame use it is legal
The subnet of IP address.
The legitimate ip address that upstream Interface due to distributing to virtual firewall uses, and distribute to and enter with virtual firewall
The legitimate ip address that uses of upstream equipment interface of row communication must belong to same network, therefore, in each subnet two can
Distribute in the legitimate ip address that main frame uses one and distribute to the upstream Interface for needing to configure and uses, another is distributed to and void
Intend the upstream equipment interface that fire wall is communicated to use.
Secondary IP address scope 10.1.1.0/30~10.1.2.0/30 can obtain distributing to main frame use shown in table 1
Legitimate ip address.
| Subnet sequence number | IP address 1 | IP address 2 |
| 1 | 10.1.1.1 | 10.1.1.2 |
| 2 | 10.1.1.5 | 10.1.1.6 |
| 3 | 10.1.1.9 | 10.1.1.10 |
| 4 | 10.1.1.13 | 10.1.1.14 |
| … | … | … |
| 65 | 10.1.1.253 | 10.1.1.254 |
Table 1
According to table 1, two in same subnet can distribute to the legitimate ip address that main frame uses, one of IP
Last position of address is odd number, and last position of another IP address is the IP of the IP address 1 in even number, such as subnet 1
10.1.1.1 last position in location is 1, and last position of the IP address 10.1.1.2 of IP address 2 is 2.
Assuming that OpenStack service ends are by IP address, last is that the IP address of odd number is defined as to distribute to virtually
The IP address of fire wall upstream Interface, the default effectively IP computational algorithms of Openstack service ends are as follows：
1), initial ip address is obtained in secondary IP address scope；
2) whether the IP address for, judging to get is legitimate ip address；If the IP address is not legitimate ip address, hold
Row 3)；If the IP address is legitimate ip address, perform 4)；
3) the IP address binary digit, is obtained in secondary IP address scope and adds the IP address after 1, judges to add the IP address after 1
Whether in IP address range, if performed 2), if not, terminating；
4), judge last parity of the IP address, if even number, then perform 3)；If odd number, by this
IP address is added in default IP lists, and is added last+4*n of IP address IP address in secondary IP address scope
Add in IP lists, wherein, n is positive integer.
5), read IP lists in last IP address, judge the IP address last plus 1 after IP address whether
In the IP address range of preset configuration.If retaining the IP address in IP lists, if it does not, by the IP address
Deleted from IP lists.
Due to two legitimate ip address in same subnet, last is that the numerical value of even number more than last position is odd number
Numerical value, therefore, above-mentioned steps 4) in, if last position of the valid ip address of first acquisition be even number, then preset
The legitimate ip address for belonging to same subnet with the IP address is not present in the IP address range of configuration, therefore, the IP address can not
With.
Because last position of each IP address in IP lists is odd number, last IP address is probably pre- in IP lists
Last IP address in the IP address range that establishing is put, therefore, above-mentioned steps 5) in need to judge last in IP lists
Last of IP address adds the IP address after 1 whether in the IP address range of preset configuration, if in IP lists
Retain the IP address, if it does not exist, then the IP address is deleted from IP lists.
Certainly, OpenStack service ends can also distribute to last of IP address for the legitimate ip address of even number
Virtual firewall upstream Interface uses.
It should be noted that in the present embodiment, effective IP computational algorithms are needed according to the IP address range being pre-configured with
Change correspondingly adjusted, effective IP computational algorithms can be with flexible and changeable, to effective IP computational algorithms not in this application
It is defined.
In the present embodiment, in OpenStack service ends initialization procedure, default IP address ordering mechanism can be based on
The valid ip address is ranked up, is then sequentially added into default IP lists；And default VLAN can be based on
VLAN ID in the VLAN scopes are ranked up by ordering mechanism, and the VLAN ID in the VLAN scopes being pre-configured with are added
Into default vlan list.
For example, with reference to above-mentioned example in the present embodiment, it is assumed that IP address ordering mechanism is according to the last of valid ip address
The order of the numerical value of one from small to large is ranked up to valid ip address, and VLAN ordering mechanisms are the numerical value according to VLAN ID
Order from small to large is ranked up to the VLAN ID in the VLAN scopes that are pre-configured with, and assumes the VLAN being pre-configured with
Scope is 1~VLAN of VLAN 50.OpenStack service ends can obtain the IP lists shown in table 2 in initialization procedure, with
And the vlan list shown in table 3.
Table 2
| Sequence number | VLAN ID |
| 1 | VLAN 1 |
| 2 | VLAN 2 |
| 3 | VLAN 3 |
| … | … |
| 50 | VLAN 50 |
Table 3
In the present embodiment, after Openstack service ends have obtained IP lists and vlan list, can establish in IP lists
Valid ip address and vlan list in same sequence number VLAN ID between binding relationship.
Wherein, VLAN ID quantity may differ in the quantity of valid ip address and vlan list in IP lists, establish
May have after binding relationship between valid ip address and the VLAN ID of same sequence number, in IP lists and be left to have for what is be bound
May have in effect IP address, or vlan list and be left as bound VLAN ID, it is also possible in IP lists valid ip address and
VLAN ID in vlan list have been bound.
Step 202：OpenStack service ends send the order for creating virtual firewall to firewall box, and will tie up
The VLAN ID determined in relation are sent to firewall box；
In the present embodiment, after OpenStack service ends complete initialization, OpenStack service ends have had been set up
The binding relationship between VLAN ID in effect IP address and the VLAN scopes being pre-configured with.When OpenStack service ends receive
When subscriber's main station sends the request for creating virtual protecting wall, OpenStack service ends can send to firewall box and create void
Intend the order of fire wall, and the VLAN ID in binding relationship are sent to firewall box.
Step 203：Order of the firewall box based on the establishment virtual firewall, virtual firewall is created, and, from
Any VLAN ID being not used by are selected as mesh in VLAN ID in the binding relationship that OpenStack service ends are sent
Mark VLAN ID；
In the present embodiment, when firewall box receives the establishment virtual firewall of OpenStack service ends transmission
During order, firewall box can be based on virtualization technology and generate a virtual firewall.Meanwhile firewall box receives
After VLAN ID in the binding relationship that OpenStack service ends are sent, firewall box can search the VLAN in binding relationship
With the presence or absence of the VLAN ID being not used by ID.
If the VLAN ID being not used by the VLAN ID in binding relationship be present, firewall box can never be made
By the use of VLAN ID in select any VLAN ID as target VLAN ID, and target VLAN ID are sent to OpenStack
Service end；If the VLAN ID in binding relationship are used, firewall box sends VLAN to OpenSatck service ends
The information that ID is used.
Step 204：When OpenStack service ends receive the target VLAN ID of firewall box transmission,
OpenStack service ends send the target ip address with target VLAN ID bindings to firewall box；
In the present embodiment, when OpenStack service ends receive the target VLAN ID of firewall box transmission,
OpenStack service ends will search the valid ip address with target VLAN ID bindings from binding relationship.OpenStack
Service end sends the target ip address to firewall box using the valid ip address as target ip address.
Step 205：When OpenStack service ends receive the information that is used of VLAN ID of firewall box transmission
When, OpenStack service ends send the prompt message of certain resource to subscriber's main station；
When OpenStack service ends receive firewall box transmission VLAN ID used information when,
OpenStack service ends, which will search, whether there is unbound valid ip address in IP lists, and be in lookup vlan list
It is no unbound VLAN ID to be present；
If there is not bound valid ip address, and the VLAN ID in the VLAN scopes are bound, to described
Subscriber's main station sends the prompt message of increase VLAN scopes；
If valid ip address is bound, and has not bound VLAN ID in the VLAN scopes, to the use
Householder's machine sends the prompt message of increase IP address range；
If valid ip address is bound, and the VLAN ID in the VLAN scopes are bound, and householder is used to described
Machine sends the prompt message of increase IP address range and VLAN scopes.
When subscriber's main station receives prompt message, keeper needs in OpenStack service ends to be increased according to prompt message
Add IP address range, and/or VLAN scopes；Wherein, increased IP address range, and/or VLAN scopes are added original respectively
Behind the IP address range of configuration, and/or the VLAN scopes originally configured, OpenStack can be so avoided to be based on originally matching somebody with somebody
After the change of the IP address range, the data of VLAN scopes generation put, reduces IP address range, and/or VLAN scopes change
OpenStack service ends are based on IP address range, the VLAN range computation valid ip address originally configured, and establish binding and close
The process of system.
Step 206：When firewall box receives target ip address, firewall box configures the up of virtual firewall
Interface, and using target ip address and target VLAN ID as the IP address of upstream Interface and VLAN ID.
In the present embodiment, when firewall box receives the target ip address of OpenStack service ends transmission, fire prevention
Wall equipment will be the virtual firewall collocating uplink interface created, the IP using the target ip address as the upstream Interface
Location, the VLAN ID using target VLAN ID as the upstream Interface.
In addition, firewall box, which will also be the upstream Interface, configures security domain, VRF (Virtual Routing and
Forwarding, virtual forwarding and route), and default route.Wherein, the next-hop ip address in default route be with it is up
Interface belongs to the IP address of consolidated network, i.e., the IP address of the upstream equipment interface to be communicated with virtual firewall, fire wall
Equipment can determine next-hop ip address based on default default route computational algorithm, and the default route computational algorithm needs basis
The IP scopes and default effectively IP computational algorithms being pre-configured with adjust accordingly.In addition, how to be configured for interface safe
Domain and VRF, correlation technique is referred to, is repeated no more in this application.
For example, with reference to the example in the present embodiment, because last position of valid ip address is odd number, and with it is each effectively
The legitimate ip address that IP address belongs to consolidated network only has one, and therefore, default route computational algorithm is：Determine Target IP
Last of address adds the IP address after 1 to be next-hop ip address in default route.If last position of valid ip address
It is even number, and the legitimate ip address for belonging to consolidated network with each valid ip address only has one, therefore, default route calculates
Algorithm is：Last IP address after subtracting 1 for determining target ip address is next-hop ip address in default route.
In the present embodiment, upstream equipment is based on IP address range, the VLAN models being pre-configured with OpenStack service ends
Enclose, binding relationship, effective IP computational algorithms etc., be configured with some interfaces to be communicated with virtual firewall in advance.Wherein, when
IP address range that OpenStack service ends are pre-configured with, VLAN scopes, binding relationship, effective IP computational algorithms etc. are wherein appointed
When one parameter changes, upstream equipment will pair interface to be communicated with virtual firewall modify.
For example, with reference to the example in the present embodiment, when valid ip address from last position is that odd number becomes last position and is
During the IP address of even number, the IP address of the interface to be communicated with virtual firewall of upstream equipment configuration is even from last position
Count and become last IP address for odd number, last position of the next-hop ip address in backhaul route becomes last for odd number
One IP address for even number.
In summary, due to being configured with IP address range and VLAN scopes in OpenStack service ends in advance, and it is based on having
Valid ip address is calculated in effect IP computational algorithm secondary IP address scopes, and has pre-established valid ip address and VLAN models
Binding relationship between the VLAN ID enclosed, therefore, when needing to create virtual firewall, OpenStack service ends will create
VLAN ID in the order of virtual firewall and binding relationship are transmitted to firewall box.Firewall box creates virtual anti-
Wall with flues, and any VLAN ID being not used by are selected as target VLAN ID from the binding relationship, by target VLAN
ID is sent to OpenStack service ends.OpenStack service ends obtain and target VLAN ID bindings from binding relationship
Target ip address, and the target ip address is sent to firewall box.Firewall box collocating uplink interface, by the Target IP
Address and target VLAN ID respectively as the upstream Interface IP address and VLAN ID, so as to realize based on OpenStack
Automatic is virtual firewall collocating uplink interface.
Embodiment two
It is corresponding with a kind of foregoing embodiment one of the method based on OpenStack configuration equipment upstream Interfaces, the application
Additionally provide a kind of embodiment two of the device based on OpenStack configuration equipment upstream Interfaces.
A kind of embodiment two of the device based on OpenStack configuration equipment upstream Interfaces of the application can be applied
In OpenStack service ends.Device embodiment two can be realized by software, can also pass through hardware or software and hardware combining
Mode is realized.It is by OpenStack service ends where it as the device on a logical meaning exemplified by implemented in software
Processor corresponding computer program instructions in nonvolatile memory are read in internal memory what operation was formed.From hardware layer
For face, as shown in figure 3, for where a kind of device that equipment upstream Interface is configured based on OpenStack of the embodiment of the present application two
A kind of hardware structure diagram of OpenStack service ends, except the processor shown in Fig. 3, internal memory, network interface and non-volatile
Property memory outside, OpenStack service ends in embodiment two where device are based on OpenStack with installing generally according to this
The actual functional capability of standby upstream Interface, can also include other hardware, this is repeated no more.
Fig. 4 is referred to, Fig. 4 is that one kind shown in the embodiment of the present application two is based on OpenStack configuration equipment upstream Interfaces
Device, applied to OpenStack service ends.Described device includes：First transmitting element 410, acquiring unit 420, second are sent out
Send unit 430.
First transmitting element 410, for when receive subscriber's main station transmission establishment virtual firewall request when,
The order for creating virtual firewall is sent to the firewall box, and by the VLAN ID in the binding relationship pre-established
Send to firewall box, so that the firewall box creates virtual firewall and obtains target from the VLAN ID
VLAN ID；Wherein, the binding relationship is the binding relationship between the VLAN ID in valid ip address and VLAN scopes；It is described
Valid ip address is to be calculated based on default effectively IP computational algorithms from the IP address range；The target VLAN
ID is any VLAN ID being not used by the VLAN ID in the binding relationship；
The acquiring unit 420, the target VLAN ID returned for receiving the firewall box, and according to institute
Binding relationship is stated, obtains the target ip address with target VLAN ID bindings；
Second transmitting element 430, for the target ip address to be sent to the firewall box, so that described
Firewall box configures the upstream Interface of the virtual firewall so that the target ip address and the target VLAN ID points
Not Cheng Wei the upstream Interface IP address and VLAN ID.
In the present embodiment, described device also includes：
Sequencing unit, for the valid ip address to be ranked up based on default IP address ordering mechanism, Yi Jiji
The VLAN ID in the VLAN scopes are ranked up in default VLAN ordering mechanisms；
Unit is established, for establishing the binding relationship between valid ip address and the VLAN ID of same sequence number.
Judging unit, if the VLAN ID in the binding relationship returned for receiving the firewall box are equal
The message used, judge whether in the valid ip address not being bound, and the VLAN scopes with the presence or absence of not by
The VLAN ID of binding；
Prompting message transmitting element, for if there is not bound valid ip address, and in the VLAN scopes
VLAN ID are bound, and the prompt message of increase VLAN scopes is sent to the subscriber's main station；If valid ip address is tied up
It is fixed, and not bound VLAN ID in the VLAN scopes be present, send carrying for increase IP address range to the subscriber's main station
Show information；If valid ip address is bound, and the VLAN ID in the VLAN scopes are bound, and householder is used to described
Machine sends the prompt message of increase IP address range and VLAN scopes.
Embodiment three
It is corresponding with a kind of foregoing embodiment one of the method based on OpenStack configuration equipment upstream Interfaces, the application
Additionally provide a kind of embodiment three of the device based on OpenStack configuration equipment upstream Interfaces.
A kind of embodiment three of the device based on OpenStack configuration equipment upstream Interfaces of the application, which can be applied, is preventing fires
On wall equipment.Device embodiment three can be realized by software, can also be realized by way of hardware or software and hardware combining.
Exemplified by implemented in software, as the device on a logical meaning, being will be non-easy by the processor of firewall box where it
Corresponding computer program instructions read what operation in internal memory was formed in the property lost memory.For hardware view, such as Fig. 5 institutes
Show, be the one of a kind of device place firewall box that equipment upstream Interface is configured based on OpenStack of the embodiment of the present application three
Kind hardware structure diagram, in addition to the processor shown in Fig. 5, internal memory, network interface and nonvolatile memory, embodiment
Firewall box in three where device configures the actual functional capability of equipment upstream Interface generally according to this based on OpenStack, also
Other hardware can be included, this is repeated no more.
Fig. 6 is referred to, Fig. 6 is that one kind shown in the embodiment of the present application three is based on OpenStack configuration equipment upstream Interfaces
Device, applied to firewall box.Described device includes：Receiving unit 610, creating unit 620, selecting unit 630, transmission
Unit 640, dispensing unit 650.
The receiving unit 610, it is virtual in the establishment for receiving subscriber's main station transmission for receiving OpenStack service ends
The order of the establishment virtual firewall sent during the request of fire wall and VLAN ID；Wherein, the OpenStack service ends
The VlAN ID of transmission are the VLAN ID in the binding relationship that the OpenStack service ends pre-establish；Wherein, the binding
Relation is valid ip address, the binding relationship with the VLAN ID in the VLAN scopes that are pre-configured with；The valid ip address is institute
OpenStack service ends are stated to be calculated from the IP address range based on default effectively IP computational algorithms；
The creating unit 620, for creating virtual firewall based on the order；
The selecting unit 630, in the VLAN ID in the binding relationship that is sent from OpenStack service ends
Any VLAN ID being not used by are selected as target VLAN ID；
The transmitting element 640, for the target VLAN ID to be sent to the OpenStack service ends, so that institute
State Openstack service ends and the target ip address bound with the target VLAN ID is obtained from the binding relationship；
The dispensing unit 650, the target ip address sent for receiving the OpenStack service ends, and match somebody with somebody
Put the upstream Interface of the virtual firewall so that the target ip address and the target VLAN ID are respectively become on described
The IP address and VLAN ID of line interface.
In the present embodiment, the transmitting element 640, is further used for：
If the VLAN ID in the binding relationship are used, the VLAN is sent to the OpenStack service ends
The information that ID is used.
The function of unit and the implementation process of effect specifically refer to and step are corresponded in the above method in said apparatus
Implementation process, it will not be repeated here.
For device embodiment, because it corresponds essentially to embodiment of the method, so related part is real referring to method
Apply the part explanation of example.Device embodiment described above is only schematical, wherein described be used as separating component
The unit of explanation can be or may not be physically separate, can be as the part that unit is shown or can also
It is not physical location, you can with positioned at a place, or can also be distributed on multiple NEs.Can be according to reality
Need to select some or all of module therein to realize the purpose of application scheme.Those of ordinary skill in the art are not paying
In the case of going out creative work, you can to understand and implement.
The preferred embodiment of the application is the foregoing is only, not limiting the application, all essences in the application
God any modification, equivalent substitution and improvements done etc., should be included within the scope of the application protection with principle.
Claims (10)
- A kind of 1. method based on OpenStack collocating uplink interfaces, applied to OpenStack service ends, it is characterised in that institute State OpenStack service ends and be pre-configured with IP address range and VLAN scopes, including：When receiving the request of establishment virtual firewall of subscriber's main station transmission, send and created virtually to the firewall box The order of fire wall, and the VLAN ID in the binding relationship pre-established are sent to firewall box, so that the fire prevention Wall equipment creates virtual firewall and target VLAN ID is obtained from the VLAN ID；Wherein, the binding relationship is to have Imitate the binding relationship between the VLAN ID in IP address and VLAN scopes；The valid ip address is based on default effective IP Computational algorithm is calculated from the IP address range；The target VLAN ID are in the VLAN ID in the binding relationship Any VLAN ID being not used by；The target VLAN ID that the firewall box returns are received, and according to the binding relationship, are obtained and the target The target ip address of VLAN ID bindings；The target ip address is sent to the firewall box, so that the firewall box configures the virtual firewall Upstream Interface so that the target ip address and the target VLAN ID respectively become the upstream Interface IP address and VLAN ID。
- 2. according to the method for claim 1, it is characterised in that the binding relationship pre-established, including：The valid ip address is ranked up based on default IP address ordering mechanism, and based on default VLAN collators VLAN ID in the VLAN scopes are ranked up by system；The binding relationship established between valid ip address and the VLAN ID of same sequence number.
- 3. according to the method for claim 1, it is characterised in that methods described also includes：If the message that the VLAN ID in receiving the binding relationship that the firewall box returns are used, judges With the presence or absence of not bound valid ip address, and with the presence or absence of not bound VLAN ID in the VLAN scopes；If there is not bound valid ip address, and the VLAN ID in the VLAN scopes are bound, to the user Main frame sends the prompt message of increase VLAN scopes；If valid ip address is bound, and has not bound VLAN ID in the VLAN scopes, householder is used to described Machine sends the prompt message of increase IP address range；If valid ip address is bound, and the VLAN ID in the VLAN scopes are bound, and are sent out to the subscriber's main station Send the prompt message of increase IP address range and VLAN scopes.
- A kind of 4. method based on OpenStack configuration equipment upstream Interfaces, applied to firewall box, it is characterised in that bag Include：Receive the establishment that OpenStack service ends are sent when receiving the request of establishment virtual firewall of subscriber's main station transmission The order of virtual firewall and VLAN ID；Wherein, the VlAN ID that the OpenStack service ends are sent are described VLAN ID in the binding relationship that OpenStack service ends pre-establish；Wherein, the binding relationship is valid ip address, with The binding relationship of VLAN ID in the VLAN scopes being pre-configured with；The valid ip address is that the OpenStack services end group It is calculated in default effectively IP computational algorithms from the IP address range；Virtual firewall is created based on the order, and, in the binding relationship sent from OpenStack service ends Any VLAN ID being not used by are selected in VLAN ID as target VLAN ID, and the target VLAN ID are sent to institute OpenStack service ends are stated, so that the Openstack service ends obtain and the target VLAN from the binding relationship The target ip address of ID bindings；The target ip address that the OpenStack service ends are sent is received, and configures the up of the virtual firewall and connects Mouthful so that the target ip address and the target VLAN ID respectively become the IP address and VLAN ID of the upstream Interface.
- 5. according to the method for claim 4, it is characterised in that methods described also includes：If the VLAN ID in the binding relationship are used, the VLAN ID are sent to the OpenStack service ends The information used.
- A kind of 6. device based on OpenStack collocating uplink interfaces, applied to OpenStack service ends, it is characterised in that institute State OpenStack service ends and be pre-configured with IP address range and VLAN scopes, including：First transmitting element, for when receive subscriber's main station transmission establishment virtual firewall request when, to the fire prevention Wall equipment sends the order for creating virtual firewall, and the VLAN ID in the binding relationship pre-established are sent to fire prevention Wall equipment, so that the firewall box creates virtual firewall and target VLAN ID are obtained from the VLAN ID；Its In, the binding relationship is the binding relationship between the VLAN ID in valid ip address and VLAN scopes；The valid ip address To be calculated based on default effectively IP computational algorithms from the IP address range；The target VLAN ID tie up to be described Determine any VLAN ID being not used by the VLAN ID in relation；Acquiring unit, the target VLAN ID returned for receiving the firewall box, and according to the binding relationship, Obtain the target ip address with target VLAN ID bindings；Second transmitting element, for the target ip address to be sent to the firewall box, so that the firewall box Configure the upstream Interface of the virtual firewall so that the target ip address and the target VLAN ID respectively become described The IP address and VLAN ID of upstream Interface.
- 7. device according to claim 6, it is characterised in that described device also includes：Sequencing unit, for being ranked up the valid ip address based on default IP address ordering mechanism, and based on pre- If VLAN ordering mechanisms the VLAN ID in the VLAN scopes are ranked up；Unit is established, for establishing the binding relationship between valid ip address and the VLAN ID of same sequence number.
- 8. device according to claim 6, it is characterised in that described device also includes：Judging unit, if the VLAN ID in the binding relationship returned for receiving the firewall box are made Message, judge whether in the valid ip address not being bound, and the VLAN scopes with the presence or absence of not being bound VLAN ID；Prompting message transmitting element, for if there is not bound valid ip address, and the VLAN in the VLAN scopes ID is bound, and the prompt message of increase VLAN scopes is sent to the subscriber's main station；If valid ip address is bound, and Not bound VLAN ID in the VLAN scopes be present, the prompting that increase IP address range is sent to the subscriber's main station is believed Breath；If valid ip address is bound, and the VLAN ID in the VLAN scopes are bound, and are sent out to the subscriber's main station Send the prompt message of increase IP address range and VLAN scopes.
- A kind of 9. device based on OpenStack configuration equipment upstream Interfaces, applied to firewall box, it is characterised in that bag Include：Receiving unit, asking for the establishment virtual firewall of subscriber's main station transmission is being received for receiving OpenStack service ends The order of the establishment virtual firewall sent when asking and VLAN ID；Wherein, the VlAN that the OpenStack service ends are sent ID is the VLAN ID in the binding relationship that the OpenStack service ends pre-establish；Wherein, the binding relationship is effective IP address, the binding relationship with the VLAN ID in the VLAN scopes that are pre-configured with；The valid ip address is described OpenStack service ends are based on default effectively IP computational algorithms and are calculated from the IP address range；Creating unit, for creating virtual firewall based on the order；Selecting unit, for selected in the VLAN ID in the binding relationship that is sent from OpenStack service ends it is any not by The VLAN ID used are as target VLAN ID；Transmitting element, for the target VLAN ID to be sent to the OpenStack service ends, so that the Openstack Service end obtains the target ip address with target VLAN ID bindings from the binding relationship；Dispensing unit, the target ip address sent for receiving the OpenStack service ends, and configure described virtual anti- The upstream Interface of wall with flues so that the target ip address and the target VLAN ID are with respectively becoming the IP of the upstream Interface Location and VLAN ID.
- 10. device according to claim 9, it is characterised in that including：The transmitting element, is further used for：If the VLAN ID in the binding relationship are used, the VLAN ID are sent to the OpenStack service ends The information used.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710740862.1A CN107517129B (en) | 2017-08-25 | 2017-08-25 | Method and device for configuring uplink interface of equipment based on OpenStack |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710740862.1A CN107517129B (en) | 2017-08-25 | 2017-08-25 | Method and device for configuring uplink interface of equipment based on OpenStack |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107517129A true CN107517129A (en) | 2017-12-26 |
| CN107517129B CN107517129B (en) | 2020-04-03 |
Family
ID=60724031
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710740862.1A Active CN107517129B (en) | 2017-08-25 | 2017-08-25 | Method and device for configuring uplink interface of equipment based on OpenStack |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107517129B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111132170A (en) * | 2019-12-31 | 2020-05-08 | 奇安信科技集团股份有限公司 | Communication method and device of virtual firewall, virtual firewall and topological structure |
| CN112491789A (en) * | 2020-10-20 | 2021-03-12 | 苏州浪潮智能科技有限公司 | OpenStack framework-based virtual firewall construction method and storage medium |
| CN112737948A (en) * | 2020-12-30 | 2021-04-30 | 北京威努特技术有限公司 | Data transmission method and device between VLANs and industrial control firewall equipment |
| CN113132294A (en) * | 2019-12-30 | 2021-07-16 | ***通信集团四川有限公司 | Data packet filtering method, system and device |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103067380A (en) * | 2012-12-26 | 2013-04-24 | 北京启明星辰信息技术股份有限公司 | Deployment configuration method and system of virtual safety device |
| CN103152256A (en) * | 2013-02-22 | 2013-06-12 | 浪潮电子信息产业股份有限公司 | Virtual routing network design method based on cloud computing data center |
| US20150096011A1 (en) * | 2013-10-01 | 2015-04-02 | Racemi, Inc. | Migration of complex applications within a hybrid cloud environment |
| CN104714823A (en) * | 2015-03-06 | 2015-06-17 | 上海新炬网络信息技术有限公司 | New mainframe configuration method based on OpenStack |
| CN105577628A (en) * | 2014-11-11 | 2016-05-11 | 中兴通讯股份有限公司 | Method and device for realizing virtual firewall |
| CN105812340A (en) * | 2014-12-31 | 2016-07-27 | 杭州华三通信技术有限公司 | Access method and device for virtual network to extranet |
| US20160234250A1 (en) * | 2015-02-10 | 2016-08-11 | International Business Machines Corporation | System and method for software defined deployment of security appliances using policy templates |
| US20160285703A1 (en) * | 2015-03-23 | 2016-09-29 | Verizon Patent And Licensing Inc. | Cpe network configuration systems and methods |
| US20160380874A1 (en) * | 2014-03-27 | 2016-12-29 | Nicira, Inc. | Packet tracing in a software-defined networking environment |
| CN106850616A (en) * | 2017-01-24 | 2017-06-13 | 南京理工大学 | The method that distributed fire wall network consistent updates are solved using SDN technologies |
-
2017
- 2017-08-25 CN CN201710740862.1A patent/CN107517129B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103067380A (en) * | 2012-12-26 | 2013-04-24 | 北京启明星辰信息技术股份有限公司 | Deployment configuration method and system of virtual safety device |
| CN103152256A (en) * | 2013-02-22 | 2013-06-12 | 浪潮电子信息产业股份有限公司 | Virtual routing network design method based on cloud computing data center |
| US20150096011A1 (en) * | 2013-10-01 | 2015-04-02 | Racemi, Inc. | Migration of complex applications within a hybrid cloud environment |
| US20160380874A1 (en) * | 2014-03-27 | 2016-12-29 | Nicira, Inc. | Packet tracing in a software-defined networking environment |
| CN105577628A (en) * | 2014-11-11 | 2016-05-11 | 中兴通讯股份有限公司 | Method and device for realizing virtual firewall |
| CN105812340A (en) * | 2014-12-31 | 2016-07-27 | 杭州华三通信技术有限公司 | Access method and device for virtual network to extranet |
| US20160234250A1 (en) * | 2015-02-10 | 2016-08-11 | International Business Machines Corporation | System and method for software defined deployment of security appliances using policy templates |
| CN104714823A (en) * | 2015-03-06 | 2015-06-17 | 上海新炬网络信息技术有限公司 | New mainframe configuration method based on OpenStack |
| US20160285703A1 (en) * | 2015-03-23 | 2016-09-29 | Verizon Patent And Licensing Inc. | Cpe network configuration systems and methods |
| CN106850616A (en) * | 2017-01-24 | 2017-06-13 | 南京理工大学 | The method that distributed fire wall network consistent updates are solved using SDN technologies |
Non-Patent Citations (1)
| Title |
|---|
| 洪军等: ""虚拟防火墙在云计算环境中的应用研究"", 《计算机与网络》 * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113132294A (en) * | 2019-12-30 | 2021-07-16 | ***通信集团四川有限公司 | Data packet filtering method, system and device |
| CN113132294B (en) * | 2019-12-30 | 2022-05-13 | ***通信集团四川有限公司 | Data packet filtering method, system and device |
| CN111132170A (en) * | 2019-12-31 | 2020-05-08 | 奇安信科技集团股份有限公司 | Communication method and device of virtual firewall, virtual firewall and topological structure |
| CN112491789A (en) * | 2020-10-20 | 2021-03-12 | 苏州浪潮智能科技有限公司 | OpenStack framework-based virtual firewall construction method and storage medium |
| CN112491789B (en) * | 2020-10-20 | 2022-12-27 | 苏州浪潮智能科技有限公司 | OpenStack framework-based virtual firewall construction method and storage medium |
| CN112737948A (en) * | 2020-12-30 | 2021-04-30 | 北京威努特技术有限公司 | Data transmission method and device between VLANs and industrial control firewall equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107517129B (en) | 2020-04-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112470436B (en) | Systems, methods, and computer-readable media for providing multi-cloud connectivity | |
| CN110896371B (en) | Virtual network equipment and related method | |
| CN106533883B (en) | A kind of method for building up, the apparatus and system of network special line | |
| CN107517129A (en) | A kind of method and apparatus based on OpenStack configuration equipment upstream Interfaces | |
| CN105634956B (en) | A kind of message forwarding method, device and system | |
| CN105763385B (en) | Traffic scheduling method and device | |
| CN106936939A (en) | A kind of message processing method, relevant apparatus and NVO3 network systems | |
| CN108810993A (en) | Network is sliced selection method, equipment, UE, control plane functional entity and medium | |
| CN103858394B (en) | Load reduction system and load reduction method | |
| CN105072096A (en) | Providing access to configurable private computer networks | |
| CN107113219A (en) | VLAN marks in virtual environment | |
| CN107948086A (en) | A kind of data packet sending method, device and mixed cloud network system | |
| AU2022201580B2 (en) | Methods and apparatus for providing traffic forwarder via dynamic overlay network | |
| CN107819891A (en) | Data processing method, device, computer equipment and storage medium | |
| CN103825826B (en) | The implementation method and device of a kind of dynamic routing | |
| CN105939267B (en) | Outband management method and device | |
| CN108989071B (en) | Virtual service providing method, gateway device, and storage medium | |
| CN105939240A (en) | Load balancing method and device | |
| CN108234211A (en) | Network control method, system and storage medium | |
| CN107547665A (en) | A kind of method, equipment and the system of dhcp address distribution | |
| CN106571992A (en) | Virtual Private Line (VPL) establishing method and device | |
| CN109474713A (en) | Message forwarding method and device | |
| CN106130926B (en) | A kind of processing method and processing device of message | |
| CN109756419A (en) | Routing iinformation distribution method, device and RR | |
| CN110391919A (en) | Flux of multicast retransmission method, device, electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |