Answer the question
In order to leave comments, you need to log in
Why is the game server (program) given the local ip of the router instead of the external ip?
Given: Game server and main server (programs). Both are on the same iron server.
LAN IP: 192.168.6.114
Router
WAN IP: xxx.xxx.xxx.xxx
LAN
IP: 192.168.6.14
using external ip. Previously, on the standard firmware of the TL-WR1043ND router, the main server caught the game connection from an external ip and, therefore, transmitted a normal white ip to all Internet clients, through which they connected to the game server.
After changing the firmware on the router to Gargoyle 1.7.1 (similar to OpenWRT), now the game server connects to the main one and in the logs I no longer see the external address of the router, but its local 192.168.6.14.
How to fix the situation?
ps. I suspect that the case is hidden somewhere here
Chain zone_lan_postrouting (1 references)
pkts bytes target prot opt in out source destination
150 14805 postrouting_lan_rule all -- any any anywhere anywhere /* user chain for postrouting */
0 0 SNAT tcp -- * * 192.168.6.0/24 192.168.6.114 tcp dpts:29339:30000 /* lfsp (reflection) */ to:192.168.6.14
0 0 SNAT udp -- * * 192.168.6.0/24 192.168.6.114 udp dpts:29339:30000 /* lfsp (reflection) */ to:192.168.6.14
Answer the question
In order to leave comments, you need to log in
In the end, something else went wrong even after rebooting the router, deleting the previous entry
and adding a new
earned.
Yes, it seems that this is the result of precisely these rules. What you want is called "hairpin nat", look for how it is done on this firmware.
well, so you have written "to: 192.168.6.14" - addresses from 192.168.6.0/24 going to 192.168.6.114 are translated to 192.168.6.14.
complete nonsense, but such is your translation rule.
habrahabr.ru/sandbox/18975 - well written what to do
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question