CN107395781A - Network communication method and device - Google Patents

Network communication method and device Download PDF

Info

Publication number
CN107395781A
CN107395781A CN201710515738.5A CN201710515738A CN107395781A CN 107395781 A CN107395781 A CN 107395781A CN 201710515738 A CN201710515738 A CN 201710515738A CN 107395781 A CN107395781 A CN 107395781A
Authority
CN
China
Prior art keywords
host
network
request
destination address
network request
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.)
Pending
Application number
CN201710515738.5A
Other languages
Chinese (zh)
Inventor
高建刚
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Xiaodu Information Technology Co Ltd
Original Assignee
Beijing Xiaodu Information Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Beijing Xiaodu Information Technology Co Ltd filed Critical Beijing Xiaodu Information Technology Co Ltd
Priority to CN201710515738.5A priority Critical patent/CN107395781A/en
Publication of CN107395781A publication Critical patent/CN107395781A/en
Pending legal-status Critical Current

Links

Classifications

    • 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/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The embodiment of the present invention provides a kind of network communication method and device, is related to field of computer technology.Wherein, methods described includes：Receive the network request up to host；Judge whether the network request comes from flannel overlay networks；Wherein, the host is configured in the flannel overlay networks；If not, being based on destination address mapping relations, it is its corresponding capsule address to change the destination address in the network request；The network request after conversion is sent to docker Microsoft Loopback Adapters；If it is, decapsulating the network request obtains source request；Send the source to ask to flannel Microsoft Loopback Adapters, the docker Microsoft Loopback Adapters are forwarded to via the flannel Microsoft Loopback Adapters.Technical scheme provided in an embodiment of the present invention is realized across the network service of the docker containers of host and outer net equipment and the network service of docker containers.

Description

Network communication method and device
Technical field
The present embodiments relate to Computer Applied Technology field, more particularly to a kind of network communication method and device.
Background technology
Docker is the application container an increased income engine, can by host create docker containers, with Containerization or virtualization are realized in host.
In the prior art, after creating docker containers in host, it is virtual docker can be created in host Network interface card is (referred to as：docker0).Docker containers are with docker0 by virtual network stack to realizing network interworking, virtual network stack To one end connect docker0, other end connection docker containers, therefore be connected to whole docker on same docker0 Container can be realized and is in communication with each other.
But be that the virtual addresses of docker container allocations is private network address in each host, can not realize across The network service of the docker containers of host and outer net equipment and the network service of docker containers.
The content of the invention
The embodiment of the present invention provides a kind of network communication method and device, to solve not realizing across place in the prior art The network service of the docker containers of main frame and outer net equipment and the technical problem of the network service of docker containers.
In a first aspect, a kind of network communication method is provided in the embodiment of the present invention, including：
Receive the network request up to host；
Judge whether the network request comes from flannel overlay networks；Wherein, the host is configured at described In flannel overlay networks；
If not, being based on destination address mapping relations, the destination address changed in the network request holds corresponding to it Device address；The network request after conversion is sent to docker Microsoft Loopback Adapters；
If it is, decapsulating the network request obtains source request；The source is sent to ask to flannel Microsoft Loopback Adapters, The docker Microsoft Loopback Adapters are forwarded to via the flannel Microsoft Loopback Adapters.
Alternatively, it is described to judge whether the network request includes from flannel overlay networks：
Whether the host port for judging to receive the network request is the first predetermined port.
Alternatively, described to be based on destination address mapping relations, the destination address changed in the network request is corresponding for it Capsule address includes：
According to the destination interface in the network request, destination address mapping relations corresponding to lookup；
Based on the destination address mapping relations, change destination address in the network request for its corresponding container Location and the destination interface are its corresponding container port.
Alternatively, the destination address mapping relations define the appearance of the physical network card address correspondence mappings of the host The container port of the host port correspondence mappings of device address and the host.
The destination address mapping relations predefine as follows：
In acquisition control platform send request to create, the request to create include the host host port and Corresponding container port；
Based on the host port, the physical network card address of the host, the container port and the container Capsule address corresponding to port, create the destination address mapping relations.
Second aspect, the embodiments of the invention provide a kind of network communication device, including：
Receiving module, the network request of host is reached for receiving；
Judge module, for judging whether the network request comes from flannel overlay networks；Wherein, the host Machine is configured in the flannel overlay networks；
Address mapping module, if the judged result for the judge module is no, based on destination address mapping relations, It is its corresponding capsule address to change the destination address in the network request；
First processing module, for sending the network request after changing to docker Microsoft Loopback Adapters；
Decapsulation module, if the judged result for the judge module is yes, decapsulates the network request and obtain Ask in source；
Second processing module, asked for sending the source to flannel Microsoft Loopback Adapters, it is virtual via the flannel Network interface card is forwarded to the docker Microsoft Loopback Adapters.
Alternatively, whether the host port that the judge module is specifically used for judging to receive the network request is first Predetermined port.
Alternatively, the address mapping module includes：
Relation searching unit, for the destination interface in the network request, destination address corresponding to lookup maps Relation；
Address mapping unit, for based on the destination address mapping relations, changing the destination in the network request Location is its corresponding capsule address and the destination interface is its corresponding container port.
Alternatively, the destination address mapping relations define the appearance of the physical network card address correspondence mappings of the host The container port of the host port correspondence mappings of device address and the host.
Alternatively, in addition to：
Acquisition module, the request to create sent for controlling platform in acquisition, the request to create include the host Host port and corresponding container port；
Relation establishes module, for based on the host port, the physical network card address of the host, the container Capsule address corresponding to port and the container port, create the destination address mapping relations.
In the embodiment of the present invention, the network request for reaching host, if it comes from flannel overlay networks, The request of acquisition source is then decapsulated to it, the source is sent and asks to flannel Microsoft Loopback Adapters, via the flannel virtual nets Card is forwarded to the docker Microsoft Loopback Adapters, and docker Microsoft Loopback Adapters can be forwarded to based on the destination address in the request of source Corresponding docker containers,, will based on destination address mapping relations if network request comes from non-flannel overlay networks Destination address in network request is converted to capsule address, so as to which network request is routed directly into docker virtual nets Card, docker Microsoft Loopback Adapters can be based on the capsule address, be forwarded to corresponding docker containers.By the embodiment of the present invention, Realize the network service and outer net equipment and the network service of docker containers between the docker containers of host.
The aspects of the invention or other aspects can more straightforwards in the following description.
Brief description of the drawings
In order to illustrate more clearly about the embodiment of the present invention or technical scheme of the prior art, below will be to embodiment or existing There is the required accompanying drawing used in technology description to be briefly described, it should be apparent that, drawings in the following description are this hairs Some bright embodiments, for those of ordinary skill in the art, on the premise of not paying creative work, can be with root Other accompanying drawings are obtained according to these accompanying drawings.
Fig. 1 shows a kind of network communication method one embodiment schematic flow sheet provided by the invention；
Fig. 2 shows a kind of schematic flow sheet of another embodiment of network communication method provided by the invention；
Fig. 3 shows a kind of network communication device one embodiment structural representation provided by the invention；
Fig. 4 shows a kind of structural representation of another embodiment of network communication device provided by the invention；
Fig. 5 shows a kind of structural representation of computer equipment one embodiment provided by the invention.
Embodiment
In order that those skilled in the art more fully understand the present invention program, below in conjunction with the embodiment of the present invention Accompanying drawing, the technical scheme in the embodiment of the present invention is clearly and completely described.
In some flows of description in description and claims of this specification and above-mentioned accompanying drawing, contain according to Particular order occur multiple operations, but it should be clearly understood that these operation can not occur herein according to it is suitable Sequence is performed or performed parallel, the sequence number such as 101,102 etc. of operation, is only used for distinguishing each different operation, sequence number Any execution sequence is not represented for itself.In addition, these flows can include more or less operations, and these operations can To perform or perform parallel in order.It should be noted that the description such as " first " herein, " second ", is to be used to distinguish not Message together, equipment, module etc., do not represent sequencing, it is different types also not limit " first " and " second ".
The technical scheme of the embodiment of the present invention realizes to be set across the network service of the docker containers of host and outer net The standby network service with docker containers.Wherein, network service can refer to by network request, to realize such as data access Deng traffic operation.
In the prior art, when docker services start, you can to create (the letter of a docker Microsoft Loopback Adapter in host Claim：Docker0), the docker containers that are created in host and docker0 are by virtual network stack to (Veth equipment to) bridge Connect, virtual network stack connects docker0, other end connection docker containers to one end.So, all docker hold in host Device is connected in a double layer network by docker0, afterwards, can be selected different from host from the private ip network segment The subnet network segment distributes to docker0, and docker0 and the docker containers that are connected in docker0 are i.e. from the subnet network segment One untapped IP address of selection uses as capsule address, so as to be connected between the docker containers on docker0 i.e. It can be in communication with each other.Its network service process is：If a docker container in same host is to another docker Container initiates network request, and the network request can arrive first at docker0, and it is another that network request is forwarded into this again by docker0 One docker container.
Because the virtual address of docker container allocations is private network address, its IP address with host is not same The network segment, therefore can not just realize across the network service of the docker containers of host and outer net equipment and the net of docker containers Network communicates.
In order to solve can not to realize in the prior art across host the communication of docker capacitor networks and outer net equipment with The technical problem of the network service of docker containers, inventor researchs and proposes technical solution of the present invention by a series of, in this hair In bright embodiment, flannel (an overlay network instrument) is installed in host, so that its docker container created is matched somebody with somebody It is placed in flannel overlay networks (Overlay Network), and configuration purpose address mapping relation, to change host Routing rule.Therefore for the network request of arrival host, if it comes from flannel overlay networks, it is unsealed The request of acquisition source is filled, the source is sent and asks to flannel Microsoft Loopback Adapters, institute is forwarded to via the flannel Microsoft Loopback Adapters Docker Microsoft Loopback Adapters are stated, docker Microsoft Loopback Adapters can be forwarded to corresponding docker based on the destination address in the request of source Container, if network request comes from non-flannel overlay networks, based on destination address mapping relations, by network request Destination address be converted to capsule address, so as to which network request is routed directly into docker Microsoft Loopback Adapters, docker is empty The capsule address can be based on by intending network interface card, be forwarded to corresponding docker containers.By the embodiment of the present invention, realize across host Network service and outer net equipment and the network service of docker containers between the docker containers of machine.
Below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is carried out clear, complete Site preparation describes, it is clear that described embodiment is only part of the embodiment of the present invention, rather than whole embodiments.It is based on Embodiment in the present invention, the every other implementation that those skilled in the art are obtained under the premise of creative work is not made Example, belongs to the scope of protection of the invention.
Fig. 1 is a kind of flow chart of network communication method one embodiment provided in an embodiment of the present invention, and this method can be with Including following steps：
101：Receive the network request up to host.
The network request is sent by transmitting terminal, and the destination address in network request is specific to the Physical Network up to host Card.The host receives network request as receiving terminal.
Being created in host has docker containers and docker Microsoft Loopback Adapters (docker0).The network request is used for Request carries out network service etc..
102：Judge whether the network request comes from flannel overlay networks, perform step 103 if not, if It is to perform step 105.
In actual applications, it is understood that there may be multiple hosts, creating in each host has docker containers, different There is also communication requirement for docker containers between host.
Therefore,, can by flannel in order to realize the communication across the docker containers of host in the embodiment of the present invention So that in same flannel overlay networks, the configuration of different hosts machine is formed into group system.
By installing flannel in host, flannel Microsoft Loopback Adapters can be created in host (referred to as： ) and flannel finger daemons flannel0.
Installation Etcd can be corresponded in each host, Etcd is a distributed key/value (key/value) to increase income Storage system, the subnet network segment of different hosts machine can be planned by Etcd, what the different hosts machine allowed in cluster created Docker containers all have the unique capsule address of complete or collected works group, and connect the network of host so that belong to different hosts machine Docker containers can obtain and belong to an Intranet and unduplicated capsule address together.
Flannel finger daemons can be specifically to change the start-up parameter that docker is serviced in host by Etcd, come Limit the subnet network segment that docker containers obtain in the host, and the assignment record in each host for passing through Etcd maintenances Ensure the uniqueness of the subnet network segment.
By setting flannel overlay networks, different hosts machine can be configured in same flannel overlay networks In, it is possible to achieve communicated across the docker containers of host.
103：Based on destination address mapping relations, change destination address in the network request for its corresponding container Location.
104：The network request after conversion is sent to docker Microsoft Loopback Adapters.
If network request comes from non-flannel overlay networks, the transmitting terminal for sending network request is outer net equipment. Outer net equipment is not at the same network segment with docker containers, can not directly access docker containers, therefore can pass through destination Location mapping relations carry out address of cache, and destination address is converted into capsule address.
Alternatively, the destination address mapping relations can be set by iptables, and iptables is a kernel component, Packet filter firewall is formed, the functions such as filtering packets, package redirection and network address translation can be completed by iptables.
Destination address mapping relations can think an iptables rule, which define different destination address correspondence mappings Capsule address and different destination interface correspondence mappings container port.
The message of network request includes the information such as destination address, destination interface, source address and source port, if network Request comes from non-flannel overlay networks, and its destination address is specially the physical network card address of host, and network request will arrive Up to not docker containers.
Therefore, the destination address in network request can be converted into its corresponding container based on destination address mapping relations Address, destination interface are converted to its corresponding container port.
After network request conversion, destination address is converted to capsule address, you can be directly forwarded to network request Network request can be forwarded to corresponding docker by docker Microsoft Loopback Adapters, docker Microsoft Loopback Adapters according to the capsule address Container.
Wherein, container port is mainly used in the foundation of destination address mapping relations.Docker Microsoft Loopback Adapters are with being based on container Location can forward network request.
105：Decapsulate the network request and obtain source request.
106：Send the source to ask to flannel Microsoft Loopback Adapters, be forwarded to via the flannel Microsoft Loopback Adapters described Docker Microsoft Loopback Adapters.
If network request comes from flannel overlay networks, the transmitting terminal for sending network request covers for same flannel Other hosts in cover net network, initiated by the docker containers in transmitting terminal.
The docker containers across host in same flannel overlay networks can communicate, and transmitting terminal please by source Package is asked to forward, receiving terminal decapsulates the request of acquisition source and realized again.
So if network request comes from flannel overlay networks, the network request can directly reach host Flannel finger daemons, source request is specifically obtained by flannel finger daemons decapsulation network request, and source is asked to send To flannel Microsoft Loopback Adapters, docker Microsoft Loopback Adapters are forwarded to by flannel Microsoft Loopback Adapters, docker Microsoft Loopback Adapters can Destination address in being asked according to source, source request is forwarded to corresponding docker containers.
Wherein, source request is specifically to be initiated by the docker containers in transmitting terminal, and the destination address in the request of source is institute The capsule address of the docker containers in host is stated, it arrives first at the docker Microsoft Loopback Adapters in host, via Docker Microsoft Loopback Adapters reach flannel Microsoft Loopback Adapters, the destination address pair that flannel finger daemons can ask according to source The physical network card address for the host answered and port, Reseal after the source request obtains network request and retransmit.
By the embodiment of the present invention, realize across the network service of the docker containers of host and outer net equipment with The network service of docker containers, and by docker virtual networks, same host can be realized according to prior art Network service between docker containers.
In the embodiment of the present invention, destination address mapping relations can be with dynamic creation, and can create multiple destination addresses and reflect Penetrate relation.
Therefore alternatively, described to be based on destination address mapping relations, it is it to change the destination address in the network request Corresponding capsule address can include：
According to the destination interface in the network request, destination address mapping relations corresponding to lookup；
Based on the destination address mapping relations, change destination address in the network request for its corresponding container Location and the destination interface are its corresponding container port.
Wherein, the destination address mapping relations define the container of the physical network card address correspondence mappings of the host The container port of the host port correspondence mappings of address and the host.Host in different destination address mapping relations Generator terminal mouth is different, and different destination address mapping relations can be made a distinction by host port.In addition, different destination addresses reflect Capsule address corresponding to the physical network card address penetrated in relation may be different, and capsule address corresponding to host port may not Together.
Therefore, by different destination address mapping relations, it may be determined that the physical network card address correspondence mappings of host Capsule address and different hosts generator terminal mouth correspondence mappings container port.
If network request comes from non-flannel overlay networks, the destination address in the network request is specially place Physical network card address in main frame, destination interface are any one host port in host.
Wherein, in certain embodiments, the destination address mapping relations can predefine as follows：
In acquisition control platform send request to create, the request to create include the host host port and Corresponding container port；
Based on the host port, the physical network card address of the host, the container port and the container Capsule address corresponding to port, create destination address mapping relations.
Wherein, the request to create can create operation in user by middle control platform response and generate, and middle control platform can carry For a display interface, operated for user and host port and corresponding container port are provided.
In order to ensure the normal operation of host, the host port that the request to create includes be specially host not The port used.
Therefore, middle control platform can select prompt message with display port, and port selection prompt message is used to prompt user The unused port of host, so that user therefrom selects any one host port, to carry out port mapping.
Wherein, the destination address mapping relations of host can be established especially by an iptables order, should Iptables orders can be with as follows：
iptables-t nat-A DOCKER！-i dokcer0-p tcp--dport$nodePort-j DNAT--to- destination$containerIp:$containerPort'；
So that network request is tcp requests as an example, the order refer to if network request to be not from docker virtual Network interface card, but tcp is asked, that is, is carried out the conversion of destination address, destination address is converted into capsule address, destination interface is converted to Container port.
In addition, in host after window destination address mapping relations, the destination address in host can also be reflected The relation of penetrating is updated.
Therefore, in certain embodiments, it is described based on the host port, the host physical network card address, Capsule address corresponding to the container port and the container port, after creating destination address mapping relations, methods described It can also include：
Receive the renewal request that the middle control platform is sent；
Update destination address mapping relations corresponding to the renewal request.
Renewal request can be removal request or modification request etc..
Wherein, the host port of request renewal can be carried in renewal request, in order to which host searches the request more Destination address mapping relations corresponding to new host port, the request for being deleted or being carried in being asked according to renewal update Container port it is updated.
Wherein, judge whether the network request comes from flannel overlay networks and there can be a variety of possible realization sides Formula：
As a kind of possible implementation, it can be determined that whether the host port for receiving the network request is first Predetermined port.
That is, in the embodiment of the present invention, can preset can receive the network request from flannel overlay networks Host port, the docker containers across host under same flannel overlay networks carry out network service, by again Encapsulate the first predetermined port that the destination interface in the network request obtained is the host of receiving terminal.
Therefore, can be by judging to receive whether the host port in network request be the first predetermined port to determine net Whether network request comes from flannel overlay networks.
It is of course also possible to according to the host port for receiving the network request whether be the second predetermined port judgement knot Fruit determines that second predetermined port is according to the host port of defined in destination address mapping relations, so if network please The destination interface asked is second predetermined port, and it is what outer net equipment was sent.
Fig. 2 is a kind of flow chart of another embodiment of network communication method provided in an embodiment of the present invention, and this method can With including following steps：
201：Receive the network request up to host.
202：Whether the host port for judging to receive the network request is the first predetermined port, if not, performing step Rapid 203, if it is, performing step 207.
203：According to the destination interface in the network request, destination address mapping relations corresponding to lookup；
204：Based on the destination address mapping relations, the destination address changed in the network request holds corresponding to it Device address and the destination interface are its corresponding container port.
205：Routing rule is searched, determines whether the capsule address matches with the docker Microsoft Loopback Adapters, if it is, Step 206 is performed, if otherwise terminating flow.
The routing rule includes the subnet network segment and the matching of flannel Microsoft Loopback Adapters of docker Microsoft Loopback Adapters matching The subnet network segment.
Host can safeguard routing table by etcd, and the routing table defines different routing rules
It is as shown in table 1 below in order to facilitate understanding, the possibility way of realization of routing table has been illustrated：
Table 1：
As seen from the above table, the routing table includes the subnet network segment (Destination), gateway (Gateway), mask And the corresponding relation between network interface card (Iface) (Genmask).Each corresponding relation is a routing rule.
The routing rule that routing table defines include docker Microsoft Loopback Adapters (docker0) matching the subnet network segment and The subnet network segment of flannel Microsoft Loopback Adapters (flannel0) matching.
Therefore, by searching routing rule, because the destination address in network request has been converted into capsule address, it is, for example, 172.17.18.2, it is known that the capsule address matches with 172.17.18.0, and therefore, it is virtual that network request is routed directly to docker Network interface card.
Wherein, if the capsule address mismatches with the docker Microsoft Loopback Adapters, the network request can be abandoned.
206：The network request after conversion is sent to the docker Microsoft Loopback Adapters.
207：Decapsulate the network request and obtain source request.
208：The source is sent to ask to flannel Microsoft Loopback Adapters.
209：Search routing rule, determine source request destination address whether with the docker Microsoft Loopback Adapters Match somebody with somebody, if it is, step 210 is performed, if it is not, then terminating flow.
210：The network request is sent to the docker Microsoft Loopback Adapters.
Wherein, the routing rule includes the subnet network segment and flannel virtual nets of docker Microsoft Loopback Adapters matching Block the subnet network segment of matching.
Still by taking upper table 1 as an example, it is assumed that be to ask to send from capsule address 172.17.46.2 docker containers in the request of source To the docker containers that capsule address is 172.17.18.2.Upper table 1 is the host of receiving terminal
After the source request that deblocking obtains reaches flannel Microsoft Loopback Adapters, it is understood according to capsule address 172.17.18.2 172.17.18.0 is matched, therefore, network request is routed directly to docker Microsoft Loopback Adapters from flannel virtual networks.
Wherein, if the destination address of source request mismatches with the docker Microsoft Loopback Adapters, can abandon the source please Ask.
By the embodiment of the present invention, network service and the outer net equipment of docker containers across host are effectively realized With the network service of docker containers, network design is simple, versatile, and risk is low.Outer net equipment can be arbitrarily in public network Browser, mobile phone arbitrary equipment, complex configurations are carried out without outer net equipment, you can to realize the access to docker containers.
From described above, based on destination address mapping relations, it is possible to achieve outer net equipment and the net of docker containers Network communicates.
In addition, in order to realize the network service of docker containers and outer net equipment, can be by iptables with establishing source Location mapping relations.
Therefore, in certain embodiments, this method can also include：
It is determined that sent from docker containers to the network request of docker Microsoft Loopback Adapters；Now host is transmitting terminal；
According to the destination address in the network request, determine whether receiving terminal is outer net equipment；
If it is, the network request is forwarded to physical network card；
Based on source address mapping relations, the source address in the network request is converted to the Physical Network of the physical network card Card address；
Send the network request after conversion.
If not, the destination address in the network request, judge whether receiving terminal is docker across host Container；
If it is, the network request is forwarded to flannel Microsoft Loopback Adapters；
Search the physical network card address and port of the receiving terminal of the corresponding destination address；
Based on the physical network card address of the receiving terminal and port, Reseal the network request and send to reception End；
If not, show that receiving terminal is the docker containers in same host, you can directly to forward the network Ask to corresponding docker containers；
Wherein, the subnet network segment for the different hosts machine that the destination address in network request and etcd are safeguarded, you can To judge whether receiving terminal is outer net equipment or for across the docker containers of host.
If receiving terminal is the docker containers across host, can be by searching routing rule, it is determined that with source address The flannel Microsoft Loopback Adapters of location matching, such as still by taking table 1 as an example, it is assumed that source address 172.17.18.2, remaining routing rule In 172.17.0.0 matchings, therefore network request can be forwarded to flannel Microsoft Loopback Adapters via docker Microsoft Loopback Adapters.
Fig. 3 is a kind of structural representation of network communication device one embodiment provided in an embodiment of the present invention, the device It can include：
Receiving module 301, the network request of host is reached for receiving；
Judge module 302, for judging whether the network request comes from flannel overlay networks；Wherein, the place Main frame is configured in the flannel overlay networks.
Alternatively, whether the host port that the judge module can be specifically used for judging to receive the network request is the One predetermined port.
Address mapping module 303, if the judged result for the judge module is no, is mapped and closed based on destination address System, it is its corresponding capsule address to change the destination address in the network request.
Alternatively, the destination address mapping relations can be set by iptables.Destination address mapping relations can For an iptables rule, capsule address and the different destination interfaces for which defining different destination address correspondence mappings are corresponding The container port of mapping.
The message of network request includes the information such as destination address, destination interface, source address and source port, if network Request comes from non-flannel overlay networks, and its destination address is specially the physical network card address of host, and network request will arrive Up to not docker containers.
Therefore, the destination address in network request can be converted into its corresponding container based on destination address mapping relations Address, destination interface are converted to its corresponding container port.
After network request conversion, destination address is converted to capsule address, you can be directly forwarded to network request Network request can be forwarded to corresponding docker by docker Microsoft Loopback Adapters, docker Microsoft Loopback Adapters according to the capsule address Container.
First processing module 304, for sending the network request after changing to docker Microsoft Loopback Adapters；
Decapsulation module 305, if the judged result for the judge module is yes, decapsulates the network request and obtain The source of obtaining request.
Wherein, source request is specifically to be initiated by the docker containers in transmitting terminal, and the destination address in the request of source is institute The capsule address of the docker containers in host is stated, it arrives first at the docker Microsoft Loopback Adapters in host, via Docker Microsoft Loopback Adapters reach flannel Microsoft Loopback Adapters, the destination address pair that flannel finger daemons can ask according to source The physical network card address for the host answered and port, Reseal after the source request obtains network request and retransmit.
Therefore, source request can be obtained by decapsulating the network request.
Second processing module 306, asked for sending the source to flannel Microsoft Loopback Adapters, it is empty via the flannel Intend network interface card and be forwarded to the docker Microsoft Loopback Adapters.
By the embodiment of the present invention, realize across the network service of the docker containers of host and outer net equipment with The network service of docker containers, and by docker virtual networks, same host can be realized according to prior art Network service between docker containers.
In the embodiment of the present invention, destination address mapping relations can be with dynamic creation, and can create multiple destination addresses and reflect Penetrate relation.Therefore, alternatively, in certain embodiments, the address mapping module can include：
Relation searching unit, for the destination interface in the network request, destination address corresponding to lookup maps Relation；
Address mapping unit, for based on the destination address mapping relations, changing the destination in the network request Location is its corresponding capsule address and the destination interface is its corresponding container port.
Wherein, destination address mapping relations define the capsule address of the physical network card address correspondence mappings of the host And the container port of the host port correspondence mappings of the host.
Therefore, by different destination address mapping relations, it may be determined that the physical network card address correspondence mappings of host Capsule address and different hosts generator terminal mouth correspondence mappings container port.
If network request comes from non-flannel overlay networks, the destination address in the network request is specially place Physical network card address in main frame, destination interface are any one host port in host.
Wherein, as shown in Figure 4 as another embodiment, the device can also include：
Acquisition module 401, the request to create sent for controlling platform in acquisition, the request to create include the host The host port of machine and corresponding container port；
Relation establishes module 402, for the physical network card address, described based on the host port, the host Capsule address corresponding to container port and the container port, create destination address mapping relations.
Wherein, the request to create can create operation in user by middle control platform response and generate, and middle control platform can carry For a display interface, operated for user and host port and corresponding container port are provided.
In addition, in certain embodiments, can also be to host in host after window destination address mapping relations In destination address mapping relations be updated.Therefore the device can also include：
Update module, the renewal request sent for receiving the middle control platform；Update mesh corresponding to the renewal request Address mapping relation.
Wherein, the host port of request renewal can be carried in renewal request, in order to which host searches the request more Destination address mapping relations corresponding to new host port, the request for being deleted or being carried in being asked according to renewal update Container port it is updated.
In certain embodiments, the first processing module is specifically used for searching routing rule, determines the capsule address Whether matched with the docker Microsoft Loopback Adapters；If the capsule address matches with the docker virtual networks, send and turn The network request after alternatively is to the docker Microsoft Loopback Adapters.
Wherein, the routing rule includes the subnet network segment and flannel virtual nets of docker Microsoft Loopback Adapters matching Block the subnet network segment of matching；
In certain embodiments, the Second processing module can be asked to flannel void specifically for sending the source Intend network interface card；The routing rule is searched, determines whether the destination address of the source request matches with the docker Microsoft Loopback Adapters； If the destination address of the source request matches with the docker Microsoft Loopback Adapters, the network request is sent to the docker Microsoft Loopback Adapter.
By the embodiment of the present invention, network service and the outer net equipment of docker containers across host are effectively realized With the network service of docker containers, network design is simple, versatile, and risk is low.Outer net equipment can be arbitrarily in public network Browser, mobile phone arbitrary equipment, complex configurations are carried out without outer net equipment, you can to realize the access to docker containers.
In a possible design, Fig. 3 or the network communication device shown in Fig. 4 can be realized and set for a computer Standby, this is as shown in Figure 5, and the computer equipment can include one or more processors 501 and one or more memories 502；Being created in the computer equipment has docker containers, and installs flannel and etcd, can additionally integrate Iptables, to realize the foundation of address mapping relation.
One or more computer instruction is stored in one or more of memories 502, wherein, described one or more Computer instruction is called for one or more of processors and performed.
One or more of processors 501 are specifically used for：
Receive network request；
Judge whether the network request comes from flannel overlay networks；Wherein, the computer collocations are in institute State in flannel overlay networks；
If not, being based on destination address mapping relations, the destination address changed in the network request holds corresponding to it Device address；The network request after conversion is sent to docker Microsoft Loopback Adapters；
If it is, decapsulating the network request obtains source request；The source is sent to ask to flannel Microsoft Loopback Adapters, The docker Microsoft Loopback Adapters are forwarded to via the flannel Microsoft Loopback Adapters.
Wherein, one or more of processors are additionally operable to perform the information acquisition method described in any of the above-described embodiment.
One or more memories can by any kind of volatibility or non-volatile memory device or they Combination is realized, such as static RAM (SRAM), Electrically Erasable Read Only Memory (EEPROM), it is erasable can Program read-only memory (EPROM), programmable read only memory (PROM), read-only storage (ROM), magnetic memory, flash memory Reservoir, disk or CD.
The embodiment of the present invention additionally provides a kind of computer-readable recording medium, the computer-readable recording medium storage There is computer program；
The computer program makes computer equipment realize the network communication method described in any of the above-described embodiment when performing.
It is apparent to those skilled in the art that for convenience and simplicity of description, the system of foregoing description, The specific work process of device and unit, the corresponding process in preceding method embodiment is may be referred to, will not be repeated here.
Device embodiment described above is only schematical, wherein the unit illustrated as separating component can To be or may not be physically separate, it can be as the part that unit is shown or may not be physics list Member, you can with positioned at a place, or can also be distributed on multiple NEs.It can be selected according to the actual needs In some or all of module realize the purpose of this embodiment scheme.Those of ordinary skill in the art are not paying creativeness Work in the case of, you can to understand and implement.
Through the above description of the embodiments, those skilled in the art can be understood that each embodiment can Realized by the mode of software plus required general hardware platform, naturally it is also possible to pass through hardware.Based on such understanding, on The part that technical scheme substantially in other words contributes to prior art is stated to embody in the form of software product, should Computer software product can store in a computer-readable storage medium, such as ROM/RAM, magnetic disc, CD, including some fingers Make to cause a computer equipment (can be personal computer, server, or network equipment etc.) to perform each implementation Method described in some parts of example or embodiment.
Finally it should be noted that：The above embodiments are merely illustrative of the technical solutions of the present invention, rather than its limitations；Although The present invention is described in detail with reference to the foregoing embodiments, it will be understood by those within the art that：It still may be used To be modified to the technical scheme described in foregoing embodiments, or equivalent substitution is carried out to which part technical characteristic； And these modification or replace, do not make appropriate technical solution essence depart from various embodiments of the present invention technical scheme spirit and Scope.
The invention discloses A1, a kind of network communication method, including：
Receive the network request up to host；
Judge whether the network request comes from flannel overlay networks；Wherein, the host is configured at described In flannel overlay networks；
If not, being based on destination address mapping relations, the destination address changed in the network request holds corresponding to it Device address；The network request after conversion is sent to docker Microsoft Loopback Adapters；
If it is, decapsulating the network request obtains source request；The source is sent to ask to flannel Microsoft Loopback Adapters, The docker Microsoft Loopback Adapters are forwarded to via the flannel Microsoft Loopback Adapters.
A2, the method according to A1, it is described to judge whether the network request includes from flannel overlay networks：
Whether the host port for judging to receive the network request is the first predetermined port.
A3, the method according to A1, it is described to be based on destination address mapping relations, change the purpose in the network request Address includes for its corresponding capsule address：
According to the destination interface in the network request, destination address mapping relations corresponding to lookup；
Based on the destination address mapping relations, change destination address in the network request for its corresponding container Location and the destination interface are its corresponding container port.
A4, the method according to A3, the destination address mapping relations are with defining the physical network card of the host The container port of the capsule address of location correspondence mappings and the host port correspondence mappings of the host.
A5, the method according to A4, the destination address mapping relations predefine as follows：
In acquisition control platform send request to create, the request to create include the host host port and Corresponding container port；
Based on the host port, the physical network card address of the host, the container port and the container Capsule address corresponding to port, create the destination address mapping relations.
A6, the method according to A5, after the destination address mapping relations foundation step, in addition to：
Receive the renewal request that the middle control platform is sent；
Update destination address mapping relations corresponding to the renewal request.
A7, the method according to A1, the network request sent after changing to docker Microsoft Loopback Adapter bags Include：
Routing rule is searched, determines whether the capsule address matches with the docker Microsoft Loopback Adapters；The route rule Then include the subnet network segment of docker Microsoft Loopback Adapters matching and the subnet network segment of flannel Microsoft Loopback Adapters matching；
If the capsule address matches with the docker virtual networks, the network request after transmission conversion is extremely The docker Microsoft Loopback Adapters.
A8, the method according to A1, the transmission source are asked to flannel Microsoft Loopback Adapters, via described Flannel Microsoft Loopback Adapters, which are sent to docker Microsoft Loopback Adapters, to be included：
The source is sent to ask to flannel Microsoft Loopback Adapters；
Routing rule is searched, determines whether the destination address of the source request matches with the docker Microsoft Loopback Adapters；Institute Stating routing rule includes the subnet network segment of docker Microsoft Loopback Adapters matching and the subnet net of flannel Microsoft Loopback Adapters matching Section；
If the destination address of the source request matches with the docker Microsoft Loopback Adapters, the network request is sent to institute State docker Microsoft Loopback Adapters.
B9, a kind of network communication device, including：
Receiving module, the network request of host is reached for receiving；
Judge module, for judging whether the network request comes from flannel overlay networks；Wherein, the host Machine is configured in the flannel overlay networks；
Address mapping module, if the judged result for the judge module is no, based on destination address mapping relations, It is its corresponding capsule address to change the destination address in the network request；
First processing module, for sending the network request after changing to docker Microsoft Loopback Adapters；
Decapsulation module, if the judged result for the judge module is yes, decapsulates the network request and obtain Ask in source；
Second processing module, asked for sending the source to flannel Microsoft Loopback Adapters, it is virtual via the flannel Network interface card is forwarded to the docker Microsoft Loopback Adapters.
B10, the device according to B9, the judge module are specifically used for judging the host for receiving the network request Whether port is the first predetermined port.
B11, the device according to B9, the address mapping module include：
Relation searching unit, for the destination interface in the network request, destination address corresponding to lookup maps Relation；
Address mapping unit, for based on the destination address mapping relations, changing the destination in the network request Location is its corresponding capsule address and the destination interface is its corresponding container port.
B12, the device according to B11, the destination address mapping relations define the physical network card of the host The container port of the capsule address of address correspondence mappings and the host port correspondence mappings of the host.
B13, the device according to B12, in addition to：
Acquisition module, the request to create sent for controlling platform in acquisition, the request to create include the host Host port and corresponding container port；
Relation establishes module, for based on the host port, the physical network card address of the host, the container Capsule address corresponding to port and the container port, create the destination address mapping relations.
B14, the device according to B13, in addition to：
Update module, the renewal request sent for receiving the middle control platform；Update mesh corresponding to the renewal request Address mapping relation.
B15, the device according to B9, the first processing module are specifically used for searching routing rule, determine the appearance Whether device address matches with the docker Microsoft Loopback Adapters；The routing rule includes the subnet of docker Microsoft Loopback Adapters matching The network segment and the subnet network segment of flannel Microsoft Loopback Adapters matching；If the capsule address and the docker virtual networks Match somebody with somebody, the network request after transmission conversion to the docker Microsoft Loopback Adapters.
B16, the device according to B9, the Second processing module, which is specifically used for the transmission source, asks to flannel Microsoft Loopback Adapter；Routing rule is searched, determines whether the destination address of the source request matches with the docker Microsoft Loopback Adapters；Institute Stating routing rule includes the subnet network segment of docker Microsoft Loopback Adapters matching and the subnet net of flannel Microsoft Loopback Adapters matching Section；If the destination address of source request matches with the docker Microsoft Loopback Adapters, the network request is sent to described Docker Microsoft Loopback Adapters.
C17, a kind of computer equipment, including one or more memories and one or more processors；
One or more computer instruction is stored in one or more of memories, wherein, one or more meter The instruction of calculation machine is called for one or more of processors to be performed；
One or more of processors are used for：
Receive the network request up to host；
Judge whether the network request comes from flannel overlay networks；Wherein, the host is configured at described In flannel overlay networks；
If not, being based on destination address mapping relations, the destination address changed in the network request holds corresponding to it Device address；The network request after conversion is sent to docker Microsoft Loopback Adapters；
If it is, decapsulating the network request obtains source request；The source is sent to ask to flannel Microsoft Loopback Adapters, The docker Microsoft Loopback Adapters are forwarded to via the flannel Microsoft Loopback Adapters.
D18, a kind of computer-readable recording medium, the computer-readable recording medium storage have computer program；
The computer program makes computer realize the information processing side as described in any one of claim 1~8 when performing Method.

Claims (10)

  1. A kind of 1. network communication method, it is characterised in that including：
    Receive the network request up to host；
    Judge whether the network request comes from flannel overlay networks；Wherein, the host is configured at described In flannel overlay networks；
    If not, be based on destination address mapping relations, change destination address in the network request for its corresponding container Location；The network request after conversion is sent to docker Microsoft Loopback Adapters；
    If it is, decapsulating the network request obtains source request；The source is sent to ask to flannel Microsoft Loopback Adapters, via The flannel Microsoft Loopback Adapters are forwarded to the docker Microsoft Loopback Adapters.
  2. 2. according to the method for claim 1, it is characterised in that described to judge whether the network request comes from flannel Overlay network includes：
    Whether the host port for judging to receive the network request is the first predetermined port.
  3. 3. according to the method for claim 1, it is characterised in that it is described to be based on destination address mapping relations, change the net Destination address in network request includes for its corresponding capsule address：
    According to the destination interface in the network request, destination address mapping relations corresponding to lookup；
    Based on the destination address mapping relations, change destination address in the network request for its corresponding capsule address with And the destination interface is its corresponding container port.
  4. 4. according to the method for claim 3, it is characterised in that the destination address mapping relations define the host Physical network card address correspondence mappings capsule address and the host host port correspondence mappings container port.
  5. 5. according to the method for claim 4, it is characterised in that the destination address mapping relations are advance as follows It is determined that：
    The request to create that platform is sent is controlled in acquisition, the request to create includes the host port and correspondingly of the host Container port；
    Based on the host port, the physical network card address of the host, the container port and the container port Corresponding capsule address, create the destination address mapping relations.
  6. A kind of 6. network communication device, it is characterised in that including：
    Receiving module, the network request of host is reached for receiving；
    Judge module, for judging whether the network request comes from flannel overlay networks；Wherein, the host is matched somebody with somebody It is placed in the flannel overlay networks；
    Address mapping module, if the judged result for the judge module is no, based on destination address mapping relations, conversion Destination address in the network request is its corresponding capsule address；
    First processing module, for sending the network request after changing to docker Microsoft Loopback Adapters；
    Decapsulation module, if the judged result for the judge module is yes, decapsulating the network request acquisition source please Ask；
    Second processing module, asked for sending the source to flannel Microsoft Loopback Adapters, via the flannel Microsoft Loopback Adapters It is forwarded to the docker Microsoft Loopback Adapters.
  7. 7. device according to claim 6, it is characterised in that the judge module is specifically used for judging to receive the network Whether the host port of request is the first predetermined port.
  8. 8. device according to claim 6, it is characterised in that the address mapping module includes：
    Relation searching unit, for the destination interface in the network request, destination address mapping relations corresponding to lookup；
    Address mapping unit, for based on the destination address mapping relations, the destination address changed in the network request is Its corresponding capsule address and the destination interface are its corresponding container port.
  9. 9. device according to claim 8, it is characterised in that the destination address mapping relations define the host Physical network card address correspondence mappings capsule address and the host host port correspondence mappings container port.
  10. 10. device according to claim 9, it is characterised in that also include：
    Acquisition module, the request to create sent for controlling platform in acquisition, the request to create include the place of the host Host port and corresponding container port；
    Relation establishes module, for based on the host port, the physical network card address of the host, the container port And capsule address corresponding to the container port, create the destination address mapping relations.
CN201710515738.5A 2017-06-29 2017-06-29 Network communication method and device Pending CN107395781A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710515738.5A CN107395781A (en) 2017-06-29 2017-06-29 Network communication method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710515738.5A CN107395781A (en) 2017-06-29 2017-06-29 Network communication method and device

Publications (1)

Publication Number Publication Date
CN107395781A true CN107395781A (en) 2017-11-24

Family

ID=60334399

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710515738.5A Pending CN107395781A (en) 2017-06-29 2017-06-29 Network communication method and device

Country Status (1)

Country Link
CN (1) CN107395781A (en)

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109412864A (en) * 2018-11-26 2019-03-01 江苏华邦网络科技有限公司 A kind of method of non-docker network environment outside access docker container environment
CN109462511A (en) * 2018-12-11 2019-03-12 中科曙光国际信息产业有限公司 The method for building up and device of network
CN109862127A (en) * 2017-11-30 2019-06-07 华为技术有限公司 A kind of method and relevant apparatus of message transmissions
CN110138606A (en) * 2019-05-06 2019-08-16 携程旅游信息技术（上海）有限公司 Capacitor network configuration method and system
CN110881007A (en) * 2018-09-05 2020-03-13 北京京东尚科信息技术有限公司 Container cluster network access method and device
CN111262784A (en) * 2020-01-13 2020-06-09 杭州朗和科技有限公司 Message forwarding method, message forwarding device, storage medium and electronic equipment
CN111756855A (en) * 2020-06-30 2020-10-09 北京来也网络科技有限公司 Remote control system, method, medium and computing device
CN111800340A (en) * 2020-06-05 2020-10-20 北京京东尚科信息技术有限公司 Data packet forwarding method and device
CN111885075A (en) * 2020-07-30 2020-11-03 广州华多网络科技有限公司 Container communication method, device, network equipment and storage medium
CN112003750A (en) * 2020-08-24 2020-11-27 浪潮云信息技术股份公司 Data center host Overlay network access control method
CN113259503A (en) * 2021-06-24 2021-08-13 浩鲸云计算科技股份有限公司 Method and system for realizing cross-network communication among different containers based on Infiniband
CN113765816A (en) * 2021-08-02 2021-12-07 阿里巴巴新加坡控股有限公司 Flow control method, system, equipment and medium based on service grid
CN114039949A (en) * 2021-12-24 2022-02-11 上海观安信息技术股份有限公司 Cloud service floating IP binding method and system
CN115208888A (en) * 2022-09-13 2022-10-18 杭州优云科技有限公司 Communication method and device for cloud instance to cross available areas and electronic equipment

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105847108A (en) * 2016-05-24 2016-08-10 中国联合网络通信集团有限公司 Method and apparatus for communication between containers
CN106067858A (en) * 2016-05-24 2016-11-02 中国联合网络通信集团有限公司 Communication means between container, Apparatus and system
US20160366233A1 (en) * 2015-06-10 2016-12-15 Platform9, Inc. Private Cloud as a service
CN106790660A (en) * 2017-01-18 2017-05-31 咪咕视讯科技有限公司 A kind of dispositions method and device for realizing distributed memory system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160366233A1 (en) * 2015-06-10 2016-12-15 Platform9, Inc. Private Cloud as a service
CN105847108A (en) * 2016-05-24 2016-08-10 中国联合网络通信集团有限公司 Method and apparatus for communication between containers
CN106067858A (en) * 2016-05-24 2016-11-02 中国联合网络通信集团有限公司 Communication means between container, Apparatus and system
CN106790660A (en) * 2017-01-18 2017-05-31 咪咕视讯科技有限公司 A kind of dispositions method and device for realizing distributed memory system

Cited By (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109862127A (en) * 2017-11-30 2019-06-07 华为技术有限公司 A kind of method and relevant apparatus of message transmissions
CN109862127B (en) * 2017-11-30 2021-05-11 华为技术有限公司 Message transmission method and related device
CN110881007A (en) * 2018-09-05 2020-03-13 北京京东尚科信息技术有限公司 Container cluster network access method and device
CN110881007B (en) * 2018-09-05 2023-03-07 北京京东尚科信息技术有限公司 Container cluster network access method and device
CN109412864A (en) * 2018-11-26 2019-03-01 江苏华邦网络科技有限公司 A kind of method of non-docker network environment outside access docker container environment
CN109412864B (en) * 2018-11-26 2021-08-10 江苏华邦网络科技有限公司 Method for externally accessing docker container environment in non-docker network environment
CN109462511B (en) * 2018-12-11 2021-12-24 中科曙光国际信息产业有限公司 Network establishing method and device
CN109462511A (en) * 2018-12-11 2019-03-12 中科曙光国际信息产业有限公司 The method for building up and device of network
CN110138606A (en) * 2019-05-06 2019-08-16 携程旅游信息技术（上海）有限公司 Capacitor network configuration method and system
CN111262784A (en) * 2020-01-13 2020-06-09 杭州朗和科技有限公司 Message forwarding method, message forwarding device, storage medium and electronic equipment
CN111262784B (en) * 2020-01-13 2022-05-17 杭州朗和科技有限公司 Message forwarding method, message forwarding device, storage medium and electronic equipment
CN111800340A (en) * 2020-06-05 2020-10-20 北京京东尚科信息技术有限公司 Data packet forwarding method and device
CN111800340B (en) * 2020-06-05 2022-08-12 北京京东尚科信息技术有限公司 Data packet forwarding method and device
CN111756855A (en) * 2020-06-30 2020-10-09 北京来也网络科技有限公司 Remote control system, method, medium and computing device
CN111756855B (en) * 2020-06-30 2023-06-20 北京来也网络科技有限公司 Remote control system, method, medium and computing device
CN111885075A (en) * 2020-07-30 2020-11-03 广州华多网络科技有限公司 Container communication method, device, network equipment and storage medium
CN112003750A (en) * 2020-08-24 2020-11-27 浪潮云信息技术股份公司 Data center host Overlay network access control method
CN112003750B (en) * 2020-08-24 2023-11-21 浪潮云信息技术股份公司 Data center host computer Overlay network access control method
CN113259503A (en) * 2021-06-24 2021-08-13 浩鲸云计算科技股份有限公司 Method and system for realizing cross-network communication among different containers based on Infiniband
CN113765816A (en) * 2021-08-02 2021-12-07 阿里巴巴新加坡控股有限公司 Flow control method, system, equipment and medium based on service grid
CN113765816B (en) * 2021-08-02 2023-12-15 阿里巴巴新加坡控股有限公司 Flow control method, system, equipment and medium based on service grid
CN114039949A (en) * 2021-12-24 2022-02-11 上海观安信息技术股份有限公司 Cloud service floating IP binding method and system
CN114039949B (en) * 2021-12-24 2024-03-26 上海观安信息技术股份有限公司 Cloud service floating IP binding method and system
CN115208888A (en) * 2022-09-13 2022-10-18 杭州优云科技有限公司 Communication method and device for cloud instance to cross available areas and electronic equipment

Similar Documents

Publication Publication Date Title
CN107395781A (en) Network communication method and device
US11470001B2 (en) Multi-account gateway
CN111817961B (en) Open vSwitch kernel flow table-based distributed routing method and device in Overlay network
CN106844000A (en) Using the method and apparatus of browser access linux container cluster under a kind of multi-user environment
CN107872392A (en) Service function chain data and service function instance data are distributed in a network
CN106911778A (en) A kind of flow bootstrap technique and system
CN108259642A (en) Public service virtual machine access method and device based on private clound
EP0658837A2 (en) Method for controlling computer network security
CN106850324A (en) Virtual network interface object
CN107105061A (en) A kind of service registry method and device
CN108111619A (en) A kind of data distribution method and device, computer equipment, storage medium
US20100257226A1 (en) Communication module and application program provided with same
CN103685281B (en) The switching method and equipment of a kind of network address agreement
CN107800603B (en) Intranet user accesses the method and storage medium of headend equipment based on VPN
CN106063229A (en) Methods and systems for forwarding data
CN106664515A (en) Method for transmitting content between terminals through service control device link
WO2014169946A1 (en) Subscriber identification and provisioning in ip translation environments
US20090313357A1 (en) Method for establishing connection between user-network of other technology and domain name system proxy server for controlling the same
CN114301868B (en) Method for quickly generating virtual container floating IP and method and device for network direct connection
CN106921716A (en) The method and device of the network service process of debugging embedded equipment
CN110266517A (en) External service call method, device and terminal device based on gateway
EP3349402B1 (en) Message processing method and device
US11558246B2 (en) Implementing service function chains
CN108667776A (en) A kind of network service diagnostic method
CN110392123A (en) The methods, devices and systems of detection outlet IP address

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20171124