This tutorial is for:
Inside intranet using public addresses to access the network server.
Bit of a mouthful, Popular, is eaten with a public IP network can be both inside and outside China Netcom, without a network and external network of a record.
Port reflux, the scientific name Hairpin NAT. The name suggests, is the same hairpin NAT, when we use the public computer network address to access the web server, router immediately changed hands to help us back to the server, will not have to go public.
Benefits are: like this will not be subject to public network bandwidth limitations, we do not remember too much access.
However, in some next-generation firewalls, DNS-Mapping may be used in this way, RouterOS naturally can. But as a router, we will speak about IP-level approach. it's actually really easy:
1. Add new rule
Action is set to Masquerade (camouflage)
Results show:
2. The principle is shown:
When 192.168.11.251 access the public network 100.1.1.121 port 8888, the router help our 192.168.11.252 disguised as public address 100.1.1.121:8888 reply to us. The premise is that we must have a third route rules before they can successfully disguise, after all ports reflux depends on the port mapping .
These are the ports reflux practice, whether inside or outside the mesh network, we only need to remember a public address on universal access.