login server code

[mwmdragon]

This has been a dream of mine for a long time. I could get a working login server than my friends and i wouldn't have to wait for a major holiday to play EQ where we can all gather to play EQEmu on the LAN. We would love to just log in togethere on the private server and play whenever but we need to rely on connections and uptime of the login server and problems with packets and such. Long story short, to play in a non lan group righ tnow is to much of a hastle for us, So we play WOWEmu instead. If EQEmu came out with a public server i KNow we would ditch WOWEmu and come back to the EQ world.

I have written a ton of quests for EQEmu but Now I am learning the WOWEmu quest scripting so my friends and I can benefit from the all the quest writing I do. If EQEmu had the loging server I would poor my time back into quests fro EQEmu..

Hope i didn't offend you developers but this is an old issue I think should be revisited.

[wize_one]

login server code will never be given out.. that has been covered 1000000000000 times before. for lan parties and such just use minilogin.. does the same thing just without the crypto, just have to manually add your friends to the db

[LeftRoad]

And that is why I don't play baseball.

[LeftRoad]

After seeing another post about someone wanting the login server code (that didn't search the boards first) I thought I'd bump this with a twist...

I have successfully connected an external user using minilogin over VPN (OpenVPN.net). Not sure how many can successfully connect this way but I did find some strange things by doing this.

1. If you have routers on both sides make sure you change your IP schema on the server side (to make life easier on others). You don't want both routers having 192.168.1.1, it won't work. Change the third octet to 192.168.2.1 or something.

2. Need to have a separate computer on the server LAN set up as a bridge server to host communications properly. I tried playing on the same machine I was using to bridge and it confused things. XP does bridging really easy. I have been trying to configure a Linux machine and have all the bridging setup but haven't had a chance to test it yet.

3. DSL, something they do causes my brother's connection to the server to drop (LD) after being in anywhere from immediately to about 20 min. Most of the time it dropped right away. I've had problems with users having DSL at home trying to connect with a mainframe app at work. As near as I could figure there was some inherent DSL firewall causing the problems, but only resolved it in one case. The user contacted their ISP and was given a shortcut workaround to allow them to connect. Still haven't confirmed or corrected this.

4. A second user had broadband (Road Runner, which we are on) and he connected fine. Played for over 2 hours with no issues. So that was 2 internal LAN users and one VPN client.

There is hope and this is a viable alternative to getting the minilogin code (which won't happen). The instructions for OpenVPN are pretty good but Linux took some serious digging before I was successful getting the thing running (still not tested though). Having the code would be easier but then everyone that knew about your server would try getting in. If you just want to play with a handful of friends around the world then a secure VPN will let them do that, then only they will be able to get in.

[castlusion]

We had set a VPN up it was when mini login had almost been banned itself ....
Any way we are planning on ussing VPN again to use the current minilogin im running debian and all connections will be done on server bo enless i get to much overhead... dought full but who knows ... i used 10.10 adresses for vpn as 192.168 are used for my network and some others had a small natting issues at one point but testing shows so far it is possible to connnect ... be warned VPN connections are pickier about there connection and may drop also the tunnel usses a little overhead ... and last some end users cant seem to get it together this could be a natting issue "NAT" look it up if some one just dosent be able to connect to the vpn at all.

[rojadruid]

Originally Posted by LeftRoad

3. DSL, something they do causes my brother's connection to the server to drop (LD) after being in anywhere from immediately to about 20 min. Most of the time it dropped right away. I've had problems with users having DSL at home trying to connect with a mainframe app at work. As near as I could figure there was some inherent DSL firewall causing the problems, but only resolved it in one case. The user contacted their ISP and was given a shortcut workaround to allow them to connect. Still haven't confirmed or corrected this.

DSL uploads are picky they have overhead to maintain bloc sync with the upstream head end.

the problem now adays with dsl's users computers is they like everyone else are infected with spyware/adware/malware whatever its being called, wich it taking up the dsl upload overhead.

[Jaezzy]

In lieu of login server code and in the interest of making vpn set up easier.

www.hamachi.cc

Very easy to set up.

Everyone gets their own IP address and joins a private network that you can set up and password protect. Your eqemu server must run hamachi and join the network too. Then you bring up hamachi, and point your eqhost.txt file to the hamachi ip address of your server.

Since everyone gets their own hamachi ip address, you can use mini login and each person has their own minilogin account with their hamachi ip as the minilogin ip.

It's encrypted, private, and fast. I've used it to connect to my eqemu server. Works very well.