0.5.7 Minilogin, and LS release - Page 2

Elkay · #16 09-17-2004, 02:22 AM

Crap!! So is the patch current at 9/6 too new or too old? I wasn't aware of a patch after 9/6 and before 9/14 and people said to just not update to 9/14. I can log into 5.8s fine just not my 5.7 since I need to use MiniLogin since I'm behind NAT.

daeken_bb · #17 09-17-2004, 02:36 AM

Too new. 5.8 clients are incompatible with 5.7.

**Doodman** · #18 09-17-2004, 05:16 AM

Quote:

Originally Posted by Melwin

Quote:

Originally Posted by daeken_bb

Very cool

Question, is the client-login protocol the same as the 5.8 clients?

No.

Well, that is not entirely true.

The protocol is the same. The main differences between a login server for 5.7 servers (pre-6/22 client) and login server for 5.7 server (6/22 or later clients) are some OP code changes and crypto on the loginrequest and loginresponse packets.

**Doodman** · #19 09-17-2004, 05:20 AM

Quote:

Originally Posted by Elkay

Crap!! So is the patch current at 9/6 too new or too old? I wasn't aware of a patch after 9/6 and before 9/14 and people said to just not update to 9/14.

Here is the run down:
5.7-DR6 is compatible with pre-6/22 client
5.8-DR1 is compatible with 6/22-9/13 client
5.8-DR2 (when complete) will be compatible with 9/14 client.

Between 5.7-DR6 and 5.8-DR1 (i.e. on 6/22) was when SoE put crypto back in to the login servers.

Quote:

Originally Posted by Elkay

I can log into 5.8s fine just not my 5.7 since I need to use MiniLogin since I'm behind NAT.

This issue of being behind a NAT and using a public login server is not an issue with the newly release loginserer with crypto: http://www.eqemulator.net/forums/viewtopic.php?t=17270

Elkay · #20 09-17-2004, 05:21 AM

Bleh. Looks like I won't be running a server again until Minilogin can get updated then since I just got back into the scene this past week and I'm behind a NAT and can't have both internal and external access to the server with an external login server. Thanks all for the info though.

**Doodman** · #21 09-17-2004, 05:25 AM

Bump, as you were posting I was editting my previous message.

Elkay · #22 09-17-2004, 05:27 AM

Hey doodman, sorry I posted right when you did. I am aware that the NAT problem is unrelated to the incompatibility with my client and 5.7DR6. My problem is the fact that I only have the most recent patch pre-9/14 and that I need to use Minilogin which is only compatible with 5.7DR6, not with 5.8. I'm basically stuck waiting for Minilogin to become compatible with 5.8 or later since I need to be able to connect from both inside and outside my NAT router.

Elkay · #23 09-17-2004, 05:27 AM

Quote:

Originally Posted by Doodman

Bump, as you were posting I was editting my previous message.

Touche :lol:

**Doodman** · #24 09-17-2004, 05:45 AM

Not true.

You can use an external login server with a server behind a NAT firewall. I do it all the time.

Elkay · #25 09-17-2004, 06:05 AM

Care to elaborate?

I spent waaaay too much time trying to find a way around it so that my internal computer that isn't the server would be forced out of the router and back in so that it appeared as the external address. I tried some advanced routing options with no success as I'm no networking expert and don't know how subnets work, etc. Additional equipment I have at my disposal if needed: a second router and an additional unused PC. Thanks for the help!

**Doodman** · #26 09-17-2004, 06:34 AM

You need to do the DNS trick.

So, say the DNS name of your -external- ip is elkay.homeip.net (or whatever your dns name is from your ISP) and your internal IP of your eqemu server is 192.168.1.100. Make sure that LoginServer.ini refers to your external DNS name as well as your boot5zones.bat, etc
LoginServer.ini

Code:

...
worldaddress=elkay.homeip.net
...

boot5zones.bat (or whatever)

Code:

zone.exe . elkay.homeip.net 7001 192.168.1.100

On the machine you play eq from, put a hosts file (\windows\system32\drivers\etc\hosts) entry that points that name to the internal IP address of your server.

Code:

192.168.1.100    elkay.homeip.net

After that you should be good to go.

Elkay · #27 09-17-2004, 06:43 AM

Hmm I think I did try just that, but I may have not quite got it right. I'll give it a shot again when I get home. Thanks!

Elkay · #28 09-17-2004, 09:19 AM

Just tried it. No dice. Settings:

worldaddress=aostang.dyndns.org

start zone . aostang.dyndns.org 8780 192.168.1.100

192.168.1.100 aostang.dyndns.org
192.168.1.101 aostang.dyndns.org

Tried interchanging and both entries in hosts on each machine and both machines, basically every combination. I'm still getting:

Zoneserver SetConnectInfo: 192.168.1.100:4555: aostang.dyndns.org:8780
176219 New client from ip: 192.168.1.101 port: 1076
Bad/expired session key: -1223839326
Removing client from ip:192.168.1.101 port:1076
252141 New client from ip: 192.168.1.101 port: 1089
Bad/expired session key: 1190736499
Removing client from ip:192.168.1.101 port:1089
263375 New client from ip: 192.168.1.101 port: 1092
Bad/expired session key: 188160628
Removing client from ip:192.168.1.101 port:1092
439469 New client from ip: 192.168.1.101 port: 1096
Bad/expired session key: 1098584789
Removing client from ip:192.168.1.101 port:1096

Not sure what to do at this point other than wait for Minilogin to get an update. :(

**Doodman** · #29 09-17-2004, 09:49 AM

Oh, you'll need to pull the new CVS dump (when it gets out) and use the login server at 5994 instead. (see my link posted earlier)

That is the IP/auth work around to the random account bug.. Now that crypto is broken, we don't need it.

After that, you'll work okay.

Cutter · #30 09-17-2004, 10:11 AM

what about the problem i am having.. can get to server select screen.. then it just puts me back to login.. after i try to enter world.. everything else works fine.. oh and i have the client compatable with 5.7DR6 .. cause i have played on scorps server and I run a test server as well.. so i know im all good there..