Grey pigeon online principle (flow chart)
The flow chart is as follows
Draw only the schematic diagram; (I hope you will take a closer look at this picture)
② of main control terminal-→ pigeon
① ③
| | |
| | |
↓ ↓
IP informs ←-④ broilers
⑤-→
Take a look at the intranet line below:
┏━┓ ┏━━┓
┃ IP Notification (IP.txt file or domain name of IP) ┃ ←-┃ broiler ┃
┗━┛ looks for the IP address of the main control terminal ┗━━┛
| | IP notification file points to
| | IP in your IP file |
| | or your domain name office |
The IP parsed by ↓.
┏━┓
┃ public network IP (usually ICS host or routing) * ┃
┗━┛, and this is where the problem lies.
↓ public network IP does not know which machine to notify to go online
┏━━━┓, this is why there is no independent public network IP machine.
┃ workstation ┃
The reason why ┗━━━┛ can't go online automatically for broilers.
One of the workstations is the machine where your master terminal is located.
* ⑴ ICS is the abbreviation of Internet connection sharing (Internet Connection Sharing)
Now let's talk about why this problem can be solved by mapping, as shown in the figure (the one with the * sign is explained at the end of the figure):
┏ ━ ← ━┓
↓ ↑
┏━┓ ① broiler will take the initiative to connect to ┏━━┓ when it is turned on.
┃ mapping machine, Avu 8000 * ┃→┓ ┃ broiler ┃
Port 8000 ┗━━┛ of IP in ┗━┛ ┃ configuration
| | ↓ |
↓
┃ ② uses mapping to map 8000 of the machine.
┏━┓
┃ public network IP (usually ICS* hosts or routes and the like) ┃ ↓ ports are mapped to the local machine to achieve broiler
┗━┛
┃ is directly connected to port 8000 of this machine, from the
↓ ↓
↓ to achieve the purpose of automatic online broiler.
┏━━━┓
┃ workstation ┃←┛
┗━━━┛
Suppose the last workstation is the machine you use, ↑
* ⑵ assumes that the location notified by IP is configured with an IP address of A, and 8000 is the default port used by the Grey Pigeon connection.
-understand the principle, but are you afraid that the gray pigeons will not be able to go online?
