[t3mp14rX]

Well I've spent about 7 hours tonight trying to see if this was possible, and I've come to the conclusion that is just isn't... as far as I know.

The personal and minilogon servers are made to work for a LAN setup, or a public setup. Not both at once.

Here's what I'm trying to set up:
My internet gateway hosting the Login server at ip 192.168.0.1.
My other machine hosting the database and worldzone servers at 192.168.0.2. Now i've tried hosting the worldzone servers on the main machine, and I'm still limited to either LAN or Public connections. The login server needs to be able to listen on 2 IPsInterfaces, and CORRECTLY send out the IP of which to connect to. The actual problem comes when, for example, my 192.168.0.1 machine is configured to advertise the server as being located at my ISP ip, (for example let's say) 123.60.123.60, so when I try to connect using my LAN machine at 192.168.0.2, EQ is told to try and connect to 123.60.123.60, yet it cannot, since that's on a different network. The same problem occurs in a vice-versa way, if I set my server's advertised IP as 192.168.0.1, then if someone on the internet tries to connect, they aren't able to since it's telling them to try and connect to 192.168.0.1 (which of course isn't accessible from the internet).

Is there ANY way for the devs to code this functionality into the login server, mini or public. I noticed they support a [LoginConfig] block with settings:
ServerMode=Standalone
ServerPort=5999
UplinkAddress=
UplinkPort=
UplinkAccount=
UplinkPassword=
Yet I have no clue if they are related and what they mean (besides port, and servermode).

By the way, the reason I'm even USING the publicmini login servers is because if I use the eqlogin.eqemu.net servers, they, once again, advertise the IP of my server as it's public IP (as specified in the worldaddress= setting), meaning connection from a lan machine isn't possible.

Also, it's 5am so try to bear with what I'm saying.

Thanks