[RELEASE] node-sro-proxy - Opensource middleware/security layer

Moved
[Only registered and activated users can see links. Click Here To Register...]

thanks for contributing , a new step in a dead community ...

Quote:

Originally Posted by dR. [d3V][GM][PR0] 39YP7 nice seeing someone making an effort but guess what, it's not going to do shit the game is dead you bunch of retards

Thats how you call yourself?
- Because we are the game.

Quote:

Originally Posted by Artuuro_lv Thats how you call yourself? - Because we are the game.

lets play this game
atm still fixing packets since some of br ones aint same xD

Quote:

Originally Posted by kebabas1600 lets play this game atm still fixing packets since some of br ones aint same xD

just set in your module your config to dev: true and see the packets

New version is out!
Changelog:
- Moved middlewares/services to proxy configuration
- Completely re-written proxy logic to fit proposal below
[Only registered and activated users can see links. Click Here To Register...]

Quote:

Originally Posted by Artuuro_lv New version is out! Changelog: - Moved middlewares/services to proxy configuration - Completely re-written proxy logic to fit proposal below [Only registered and activated users can see links. Click Here To Register...]

what this does? have to add inside filter?

Quote:

Originally Posted by Beba Army what this does? have to add inside filter?

This is the way how the proxy now works (latest commits).
Basically there is a master process that will spawn a child for each client connected and this child will act as the proxy while master is routing the packets from to client separately and redirects them to slaves.
This way we can keep the client connections very stable and smooth as each instance works with client separately - only doubts that I have not yet tested is the limitations of process.fork in nodejs.
Will let know soon.

Awesome work

Quote:

Originally Posted by Artuuro_lv New version is out! Changelog: - Moved middlewares/services to proxy configuration - Completely re-written proxy logic to fit proposal below [Only registered and activated users can see links. Click Here To Register...]

Nice idea, how it'll work exactly ? Every slave will be a little "tcp proxy" ? Then return to Master everytime there is a packet processing? Then master will accept or not to forward ?

Or you put all the same logic on every slave ?

Sorry didn't make a look on code before asking this

Quote:

Originally Posted by gigola123 Nice idea, how it'll work exactly ? Every slave will be a little "tcp proxy" ? Then return to Master everytime there is a packet processing? Then master will accept or not to forward ? Or you put all the same logic on every slave ? Sorry didn't make a look on code before asking this

Yea you've guessed right - master decides whether the packet will be routed or not - slave can do that as well with this I will be also able to have good way of packet broadcasting, e.g. the master could broadcast a message from another slave (lets say event bot) to the ones it wants or everyone and so on..

Next steps will be implementing this [Only registered and activated users can see links. Click Here To Register...] and making an scriptable game event API.

Another cool thing: [Only registered and activated users can see links. Click Here To Register...]
(entire sro database turned into JavaScript models / schemas) with little bit of expressjs magic this becomes an actual rest API that slaves can use to get / send data to.

Quote:

Originally Posted by Artuuro_lv Yea you've guessed right - master decides whether the packet will be routed or not - slave can do that as well with this I will be also able to have good way of packet broadcasting, e.g. the master could broadcast a message from another slave (lets say event bot) to the ones it wants or everyone and so on.. Next steps will be implementing this [Only registered and activated users can see links. Click Here To Register...] and making an scriptable game event API. Another cool thing: [Only registered and activated users can see links. Click Here To Register...] (entire sro database turned into JavaScript models / schemas) with little bit of expressjs magic this becomes an actual rest API that slaves can use to get / send data to. [Only registered and activated users can see links. Click Here To Register...]

What about master multiprocess, in case there is multi agent server filter ? In case you want a communication between all AgentServer (for event purpose). I used redis but too much factor to handle and I wanted something simple.

This filter if perfect to use on an other server, like a simple server @ digitalocean, really nice work Artuuro :). I'll probably try to optimize SilkroadSecuiryJS if I've time in futur.

And really nice stuff about the Sro DB representation with Sequelize model, I use Sequelize for 5 years now and it's a real perfect orm, I'll use your stuff here for some test purpose, if you want I contributed on a little lib for handle more querystring stuff (for use "like", "between" ect..) ([Only registered and activated users can see links. Click Here To Register...]).

I hope I'll have time to contribe to this project, too much work thoses weeks, GG for everything :D

Quote:

Originally Posted by gigola123 What about master multiprocess, in case there is multi agent server filter ? In case you want a communication between all AgentServer (for event purpose). I used redis but too much factor to handle and I wanted something simple. This filter if perfect to use on an other server, like a simple server @ digitalocean, really nice work Artuuro :). I'll probably try to optimize SilkroadSecuiryJS if I've time in futur. And really nice stuff about the Sro DB representation with Sequelize model, I use Sequelize for 5 years now and it's a real perfect orm, I'll use your stuff here for some test purpose, if you want I contributed on a little lib for handle more querystring stuff (for use "like", "between" ect..) ([Only registered and activated users can see links. Click Here To Register...]). I hope I'll have time to contribe to this project, too much work thoses weeks, GG for everything :D

ATM been only doing this for single agentserver as my own project runs only one - might look into that at future.

New version is out!
Changelog:
- Shared DB api server - workers can now access database without doing it on the same thread
- Fully exported schemas in sequelize.js for entire SRO database.
- Added 3 new API services representing main databases used.
- Added auto-crud.
- IP Blacklist example

New updates (27.11.2020):
Changelog:
- Added IP/HWID blocking (blacklisting).
- Added HWID dll (comes from sr_proxy)
- More express handles
- Added weather packet handler allows to set constant type of weather in game (snowing everywhere, all the time).

New version 2.0.2
- Refactoring/Code improvements
- Actually working HWID/IP limits
- HWID blacklisting
- User Session + Connection / DC detection
- Added Shared "cross-database" API access for all server modules
- Instance saving/updating in database
- User can now be gracefully disconnected from almost anywhere in the code
- Added ".bat" launchers for noobs

Required pk2 edits
TextUISystem.txt

[Only registered and activated users can see links. Click Here To Register...]