[DiscordArchive] Is `8085` the world server? Or `86`?
[DiscordArchive] Is `8085` the world server? Or `86`?
Original source
Is `8085` the world server? Or `86`?
rektbyfaith
10-04-2023, 03:47 AM #1Archived author: Michael Crilly • Posted: 2023-10-04T03:47:07.780000+00:00
Original source
Is `8085` the world server? Or `86`?
Original source
85 by default
rektbyfaith
10-04-2023, 03:50 AM #2Archived author: Bench • Posted: 2023-10-04T03:50:41.244000+00:00
Original source
85 by default
Original source
I've been meaning to do this diagram for a while. Does this help?
A. Your local WoW client makes a connection to the Auth Server;
B. The Auth Server knows that your internal IP is in the same subnet mask;
C. So it returns the `localAddress` from the `realmlist` database table;
D. Then your WoW client connects to the World Server ("realm") on the `localAddress` it was given.
It's more complicated with an external client due to the networking involved in the middle, but...
1. Your external/remote WoW client makes a connection to your public IP address;
2. Your router listens on port `8086` for the inbound connection;
3. It NATs/forwards the connection to the _internal_ IP address of the Auth Server, on the same port (it can be different);
4. The Auth Server knows your _external_ IP is __not__ on the LAN, so it returns the `address` value from the `realmlist` table;
5. Your WoW client receives the IP from the `address` column and then connects to the World Server ("realm") on that IP address;
6. because you're also hosting the World Server _inside_ your LAN, the connection once again comes into your public IP, this time on port `8085`;
7. The router foes a NAT/forward of the connection to the _internal_ IP of the World Server.
And just like that, the external client is connected.
![[Image: image.png?ex=690c2075&is=690acef5&hm=b4b...19acd6c77&]](https://cdn.discordapp.com/attachments/284406375495368704/1158980236625596476/image.png?ex=690c2075&is=690acef5&hm=b4bb5f2ae0f01f0ce3d9d49e60e7388fdb081e90d97bf787876b57219acd6c77&)
rektbyfaith
10-04-2023, 04:13 AM #3Archived author: Michael Crilly • Posted: 2023-10-04T04:13:41.270000+00:00
Original source
I've been meaning to do this diagram for a while. Does this help?
A. Your local WoW client makes a connection to the Auth Server;
B. The Auth Server knows that your internal IP is in the same subnet mask;
C. So it returns the `localAddress` from the `realmlist` database table;
D. Then your WoW client connects to the World Server ("realm") on the `localAddress` it was given.
It's more complicated with an external client due to the networking involved in the middle, but...
1. Your external/remote WoW client makes a connection to your public IP address;
2. Your router listens on port `8086` for the inbound connection;
3. It NATs/forwards the connection to the _internal_ IP address of the Auth Server, on the same port (it can be different);
4. The Auth Server knows your _external_ IP is __not__ on the LAN, so it returns the `address` value from the `realmlist` table;
5. Your WoW client receives the IP from the `address` column and then connects to the World Server ("realm") on that IP address;
6. because you're also hosting the World Server _inside_ your LAN, the connection once again comes into your public IP, this time on port `8085`;
7. The router foes a NAT/forward of the connection to the _internal_ IP of the World Server.
And just like that, the external client is connected.
Original source
It also depends on your router. I have address and localAddress set to my public ip because my router supports nat loopback/hairpinning so the authserver doesn't have to care about where to send me nor does it need to determine if I'm local or not because that's handled by the router. I have yet to personally encounter a router that doesn't support that so it always seem to surprise me when one doesn't.
rektbyfaith
10-04-2023, 05:23 AM #4Archived author: Revision • Posted: 2023-10-04T05:23:25.278000+00:00
Original source
It also depends on your router. I have address and localAddress set to my public ip because my router supports nat loopback/hairpinning so the authserver doesn't have to care about where to send me nor does it need to determine if I'm local or not because that's handled by the router. I have yet to personally encounter a router that doesn't support that so it always seem to surprise me when one doesn't.
Original source
Aye. I could cover other use cases with different diagrams. I think the one I've outlined above is the most common.
rektbyfaith
10-04-2023, 05:25 AM #5Archived author: Michael Crilly • Posted: 2023-10-04T05:25:13.003000+00:00
Original source
Aye. I could cover other use cases with different diagrams. I think the one I've outlined above is the most common.
Original source
And it's more aimed at explaining what the `localAddress` and `localSubnetMask` columns are for.
rektbyfaith
10-04-2023, 05:25 AM #6Archived author: Michael Crilly • Posted: 2023-10-04T05:25:33.583000+00:00
Original source
And it's more aimed at explaining what the `localAddress` and `localSubnetMask` columns are for.
1 Guest(s)
1 Guest(s)