0.5.7 Minilogin, and LS release

[smogo]

Lot'sa people talking about LS and the stuff ... i've been working on a LS / minilogin for a while, so here it is. Many thanks to those who helped, both with information, sidework, and testing.


In the package you get source for both minilogin and regular login. Both should work on any network. Regular login would not work on Windows machines, as far as i tried.

It's designed for 0.5.7dr6 version. It could work with earlier versions too, though i did not test them. It requires some code changes to go with 0.5.8. Maybe i'll work on this, maybe not. So atm if you want so, start digging the code and just do it yourself.

In the package is a README file. You will read it, as it will avoid you 90% of troubles you could get in. The remaining 10% ... you're sol.

This is alpha developer release. No support

get it here (http://perso.wanadoo.fr/afou/khalzed-dur/download/minilogin.zip)

Have fun ;)

[govtcheeze]

smogo, you complete me

/em races off to try this

[daeken_bb]

Very cool :)

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

[smogo]

Forgot to add (and did not include in the zip)
Regular version requires database with the followin tables :

-- MySQL dump 9.08
--
-- Host: localhost Database: login
---------------------------------------------------------
-- Server version 4.0.15a

--
-- Table structure for table 'lslogin'
--

CREATE TABLE lslogin (
id int(11) NOT NULL default '0',
login varchar(30) default NULL,
passwd varchar(30) default NULL,
status tinyint(4) default '0'
) TYPE=MyISAM;

--
-- Table structure for table 'lsservers'
--

CREATE TABLE lsservers (
socket tinyblob NOT NULL,
category tinyint(4) NOT NULL default '0',
alive datetime NOT NULL default '0000-00-00 00:00:00',
handle varchar(100) NOT NULL default '',
status int(11) NOT NULL default '0',
zones int(11) NOT NULL default '0',
clients int(11) NOT NULL default '0',
url varchar(201) NOT NULL default '',
name varchar(250) NOT NULL default '',
version varchar(100) NOT NULL default '',
protocol varchar(100) NOT NULL default '',
type int(11) NOT NULL default '0',
account varchar(100) default '',
passwd varchar(15) default ''
) TYPE=MyISAM;



i strongly reocmmend you experiment with minilogin first, though ;)

[Melwin]

Very cool :)

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

No.

[Cisyouc]

Im not able to run ls.pl. Every time I install a new module it says it requires I get a new one it needs.

[Elkay]

Hey,

I am trying to use minilogin and I am getting the following error when I click login from the login screen:

-------------------------------

-->incoming
Client 192.168.1.1:1079 sent 14 bytes, message type : 0x01 retry count : 0x00
00 01 00 00 00 02 00 29 48 23 00 00 02 00
new client, sending reply to 192.168.1.1:1079
key is : 192.168.1.1:1079

-->incoming
Client 192.168.1.1:1079 sent 18 bytes, message type : 0x09 retry count : 0x00
00 09 00 00 01 00 01 00 00 00 00 00 00 00 00 00 04 00
opcode 1 , sequence id 0
key is : 192.168.1.1:1079

-->incoming
Client 192.168.1.1:1079 sent 4 bytes, message type : 0x15 retry count : 0x00
00 15 00 00
message type 0x15, packet # 0 received and acknowledged by client
key : 127.0.0.1:1470
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 1
key is : 192.168.1.1:1079

-->incoming
Use of uninitialized value in printf at client.pl line 60.
Client 192.168.1.1:1079 sent 2 bytes, message type : 0x06 retry count : 0x00
00 06
Attention !! unexpected packet
key : 127.0.0.1:1470
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 1
currently on :
server from 127.0.0.1:1470 : Elite Corral
client from 192.168.1.1:1079
key is : 192.168.1.1:1079

-----------------------------------

This keeps repeating until I close everything down, and the client freezes at connecting to login server until I terminate the process. I'm using the client that was live as of 9/6/04 (definitely pre-9/14). Any ideas? TIA.

[giulietta]

I can load mini-login
I can load world.exe
I can load 5 zones

all work perfect before client launch

I know my eqhost.txt is correctly labelled

that being said I will post anything needed to confirm or not confirm my problem as the case might be but this is what I thought helpfull right away... text from loginserver on client attempt

reading : 127.0.0.1 testing testing
setting 0 to id 591, testing / testing
udp server listening on port : 5996
tcp server listening on port : 5996
now to work ...
currently on :
new incomming server ...
key : 127.0.0.1:1663
key : 127.0.0.1:1663
opcode : 4096, length : 607
World protocol : 0.3.10
World version : 0.5.7-DR6
World account :
World name : dukemiesters
World key : 127.0.0.1:1663
World passwd :
World url : 127.0.0.1
World type : 0
World category : 34
key : 127.0.0.1:1663
opcode : 4097, length : 16
Status : -2, Clients 0, Zones 0
key : 127.0.0.1:1663
opcode : 4097, length : 16
Status : -2, Clients 0, Zones 0
currently on :
server from 127.0.0.1:1663 : dukemiesters
key : 127.0.0.1:1663
opcode : 4097, length : 16
Status : -2, Clients 0, Zones 0
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x00
32 00 00 00 4c 2d 01 00 59 00 1d ffffff82 ffffff9a ffffffa9
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x01
32 00 00 01 4c 2d 01 00 59 00 ffffffbb fffffff5 ffffff91 1d
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x02
32 00 00 02 4c 2d 01 00 59 00 ffffff8a 1d ffffff8b ffffff80
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x03
32 00 00 03 4c 2d 01 00 59 00 2c 6a ffffff80 34
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x04
32 00 00 04 4c 2d 01 00 59 00 ffffffe9 ffffffcd ffffffbe ffffffba
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x05
32 00 00 05 4c 2d 01 00 59 00 4f ffffffba ffffffb5 0e
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x06
32 00 00 06 4c 2d 01 00 59 00 7e 52 ffffffaf ffffff93
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x07
32 00 00 07 4c 2d 01 00 59 00 ffffffd8 25 ffffffa4 27
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x08
32 00 00 08 4c 2d 01 00 59 00 2e 6d ffffffd4 ffffffce
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x09
32 00 00 09 4c 2d 01 00 59 00 ffffff88 1a ffffffdf 7a
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x0a
32 00 00 0a 4c 2d 01 00 59 00 ffffffb9 fffffff2 ffffffc5 ffffffe7
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x0b
32 00 00 0b 4c 2d 01 00 59 00 1f ffffff85 ffffffce 53
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x0c
32 00 00 0c 4c 2d 01 00 59 00 ffffffda 22 fffffff0 ffffffdd
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x0d
32 00 00 0d 4c 2d 01 00 59 00 7c 55 fffffffb 69
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x0e
32 00 00 0e 4c 2d 01 00 59 00 4d ffffffbd ffffffe1 fffffff4
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x0f
32 00 00 0f 4c 2d 01 00 59 00 ffffffeb ffffffca ffffffea 40
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x10
32 00 00 10 4c 2d 01 00 59 00 7a 5c 06 67
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x11
32 00 00 11 4c 2d 01 00 59 00 ffffffdc 2b 0d ffffffd3
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x12
32 00 00 12 4c 2d 01 00 59 00 ffffffed ffffffc3 17 4e
Attention !! unexpected packet
key is : 127.0.0.1:1669

-->incoming
Client 127.0.0.1:1669 sent 14 bytes, message type : 0x00 retry count : 0x13
32 00 00 13 4c 2d 01 00 59 00 4b ffffffb4 1c fffffffa
Attention !! unexpected packet
key : 127.0.0.1:1663
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 5
currently on :
server from 127.0.0.1:1663 : dukemiesters
key : 127.0.0.1:1663
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 5


please assist

[daeken_bb]

Are you sure you're using the proper client revision?

[Cutter]

ok, i am using 5.7dr6
and using a client that logs into eqemu servers when i am online..

i tried minilogin.. and works great .. i login..
using dave davespassword

get to the part where you select a server..

see my server..
then the comes the part where it starts to load graphics blah blah..

well it dont get to that part.. and just goes back to login screen

btw what should my eqhost.txt say now?

im excited about using this... cause i was probably one of the lots thats been crying about it.. btw thank you so much

[Elkay]

Yes I get to server select just fine with eqemu loginserver.

[Cutter]

yes, i do also
so, waiting on response.. i know it works ... just gotta figure out what im doing wrong

[Elkay]

Also a quick FYI.. my patch date is around 9/6/04, definitely pre-9/14 but not sure if there was any other patching in between those dates.

[Cutter]

I dont think so... i read the readme file and the person he was talking to seemed to log right in no problem..

[killspree]

9/6/2004 date of live patch does NOT work with 5.7dr6, that's your problem if you're experiencing any with this minilogin, most likely.

[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. 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]

Too new. 5.8 clients are incompatible with 5.7.

[Doodman]

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]

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.

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]

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]

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

[Elkay]

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]

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

Touche :lol:

[Doodman]

Not true.

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

[Elkay]

Care to elaborate? :D 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]

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...
worldaddress=elkay.homeip.net
...
boot5zones.bat (or whatever)

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.
192.168.1.100 elkay.homeip.net

After that you should be good to go.

[Elkay]

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]

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]

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]

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..

[Elkay]

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.

Awesome, thanks for the info. :D

[giulietta]

Guess I do have the 5.8 client although I dont remember patchign up to i t. Oh well I guess I just have to wait for the mini login update......

/fish

/fish

/drink

/fish.....

[KhaN]

Oh well I guess I just have to wait for the mini login update......

Wont happen tomorrow, this LS is the result of Smogo work for "World of Alkora" LS, and he decided to make it public so it would maybe be the start of an opensource LS.

We could spent time like Doodman did to break crypto to release a 5.8/live version of the LS, but we have other priorities on our task list and also because "World of Alkora" use 5.7 client, and we dont intend to be live compatible during the development phase, so i dont think LS live version will be made for the next months, since our first objective for the LS is attained, aka make a LS allowing peoples to login.

We are actually fixing some minor bugs, moving LS to C++. From time to time, new version will be posted, since we really want it to be opensource.

This LS instead EQEmu LS is intend to be opensource, but as its only a small part of the "World of Alkora" project, we cant fully work on it, if any of you made fix, made a live version, i would suggest to post them here, or PM smogo, and it will be added to the next versions.

[Elkay]

Thanks for the update, will just have to be patient and wait as usual hehe.

[giulietta]

Thanks for the update...

Guess I will byte the bullet and learn the one area of computers I swore I would never learn in detail.. programming.

Take me a couple months to bring my basic skills up to speed and then I'll try to contribute back to this community.

P.s. Any needs in any Networking areas...software....permissions etc I can assist in almost all with mroe than 10 years exp...just swore I would let others do the zeros and ones thing until now :)

[daeken_bb]

I think the problem here is the same as why we aren't including official LS support in OpenEQ... the crypto is DES-derived and depends on the key and algo being hidden to protect the data. If the algorithm gets out, it's no stronger than plaintext. I'd really like to work with you to get this to support OpenEQ clients when the time comes... we plan on using SSL, so there's no problem with opening the source as long as we don't distribute private keys to people hehe.

[giulietta]

Thought... would it be possible to re-encrypt after decryption?

I am assuming the eq client uses DES so we need to do the same to get communication back and forth... but once the DES is recieved by Login-server can we not re-encrypt? differently and then put back to DES on the return signal to client?


I know there are encryption algorithms like .net ones that take variable information as part of the key based on computer settings from clients machine which make knowing the algorithm itself useless to people because they would also need information about the clients machien such as computer name or the like.

[daeken_bb]

We don't have a whole lot of room to move though while keeping compatibility with the official client. you either use the crypto or you don't... can't change what the crypto is or how it's used, really.

[tcsmyworld]

..

[KhaN]

Daeken_bb, i would be for an MD5 encryption, here, lots would wonder why ? Because PHPBB forums use MD5 encryption, and it would be a good way to a cross user DB for forum / website / server.

[sotonin]

You do know that md5 is one way right? Once it's encrypted there's no going back.

[daeken_bb]

The problem with that is that if they sniff packets they can pull out the md5, and even though they can't get it back out, they can send it already hashed. Of course, we could defeat that with a salt, but SSL would still be far more secure.

[Elkay]

I say, as long as it's compatible and secure, the method does not matter to me. :D

FYI: We used DES3 with our software, though I had nothing to do with that part of our projects.

[RangerDown]

The problem with that is that if they sniff packets they can pull out the md5, and even though they can't get it back out, they can send it already hashed. Of course, we could defeat that with a salt, but SSL would still be far more secure.


No, don't try to make the client hash the password before sending it up. Send the password encrypted, but using something that can be decrypted. SSL would be perfect because the keys are dynamically generated, and the server would be able to decrypt the block once it got it. Then, using the (now decrypted and now plaintext) password, the server compares a hash of it to the hash you have in the user database, to see if the password is correct.

[Elkay]

That sounds like it would work. I do have one question though, well a few. First, who on here actually runs the EQEmu LS? And second question, what is not secure about the code in it that disallows it's distribution, or is the EQEmu LS code not compiled code? I know that the recent but currently defunct Minilogin was written in Perl, and I do know of utilities out there that compile Perl code into a standalone executeable.

[smogo]

I know that the recent but currently defunct Minilogin was written in Perl
hmm, i'm not sure about the 'defunct' world. i admit it's getting old, and does not speak loud, but it can still be used afaik. Technical reasons prevent me from really working on it at the moment though.

[Elkay]

Ack, sorry smogo didn't mean it like it came out. It does work well.. for 5.7DR6. I meant that it is not compatible with 5.8/9. Sorry about that! From a technical perspective, what is it that is keeping you from being able to update ML? Did Sony change something in the handshake that can't be simply updated?

[smogo]

np. No there's no impossible thing to update, it's just not scheduled yet ;)

[KhaN]

First, who on here actually runs the EQEmu LS?
Doodman make LS, LE host it (i think, correct me if im wrong)

And second question, what is not secure about the code in it that disallows it's distribution, or is the EQEmu LS code not compiled code?
There are a lots of topics about this subject, nothing really prevent them to release it, they just dont want to, its their choice,.

I know that the recent but currently defunct Minilogin was written in Perl
I wouldnt say defunct, neither old, but yes, on some points, you are right, Minilogin is no more compatible EQLive.

From a technical perspective, what is it that is keeping you from being able to update ML? Did Sony change something in the handshake that can't be simply updated?
First, few peoples have the skills required to work on a LoginServer, this make only 1 months now we are working on "World of Alkora" one. Basically, "World of Alkora" server is meant to run our server which is on 5.7DR6, and we decided to release the source to allow other peoples to become independant from EQEmu LS. Now, what retain us from going to live ? Well, our vision is rather different than EQEmu one, our server is under development, and catching live is far from being a priority, mainly because we have a tons of things to dvelop. We are actually converting our PERL LS to C++, to allow more people to work and improving it, making it opensource LS. With all the hands on EQEmu, im sure we can all work together to make a valuable LS that can quickly catch up live.

[Cisyouc]

We are actually converting our PERL LS to C++, to allow more people to work and improving it, making it opensource LS. <3

[Elkay]

Awesome guys, thanks for the updates. There's no rush really as long as EQEmu LS stays active. My only real concern is being able to still run my server if (god forbid) something should happen to the official EQEmu one. I also like the fact that it's being converted from Perl to C++ as it is more widely known and there will be more people able to contribute to it's development.

[Camaris]

Hi all, I really would appreciate any help...i am getting the next problem with minilogin, i am using WoA backpacht then i guess that my client version is correct, i have tried 7-31 , 6-16 and 6-21 servers (all are 5.7-DR 6) and i am getting always the same error, i get to server selection screen, i push play Everquest, then i get back to login account screen... This is the mini.log file that i get using: perl -w minilogin.pl > mini.log

reading : 127.0.0.1 eqemu3 eqemu3
setting 0 to id 591, eqemu3 / eqemu3
udp server listening on port : 5996
tcp server listening on port : 5996
now to work ...
currently on :
currently on :
new incomming server ...
key : 127.0.0.1:1032
key : 127.0.0.1:1032
opcode : 4096, length : 607
World protocol : 0.3.10
World version : 0.5.7-DR6
World account :
World name : Arex's revenge
World key : 127.0.0.1:1032
World passwd :
World url : 127.0.0.1
World type : 0
World category : 34
key : 127.0.0.1:1032
opcode : 4097, length : 16
Status : -2, Clients 0, Zones 0
key : 127.0.0.1:1032
opcode : 4097, length : 16
Status : -2, Clients 0, Zones 0
currently on :
server from 127.0.0.1:1032 : Arex's revenge
key : 127.0.0.1:1032
opcode : 4097, length : 16
Status : -2, Clients 0, Zones 0
key : 127.0.0.1:1032
opcode : 4097, length : 16
Status : -2, Clients 0, Zones 0
currently on :
server from 127.0.0.1:1032 : Arex's revenge
key : 127.0.0.1:1032
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 2
key : 127.0.0.1:1032
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 2
currently on :
server from 127.0.0.1:1032 : Arex's revenge
key : 127.0.0.1:1032
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 2
key : 127.0.0.1:1032
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 2
currently on :
server from 127.0.0.1:1032 : Arex's revenge
key : 127.0.0.1:1032
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 2
key : 127.0.0.1:1032
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 2
currently on :
server from 127.0.0.1:1032 : Arex's revenge
key is : 127.0.0.1:1037

-->incoming
Client 127.0.0.1:1037 sent 14 bytes, message type : 0x01 retry count : 0x00
00 01 00 00 00 02 00 29 48 23 00 00 02 00
new client, sending reply to 127.0.0.1:1037
key is : 127.0.0.1:1037

-->incoming
Client 127.0.0.1:1037 sent 18 bytes, message type : 0x09 retry count : 0x00
00 09 00 00 01 00 01 00 00 00 00 00 00 00 00 00 03 00
opcode 1 , sequence id 0
key is : 127.0.0.1:1037

-->incoming
Client 127.0.0.1:1037 sent 40 bytes, message type : 0x03 retry count : 0x00
00 03 04 00 15 00 00 20 00 09 00 01 02 00 02 00 00 00 00 00 00 00 00 00 65 71 65 6d 75 33 00 65 71 65 6d 75 33 00 00 00
in reply to seq # 0
leading block
leading block
in reply to seq # 0
message in packet is :
00 09 00 01 02 00 02 00 00 00 00 00 00 00 00 00 65 71 65 6d 75 33 00 65 71 65 6d 75 33 00 00 00
opcode 2 , sequence id 1
message type 0009 0001, answer with ... ack
login = eqemu3 eqemu3
login : eqemu3
pass : eqemu3
login match : eqemu3 ( eqemu3,eqemu3)
client id is : 1
auth key : ER1lb3TdJ
sending login key informaion
aknowledging seq id 1 to client (pure ack)
client authentified
key is : 127.0.0.1:1037

-->incoming
Client 127.0.0.1:1037 sent 24 bytes, message type : 0x03 retry count : 0x00
00 03 04 00 15 00 01 10 00 09 00 02 04 00 03 00 00 00 00 00 00 00 00 00
in reply to seq # 1
leading block
leading block
in reply to seq # 1
message in packet is :
00 09 00 02 04 00 03 00 00 00 00 00 00 00 00 00
opcode 4 , sequence id 2
acquired lock for server list
server from 127.0.0.1:1032 : Arex's revenge
4950554648464846490
sending info for 1 servers, total 47 bytes
127.0.0.1:1032
key is : 127.0.0.1:1037

-->incoming
Client 127.0.0.1:1037 sent 4 bytes, message type : 0x15 retry count : 0x02
00 15 00 02
message type 0x15, packet # 2 received and acknowledged by client
key : 127.0.0.1:1032
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 2
key is : 127.0.0.1:1037

-->incoming
Client 127.0.0.1:1037 sent 16 bytes, message type : 0x09 retry count : 0x02
00 09 00 02 04 00 03 00 00 00 00 00 00 00 00 00
opcode 4 , sequence id 2
acquired lock for server list
server from 127.0.0.1:1032 : Arex's revenge
4950554648464846490
sending info for 1 servers, total 47 bytes
127.0.0.1:1032
key is : 127.0.0.1:1037

-->incoming
Client 127.0.0.1:1037 sent 4 bytes, message type : 0x15 retry count

[mystic414]

I also am having the same problems as several people in this thread: I run minilogin.pl, world.exe, boot5zones.bat and all seems fine. Then I login to the server select screen (after it tells me that there have been 1.4 BILLION failed login attempts since my last login, if that tells you anything). I select my server from the list, click play eq, and am promptly dumped back to the login screen.

I'm running a 5.7 DR6 server and am able to login and play just fine on other 5.7 DR6 servers.

For the record, the server is running on 192.168.0.2 and I'm trying to login from 192.168.0.1.

Configuration files:

miniloginaccounts.ini: (in directory with minilogin.pl)
192.168.0.1 minilogin minilogin_ (the _ is a supposed to be a space

db.ini: (no spaces at end of lines)
[Database]
host=localhost
user=****
password=****
database=eq
compression=off

loginserver.ini:
[LoginServer]
loginserver=192.168.0.2
loginport=5996
worldname=My World Name
worldaddress=192.168.0.2
locked=false

[WorldServer]
Defaultstatus=0
Unavailzone=

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

[ChatChannelServer]
server=localhost

Output from minilogin.pl: (from initial run to after client gets booted)


C:\minilogin>perl -w minilogin.pl
Name "main::socket" used only once: possible typo at minilogin.pl line 118.
reading : 192.168.0.1 minilogin minilogin
setting 0 to id 591, minilogin / minilogin
Useless use of a constant in void context at world.pl line 183.
udp server listening on port : 5996
tcp server listening on port : 5996
now to work ...
currently on :
new incomming server ...
key : 192.168.0.2:1081
key : 192.168.0.2:1081
opcode : 4096, length : 607
World protocol : 0.3.10
World version : 0.5.7-DR6
World account :
World name : My World Name
World key : 192.168.0.2:1081
World passwd :
World url : 192.168.0.2
World type : 0
World category : 34
key : 192.168.0.2:1081
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 5

-->incoming
Client 192.168.0.1:3045 sent 14 bytes, message type : 0x01 retry count : 0x00
00 01 00 00 00 02 00 29 48 23 00 00 02 00
new client, sending reply to 192.168.0.1:3045
key is : 192.168.0.1:3045

-->incoming
Client 192.168.0.1:3045 sent 18 bytes, message type : 0x09 retry count : 0x00
00 09 00 00 01 00 01 00 00 00 00 00 00 00 00 00 03 00
opcode 1 , sequence id 0
key is : 192.168.0.1:3045

-->incoming
Client 192.168.0.1:3045 sent 46 bytes, message type : 0x03 retry count : 0x00
00 03 04 00 15 00 00 26 00 09 00 01 02 00 02 00 00 00 00 00 00 00 00 00 6d 69 6e
69 6c 6f 67 69 6e 00 6d 69 6e 69 6c 6f 67 69 6e 00 00 00
in reply to seq # 0
leading block
leading block
in reply to seq # 0
message in packet is :
00 09 00 01 02 00 02 00 00 00 00 00 00 00 00 00 6d 69 6e 69 6c 6f 67 69 6e 00 6d
69 6e 69 6c 6f 67 69 6e 00 00 00
opcode 2 , sequence id 1
message type 0009 0001, answer with ... ack
login = minilogin minilogin
login : minilogin
pass : minilogin
login match : minilogin ( minilogin,minilogin)
client id is : 1
auth key : ezBTqdPbB
sending login key informaion
aknowledging seq id 1 to client (pure ack)
client authentified
key is : 192.168.0.1:3045

-->incoming
Client 192.168.0.1:3045 sent 24 bytes, message type : 0x03 retry count : 0x00
00 03 04 00 15 00 01 10 00 09 00 02 04 00 03 00 00 00 00 00 00 00 00 00
in reply to seq # 1
leading block
leading block
in reply to seq # 1
message in packet is :
00 09 00 02 04 00 03 00 00 00 00 00 00 00 00 00
opcode 4 , sequence id 2
acquired lock for server list
server from 192.168.0.2:1081 : My World Name
49575046495456464846500
Use of uninitialized value in pack at client.pl line 176.
sending info for 1 servers, total 53 bytes
192.168.0.2:1081
key is : 192.168.0.1:3045

-->incoming
Client 192.168.0.1:3045 sent 4 bytes, message type : 0x15 retry count : 0x02
00 15 00 02
message type 0x15, packet # 2 received and acknowledged by client
key : 192.168.0.2:1081
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 5
key is : 192.168.0.1:3045

-->incoming
Client 192.168.0.1:3045 sent 16 bytes, message type : 0x09 retry count : 0x02
00 09 00 02 04 00 03 00 00 00 00 00 00 00 00 00
opcode 4 , sequence id 2
acquired lock for server list
server from 192.168.0.2:1081 : My World Name
49575046495456464846500
Use of uninitialized value in pack at client.pl line 176.
sending info for 1 servers, total 53 bytes
192.168.0.2:1081
key is : 192.168.0.1:3045

-->incoming
Client 192.168.0.1:3045 sent 4 bytes, message type : 0x15 retry count : 0x02
00 15 00 02
message type 0x15, packet # 2 received and acknowledged by client
key is : 192.168.0.1:3045

-->incoming
Client 192.168.0.1:3045 sent 16 bytes, message type : 0x09 retry count : 0x02
00 09 00 02 04 00 03 00 00 00 00 00 00 00 00 00
opcode 4 , sequence id 2
acquired lock for server list
server from 192.168.0.2:1081 : My World Name
49575046495456464846500
Use of uninitialized value in pack at client.pl line 176.
sending info for 1 servers, total 53 bytes
192.168.0.2:1081
key is : 192.168.0.1:3045

-->incoming
Client 192.168.0.1:3045 sent 4 bytes, message type : 0x15 retry count : 0x02
00 15 00 02
message type 0x15, packet # 2 received and acknowledged by client
key is : 192.168.0.1:3045

-->incoming
Client 192.168.0.1:3045 sent 20 bytes, message type : 0x09 retry count : 0x03
00 09 00 03 0d 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00
opcode 13 , sequence id 3
request to contact server # 0
aknowledging seq id 3 to client (pure ack)
connecting to server : 192.168.0.2:1081,
client id : 1
name minilogin
CLE ezBTqdPbB (0, 0)
packet pending in out queue, length : 71
packet for tcp transfer is : 71 long
2 16 71 0 1 0 0 0 109 105 110 105 108 111 103 105 110 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 101 122 66 84 113 100 80 98 66 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0
sending packet to tcp socket ... transmitted
)key is : 192.168.0.1:3045

-->incoming
Client 192.168.0.1:3045 sent 4 bytes, message type : 0x15 retry count : 0x03
00 15 00 03
message type 0x15, packet # 3 received and acknowledged by client
key is : 192.168.0.1:3045

-->incoming
Client 192.168.0.1:3045 sent 16 bytes, message type : 0x09 retry count : 0x04
00 09 00 04 03 00 05 00 00 00 00 00 00 00 00 00
opcode 3 , sequence id 4
message opcode 0004, answer with type .. ??
key is : 192.168.0.1:3045

-->incoming
Client 192.168.0.1:3045 sent 8 bytes, message type : 0x05 retry count : 0x29
00 05 00 29 48 23 00 06
client quitting
key : 192.168.0.2:1081
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 5
currently on :
server from 192.168.0.2:1081 : My World Name
key : 192.168.0.2:1081
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 5


Thanks in advance for any help! Anyone have an ideas as to what the problem might be?

[smogo]

@mystic :
if you still get the pb, it seems the server gets contacted by the client, and kicks it right away because ... something

Now check your logs.world.log file in the EQEMu server directory. You might read something about 'Bad/Expired key'. Can youconfirm that ?

[smogo]

@camaris :
might be same pb. Checkout your output from the world server (world.exe), it will tell if client tries to connect (what i believe, as you get actively kicked)

[Camaris]

I have checked that mistyc and me are getting problems with sequence id 4, and it dont get sequence 5 and 6. And i neither am sure if opcodes are really correct. Any help would be very appreciate....

I am using now a name and password in DB, because i am using minilogin (not ls) then i ll past here my new minilogin.log and world.log, and i also get this warnings:

Name "main::socket" used only once: possible typo at minilogin.pl line 118.
Useless use of a constant in void context at world.pl line 183.



WORLD.EXE (log):

[Status] CURRENT_WORLD_VERSION:EQEMu 0.5.7-DR6
[Status] Loading variables..
[Status] Loading zones..
[Status] Loading items..
[Status] EMuShareMem loaded
[Status] Loading items from database: count=34229, max id=77505
[Status] ./LoginServer.ini read.
[Status] Loading guild ranks..
[Status] Loading ./addon.ini..
[Status] Loading EQ time of day..
[Status] Deleted 0 stale player corpses from database
[Status] Deleted 0 stale player backups from database
Warning: You need to get laid...
TCP listening on: 127.0.0.1:9000
World server listening on: 127.0.0.1:9000
Connected to LoginServer: 127.0.0.1:5996
60778 New TCP connection: 127.0.0.1:1043
New zoneserver: #1 127.0.0.1:1043
Zoneserver SetConnectInfo: 127.0.0.1:1043: 127.0.0.1:7996
60848 New TCP connection: 127.0.0.1:1044
New zoneserver: #2 127.0.0.1:1044
Zoneserver SetConnectInfo: 127.0.0.1:1044: 127.0.0.1:7995


MINILOGIN.PL (log)
reading : 127.0.0.1 eqemu eqemu
setting 0 to id 591, eqemu / eqemu
udp server listening on port : 5996
tcp server listening on port : 5996
now to work ...
currently on :
new incomming server ...
key : 127.0.0.1:1054
key : 127.0.0.1:1054
opcode : 4096, length : 607
World protocol : 0.3.10
World version : 0.5.7-DR6
World account :
World name : World of Norrath
World key : 127.0.0.1:1054
World passwd :
World url : 127.0.0.1
World type : 0
World category : 34
key : 127.0.0.1:1054
opcode : 4097, length : 16
Status : -2, Clients 0, Zones 0
key : 127.0.0.1:1054
opcode : 4097, length : 16
Status : -2, Clients 0, Zones 0
currently on :
server from 127.0.0.1:1054 : World of Norrath
key : 127.0.0.1:1054
opcode : 4097, length : 16
Status : -2, Clients 0, Zones 0
key : 127.0.0.1:1054
opcode : 4097, length : 16
Status : -2, Clients 0, Zones 0
currently on :
server from 127.0.0.1:1054 : World of Norrath
key : 127.0.0.1:1054
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 2
key : 127.0.0.1:1054
opcode : 4097, length : 16
Status : 0, Clients 0, Zones 2
key is : 127.0.0.1:1059

-->incoming
Client 127.0.0.1:1059 sent 14 bytes, message type : 0x01 retry count : 0x00
00 01 00 00 00 02 00 29 48 23 00 00 02 00
new client, sending reply to 127.0.0.1:1059
key is : 127.0.0.1:1059

-->incoming
Client 127.0.0.1:1059 sent 18 bytes, message type : 0x09 retry count : 0x00
00 09 00 00 01 00 01 00 00 00 00 00 00 00 00 00 03 00
opcode 1 , sequence id 0
key is : 127.0.0.1:1059

-->incoming
Client 127.0.0.1:1059 sent 38 bytes, message type : 0x03 retry count : 0x00
00 03 04 00 15 00 00 1e 00 09 00 01 02 00 02 00 00 00 00 00 00 00 00 00 65 71 65 6d 75 00 65 71 65 6d 75 00 00 00
in reply to seq # 0
leading block
leading block
in reply to seq # 0
message in packet is :
00 09 00 01 02 00 02 00 00 00 00 00 00 00 00 00 65 71 65 6d 75 00 65 71 65 6d 75 00 00 00
opcode 2 , sequence id 1
message type 0009 0001, answer with ... ack
login = eqemu eqemu
login : eqemu
pass : eqemu
login match : eqemu ( eqemu,eqemu)
client id is : 1
auth key : FwrPYbXVm
sending login key informaion
aknowledging seq id 1 to client (pure ack)
client authentified
key is : 127.0.0.1:1059

-->incoming
Client 127.0.0.1:1059 sent 24 bytes, message type : 0x03 retry count : 0x00
00 03 04 00 15 00 01 10 00 09 00 02 04 00 03 00 00 00 00 00 00 00 00 00
in reply to seq # 1
leading block
leading block
in reply to seq # 1
message in packet is :
00 09 00 02 04 00 03 00 00 00 00 00 00 00 00 00
opcode 4 , sequence id 2
acquired lock for server list
server from 127.0.0.1:1054 : World of Norrath
4950554648464846490
sending info for 1 servers, total 49 bytes
127.0.0.1:1054
key is : 127.0.0.1:1059

-->incoming
Client 127.0.0.1:1059 sent 4 bytes, message type : 0x15 retry count : 0x02
00 15 00 02
message type 0x15, packet # 2 received and acknowledged by client
key is : 127.0.0.1:1059

-->incoming
Client 127.0.0.1:1059 sent 20 bytes, message type : 0x09 retry count : 0x03
00 09 00 03 0d 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00
opcode 13 , sequence id 3
request to contact server # 0
aknowledging seq id 3 to client (pure ack)
connecting to server : 127.0.0.1:1054,
client id : 1
name eqemu
CLE FwrPYbXVm (0, 0)
packet pending in out queue, length : 71
packet for tcp transfer is : 71 long
2 16 71 0 1 0 0 0 101 113 101 109 117 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 70 119 114 80 89 98 88 86 109 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
sending packet to tcp socket ... transmitted
)key is : 127.0.0.1:1059

-->incoming
Client 127.0.0.1:1059 sent 4 bytes, message type : 0x15 retry count : 0x03
00 15 00 03
message type 0x15, packet # 3 received and acknowledged by client
key is : 127.0.0.1:1059

-->incoming
Client 127.0.0.1:1059 sent 16 bytes, message type : 0x09 retry count : 0x04
00 09 00 04 03 00 05 00 00 00 00 00 00 00 00 00
opcode 3 , sequence id 4
message opcode 0004, answer with type??

[smogo]

hi,

minilogin works not too bad afaik (we use it eeveryday for development purpose). However some of you had problems connecting.

It seems it happens on localhost ips (127.0.0.1) mostly (if not only, though i can't imagine the reason). Has anyone had success using 127.0.0.1 ?

If so, can you describe what config files you are using, and how you got it to work (i can't test this because i run server on linux only)

Thank you for contribution.

[KhaN]

My config files :
192.168.0.123 khan kurultai
192.168.0.101 dave davespassword
192.168.0.102 harry harryspassword
192.168.0.100 steph stephspassword