Mobile (applications) on the gre tunnel:
NAT server global 172.16.0.1 inside 192.168.4.7
Telecom (application with different mobile network port) :
NAT server global 172.16.0.1 inside 192.168.4.7
Traffic are from outside the network into the actual found two NAT network has the transformation, but the export of mobile TCP session cannot be established, further caught and NAT debug found back pack is not of the export of mobile address translation (i.e., no 192.168.4.7 -> 172.16.0.1 records), is still within the web address, when source address does not match the network TCP handshake are unable to connect to the export of telecom and NAT is not the problem, normal is likely to be caught and NAT denug leads to move back to the package of the NAT translation in which failure?
CodePudding user response:
To achieve 192.168.4.7 -> 172.16.0.1 also NAT, light has NAT server is not enough, also use NAT outbound, 172.16.0.1 where this address is? The topology posted to see,CodePudding user response:
192.168.4.7 the export of this server is the only, you this is a typical multiple wire release scenario,https://mp.weixin.qq.com/s/Pp5z5WqnzYlFOL9bb4yA2g server network selection and multi-line access configuration