CN112954063A - TFTP intranet penetration method and TFTP server - Google Patents
TFTP intranet penetration method and TFTP server Download PDFInfo
- Publication number
- CN112954063A CN112954063A CN202110210956.4A CN202110210956A CN112954063A CN 112954063 A CN112954063 A CN 112954063A CN 202110210956 A CN202110210956 A CN 202110210956A CN 112954063 A CN112954063 A CN 112954063A
- Authority
- CN
- China
- Prior art keywords
- client
- tftp
- target data
- context
- server
- 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
Links
Images
Classifications
-
- 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/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- 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/256—NAT traversal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
- H04L69/162—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields involving adaptations of sockets based mechanisms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2101/00—Indexing scheme associated with group H04L61/00
- H04L2101/60—Types of network addresses
- H04L2101/618—Details of network addresses
- H04L2101/663—Transport layer addresses, e.g. aspects of transmission control protocol [TCP] or user datagram protocol [UDP] ports
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention provides a TFTP intranet penetration method and a TFTP server, which are used for receiving a first downloading request sent by a TFTP client, wherein the first downloading request comprises a client context; and storing the first downloading request, obtaining first target data according to the client context, and returning the first target data through a single fixed server port bound with the TFTP client. The invention realizes the unique correspondence between the server port and the TFTP client by distributing the unique server port for each TFTP client, thereby accurately positioning the TFTP client and further realizing the intranet penetration.
Description
Technical Field
The invention relates to the field of network communication, in particular to a TFTP intranet penetration method and a TFTP server.
Background
The intranet is penetrated, that is, NAT is penetrated, and NAT (Network Address Translation) is used to translate an intranet Address and an intranet port number into a legal public Network Address and a legal public Network port number, establish a session, and implement communication with a public Network host.
The TFTP Protocol (simple File Transfer Protocol) is a simple Protocol for transferring files, and is implemented based on a UDP (User Datagram Protocol), but sometimes it cannot be determined whether some TFTP protocols are implemented based on other Transfer protocols, and the TFTP Protocol is designed for small File Transfer, so that it does not have many functions of a general FTP, and the TFTP Protocol can only obtain or write files from a File server, and cannot list directories, and does not perform authentication.
In the embedded device, TFTP is mostly based on UDP protocol communication, and the UDP protocol is connectionless, and when a port is monitored, all data can enter and exit from the port, as shown in fig. 8, the TFTP protocol adopts a mode of requesting a port + a random port to perform data transmission, when each client requests downloading, a port is randomly allocated to the client by the server, and then data transmission of the client and the server is performed at the random port; although the mode skillfully avoids the connectionless characteristic of the UDP protocol and allocates one port to each client, the communication can be carried out only in the intranet, and the intranet penetration cannot be realized.
In practice, the embedded device needs to transmit a cross-network segment file at the bootloader stage, and most bootloaders simply implement the programs of UDP protocol and TFTP protocol, so that it is necessary to configure port mapping in a router or adopt other text transmission protocols to implement cross-network segment transmission, the former can only be used for a small amount of devices with large limitation, and the latter has high development cost.
Disclosure of Invention
The technical problem to be solved by the invention is as follows: a TFTP intranet penetration method and a terminal are provided.
In order to solve the technical problems, the invention adopts a technical scheme that:
a TFTP intranet penetration method comprises the following steps:
s1, receiving a first downloading request sent by the TFTP client, wherein the first downloading request comprises a client context;
s2, storing the first download request, obtaining the first target data according to the client context, and returning the first target data through the single fixed server port bound with the TFTP client.
In order to solve the technical problem, the invention adopts another technical scheme as follows:
a TFTP server comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program:
s1, receiving a first downloading request sent by the TFTP client, wherein the first downloading request comprises a client context;
s2, storing the first download request, obtaining the first target data according to the client context, and returning the first target data through the single fixed server port bound with the TFTP client.
The invention has the beneficial effects that: when a first downloading request sent by a client is received, target data are returned according to the context of the client and the first downloading request is stored, an independent and fixed server port is independently allocated to the client, after the downloading request is subsequently received, the target data can be continuously returned according to the stored server port and the context of the client, the client can be accurately positioned according to the server port allocated to the client and the stored context of the client when an intranet penetrates, namely, the port is fixed when a UDP (user datagram protocol) and a TFTP (transport stream protocol) are used, the fixed port of a data receiving party of each data packet is determined, and accordingly, the intranet penetrates.
Drawings
Fig. 1 is a flowchart illustrating steps of a TFTP intranet penetration method according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a TFTP server according to an embodiment of the present invention;
fig. 3 is a schematic diagram of a UDP protocol interaction process according to an embodiment of the present invention;
fig. 4 is a schematic process diagram of a TFTP intranet penetration method according to an embodiment of the present invention;
fig. 5 is a schematic process diagram of a TFTP intranet penetration method implemented by a thread pool according to an embodiment of the present invention;
FIG. 6 is a diagram illustrating a process of transmitting data in a thread pool according to an embodiment of the present invention;
fig. 7 is a schematic diagram of a data communication process of a TFTP intranet penetration method according to an embodiment of the present invention;
FIG. 8 is a schematic diagram of a UDP protocol interaction process in the prior art;
description of reference numerals:
1. a TFTP server; 2. a processor; 3. a memory.
Detailed Description
In order to explain technical contents, achieved objects, and effects of the present invention in detail, the following description is made with reference to the accompanying drawings in combination with the embodiments.
Referring to fig. 1 and fig. 3 to 7, a TFTP intranet penetration method includes the steps of:
s1, receiving a first downloading request sent by the TFTP client, wherein the first downloading request comprises a client context;
s2, storing the first download request, obtaining the first target data according to the client context, and returning the first target data through the single fixed server port bound with the TFTP client.
From the above description, the beneficial effects of the present invention are: when a first downloading request sent by a client is received, target data are returned according to the context of the client and the first downloading request is stored, an independent and fixed server port is independently allocated to the client, after the downloading request is subsequently received, the target data can be continuously returned according to the stored server port and the context of the client, the client can be accurately positioned according to the server port allocated to the client and the stored context of the client when an intranet penetrates, namely, the port is fixed when a UDP (user datagram protocol) and a TFTP (transport stream protocol) are used, the fixed port of a data receiving party of each data packet is determined, and accordingly, the intranet penetrates.
Further, the S1 specifically includes:
receiving a first downloading request sent by a TFTP client, wherein the first downloading request comprises a client identifier and a client context;
after S2, the method further includes:
s3, receiving a non-primary download request sent by the TFTP client, wherein the non-primary download request comprises a first client identifier;
s4, acquiring a corresponding first client context according to the first client identifier;
s5, obtaining non-primary target data according to the first client context, and returning the non-primary target data through a single fixed server port bound with the TFTP client.
As can be seen from the above description, the non-initial download request includes a client identifier, a corresponding client context is obtained according to the client identifier, a corresponding client identifier is allocated to each client, the client identifier is carried when accessing the server, and the server can determine a server port to which the server is bound according to the client identifier, thereby implementing unique correspondence between the client and the port.
Further, the returning of the target data according to the client context in S2 is specifically that:
s21, adding the client context and the target data into a to-be-sent list and a thread pool queue;
s22, sending target data to the client according to the client context;
s23, deleting the client context and the target data in the list to be sent.
According to the above description, the client context and the target data are added to the to-be-sent list and the thread pool queue, and after the successful sending, the record is deleted in the to-be-sent list, so that the to-be-sent list can quickly acquire the current target data to be sent, and after the sending is completed, the data is deleted, so that the storage space is saved, and only the data to be sent is ensured to be listed in the to-be-sent list, thereby facilitating the understanding of the sending condition of the target data.
Further, the S1 is preceded by:
and creating a socket, and binding a client IP of the TFTP client and a server port number fixedly allocated to the TFTP client by using a UDP (user Datagram protocol), wherein the socket is used for carrying out interprocess communication with the client.
As can be seen from the above description, the interaction of data is started only after the binding between the port number of the service end and the client is realized based on the UDP protocol, and each client has a corresponding fixed port number, which is convenient for positioning different clients when the intranet penetrates through the network.
Further, the client identification representation comprises a client IP and a server port number.
As can be seen from the above description, the client IP and the service port number are directly used as the client identifier, the client carries the service port number and its own IP address during each access, and the server does not need to maintain the correspondence between the client and the service port number.
Referring to fig. 2, a TFTP server includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor executes the computer program to implement the following steps:
s1, receiving a first downloading request sent by the TFTP client, wherein the first downloading request comprises a client context;
s2, storing the first download request, obtaining the first target data according to the client context, and returning the first target data through the single fixed server port bound with the TFTP client.
From the above description, the beneficial effects of the present invention are: when a first downloading request sent by a client is received, target data are returned according to the context of the client and the first downloading request is stored, an independent and fixed server port is independently allocated to the client, after the downloading request is subsequently received, the target data can be continuously returned according to the stored server port and the context of the client, the client can be accurately positioned according to the server port allocated to the client and the stored context of the client when an intranet penetrates, namely, the port is fixed when a UDP (user datagram protocol) and a TFTP (transport stream protocol) are used, the fixed port of a data receiving party of each data packet is determined, and accordingly, the intranet penetrates.
Further, the S1 specifically includes:
receiving a first downloading request sent by a TFTP client, wherein the first downloading request comprises a client identifier and a client context;
after S2, the method further includes:
s3, receiving a non-primary download request sent by the TFTP client, wherein the non-primary download request comprises a first client identifier;
s4, acquiring a corresponding first client context according to the first client identifier;
s5, obtaining non-primary target data according to the first client context, and returning the non-primary target data through a single fixed server port bound with the TFTP client.
As can be seen from the above description, the non-initial download request includes a client identifier, a corresponding client context is obtained according to the client identifier, a corresponding client identifier is allocated to each client, the client identifier is carried when accessing the server, and the server can determine a server port to which the server is bound according to the client identifier, thereby implementing unique correspondence between the client and the port.
Further, the returning of the target data according to the client context in S2 is specifically that:
s21, adding the client context and the target data into a to-be-sent list and a thread pool queue;
s22, sending target data to the client according to the client context;
s23, deleting the client context and the target data in the list to be sent.
According to the above description, the client context and the target data are added to the to-be-sent list and the thread pool queue, and after the successful sending, the record is deleted in the to-be-sent list, so that the to-be-sent list can quickly acquire the current target data to be sent, and after the sending is completed, the data is deleted, so that the storage space is saved, and only the data to be sent is ensured to be listed in the to-be-sent list, thereby facilitating the understanding of the sending condition of the target data.
Further, the S1 is preceded by:
and creating a socket, and binding a client IP of the TFTP client and a server port number fixedly allocated to the TFTP client by using a UDP (user Datagram protocol), wherein the socket is used for carrying out interprocess communication with the client.
As can be seen from the above description, the interaction of data is started only after the binding between the port number of the service end and the client is realized based on the UDP protocol, and each client has a corresponding fixed port number, which is convenient for positioning different clients when the intranet penetrates through the network.
Further, the client identification representation comprises a client IP and a server port number.
As can be seen from the above description, the client IP and the service port number are directly used as the client identifier, the client carries the service port number and its own IP address during each access, and the server does not need to maintain the correspondence between the client and the service port number.
Referring to fig. 1, fig. 3, fig. 4 and fig. 7, a first embodiment of the present invention is:
a TFTP intranet penetration method comprises the following steps:
s1, creating a Socket (Socket), and binding a port required by the TFTP service by using a UDP protocol, wherein the data transmission of all TFTP clients passes through the port;
s2, receiving a first downloading request sent by the TFTP client, wherein the first downloading request comprises a client identifier and a client context; the client identification comprises a client IP and a server port number;
in an optional implementation manner, a first hash table is used, a key-value manner is adopted to store a first downloading request, specifically, a client identifier is used as a key value, and a client context is used as a value;
s3, storing the first downloading request, obtaining first target data according to the client context, and returning the first target data through a single fixed server port bound with the TFTP client;
s4, receiving a non-primary download request sent by the TFTP client, wherein the non-primary download request comprises a first client identifier;
s5, acquiring a corresponding first client context according to the first client identifier;
s6, obtaining non-primary target data according to the first client context, and returning the non-primary target data through a single fixed server port bound with the TFTP client; updating the first client context;
referring to fig. 3, 4 and 7, in an alternative embodiment, a TFTP client is allocated 69 ports with a service port number of 69; inquiring whether a socket corresponding to a server port number has a non-primary download request to be processed or not, if so, acquiring a client identifier (a client IP and the server port number) therein, acquiring a corresponding client context from a hash list, acquiring non-primary target data according to the client context, and returning the non-primary target data through a single fixed server port bound with a TFTP client;
if the socket does not contain the data packet to be processed, entering an inquiry overtime task to execute overtime judgment, if the preset time threshold is not exceeded, repeatedly executing the operation of inquiring whether the data packet to be processed is in the socket, and if the preset time threshold is exceeded, deleting the context of the client from the first hash table;
specifically, when the Socket is queried to have no data, the first hash table is traversed, the context of the client is read out, then the timestamp of the last received data packet in the context is compared with the current timestamp, and if the timestamp is overtime, the context of the client is deleted from the table;
the data packet comprises a non-first-time downloading request and a first-time downloading request;
in an alternative embodiment, the TFTP client is an embedded device.
Referring to fig. 5 and fig. 6, a second embodiment of the invention is:
a TFTP intranet penetration method, which is different from the first embodiment in that:
the S1 also comprises an initialization thread pool;
in S3, the returning of the target data according to the client context specifically includes:
s31, adding the client context and the target data into a to-be-sent list and a thread pool queue;
s32, sending target data to the client according to the client context;
s33, deleting the client context and the target data in the list to be sent;
the target data comprises first target data and non-first target data;
referring to fig. 5, a TFTP ue is allocated 69 ports with a service port number of 69; inquiring whether a socket corresponding to the server port number has a non-primary download request to be processed or not, if so, acquiring a client identifier (a client IP and the server port number) therein, acquiring a corresponding client context from a hash list, and acquiring non-primary target data according to the client context; adding the client context and the target data into a to-be-sent list and a thread pool queue; referring to fig. 6, when a thread pool task starts, processing non-primary target data of the current transmission according to a client context in the thread pool, and after the transmission is completed, deleting the client context and the non-primary target data from a to-be-sent list, wherein the to-be-sent list is a second hash table;
the progress information of the transmission file is stored in the client context, and the target data of the transmission can be obtained according to the progress information.
Referring to fig. 2, a third embodiment of the present invention is:
a TFTP server 1, comprising a processor 2, a memory 3, and a computer program stored in the memory 3 and operable on the processor 2, wherein the processor 2 implements the steps of the first embodiment or the second embodiment when executing the computer program.
In summary, the present invention provides a TFTP intranet penetration method and a TFTP server, which change the way that a traditional UDP protocol randomly allocates a server port number to a client for access, allocate a fixed and unique port number to different clients for access, when a TFTP client sends a download request to a TFTP server for the first time, send a client identifier including its own IP and the allocated server port number, and send its own client context, the TFTP server stores the correspondence between the client identifier and the client context, and by allocating a unique server port to each TFTP client, unique correspondence between the server port and the TFTP client is achieved, so that the TFTP client can be accurately located, and intranet penetration can be achieved; moreover, overtime judgment is added, if overtime happens, the binding corresponding relation between the port of the server and the TFTP client is removed, resource waste caused by long-time idle of the port of the server is avoided, and a thread pool mechanism is introduced, so that the parallel processing capacity of the server is further improved.
The above description is only an embodiment of the present invention, and not intended to limit the scope of the present invention, and all equivalent changes made by using the contents of the present specification and the drawings, or applied directly or indirectly to the related technical fields, are included in the scope of the present invention.
Claims (10)
1. A TFTP intranet penetration method is characterized by comprising the following steps:
s1, receiving a first downloading request sent by the TFTP client, wherein the first downloading request comprises a client context;
s2, storing the first download request, obtaining the first target data according to the client context, and returning the first target data through the single fixed server port bound with the TFTP client.
2. The TFTP intranet penetration method according to claim 1, wherein the S1 specifically is:
receiving a first downloading request sent by a TFTP client, wherein the first downloading request comprises a client identifier and a client context;
after S2, the method further includes:
s3, receiving a non-primary download request sent by the TFTP client, wherein the non-primary download request comprises a first client identifier;
s4, acquiring a corresponding first client context according to the first client identifier;
s5, obtaining non-primary target data according to the first client context, and returning the non-primary target data through a single fixed server port bound with the TFTP client.
3. The TFTP intranet penetration method according to claim 1, wherein the returning of the target data according to the client context in S2 specifically includes:
s21, adding the client context and the target data into a to-be-sent list and a thread pool queue;
s22, sending target data to the client according to the client context;
s23, deleting the client context and the target data in the list to be sent.
4. The TFTP intranet penetration method according to claim 1, wherein the step S1 is preceded by:
and creating a socket, and binding a client IP of the TFTP client and a server port number fixedly allocated to the TFTP client by using a UDP (user Datagram protocol), wherein the socket is used for carrying out interprocess communication with the client.
5. The TFTP intranet penetration method according to claim 2, wherein the client identifier representation comprises a client IP and a server port number.
6. A TFTP server comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor implements the following steps when executing the computer program:
s1, receiving a first downloading request sent by the TFTP client, wherein the first downloading request comprises a client context;
s2, storing the first download request, obtaining the first target data according to the client context, and returning the first target data through the single fixed server port bound with the TFTP client.
7. The TFTP server of claim 6, wherein the S1 specifically is:
receiving a first downloading request sent by a TFTP client, wherein the first downloading request comprises a client identifier and a client context;
after S2, the method further includes:
s3, receiving a non-primary download request sent by the TFTP client, wherein the non-primary download request comprises a first client identifier;
s4, acquiring a corresponding first client context according to the first client identifier;
s5, obtaining non-primary target data according to the first client context, and returning the non-primary target data through a single fixed server port bound with the TFTP client.
8. The TFTP server of claim 6, wherein the returning of the target data according to the client context in S2 is specifically:
s21, adding the client context and the target data into a to-be-sent list and a thread pool queue;
s22, sending target data to the client according to the client context;
s23, deleting the client context and the target data in the list to be sent.
9. The TFTP server of claim 6, wherein the S1 is preceded by:
and creating a socket, and binding a client IP of the TFTP client and a server port number fixedly allocated to the TFTP client by using a UDP (user Datagram protocol), wherein the socket is used for carrying out interprocess communication with the client.
10. The TFTP server of claim 7, wherein the client identity representation comprises a client IP and a server port number.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110210956.4A CN112954063A (en) | 2021-02-25 | 2021-02-25 | TFTP intranet penetration method and TFTP server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110210956.4A CN112954063A (en) | 2021-02-25 | 2021-02-25 | TFTP intranet penetration method and TFTP server |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112954063A true CN112954063A (en) | 2021-06-11 |
Family
ID=76246105
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110210956.4A Pending CN112954063A (en) | 2021-02-25 | 2021-02-25 | TFTP intranet penetration method and TFTP server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112954063A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150039676A1 (en) * | 2013-07-31 | 2015-02-05 | Microsoft Corporation | Messaging api over http protocol to establish context for data exchange |
| CN108737505A (en) * | 2018-04-27 | 2018-11-02 | 厦门理工学院 | A kind of method of resource downloading, system and terminal device |
| US20190273809A1 (en) * | 2016-06-24 | 2019-09-05 | Orange | Method for multi-path udp communication method between two terminals |
| CN112398847A (en) * | 2020-11-12 | 2021-02-23 | 华侨大学 | Intranet penetration method and system based on TCP Socket and improved heartbeat mechanism |
-
2021
- 2021-02-25 CN CN202110210956.4A patent/CN112954063A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150039676A1 (en) * | 2013-07-31 | 2015-02-05 | Microsoft Corporation | Messaging api over http protocol to establish context for data exchange |
| US20190273809A1 (en) * | 2016-06-24 | 2019-09-05 | Orange | Method for multi-path udp communication method between two terminals |
| CN108737505A (en) * | 2018-04-27 | 2018-11-02 | 厦门理工学院 | A kind of method of resource downloading, system and terminal device |
| CN112398847A (en) * | 2020-11-12 | 2021-02-23 | 华侨大学 | Intranet penetration method and system based on TCP Socket and improved heartbeat mechanism |
Non-Patent Citations (1)
| Title |
|---|
| 王鲁达;曾凡仔;张澎;唐日成;: "信息共享系统的防火墙穿透技术的研究与实现", 计算机工程与科学, no. 01 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20230336640A1 (en) | Methods and Systems for Caching Data Communications Over Computer Networks | |
| US8082290B2 (en) | Intelligent establishment of peer-to-peer communication | |
| CN109981803B (en) | Service request processing method and device | |
| WO2017054526A1 (en) | Arp entry generation method and device | |
| CN107613037B (en) | Domain name redirection method and system | |
| US8386614B2 (en) | Network connection manager | |
| CN113452686B (en) | Data processing method, data processing device, proxy server and storage medium | |
| WO2015062228A1 (en) | Method and device for accessing shared memory | |
| CN110995656B (en) | Load balancing method, device, equipment and storage medium | |
| CN109067936B (en) | Domain name resolution method and device | |
| US9894032B1 (en) | Method and apparatus of establishing a connection between devices using cached connection information | |
| KR20110036573A (en) | Providing access over an ip network to a server application program | |
| US20160099913A1 (en) | Internet Protocol (IP) Address Virtualization for Terminal Server Sessions | |
| EP4135296A1 (en) | Real-time communication (rtc) connection method, server, and storage medium | |
| CN112653740A (en) | Load balancing method and device supporting QUIC connection migration and computer product | |
| WO2014048746A1 (en) | Device, system and method for reducing attacks on dns | |
| KR20120132206A (en) | Server connectiong method, information providng method of device and device applying the same, Cloud Computing Network system and operation method thereof | |
| CN112929411A (en) | Distributed file transmission method, server and private cloud equipment | |
| CN112597039A (en) | Virtual machine access method, system, device and computer readable storage medium | |
| US11201915B1 (en) | Providing virtual server identity to nodes in a multitenant serverless execution service | |
| CN111901386B (en) | Method, system, equipment and readable storage medium for processing remote files | |
| US8972604B1 (en) | Network address retention and assignment | |
| CN112954063A (en) | TFTP intranet penetration method and TFTP server | |
| US10148613B2 (en) | Increased port address space | |
| CN102833287A (en) | Distributed file system and method for visiting data resource in distributed system |
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 |