You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not a bug but couldn't find a better place to put it.
Issue
When running the Server on the same local subnet as the client and trying to host a public server there is a nat port issue when using an IP for the realmlist entry in the DB vs a URL.
Example:
Public IP
Router IP
Private IP
Local Client 1 -> Public IP:8085-> Nat Router IP:8085 -> Private IP:8085
Local Client 2 -> Public IP:8085 -> Nat Router IP:8085 -> Private IP:8085 (Client 2 Can't connect due to it being on the same port for the NAT)
Workaround:
External DNS and Internal DNS resolution
Requires a Domain or stub domain like azerothcore.mydomain.com
External DNS points to Public IP
azerothcore.mydomain.com -> 55.555.555.55 (Public IP were hosted)
Internal DNS points to Private IP (Use the host file if you can't set local URL resolution)
azerothcore.mydomain.com -> 192.168.X.X (Private IP were hosted)
Realm DB
update realmlist set address = 'azerothcore.mydomain.com' where id=1;
To reproduce
Host a public server with a PNAT configuration
Have an external client join
try to have two internal clients join.
Expected behavior
None, this is a networking issue for internal and externally hosted servers which required a redirect to a separate resource.
Screenshots
No response
Desktop
Any / NA
Smartphone
N/A
Additional context
Not a bug, just a recommendation for a wiki update as a warning during install.
The text was updated successfully, but these errors were encountered:
If it is not a bug, next time you can use the Feature request template. Or if you need another template, because it does not match what you want to describe, you can create another template. Anyway, later, I will analyze what you are mentioning here, because now I am on my cell phone, and I can't read it well. Thank you.
@XSNomad still among us to tell me if this "issue" still exists? If yes and can you reproduce it could make a quick video demonstrating what the issue is.
Describe the bug
Not a bug but couldn't find a better place to put it.
Issue
When running the Server on the same local subnet as the client and trying to host a public server there is a nat port issue when using an IP for the realmlist entry in the DB vs a URL.
Example:
Public IP
Router IP
Private IP
Local Client 1 -> Public IP:8085-> Nat Router IP:8085 -> Private IP:8085
Local Client 2 -> Public IP:8085 -> Nat Router IP:8085 -> Private IP:8085 (Client 2 Can't connect due to it being on the same port for the NAT)
Workaround:
External DNS and Internal DNS resolution
Requires a Domain or stub domain like azerothcore.mydomain.com
External DNS points to Public IP
Internal DNS points to Private IP (Use the host file if you can't set local URL resolution)
Realm DB
To reproduce
Host a public server with a PNAT configuration
Have an external client join
try to have two internal clients join.
Expected behavior
None, this is a networking issue for internal and externally hosted servers which required a redirect to a separate resource.
Screenshots
No response
Desktop
Any / NA
Smartphone
N/A
Additional context
Not a bug, just a recommendation for a wiki update as a warning during install.
The text was updated successfully, but these errors were encountered: