Go Back   EQEmulator Home > EQEmulator Forums > General > General::General Discussion

General::General Discussion General discussion about EverQuest(tm), EQEMu, and related topics.
Do not post support topics here.

Reply
 
Thread Tools Display Modes
  #1  
Old 03-29-2009, 06:59 AM
trevius's Avatar
trevius
Developer
 
Join Date: Aug 2006
Location: USA
Posts: 5,946
Default

You obviously are still completely misunderstanding what I am proposing and why it is the best solution and still just as secure as anything you might propose.

I said nothing at all about sharing account information between any servers, private or public. There is no sharing involved at all... All account information for this idea would be held and accessed only on the server running it's own private Login Server. It would work exactly like a private Login Server should, exactly like you are suggesting, accept with more options. It has nothing to do with any other server's Private LS and doesn't interfere or interact with them in any way at all. I don't know why this is hard to understand as the concept is really quite simple.

Yes, the eqhost.txt file cannot accept multiple Login Servers to be set in it to be used at the same time, but you can set as many as you want in there and comment them out using the # sign and then simply uncomment whichever one you are wanting to use at that time and comment the previous one you were using out. Something like this works perfectly fine:

Code:
[LoginServer]
#Host=eqemulator.net:5998
Host=192.168.1.101:5999
#Host=209.17.190.80:5999
Also, I am positive that moving an account from 1 server to another on EQLive or WoW, or whatever is as simple as having an admin either run a very simple command or just click a button in a UI. It isn't an involved process. It shouldn't be any more involved than our webtool being able to move a character from 1 account to another, which takes about 2 seconds. Really, that has nothing to do with this conversation, but since you brought it up, I figured it was worth clarifying that.

I'm not sure what it is that you are not getting about this idea, but I think that if you understood it, you would be perfectly fine with it.

As far as how much work it would take to code exactly what I am talking about, I really don't think it would be that much at all. Then again, I have been working on getting the Secrets of Faydwer expansion to be fully compatible with the emulator for 4 months now for hours every single night. So, compared to that, most things pale in comparison :P At least it is almost done now, so it shouldn't be long before I can move onto doing other things and hopefully find time to start working on new content for the server I run.

I may be wrong, but I think Image said it only took him a couple of days to code the whole new Mini-Login and Public LS that they have now. If that is so, even if a good portion of it had to be adjusted to work for this idea, it isn't like we are talking about an insane amount of work to do it. Not that I am asking him to do it, but just saying it probably isn't as bad as you are thinking it is.

The whole concept of this idea would be to have dual LS capability for server. People would set their server to connect to the public LS just like normal (though, that would be optional and not required if you just wanted to use the Private one). Then, they would also set it to use the Private LS running on their own server and using their own accounts database at the same time. Ideally, servers would be connected to both all of the time. But, in the case that the Public LS goes down for any reason, their players could then change their eqhost.txt to point to the private one for that particular server. Also, if people wanted to avoid the Public LS even when it was up, they would still be able to use just the Private LS for that particular server since they would both be connected at all times.

The private LS wouldn't use the LS account ID numbers like the Public one does. Authentication for the private LS would ignore the "lsaccount_id" field completely since it would have no way of knowing what it should be. Instead, it would use the password field when people log into their private LS and then just forward any accounts that pass the authentication check at that point straight to the server as authenticated. That is it. Am I missing anything to make this more clear?

I am not trying to start an argument here. It seems that no matter what I say, you have to disagree, Aergad. That is perfectly fine, as everyone is entitled to their own opinion and you aren't breaking any kind of rules. But, I am not going to bother discussing it any further with you until you can understand that I am not out to control you or anyone else. All I am here for is to be helpful. I know you haven't been around this community long (maybe 2 weeks), but if you give it time, you might see that I am a fair person who just wants to help :P
__________________
Trevazar/Trevius Owner of: Storm Haven
Everquest Emulator FAQ (Frequently Asked Questions) - Read It!
Reply With Quote
  #2  
Old 03-29-2009, 03:27 PM
AndMetal
Developer
 
Join Date: Mar 2007
Location: Ohio
Posts: 648
Default

Quote:
Originally Posted by trevius View Post
The whole concept of this idea would be to have dual LS capability for server. People would set their server to connect to the public LS just like normal (though, that would be optional and not required if you just wanted to use the Private one). Then, they would also set it to use the Private LS running on their own server and using their own accounts database at the same time. Ideally, servers would be connected to both all of the time. But, in the case that the Public LS goes down for any reason, their players could then change their eqhost.txt to point to the private one for that particular server. Also, if people wanted to avoid the Public LS even when it was up, they would still be able to use just the Private LS for that particular server since they would both be connected at all times.

The private LS wouldn't use the LS account ID numbers like the Public one does. Authentication for the private LS would ignore the "lsaccount_id" field completely since it would have no way of knowing what it should be. Instead, it would use the password field when people log into their private LS and then just forward any accounts that pass the authentication check at that point straight to the server as authenticated. That is it.
I second.

I think it would be good to have an option to turn off the "public" part of it for those who either just want to play on a LAN, or just don't want to be connected to the public login server (either in the short term during development, or in the long term for whatever reasons).

I think ideally it would be best to incorporate this into world, but we'd need to keep the crypto out of the source (.dll, .so, etc) so others can't just start packet sniffing client authentication & reverse the username/password hash.

Quote:
Originally Posted by image View Post
I see what we are getting at with the shared LS, we would need a way to generate UNIQUE id's that way, sort of like how everquest has those item id tags.

The reason I say this is, if I have LSID account 1 on my public server (which we obviously do), the private server would have LSID 1 of a different user. The Login server uses the LSID to identify and pass. Yes you can setup a private password with #setpass if they have the tables meshed in the same database, but the LSID would still be an issue.

So I think this would require a bit of re-work.

Edit: The reason I want unique LSID's is there still are a lot of database functions/calls that use the LSID and this would cause problems with login and world.
I think if we change to use the id rather than the lsaccount_id from the account table, that should help clear that up. Then, if an account authenticates via the public login server instead, we can update the lsaccount_id column with the info, but still use the local id.

After brief digging into the world source, I wasn't able to determine how dependent we are on the lsaccount_id, so I'm not really sure how difficult of a change this would be.
__________________
GM-Impossible of 'A work in progress'
A non-legit PEQ DB server
How to create your own non-legit server

My Contributions to the Wiki
Reply With Quote
  #3  
Old 03-29-2009, 05:18 PM
trevius's Avatar
trevius
Developer
 
Join Date: Aug 2006
Location: USA
Posts: 5,946
Default

Image, if your last post that mentioned "shared LS" was a reply about my idea, then I still don't think you are understanding the idea. There would be no sharing of the Login Server. There would be a public (optional) Login Server connection and also a private (unshared and also optional) mini-login-like connection.

Here is a simple example of how it could work:

[Client]--->[Public Login Server]--->[Authenticate to Public LS Database]--->[Server]

Or

[Client]--->[Private Login Server]--->[Authenticate to Server's Account Table]--->[Server]

No sharing involved :P
__________________
Trevazar/Trevius Owner of: Storm Haven
Everquest Emulator FAQ (Frequently Asked Questions) - Read It!
Reply With Quote
  #4  
Old 03-29-2009, 05:31 PM
image
Demi-God
 
Join Date: Jan 2002
Posts: 1,290
Default

I don't think I am able to express the design limitations of this to you, so I am just going to leave it at that.
__________________
www.eq2emu.com
EQ2Emu Developer
Former EQEMu Developer / GuildWars / Zek Seasons Servers
Member of the "I hate devn00b" club.
Reply With Quote
  #5  
Old 03-30-2009, 10:19 AM
KingMort
Banned
 
Join Date: Sep 2006
Posts: 841
Default

Well folks you know my stance .. Have gained heated discussion in other topics..

I 100% support EQEMU but everyone knows that the Eqemu staff may resolve to go open source... and maybe they don't... that's fine too.....


This is no time to lose confidence the team is making MUCH PROGRESS .....

Funds will be given and things will move forward as always...

REMEMBER we are a community... and we must NOT split up by any means .....

I don't care what happens to my own server as long as we pull together in these hard times...

Do not make the mistake to totally disregard Eqemu.... Do not make the mistake to totally disregard other options...

I strongly believe that KLS and Doodman and the other team members will pull through this.. However it's good that folks have been working on other options...

KEEP UP THE GOOD WORK !!!

King
Reply With Quote
  #6  
Old 03-30-2009, 01:38 PM
PathToEternity
Fire Beetle
 
Join Date: Mar 2009
Location: Knoxville
Posts: 28
Default Proposal?

I've been watching this thread (as well as others over the last few days) and thought I'd share an idea. I'd be interested in the thoughts of others on something like this.

How about having a very simple launcher program?

I am not a big fan of launchers, but have been rolling this idea around in my head.

We could have a simple (and I am stressing simplicity, though no need for it to look shoddy) launcher program. You would run the launcher instead of the shortcut, and it would open up showing a list of servers. The servers would list from two separate sources. First, they could be manually added (server ops can give the ip/port of their private LS); second, eqemulator.net would host a downloadable file (not just real time gathered information) which would list all the servers (as in, servers with submitted server info) and this could be updated from within the launcher (download a small text file, for example). So, based on the personal list and the public list, all the servers you have ip/port info for would show on this list.

Obviously a server which is down/not operating would say as much on the server list.

Hopefully, the private LS information can not only report to the launcher whether the server is up or down, but also current population. Thus, based on the list of servers from both the personal and public lists, we could mimic the client's server list. Of course, because these would be private LS's, the username and password would/could vary from server to server, and that would have to be entered within the client later.

This puts the power in the hands of the user as to what servers he wants to keep up with/connect to, while not divorcing him from the EQEmu community because of the (optionally downloaded) public server list.

I'm at work right now, so can't come up with a nice picture to explain, but basically the idea I have is an interface with a listing of the servers, a button to download the latest EQEmu server list (but all using private LS now), a button to manually add a private LS, and of course a button to launch the game (eqgame patchme).

Additionally, with a little more work, perhaps it would be possible for servers which use custom files to use the launcher to swap files in and out on the fly, but that is probably wading out a little deeper than my mind is willing to go.

Anyway, if this idea is worthless and nothing can be done with it, so be it. Otherwise, I have always wanted (and I think I speak for the community) to see something which allows EQEmu to continue on, even if the public LS is down (temporarily or, God forbid, indefinitely). And sorry for so many parentheses, but seemed unavoidable.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

   

All times are GMT -4. The time now is 08:04 AM.


 

Everquest is a registered trademark of Daybreak Game Company LLC.
EQEmulator is not associated or affiliated in any way with Daybreak Game Company LLC.
Except where otherwise noted, this site is licensed under a Creative Commons License.
       
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Template by Bluepearl Design and vBulletin Templates - Ver3.3