CN114244802A - Method and system for maintaining IPv4/IPv6 dual-stack load balancing session - Google Patents

Method and system for maintaining IPv4/IPv6 dual-stack load balancing session Download PDF

Info

Publication number
CN114244802A
CN114244802A CN202111561487.7A CN202111561487A CN114244802A CN 114244802 A CN114244802 A CN 114244802A CN 202111561487 A CN202111561487 A CN 202111561487A CN 114244802 A CN114244802 A CN 114244802A
Authority
CN
China
Prior art keywords
load balancing
address
ipv4
session
source
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
CN202111561487.7A
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 Chenglongma Beijing Technology Co ltd
Original Assignee
Beijing Chenglongma Beijing 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 Chenglongma Beijing Technology Co ltd filed Critical Beijing Chenglongma Beijing Technology Co ltd
Priority to CN202111561487.7A priority Critical patent/CN114244802A/en
Publication of CN114244802A publication Critical patent/CN114244802A/en
Pending legal-status Critical Current

Links

Images

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
    • H04L61/2542—Translation of Internet protocol [IP] addresses involving dual-stack hosts
    • 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
    • H04L61/255—Maintenance or indexing of mapping tables
    • 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/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/1012—Server selection for load balancing based on compliance of requirements or conditions with available server resources
    • 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/14—Session management

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)

Abstract

The invention provides a method and a system for maintaining IPv4/IPv6 double-stack load balancing sessions, and relates to the field of Internet. A method for maintaining an IPv4/IPv6 dual stack load balancing session comprises the following steps: when the client accesses the application system by using the IPv6 network, the address translation system translates the source address of the user; randomly selecting an IPv4 address from an IPv4 address pool built in the conversion system as a source address; initiating a request to the load balancing equipment by using the IPv4 address as a source address, and recording related information of the session connection in a mapping table inside a conversion system; when the access request passes through the load balancing device, the load balancing device realizes session maintenance based on the source IP of the client. It can ensure that each call back adopts a fixed source IP address through a mapping table technology, thereby realizing the session maintenance with balanced load.

Description

Method and system for maintaining IPv4/IPv6 dual-stack load balancing session
Technical Field
The invention relates to the field of Internet, in particular to a method and a system for maintaining an IPv4/IPv6 dual-stack load balancing session.
Background
IP is an important bridge of the internet, and is a protocol designed for communication between computer networks, and the internet has rapidly developed into the largest and open computer communication network in the world due to the IP protocol. The protocol suite employed by the global internet is the TCP/IP protocol suite. IP is a protocol of a network layer in the TCP/IP protocol family, and is a core protocol of the TCP/IP protocol family. The version number of the IP protocol is currently 4 (abbreviated as IPv4), and developments have been used for more than 30 years to date. The IP protocol version IPv4 currently used by the nenet faces a series of problems, of which the imminent exhaustion of IP addresses is certainly the most serious, due to various drawbacks of its own. To completely solve the problem of IPv4, IETF started to research and develop the next-generation IP protocol, i.e., IPv6, from 1995. The IPv6 has an address space as long as 128 bits, which can completely solve the problem of insufficient IPv4 addresses, and besides, the IPv6 also adopts many technologies such as hierarchical address mode, efficient IP header, quality of service, automatic configuration of host addresses, authentication, and encryption.
When an IPv4/IPv6 protocol conversion system is used to realize IPv6 transformation in an address translation mode, the source address of an IPv4 request initiated by a conversion device to a load balancing device is often single from the conversion device to the load balancing device, and load balancing based on IP addresses cannot be realized.
Disclosure of Invention
The invention aims to provide a method for maintaining an IPv4/IPv6 dual-stack load balancing session, which can adopt a plurality of source addresses for accessing from a conversion device to a load balancing device by setting an address pool and an address mapping table technology and ensure that each return session adopts a fixed source IP address by the mapping table technology, thereby realizing the session maintenance of load balancing.
Another object of the present invention is to provide a system for IPv4/IPv6 dual stack load balancing session maintenance, which is capable of operating a method for IPv4/IPv6 dual stack load balancing session maintenance.
The embodiment of the invention is realized by the following steps:
in a first aspect, an embodiment of the present application provides a method for IPv4/IPv6 dual stack load balancing session maintenance, which includes that when a client accesses an application system using an IPv6 network, an address translation system translates a source address of a user; randomly selecting an IPv4 address from an IPv4 address pool built in the conversion system as a source address; initiating a request to the load balancing equipment by using the IPv4 address as a source address, and recording related information of the session connection in a mapping table inside a conversion system; when the access request passes through the load balancing device, the load balancing device realizes session maintenance based on the source IP of the client.
In some embodiments of the present invention, the initiating a request to the load balancing device by using the IPv4 address as a source address, and recording the relevant information of the session connection in a mapping table inside the translation system includes: and recording the source IP, the source port number, the destination IP, the destination port number, the protocol type and the effective remaining time information of the session connection in a mapping table inside the conversion system.
In some embodiments of the present invention, the initiating a request to the load balancing device by using the IPv4 address as a source address, and recording the relevant information of the session connection in a mapping table inside the translation system includes: the mapping table records a source IP, a source port number, a destination IP, a destination port number, a protocol type and effective remaining time, wherein the effective remaining time is a countdown timer, when each mapping record is newly created, an initial value is set for the timer, the timer counts down in seconds, and when the count of the countdown timer is 0, the corresponding mapping record is cleared by the system.
In some embodiments of the present invention, the above further includes: when the load balancing device receives a TCP SYN data packet, the load balancing device inquires whether a session record of a source IP address of the TCP SYN data packet exists in a session table of the load balancing device.
In some embodiments of the present invention, the above further includes: if not, the load balancer determines the new user request, matches the corresponding server according to the load balancing algorithm, and forwards the TCP SYN data packet, and meanwhile, adds a record in the session table.
In some embodiments of the present invention, the above further includes: if the record of the source IP address of the TCP SYN data packet exists in the session table, the load balancer forwards the TCP SYN request packet to the same server which processes the request before, and the server is not matched through the load balancing algorithm any more.
In some embodiments of the present invention, the above further includes: when a TCP FIN and/or RESET packet is received, the load balancer suspends the session, keeping track of the session table, remembering the source IP address of the connection and the address of the server handling the connection.
In a second aspect, the embodiment of the present application provides a system for IPv4/IPv6 dual stack load balancing session maintenance, which includes a client module, configured to translate, by an address translation system, a source address of a user when a client accesses an application system using an IPv6 network;
the address pool module is used for randomly selecting an IPv4 address from an IPv4 address pool built in the conversion system as a source address;
a mapping table module, configured to initiate a request to the load balancing device using the IPv4 address as a source address, and record relevant information of the session connection in a mapping table inside the conversion system;
and the load balancing equipment module is used for realizing session maintenance by the load balancing equipment based on the source IP of the client when the access request passes through the load balancing equipment.
In some embodiments of the invention, the above includes: at least one memory for storing computer instructions; at least one processor in communication with the memory, wherein the at least one processor, when executing the computer instructions, causes the system to:
in a third aspect, embodiments of the present application provide a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements a method such as any one of the methods of IPv4/IPv6 dual stack load balancing session preservation.
Compared with the prior art, the embodiment of the invention has at least the following advantages or beneficial effects:
the invention adopts a plurality of source addresses from the conversion equipment to the load balancing equipment by setting an address pool and an address mapping table technology, and ensures that each call back adopts a fixed source IP address by the mapping table technology, thereby realizing the session maintenance of load balancing.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.
Fig. 1 is a schematic diagram illustrating steps of a method for maintaining an IPv4/IPv6 dual stack load balancing session according to an embodiment of the present invention;
fig. 2 is a schematic diagram illustrating detailed steps of a method for maintaining an IPv4/IPv6 dual stack load balancing session according to an embodiment of the present invention;
fig. 3 is a schematic block diagram of a system for maintaining an IPv4/IPv6 dual stack load balancing session according to an embodiment of the present invention;
fig. 4 is an electronic device according to an embodiment of the present invention;
FIG. 5 is a diagram illustrating IPv4/IPv6 translation interaction provided by an embodiment of the present invention.
Icon: 10-a client module; 20-address pool module; 30-mapping table module; 40-a load balancing device module; 101-a memory; 102-a processor; 103-communication interface.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
It is to be noted that the term "comprises," "comprising," or any other variation thereof is intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Some embodiments of the present application will be described in detail below with reference to the accompanying drawings. The embodiments described below and the individual features of the embodiments can be combined with one another without conflict.
Example 1
Referring to fig. 1 and fig. 5, fig. 1 is a schematic diagram of steps of a method for maintaining an IPv4/IPv6 dual stack load balancing session according to an embodiment of the present invention, and the method is as follows:
step S100, when the client accesses the application system by using the IPv6 network, the address translation system translates the source address of the user;
step S110, randomly selecting an IPv4 address from an IPv4 address pool built in the conversion system as a source address;
in some embodiments, assuming that the VLAN segment of the IPv4 network of the transition device is 192.168.10.0/24, the address pool uses 100 addresses of the segment, and the address pool is: 192.168.10.2-192.168.10.101 total 100 addresses. These 100 addresses are configured on the translation device, that is to say 100 IPv4 addresses are configured on the network card of the translation device.
Step S120, the IPv4 address is used as a source address to initiate a request to the load balancing equipment, and the related information of the session connection is recorded in a mapping table in the conversion system;
in some embodiments, the relevant information includes: source IP, source port number, destination IP, destination port number, protocol type, valid remaining time.
In some embodiments, assuming that the IPv6 address of a client is 2408:100:200: 18 and the address pool of the translation device uses the addresses in the above example, then a record of the mapping table may be:
2408:100:200::1813280192.168.10.2613280TCP 240
the first IPv6 address is the actual address of the client, 13280 is the actual port number used by the client in the session, 192. 168.10.26 the address is the IPv4 address randomly selected by the system from the address pool to initiate the request to the load balancing device, the next 13280 is the port number used by the IPv4 address to initiate the request, TCP is the protocol used by the session, and 240 is the effective duration of the session in seconds.
Step S130, when the access request passes through the load balancing device, the load balancing device realizes session maintenance based on the source IP of the client.
Example 2
Referring to fig. 2, fig. 2 is a detailed step diagram of a method for maintaining an IPv4/IPv6 dual stack load balancing session according to an embodiment of the present invention, which is shown as follows:
step S200, record the source IP, source port number, destination IP, destination port number, protocol type, and valid remaining time information of the session connection in the mapping table inside the conversion system.
Step S210, the mapping table records a source IP, a source port number, a destination IP, a destination port number, a protocol type, and a valid remaining time, where the valid remaining time is a countdown timer, when each mapping record is newly created, an initial value is set for the timer, the timer counts down in seconds, and when the count of the countdown timer is 0, the corresponding mapping record is cleared by the system.
In step S220, after the load balancing device receives a TCP SYN packet, the load balancing device queries whether a session record of the source IP address of the TCP SYN packet exists in its session table.
Step S230, if not found, the load balancer determines that the new user request is received, matches the corresponding server according to the load balancing algorithm, and forwards the TCP SYN packet, and meanwhile, adds a record in the session table.
In step S240, if there is a record of the source IP address of the TCP SYN packet in the session table, the load balancer forwards the TCP SYN request packet to the same server that has previously processed the request, and does not match the server through the load balancing algorithm.
In step S250, when receiving a TCP FIN and/or RESET packet, the load balancer suspends the session and keeps a record in the session table to remember the source IP address of the connection and the address of the server handling the connection.
In some embodiments, a source IP address based session maintenance technique:
when the load balancing device receives a TCP SYN packet, the load balancing device will look up in its session table whether there is a session record for the source IP address. If not, the load balancer considers that the request is a new user request, selects a proper server according to the load balancing algorithm, and forwards the TCP SYN data packet, and meanwhile, adds a record in the session table. If there is a record of the source IP address in the session table, the load balancer will forward the TCP SYN request packet to the same server that previously handled the request, and no longer select a server through the load balancing algorithm. When a TCP FIN or RESET packet is received, the load balancer will terminate the session, but will keep track of the source IP address of the connection and the address of the server handling the connection in the session table.
Since the load balancer does not understand the application layer protocol, it does not know when an application interaction starts and ends in order to continue or abort the session-keeping process. Thus, while on session hold, the load balancer will start a timer for each record in the session table, starting from the end of the last active connection by the user. This timer, also called the session hold timer, primarily records the length of time that the connection is idle. If the user does not have a new connection request before the timer expires, the load balancer will delete the user's corresponding session maintenance record. If a new connection request is received from the user before the timer expires, the load balancer will reset the timer and restart when the user's last active connection is over.
When the back-end server receives the request, the back-end server returns response information to the load balancing device, the destination address of the response is the IPv4 address randomly generated by the previous conversion device, the load balancing device forwards the response to the address conversion device, the address conversion device is provided with an address mapping table, the IPv6 address of the actual client corresponding to the randomly generated IPv4 address is recorded in the address mapping table, then the IPv4 address randomly generated before is replaced by the actual IPv6 to serve as the destination address, and the response data of the back-end server is sent to the client.
When the IPv6 client initiates a request to the conversion equipment through the IPv6 network again, the conversion equipment searches whether a source IPv6 address of the client has a valid record in a mapping table, if so, the previously recorded and randomly generated IPv4 address is used as a source address, an access request is initiated to the load balancing equipment, and because the source IPv4 address requested for the second time from the conversion equipment is the same as the source IPv4 address requested for the first time, the load balancing equipment can realize session maintenance based on an IP address according to the IPv4 address, and the request of the client is forwarded to a server fixed at the back end.
The processing flow of the second response feedback of the back-end server is the same as the processing flow of the first response feedback.
Management of the internal mapping table of the conversion equipment:
the mapping table records a source IP, a source port number, a destination IP, a destination port number, a protocol type and valid remaining time, wherein the valid remaining time is a countdown timer, when each mapping record is newly created, an initial value is set for the timer, the timer counts down by taking seconds as a unit, and when the count of the countdown timer is 0, the corresponding mapping record is cleared by the system. In addition, when a TCP FIN or RESET packet is received, the corresponding mapping record is also cleared.
By combining the steps described above, by setting an address pool and an address mapping table technique, multiple source addresses are used for access from the translation device to the load balancing device, and a fixed source IP address is used for each call back by the mapping table technique, thereby realizing session maintenance for load balancing.
Example 3
Referring to fig. 3, fig. 3 is a schematic diagram of system modules for maintaining an IPv4/IPv6 dual stack load balancing session according to an embodiment of the present invention, and the system modules are as follows:
a client module 10 for converting a source address of a user by an address conversion system when a client accesses an application system using an IPv6 network;
an address pool module 20, configured to randomly select an IPv4 address from an IPv4 address pool built in the translation system as a source address;
a mapping table module 30, configured to initiate a request to the load balancing device by using the IPv4 address as a source address, and record relevant information of the session connection in a mapping table inside the conversion system;
and the load balancing device module 40 is used for realizing session maintenance by the load balancing device based on the source IP of the client when the access request passes through the load balancing device.
As shown in fig. 4, an embodiment of the present application provides an electronic device, which includes a memory 101 for storing one or more programs; a processor 102. The one or more programs, when executed by the processor 102, implement the method of any of the first aspects as described above.
Also included is a communication interface 103, and the memory 101, processor 102 and communication interface 103 are electrically connected to each other, directly or indirectly, to enable transfer or interaction of data. For example, the components may be electrically connected to each other via one or more communication buses or signal lines. The memory 101 may be used to store software programs and modules, and the processor 102 executes the software programs and modules stored in the memory 101 to thereby execute various functional applications and data processing. The communication interface 103 may be used for communicating signaling or data with other node devices.
The Memory 101 may be, but is not limited to, a Random Access Memory 101 (RAM), a Read Only Memory 101 (ROM), a Programmable Read Only Memory 101 (PROM), an Erasable Read Only Memory 101 (EPROM), an electrically Erasable Read Only Memory 101 (EEPROM), and the like.
The processor 102 may be an integrated circuit chip having signal processing capabilities. The Processor 102 may be a general-purpose Processor 102, including a Central Processing Unit (CPU) 102, a Network Processor 102 (NP), and the like; but may also be a Digital Signal processor 102 (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware components.
In the embodiments provided in the present application, it should be understood that the disclosed method and system can be implemented in other ways. The method and system embodiments described above are merely illustrative, for example, the flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of methods and systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
In another aspect, embodiments of the present application provide a computer-readable storage medium, on which a computer program is stored, which, when executed by the processor 102, implements the method according to any one of the first aspect described above. The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory 101 (ROM), a Random Access Memory 101 (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
To sum up, the present invention provides a method and a system for maintaining an IPv4/IPv6 dual stack load balancing session, where an address pool and an address mapping table technology are set, multiple source addresses are used for access from a translation device to a load balancing device, and a fixed source IP address is used for each return session through the mapping table technology, so as to implement load balancing session maintenance.
The above is only a preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes will occur to those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
It will be evident to those skilled in the art that the present application is not limited to the details of the foregoing illustrative embodiments, and that the present application may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned.

Claims (10)

1. An IPv4/IPv6 dual stack load balancing session keeping method is characterized by comprising the following steps:
when the client accesses the application system by using the IPv6 network, the address translation system translates the source address of the user;
randomly selecting an IPv4 address from an IPv4 address pool built in the conversion system as a source address;
initiating a request to the load balancing equipment by using the IPv4 address as a source address, and recording related information of the session connection in a mapping table inside a conversion system;
when the access request passes through the load balancing device, the load balancing device realizes session maintenance based on the source IP of the client.
2. The method for IPv4/IPv6 dual stack load balancing session maintenance according to claim 1, wherein the initiating a request to the load balancing device using the IPv4 address as a source address, and recording the relevant information of the session connection in a mapping table inside the translation system includes:
and recording the source IP, the source port number, the destination IP, the destination port number, the protocol type and the effective remaining time information of the session connection in a mapping table inside the conversion system.
3. The method for IPv4/IPv6 dual stack load balancing session maintenance according to claim 1, wherein the initiating a request to the load balancing device using the IPv4 address as a source address, and recording the relevant information of the session connection in a mapping table inside the translation system includes:
the mapping table records a source IP, a source port number, a destination IP, a destination port number, a protocol type and effective remaining time, wherein the effective remaining time is a countdown timer, when each mapping record is newly created, an initial value is set for the timer, the timer counts down in seconds, and when the count of the countdown timer is 0, the corresponding mapping record is cleared by the system.
4. The method of IPv4/IPv6 dual stack load balancing session maintenance as recited in claim 1, further comprising:
when the load balancing device receives a TCP SYN data packet, the load balancing device inquires whether a session record of a source IP address of the TCP SYN data packet exists in a session table of the load balancing device.
5. The method of IPv4/IPv6 dual stack load balancing session maintenance as recited in claim 4, further comprising:
if not, the load balancer determines the new user request, matches the corresponding server according to the load balancing algorithm, and forwards the TCP SYN data packet, and meanwhile, adds a record in the session table.
6. The method of IPv4/IPv6 dual stack load balancing session maintenance as recited in claim 4, further comprising:
if the record of the source IP address of the TCP SYN data packet exists in the session table, the load balancer forwards the TCP SYN request packet to the same server which processes the request before, and the server is not matched through the load balancing algorithm any more.
7. The method of IPv4/IPv6 dual stack load balancing session maintenance as recited in claim 4, further comprising:
when a TCP FIN and/or RESET packet is received, the load balancer suspends the session, keeping track of the session table, remembering the source IP address of the connection and the address of the server handling the connection.
8. A system for IPv4/IPv6 dual stack load balancing session maintenance, comprising:
the client module is used for converting the source address of the user by the address conversion system when the client accesses the application system by using the IPv6 network;
the address pool module is used for randomly selecting an IPv4 address from an IPv4 address pool built in the conversion system as a source address;
a mapping table module, configured to initiate a request to the load balancing device using the IPv4 address as a source address, and record relevant information of the session connection in a mapping table inside the conversion system;
and the load balancing equipment module is used for realizing session maintenance by the load balancing equipment based on the source IP of the client when the access request passes through the load balancing equipment.
9. The IPv4/IPv6 dual stack load balancing session maintenance system of claim 8, further comprising:
at least one memory for storing computer instructions;
at least one processor in communication with the memory, wherein the at least one processor, when executing the computer instructions, causes the system to perform: the device comprises a client module, an address pool module, a mapping table module and a load balancing equipment module.
10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-7.
CN202111561487.7A 2021-12-20 2021-12-20 Method and system for maintaining IPv4/IPv6 dual-stack load balancing session Pending CN114244802A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111561487.7A CN114244802A (en) 2021-12-20 2021-12-20 Method and system for maintaining IPv4/IPv6 dual-stack load balancing session

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111561487.7A CN114244802A (en) 2021-12-20 2021-12-20 Method and system for maintaining IPv4/IPv6 dual-stack load balancing session

Publications (1)

Publication Number Publication Date
CN114244802A true CN114244802A (en) 2022-03-25

Family

ID=80759230

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111561487.7A Pending CN114244802A (en) 2021-12-20 2021-12-20 Method and system for maintaining IPv4/IPv6 dual-stack load balancing session

Country Status (1)

Country Link
CN (1) CN114244802A (en)

Similar Documents

Publication Publication Date Title
US7472201B1 (en) Method and system for resolving domain name system queries in a multiprotocol communications network
JP3443529B2 (en) Method of providing firewall service and computer system providing firewall service
US7392241B2 (en) Searching method for a security policy database
US7450524B2 (en) Method and apparatus for determining network topology in a peer-to-peer network
US7398301B2 (en) Method and apparatus for facilitating distributed delivery of content across a computer network
US6526444B1 (en) Using an authentication server to obtain dial-out information on a network
US9641561B2 (en) Method and system for managing a SIP server
US8874718B2 (en) Method and device for storing domain name system records, method and device for parsing domain name
US20070162968A1 (en) Rule-based network address translation
EP2666281B1 (en) Domain name system server
JP2003198637A (en) Packet verifying method
JPH10243028A (en) Session cache and rule cashing method for dynamic filter
US20170264590A1 (en) Preventing dns cache poisoning
WO2014101777A1 (en) Flow table matching method and device, and switch
EP2469787A1 (en) Method and device for preventing network attacks
US20080101222A1 (en) Lightweight, Time/Space Efficient Packet Filtering
EP3618355B1 (en) Systems and methods for operating a networking device
WO2015131720A1 (en) Packet processing method and device
US6735220B1 (en) Using a centralized server to coordinate assignment of identifiers in a distributed system
WO2012088934A1 (en) Method and switching device for filtering messages
US8307415B2 (en) Safe hashing for network traffic
US20220231945A1 (en) Message matching table lookup method, system, storage medium, and terminal
JP6056857B2 (en) Communication control device and communication control method
CN114244802A (en) Method and system for maintaining IPv4/IPv6 dual-stack load balancing session
CN105207977A (en) TCP data packet processing method and device

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