Help Roles & Features For L2 On Win 08

[NeverHide]

Hi kind peeps, I'm new to this, so the first suggestion I'm inclined to hear is whether its important to pick certain Win Server 08 Roles and/or Features for the optimal functionality of L2Off platform. Basically I'm curious if there are programs that would enhance the Live Server experience in any meaningful way. Thanks in advance

Edited July 17, 2015 by NeverHide

[tk422]

I can't speak for VG pack specifically but you should not need to install any additional roles onto the machine.

Just make sure you have all the latest updates and security patches for MSSQL and the OS.

MS seems to only release SQL updates purely as service packs so just grab the latest.

Install all the .Net's manually though, then just grab the updates and security patches though WU.

 

General security advice:

- Disable Windows Firewall and get a real piece of gear to handle protection. Mikrotik is great though there is a bit of a learning curve if you're not familiar with networking.

- Block all inbound ports to the server except Auth and L2Server.

- Allow RDP access but only from specific IP's. Better yet use NAT to change the port to something silly.

- Log all outbound connections from the server.

- Do NOT run the registration system on the machine. Run it somewhere else and filter / proxy the connection.

[xeL]

What pack you want to run?

[NeverHide]

What pack you want to run?

Yet undecided, leaning towards Vanganth IL ext, I'm currently playing around with his older release. 

[xeL]

Yet undecided, leaning towards Vanganth IL ext, I'm currently playing around with his older release. 

You don't need to install much beside vc++ redist 2005/2008/2010. It works fin on win8 or winserver 2012. Recomanded is win2k8 for more stability.

[NeverHide]

Many thanks to both of you folks.

 

@tk422, I'm grateful for your insight regarding network security. Concerning the last peace of advice about registration system, are you only talking about web account manager, or something from the server files as well?

Edited July 19, 2015 by NeverHide

[tk422]

The best case scenario would be this:

- Write a rest API that runs on the same network as your game server(s) that handles / abstracts the various potentially dangerous tasks.

    ( Account Creation, Activation, Item Delivery, etc)

- Open the port the API runs on to your webserver but set the scope to ONLY talk to your web server's IP.

- The web server should only talk to your rest API. Never to anything sensitive.

 

Player > Web Server > API > Scary L2 Shit :P

 

 

Assuming the API is resilient and secure enough you now have a very minimal attack surface.

I wouldn't go crazy with SSL between the API and the web server. No one can touch the traffic anyway

... unless your web server gets haxxed. :D

 

 

Definitely set up notifications and make sure to keep very comprehensive logs.

[NeverHide]

The best case scenario would be this:

- Write a rest API that runs on the same network as your game server(s) that handles / abstracts the various potentially dangerous tasks.

    ( Account Creation, Activation, Item Delivery, etc)

- Open the port the API runs on to your webserver but set the scope to ONLY talk to your web server's IP.

- The web server should only talk to your rest API. Never to anything sensitive.

 

Player > Web Server > API > Scary L2 Shit :P

 

 

Assuming the API is resilient and secure enough you now have a very minimal attack surface.

I wouldn't go crazy with SSL between the API and the web server. No one can touch the traffic anyway

... unless your web server gets haxxed. :D

 

 

Definitely set up notifications and make sure to keep very comprehensive logs.

Thats pretty clever, but the problem is, I don't know s**t about REST API  :poker face:  Thanks for your input anyway.

[xeL]

Thats pretty clever, but the problem is, I don't know s**t about REST API  :poker face:  Thanks for your input anyway.

Just stay with account manager/registration manager out of server . Host in another place. As tk422 say , is pretty risky to host on same pc because can be many injections trough sql or other. Beside that . Never open port 2012 on outside. Is cached admin port.    :)

Edited July 23, 2015 by xeL