KR102015735B1 - Communication method and apparatus of peer for peer to peer(p2p) handshaking control - Google Patents

Abstract

According to an embodiment of the present invention, provided are a communication method of a peer for peer to peer (p2p) shaking control and an apparatus thereof. The communication method comprises the steps of: receiving a connection request packet from a neighboring peer to a first peer; determining whether a connection request packet is original or duplicated; duplicating the connection request packet to generate a plurality of duplicate connection request packets when the connection request packet is determined to be an original; and transmitting the duplicated connection request packets to a plurality of second peers.

Description

TECHNICAL METHOD AND APPARATUS OF PEER FOR PEER TO PEER (P2P) HANDSHAKING CONTROL}

The following embodiments are directed to a method and apparatus for communication of a peer for P2P handshaking control.

By randomizing the occurrence of a transaction, the server continues to give a response to the occurrence of the transaction. For example, if an attacker such as a hacker or the like sends a packet and randomly generates a transaction by tricking the recipient's address, the server has no way of determining whether the address is correct. This forces the server to use as much memory and network traffic as the packets it needs to send, which can make the server vulnerable to attack.

According to an embodiment, the security of the server may be improved by bypassing an attack on the network server through distributed response processing through distributed processing of a connection request (SYN) packet.

According to an embodiment, the security of the server may be improved through distributed response processing through distributed processing of a connection request (SYN) packet.

According to one side, a communication method comprises: receiving a connection request (SYN) packet from a neighboring peer to a first peer; Determining whether the access request packet is original or duplicated; Generating a plurality of duplicate connection request packets by copying the connection request packet when it is determined that the connection request packet is original; And sending the duplicate connection request packets to a plurality of second peers.

Source information of the duplicate connection request packets may be the same as source information of the connection request packet.

Generating the duplicate connection request packets may include changing the source information from the first peer to the peripheral peer to generate the duplicate connection request packets.

The communication method may further include: generating a connection request response (SYN ACK) packet corresponding to the connection request packet when it is determined that the connection request packet is duplicated; And transmitting the access request response packet to a neighboring peer corresponding to the source information of the access request packet.

The determining of whether the connection request packet is original or duplicated may include determining whether the connection request packet is original or duplicated based on a flag of a specific bit included in a header of the connection request packet. It may include determining whether or not.

The communication method includes receiving connection request response packets from neighbor peers to the first peer; Determining whether the received connection request response packets correspond to a connection request packet previously transmitted by the first peer; Generating an ACK packet for establishing a session based on the determination result; And transmitting the Ack packet to a neighboring peer corresponding to the destination information of the previously transmitted connection request packet.

The determining of whether the connection request response packets correspond to the previously transmitted connection request packet is based on the sequence number of the previously transmitted connection request packet and the sequence numbers of the connection request response packets. The method may include determining whether packets correspond to the previously transmitted connection request packet.

According to one side, a communication device includes a communication interface for receiving a connection request packet from a neighboring peer to a first peer; And a processor configured to determine whether the access request packet is original or duplicated, and if the access request packet is determined to be original, duplicate the access request packet to generate a plurality of duplicate access request packets. The communication interface sends the duplicate connection request packets to a plurality of second peers.

According to one side, it is possible to improve the security of the server through the distributed response processing through the distributed processing of the access request (SYN) packet.

According to one side, it is possible to provide a variable DNS (Domain Name System) processing technology to improve the efficiency by distributing the responsiveness of the P2P server.

1 is a diagram illustrating a session connection process between peers according to an exemplary embodiment.
2 is a flowchart illustrating a communication method according to an embodiment.
3 is a diagram illustrating a three-way handshaking process according to one embodiment.
4 is a diagram illustrating a transmission process of a connection request (SYN) packet and a duplicate connection request packet between peers according to an embodiment.
5 to 6 are diagrams for explaining a process of generating and transmitting a plurality of duplicate connection request packets according to embodiments.
7 is a block diagram of a communication device according to one embodiment.

Hereinafter, exemplary embodiments will be described in detail with reference to the accompanying drawings. Like reference numerals in the drawings denote like elements.

Various modifications may be made to the embodiments described below. The examples described below are not intended to be limited to the embodiments and should be understood to include all modifications, equivalents, and substitutes for them.

The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting of examples. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this specification, terms such as "comprise" or "have" are intended to indicate that there is a feature, number, step, action, production element, part, or combination thereof described on the specification, one or more other features. It is to be understood that the present invention does not exclude the possibility of the presence or the addition of numbers, steps, operations, production elements, components, or combinations thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art. Terms such as those defined in the commonly used dictionaries should be construed as having meanings consistent with the meanings in the context of the related art and shall not be construed in ideal or excessively formal meanings unless expressly defined in this application. Do not.

In addition, in the following description with reference to the accompanying drawings, the same generating elements are given the same reference numerals regardless of the reference numerals and duplicate description thereof will be omitted. In the following description of the embodiment, when it is determined that the detailed description of the related known technology may unnecessarily obscure the gist of the embodiment, the detailed description thereof will be omitted.

1 is a diagram illustrating a session connection process between peers according to an exemplary embodiment. Referring to FIG. 1A, a TCP session connection process between a client (device) 101 and a server 103 is shown. Here, both the client 101 and the server 103 are functional units or devices that operate in the same position in the same protocol layer of a communication network using a hierarchical protocol, and according to an embodiment, a 'peer' ( May be equivalent to

The client 101 and the server 103 may perform a handshaking process of exchanging a response and an acknowledgment in a one-dimensional relationship, for example, ACK, NAK, NOK, OK, etc., in order to establish a reliable session relationship. Can be. 'Handshaking' may correspond to a process of dynamically setting a variable of a communication channel established between two communication entities before normal communication for the channel is started. Handshaking entails physical establishment of the channel, which may be performed prior to normal information transmission.

More specifically, the client 101 wishing to communicate with the server 103 may send a connection request (SYN) packet for synchronization to the server 103 for a TCP connection (110). In this case, the access request (SYN) packet may include its own sequence number x.

The server 103 receiving the access request (SYN) packet may transmit an access request response (SYN ACK) packet to the client 101 in response to the access request (SYN) packet (130). In this case, the SYN ACK packet may include, for example, its own sequence number y and response number x + 1.

Upon receiving the SYN ACK packet, the client 101 may transmit an ACK packet to the server 103 (150). In this case, the acknowledgment packet may include, for example, a response number y + 1.

Since the above-described process is performed through a process of exchanging three responses between the client 101 and the server 103 which are communication subjects, it is called 3-way handshaking. After three-way handshaking, a TCP session may be established between the client 101 and the server 103 (170).

Referring to (b) of FIG. 1, the client 101 corresponding to the originator of the connection request (SYN) requests the server 103 corresponding to the first peer to record the address of the receiver as the client 101 ( A process of transmitting a SYN) packet and receiving a SYN ACK packet in response thereto is illustrated.

For example, if a transaction occurs, such as a packet transmission and / or response, the server 103 continues to give the transaction a response to the occurrence. Therefore, the server 103 that receives the continuous connection request (SYN) packet from the client 101 must allocate memory for the consecutively received connection request (SYN) packet. In addition, server 103 may use network traffic to send a response (eg, a connection request response (SYN ACK) packet) to successive connection request (SYN) packets.

Referring to FIG. 1C, a case in which the hacker 105 cheats and transmits a transaction to the server 103 as a connection request (SYN) generator is illustrated.

For example, suppose the hacker 105 cheated the recipient's address and sent a successive connection request (SYN) packet. In this case, if a transaction occurs randomly, the server 103 has no way of determining whether the corresponding address is correct. Therefore, the server 103 has no choice but to use memory and network traffic as much as a SYN ACK packet corresponding to a successive SYN packet.

When such an attack comes in, the server 103 continuously transmits a SYN ACK packet to an incorrect address, and then an error message is displayed when a predetermined time is reached or the threshold of the transmission number is exceeded. When an error message occurs, the protection mechanism is activated in the network system, which increases the possibility of giving a response to the communication subjects by increasing the OS's access rights or the file system's access rights. At this time, the hacker 105 is more likely to achieve the purpose of the attack.

Therefore, in one embodiment, the attack of the hacker 105 may be avoided through a P2P handshaking process that confirms the occurrence of the connection request (SYN) event through peers other than the peer receiving the connection request (SYN) packet. .

2 is a flowchart illustrating a communication method according to an exemplary embodiment. Referring to FIG. 2, a P2P handshaking process according to an embodiment is shown.

According to an embodiment, the first peer receives a connection request (SYN) packet from a neighboring peer to a first peer (210). The source information recorded in the access request (SYN) packet may be a neighboring peer, and the destination information may be a packet that is a first peer. In this case, the connection request SYN may be located, for example, at a specific offset of the TCP header.

The first peer determines whether the connection request packet is original or duplicated (220). Herein, the "source" of the connection request packet indicates that the connection request packet is first generated by the peer without the connection request packet received from the neighboring peer. In addition, the fact that the access request packet is 'replicated' may correspond to a packet generated based on the peer receiving the access request packet corresponding to the original. In step 220, the first peer may determine whether the connection request packet is original or duplicated, for example, based on a flag of a specific bit included in the header of the connection request packet. Can be. In this case, when a flag of a specific bit is '1', the first peer may determine the connection request packet as an original. Alternatively, when the plaid of a specific bit is '0', the first peer may determine that the connection request packet is duplicated.

If it is determined in step 220 that the connection request packet is the original, the first peer generates a plurality of duplicate connection request packets by duplicating the connection request packet (230). In this case, the source information of the duplicate connection request packets may be the same as the source information of the connection request packet. In step 230, the first peer may change the source information from the first peer to the neighbor peer, for example, to generate duplicate connection request packets.

If it is determined in step 220 that the connection request packet has been duplicated, the first peer generates a SYN ACK packet corresponding to the connection request packet, and sends it to a neighboring peer corresponding to the source information of the connection request packet. The connection request response packet may be transmitted.

The first peer transmits 240 duplicate connection request packets to the plurality of second peers. The first peer may send, for example, duplicate connection request packets to the plurality of second peers to maintain a session for transmission of connection request response (SYN ACK) packets corresponding to the duplicate connection request packets.

According to an embodiment, the server may determine whether the connection request packet is original or duplicated based on deep learning, and generate duplicate connection request packets or connection request response packets based on the determination result. The server may be the first peer described above.

The server may generate a first input vector based on the connection request packet. Here, the vector may be defined in various forms according to design intention, such as a one-hot vector or a real vector. Weights may be applied to various variables in the connection request packet when generating the first input vector. Here, the weights may be optimized when learning the neural network. The server may apply the first input vector to the first learned neural network. The first input vector may correspond to an input layer of the first neural network.

The server may generate a first output vector generated from the first neural network to which the first input vector is applied. The first output vector may correspond to an output layer of the first neural network. The server may generate a determination result on whether the connection request packet is original or duplicated based on the first output vector. The value of the determination result may be represented discretely or as a continuous value like a plurality of grades.

According to an embodiment, the server may perform a duplicate connection request packet or a connection request packet based on deep learning. The value of the packet may be expressed in a predefined type.

According to an embodiment, the server may obtain a first output vector. The server may generate a second input vector based on the first output vector. Weights may be applied to variables in the first output vector when generating the second input vector. Here, the weights may be optimized when learning the neural network.

The server may apply the second input vector to the previously learned second neural network. The second input vector may correspond to the input layer of the second neural network.

The server may generate a second output vector generated from the second neural network to which the second input vector is applied. The second output vector may correspond to the output layer of the second neural network.

If the value corresponding to the first output vector corresponds to the original, the server may generate duplicate connection request packets based on the second output vector. If the value corresponding to the first output vector corresponds to the duplication, the server may generate a connection request response packet based on the second output vector. The second neural network may generate a duplicate connection request packet or a connection request response packet according to the original or duplicate of the connection request packet. The second neural network may generate a second output vector representing the packet.

The neural network includes an input layer to which training samples are input and an output layer to output training outputs, and can be learned based on the difference between the training outputs and the labels. Here, the labels may be defined based on determination results of whether the connection request packet is original, duplicate connection request packets, and connection request response packets. A neural network is connected to a group of nodes and is defined by weights between the connected nodes and an activation function that activates the nodes.

The learning apparatus may train a neural network using a gradient decent (GD) technique or a stochastic gradient descent (SGD) technique. The learning device may use a loss function designed by the outputs and labels of the neural network.

The learning apparatus may calculate the training error using a predefined loss function. The loss function can be predefined with labels, outputs and parameters as input variables, where the parameters can be set by weights in the neural network. For example, the loss function may be designed in the form of Mean Square Error (MSE), entropy, or the like. Various embodiments or methods may be employed in embodiments in which the loss function is designed.

The learning apparatus may find weights that affect training errors using a backpropagation technique. Here, the weights are relationships between nodes in the neural network. The learning apparatus may use the SGD technique with labels and outputs to optimize the weights found through the backpropagation technique. For example, the learning apparatus can update the weights of the loss function defined based on the labels, outputs and weights using the SGD technique.

The server may acquire the first output vector and the second output vector by using the neural network on which the learning is completed, determine whether the connection request packet is original, and generate duplicate connection request packets or connection request response packets.

3 is a diagram illustrating a 3-way handshaking process according to an embodiment. For example, assume that a connection request (SYN) packet has been sent to the recipient peer (310). The receiver peer may change the source information from the receiver peer to the neighbor peer to generate duplicate connection request packets, and send the generated duplicate connection request packet to another peer (320). The other peer receiving the duplicate connection request packet transmits a connection request response (SYN ACK) packet on behalf of the receiver peer (330).

The server receiving the SYN ACK packet from another peer may establish an session by sending an ACK packet to the receiver peer.

4 is a diagram illustrating a transmission process of a connection request (SYN) packet and a duplicate connection request packet between peers according to an embodiment. Referring to FIG. 4, a connection request generator (SYN) originator peer 401, a first peer 403, and a plurality of second peers 405, 407, 409 are shown.

Assume that the connection request (SYN) originator peer 401 continuously transmits the original connection request (SYN) packet to the first peer 403. In this case, the source information of the access request (SYN) packet may be the access request (SYN) generator peer 401, and the destination information may be the first peer 403. The first peer 403 may duplicate the connection request packet to generate a plurality of duplicate connection request packets, and send the duplicate connection request packets to the plurality of second peers 405, 407, and 409. At this time, the source information of the duplicate connection request packets may be the same as the connection request (SYN) generator peer 401 which is the source information of the connection request packet. Accordingly, the plurality of second peers 405, 407, 409 that have received the duplicate connection request packets are in accordance with the source information (eg, connection request (SYN) originator peer 401) of the duplicate connection request packets. Connection request response packets may be sent to a connection request (SYN) originator peer 401.

In this case, the SYN generator peer 401 that receives the connection request response packets from the neighbor peer, that is, the plurality of second peers 405, 407, and 409 may transmit the received connection request response packets. It may be determined whether it corresponds to a connection request packet. The connection request generator (SYN) originator 401 may determine that the connection request response packets are sent to the previously transmitted connection request packet based on, for example, the sequence number of the previously transmitted connection request packet and the sequence numbers of the connection request response packets. It can be determined whether or not the correspondence.

For example, if it is determined that the received connection request response packets correspond to the previously transmitted connection request packet, the SYN originator peer 401 may generate an ACK packet for establishing a session. Can be. The access request (SYN) generator peer 401 may transmit an Ack packet to a neighbor peer corresponding to destination information of the previously transmitted access request packet, that is, the first peer 403.

According to an embodiment, the response load for an attack received by an individual peer may be reduced by distributing connection request response packets through multiple peers in P2P for a connection request (SYN) attack. For example, if 100 bytes of memory are consumed to receive a connection request (SYN) packet and to transmit a connection request response packet, 200 bytes of call processing space is required, and the load on the processor is high. You lose. Therefore, simply distributing the connection request response packets can reduce the processing space and the processor load in half to reduce the quality of the bypass attack and reduce the effects on the attack.

5 is a diagram for describing a process of generating and transmitting a plurality of duplicate connection request packets according to an embodiment. Referring to FIG. 5, peer # 10 (501) corresponding to the originator of a connection request (SYN) transmits consecutive connection request (SYN) packets 502 to peer # 1 (Peer # 1). The situation of attacking 503 is shown. At this time, the source information of the connection request (SYN) packets 502 is described as peer # 50 that does not exist in the current network, not peer # 10 (501), destination information is described as peer # 1 (503). Can be. Peer # 1 503 that has received the connection request (SYN) packets 502 may duplicate the connection request packets 502 to generate a plurality of duplicate connection request packets 504, 506, 508. At this time, the source information of the duplicate connection request packets are the same as peer # 50, which is the source information of the connection request packet 502, and the destination information is a plurality of second peers ((peer # 2 505, peer # 3 507). Peer # 4 (509))). Peer # 1 503 may send duplicate connection request packets 504, 506, 508 to the plurality of second peers 505, 507, 509.

The plurality of second peers 505, 507, 509 that have received the duplicate connection request packets 504, 506, 508 receive the connection request according to the source information (eg, peer # 50) of the duplicate connection request packets. The response packets may be sent to peer # 50.

Since peer # 50 does not exist on the network, the access request response packets may be destroyed after a certain time according to the time to live (TTL). In this case, the TTL of each connection request response packet may be configured to automatically extinguish the packet to this value by designating the time that the packet is alive in order to prevent the packet from running for a long time on the network. The TTL defaults to, for example, 0xFF (255).

6 is a diagram illustrating a transmission of a plurality of duplicate connection request packets and a transmission process of an Ack packet corresponding thereto according to an embodiment. Referring to FIG. 6, peer # 10 (601) corresponding to a connection request (SYN) originator transmits consecutive connection request (SYN) packets 611 to peer # 1 (Peer # 1). The situation of attacking 602 and Peer # 50 606 is shown. At this time, the source information of the connection request (SYN) packets 611 is described as peer # 50 (606), not the peer # 10 (601), destination information is sent to the peer # 1 (602). It may be described.

Receiving connection request (SYN) packets 611 from peer # 10 601, peer # 1 602 duplicates the connection request packets 611 to send a plurality of duplicate connection request packets 612, 613, 614. ) Can be created. In this case, the source information of the replication connection request packets 612, 613, and 614 is the same as peer # 50 which is the source information of the connection request packet 611, and the destination information is a plurality of second peers (peer # 2 603). ), Peer # 3 604, peer # 4 605). Peer # 1 602 may send duplicate connection request packets 612, 613, 614 to the plurality of second peers 603, 604, 605.

The plurality of second peers 603, 604, and 605 that have received the duplicate connection request packets 612, 613, and 614 receive the duplicate connection according to the source information (eg, peer # 50) of the duplicate connection request packets. Request response packets (replicate SIN ACKs) may be sent to peer # 50 606.

Peer # 50 606 that has received the duplicate connection request response packets (replication SIN ACKs), for example, if it is determined that the received connection request response packets correspond to the previously transmitted connection request packet, it is necessary to establish a session. An ACK packet may be generated and transmitted. However, since peer # 50 606 has never transmitted a connection request packet, it may not generate and / or transmit an ACK packet.

7 is a block diagram of a communication device according to an embodiment. Referring to FIG. 7, a communication device 700 according to an embodiment may include a processor 710, a memory 730, and a communication interface 750. The processor 710, memory 730, and communication interface 750 may communicate with each other via a communication bus 705.

The processor 710 determines whether the connection request packet received through the communication interface 750 is original or duplicated. When it is determined that the connection request packet is the original, the processor 710 generates a plurality of duplicate connection request packets by duplicating the connection request packet. Program code executed by the processor 710 may be stored in the memory 730.

The memory 730 may be a volatile memory or a nonvolatile memory. The memory 730 may, for example, store instructions that, when executed by the processor 710, cause the processor 710 to execute any one or a combination of the processes described in connection with FIGS. 1 through 6. have.

The communication interface 750 receives a connection request packet from a neighboring peer to the first peer. The communication interface 750 also transmits duplicate connection request packets to the plurality of second peers.

In addition, the processor 710 may execute any one or a combination of the operations described with respect to the communication device 700 in FIGS.

Method according to an embodiment of the present invention can be implemented in the form of program instructions that can be executed by various computer means may be recorded on a computer readable medium. The computer readable medium may include program instructions, data files, data structures, etc. alone or in combination. The program instructions recorded on the media may be those specially designed and generated for the present invention, or they may be of the kind well-known and available to those having skill in the computer software arts. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tape, optical media such as CD-ROMs, DVDs, and magnetic disks, such as floppy disks. Magneto-optical media, and hardware devices specifically created to store and execute program instructions, such as ROM, RAM, flash memory, and the like. Examples of program instructions include not only machine code generated by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like. The hardware device described above may be created to operate as one or more software modules to perform the operations of the present invention, and vice versa.

As described above, the present invention has been described by way of limited embodiments and drawings, but the present invention is not limited to the above embodiments, and those skilled in the art to which the present invention pertains have various modifications and variations from these descriptions. Is possible. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the claims below, but also by those equivalent to the claims.

700: communication device
705: communication bus
710: processor
730: memory
750: communication interface

Claims (9)

A connection request (SYN) packet from a neighbor peer to a first peer-source information of the connection request packet corresponds to the neighbor peer, and destination information of the connection request packet is the first peer. Corresponding to the peer;
Determining whether the connection request packet is original or duplicated, based on whether the connection request packet was originally generated by the neighboring peer;
If it is determined that the access request packet is the original,
Changing source information from the first peer to correspond to the neighboring peer, and corresponding destination information to a plurality of second peers, thereby replicating the connection request packet;
Generating, by the copy, a plurality of duplicate connection request packets having source information such as source information of the connection request packet; And
Sending the duplicate connection request packets to the plurality of second peers.
Including,
If it is determined that the access request packet has been duplicated,
Generating a connection request response (SYN ACK) packet corresponding to the connection request packet; And
Transmitting the access request response packet to a neighboring peer corresponding to source information of the access request packet.
Including, communication method.
The method of claim 1,
Determining whether the access request packet is original or duplicated
Generating a first input vector based on the connection request packet;
Applying the first input vector to a first learned neural network;
Obtaining a first output vector generated by the first neural network; And
Determining whether the access request packet is original or duplicated based on the first output vector
Including,
An input layer of the first neural network corresponds to the first input vector,
The output layer of the first neural network corresponds to the first output vector,
The first neural network is trained based on a difference between labels defined based on determination results of whether the training connection request packets are original and training outputs corresponding to the training connection request packets.
Communication method.
The method of claim 2,
If the value corresponding to the first output vector corresponds to the original,
Generating the duplicate connection request packets
Generating a second input vector based on the first output vector corresponding to determining whether the access request packet is original or duplicated;
Applying the second input vector to a previously learned second neural network;
Obtaining a second output vector generated by the second neural network; And
Generating the duplicate connection request packets based on the second output vector
Including,
If a value corresponding to the first output vector corresponds to duplication,
Generating the access request response packet
Generating the second input vector based on the first output vector corresponding to determining whether the connection request packet is original or duplicated;
Applying the second input vector to the second neural network;
Obtaining the second output vector generated by the second neural network; And
Generating the connection request response packet based on the second output vector
Including,
Communication method.
delete The method of claim 1,
Determining whether the access request packet is original or duplicated
Determining whether the connection request packet is original or duplicated based on a flag of a specific bit included in a header of the connection request packet;
Including, communication method.
The method of claim 1,
Receiving connection request response packets from peripheral peers to the first peer;
Determining whether the received connection request response packets correspond to a connection request packet previously transmitted by the first peer;
Generating an ACK packet for establishing a session based on the determination result; And
Transmitting the Ack packet to a neighboring peer corresponding to the destination information of the previously transmitted connection request packet.
Further comprising, a communication method.
The method of claim 6,
Determining whether the access request response packets correspond to the previously transmitted access request packet
Determining whether the connection request response packets correspond to the previously transmitted connection request packet based on the sequence number of the previously transmitted connection request packet and the sequence numbers of the connection request response packets.
Including, communication method.
A computer program stored in a medium in combination with hardware to carry out the method of any one of claims 1 to 3 and 5 to 7.
A connection request packet from a neighbor peer to a first peer, wherein source information of the connection request packet corresponds to the neighbor peer, and destination information of the connection request packet corresponds to the first peer; A receiving communication interface; And
Determine whether the connection request packet is original or duplicated, based on whether the connection request packet was originally generated by the neighboring peer,
If it is determined that the access request packet is the original,
Change the source information from the first peer to correspond to the neighboring peer, the destination information to correspond to a plurality of second peers, duplicate the connection request packet,
Generating, by the copy, a plurality of duplicate connection request packets having source information such as source information of the connection request packet,
Send the duplicate connection request packets to the plurality of second peers,
If it is determined that the access request packet has been duplicated,
Generate a connection request response (SYN ACK) packet corresponding to the connection request packet;
A processor for transmitting the access request response packet to a neighboring peer corresponding to the source information of the access request packet
Containing
Communication device.

Images