Kryppy : "it should be like it is for the spam restriction , loading a .txt file with all IP , IP ranges , CID who are not welcome in the hub. ( a kind of peer-guardian for hub-side and why not with an update button ) I mean something different than BAN comand."
Why should do that?
What;s the difference between your txt file and the system dshub already has?
What;s the difference between editing some txt file or editing bans via commands or interface ?
Why should i use this system instead of the current one?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i don't want this system instead of the current one , i think it can be used as a complement.
some dcmods have feature (ipguard for apex , peerguardian for airdc ) for blocking malicious ip ranges.people who use dc++ or others clients aren't protected.it would be nice if the hub can protect his users from these ip ranges blocking access to hub.
why a .txt file? - owners of hubs from the same net should share it (same protection for all hubs of the net)
- there should be a third-part list which should be updated often . (as AML does for clients)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2008-02-10
Logged In: YES
user_id=1695600
Originator: NO
use a firewall or windows services to drop packets from those ip adresses that u dont want to have in your hub instead
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1800013
Originator: YES
Why should do that?
What;s the difference between your txt file and the system dshub already has?
What;s the difference between editing some txt file or editing bans via commands or interface ?
Why should i use this system instead of the current one?
Logged In: YES
user_id=1941941
Originator: NO
i don't want this system instead of the current one , i think it can be used as a complement.
some dcmods have feature (ipguard for apex , peerguardian for airdc ) for blocking malicious ip ranges.people who use dc++ or others clients aren't protected.it would be nice if the hub can protect his users from these ip ranges blocking access to hub.
why a .txt file? - owners of hubs from the same net should share it (same protection for all hubs of the net)
- there should be a third-part list which should be updated often . (as AML does for clients)
Logged In: YES
user_id=1695600
Originator: NO
use a firewall or windows services to drop packets from those ip adresses that u dont want to have in your hub instead