[WIP] Ducksoup - c# filter

[Devsome]

Filter != DDOS or Flood protection.
You are just filtering Packets and can modify them.

[b0ykoe]

Like @ said. Filter isn't a DDOS Protection, at least not this filter. There is a reason why there that less DDOS Protection companies. Without going into deep, we - as Silkroad community - will never be able to build up enough bandwith to migrate ddos attacks.

About the flooding, we can (and we are!) catching that to a certain limit. For example if someone is trying to spam 5k movement packets at once he will get caught and kicked since he exceedet a byte limit.

[devdash]

Originally Posted by Devsome

Filter != DDOS or Flood protection.
You are just filtering Packets and can modify them.

Originally Posted by b0ykoe

Like @ said. Filter isn't a DDOS Protection, at least not this filter. There is a reason why there that less DDOS Protection companies. Without going into deep, we - as Silkroad community - will never be able to build up enough bandwith to migrate ddos attacks.

About the flooding, we can (and we are!) catching that to a certain limit. For example if someone is trying to spam 5k movement packets at once he will get caught and kicked since he exceedet a byte limit.

Thank you so much for the explanation

So OVH = DDOS protection
Filter = Limit packets = FLOOD protection

so if we upgrade this filter to contain flood protection, and start using an OVH dedicated server, and closed some ports, then we should be 100% safe

am i getting this right?

Why am i asking so much questions? because this case has been bothering me for so many years now

[janicka]

Originally Posted by alydandy

Thank you so much for the explanation

So OVH = DDOS protection
Filter = Limit packets = FLOOD protection

so if we upgrade this filter to contain flood protection, and start using an OVH dedicated server, and closed some ports, then we should be 100% safe

am i getting this right?

Why am i asking so much questions? because this case has been bothering me for so many years now

Basic networking issue. "bothering me for so many years now" That explains alot.

[halloway520]

thank you bro,

[WolfgangNeverDie]

Bro! What's ManagementServer ?

[Mc-Diesel]

Originally Posted by WolfgangNeverDie

Bro! What's ManagementServer ?

i think that's where you gonna put your features Limits Delays etc

[b0ykoe]

Originally Posted by WolfgangNeverDie

Bro! What's ManagementServer ?

Originally Posted by Mc-Diesel

i think that's where you gonna but your features Limits Delays etc

Yup that's what it what it was intendet for. To synchronise all the events and so on. It won't hold player connections. I've given it some deep thoughts and decided to hop on websockets for that. That way you can connect a homepage onto the ManagementServer and fire events via. the homepage (or send a notice or whatever). It should be pretty secure because it will have a ip whitelist (so you can whitelist your serverips) and a basic auth (id+pw).

[mudik]

Planned Features
- a centralized management server which handles requests regarding max IP, max hwid, synchronized actions and events
- silk per hour
- HWID restrictions
- IP restrictions
- sheduled notices (for all players & individual players)
- max plus
- plus notice
- and so on.. The basic filter stuff


Wann kann man mit den extra Features rechnen? Finde das Projekt echt nice

[thanhtrungn84]

Come on, you need people like you. The sro community needs people like you

[b0ykoe]

Originally Posted by mudik

Planned Features
- a centralized management server which handles requests regarding max IP, max hwid, synchronized actions and events
- silk per hour
- HWID restrictions
- IP restrictions
- sheduled notices (for all players & individual players)
- max plus
- plus notice
- and so on.. The basic filter stuff


Wann kann man mit den extra Features rechnen? Finde das Projekt echt nice

Nur weil Features geplant sind heißt es nicht, dass ich sie auch priorisiere. Momentan gibt es deutlich wichtigere sachen als kleine Spielerrein. Ich hab in den letzten Tagen das Modulsystem einmal über den Haufen geworfen und alle Module vom Filter starten lassen. Die Aufgeteilten Module sind sicherlich cool für große Server, aber größere Server werden vermutlich etwas eigenes Entwickeln.

Dadurch fällt auch der zentrale Managementserver raus, das können wir jetzt alles Filterintern klären.

Als nächstes wird vermutlich erstmal irgendetwas in richtung Events folgen damit man dort einen Strukturierten Weg hat diese einzupflegen.

Originally Posted by thanhtrungn84

Come on, you need people like you. The sro community needs people like you

yes.

[VeRo!]

This is a very huge project when it comes to performance and latency!

But I don't think memory is okay, it stores like 0.1~0.3mb/connection and it doesn't free memory after that, Looking forward to hear from you!

[b0ykoe]

Originally Posted by VeRo!

This is a very huge project when it comes to performance and latency!

But I don't think memory is okay, it stores like 0.1~0.3mb/connection and it doesn't free memory after that, Looking forward to hear from you!

Since memory is basically cheaper and easier to expand, at least if you compare to processor power, it wasn't a top priority to me to keep it low. Somewhere when I find time to finish the v2 I might release that. I've made sure to cleanup the memory after session exists on there.

[VeRo!]

Originally Posted by b0ykoe

Since memory is basically cheaper and easier to expand, at least if you compare to processor power, it wasn't a top priority to me to keep it low. Somewhere when I find time to finish the v2 I might release that. I've made sure to cleanup the memory after session exists on there.

Looking forward to it, the project is really interested!

Thank you.

[Q8Quard]

can you upload the artifacts.zip file to mega or google