[DiscordArchive] Yeah, the errors for empty tables, those are really just because there hasn't been data entered yet,
[DiscordArchive] Yeah, the errors for empty tables, those are really just because there hasn't been data entered yet,
Archived author: Zeraphicus • Posted: 2023-10-21T00:07:20.033000+00:00
Original source
Yeah, the errors for empty tables, those are really just because there hasn't been data entered yet, correct?
Archived author: substitute • Posted: 2023-10-21T00:36:30.146000+00:00
Original source
It’s a soft error
Archived author: substitute • Posted: 2023-10-21T00:37:03.280000+00:00
Original source
It would only really matter on super lightweight systems where process priority might actually make a big difference
Archived author: Zeraphicus • Posted: 2023-10-21T01:26:51.676000+00:00
Original source
Thank you, are you guys familiar with the realmlist addresses and external/internal setup? I had it working internally, trying to get it externally through my dynamic dns, not able to connect for some reason. From what I understand I need to set "address" to whatever means I want to connect. I've forwarded all 3 ports, let them through the local devices firewalls. "localaddress" was set to 127.0.0.1 and that was working with local ip for address to connect locally, but now I'm not even getting to the realm list while connecting externally, do I need to setup port triggering on my local network to the device running the wow client to go out then back in? lol
Archived author: Zeraphicus • Posted: 2023-10-21T01:27:30.032000+00:00
Original source
You'd think it wouldn't matter if you used the local ip as long as you came in on the correct port, but I guess this is a little more specific
Archived author: KJack • Posted: 2023-10-21T02:08:31.126000+00:00
Original source
It's not immediately obvious, but here's how that works.
`localAddress` is the local LAN IP. the way the auth server knows whether to hand the client this IP or not is by checking the `localSubnetMask`. If you know anything about networking, it's using this mask to determine how big the "LAN" is, so it knows which client IPs it should provide the LAN IP to.
So if I had a `localAddress` of `192.168.0.25` and a `localSubnetMask` of `255.255.0.0`, any client coming from an IP in the range `192.168.0.0 - 192.168.255.255` woud be given the `localAddress` to connect to.
As you may have guessed, anything OUTSIDE that range will get the `address` IP instead.
Side note: you may use DNS names for the `localAddress` and `address` fields, but they will be resolved by the server and not by the client. I personally use `whoami.akamai.net` for my `address` field, which will resolve to whatever public IP is being used to reach the Akamai DNS server.
Archived author: Zeraphicus • Posted: 2023-10-21T02:09:45.990000+00:00
Original source
Yeah I'm able to ping my DNS servers, who knows it might be working from the outside and that is why I am having issues is I need to use the local address to connect from this subnet
Archived author: Zeraphicus • Posted: 2023-10-21T02:10:23.693000+00:00
Original source
do you know if you need to restart the server when changing realmlist entries? It seems the "data" ie server entries update real time, not so sure about the main realmlist
Archived author: KJack • Posted: 2023-10-21T02:10:46.468000+00:00
Original source
your realmlist file is going to point to the auth server always, either the local IP or the internet ip depending on where you are. the table affects what the auth server tells your client about where the world (realm) server is.
Archived author: KJack • Posted: 2023-10-21T02:11:01.444000+00:00
Original source
i'm not sure on changes, i set it and forgot about it