Personal\Mini Login Server Restrictions

t3mp14rX · #1 05-03-2002, 09:58 PM

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

Darkman · #2 05-03-2002, 11:09 PM

Simple to fix.

Set up the servers as if you were making a "public" server. Then, set up your eqhost.txt file to point to the "public" IP(s) of your server.

Unless you have a screwy routing table (ie: not the default one NT gives ya), you'll be able to connect to your EQEmu server from the Internet or LAN (or both) with ease.

Lurker_005 · #3 05-04-2002, 04:06 AM

Also delete the [loginconfig] section. It isn't needed, and I think it screws things up.

I am still trying to figure out where that section is comming from. If you can point me to the place you got it, an attempt to clear things up can be made.

tcsmyworld · #4 05-04-2002, 05:27 AM

I have the same problem, running smal LAN with hub, no router (modem to access i-net, in server machine).
Can't log into server at all if I set it up for local and am online.
It trys to connect thru the internet ip address, while the machines try to use the local ip.
If i shut down i-net connection it works fine.
Would be nice if I could set it up to work while online, and be able to login with both machines.

tygrmouse · #5 10-18-2003, 07:24 AM

If I'm not mistaken, if I've read this right, I've seen people saying that "I don't know where this is coming from" ...

[LoginConfig]
ServerMode=Standalone
ServerPort=5999
UplinkAddress=
UplinkPort=
UplinkAccount=
UplinkPassword=

ok ... I just downloaded 4.4, I just went through your message boards, and you have included that in the Loginserver.ini on your release through sourceforge at the NC mirror. That is one place it comes from. Also, you have about 20% of the posts (that mention it) in the forum saying it's needed. Not being smart, trying not to be rude, but to answer your question, it's coming from all over the place.

The problems I'm having are definitely version problems, but I don't think it's the software, it's a total inconsistancy within the forums. Now, I've seen and followed alot of these walkthroughs, and I think you guys are doing a beautiful job, and I know this is still alpha and changes everyday, but there really needs to be a current document that addresses issues and limitations of the software. I've spent 30 something hours hashing through this forum, and I know you can't control where people post and where the walkthrough instructions end up.

So anyway, this is totally unrelated to this thread, exept it answers your question. I don't mean to be rude, and I certainly don't mean to discourage anyone, I think this project is a wonderful thing ... but I'm fighting bug after bug and trying everything and I am a computer user and the server doesn't give me errors but I can't see it on the list and I find out the minilogon is a one player deal and I have programmed professionally and I know it's not just me and if you would like I can help you organise some of your bug tracking when I can find the time. Alot of these bugs are inconsistancy and disarray of organisation in the instructions. You guys are programmers and don't have time,I know this, maybe if all the walkthroughs and all the bug fixes were organised in a way that a person doesn't have to read the entire forum ...

grrr, don't mind me, I'm a 'noob' that changes diapers from day to day, maybe just getting old.
:evil:

Lurker_005 · #6 10-21-2003, 04:23 PM

tygrmouse: While I am glad to see someone uses search, at least I am guessing that is how you came to read this thread... the last post was 17 months ago. As such it must relate to EQEmu 3.1.1 NOT 4.4 Things were moving a lot faster back then, less trouble with changes on live! I think the last 10 months have been spent mostly on getting/keeping the emulator working with the current live client.

Speeking of which, you problem is probley due to patching. 4.4 only works with EQ files patched months ago. the 5.0 DR server only works with files patched up to Oct 9th per the news forum.

mollymillions · #7 10-22-2003, 03:05 AM

Quote:

Originally Posted by tcsmyworld

Can't log into server at all if I set it up for local and am online. It trys to connect thru the internet ip address, while the machines try to use the local ip.
If i shut down i-net connection it works fine.
Would be nice if I could set it up to work while online, and be able to login with both machines.

I use the computername instead of its IP address in Boot5Zones.bat and EQHosts.txt files to get around this problem.