Core
Member
- Nov 10, 2016
- 356
- 138
FreeProxy
InformationMy aim is to construct an advanced proxy manager which is designed around Habbo retros. Some of the things which I would like to incorporate are ~ real time statistics, transparent layer, plugin modules, restful api, firewall, black listing and white listing. It's going to be a completely free service once completed but will be limited to fair use. Of course upon request, the fair use can be expanded if you a more intensive retro ~ by default each proxy will be limited to around 250 concurrent connections.
Progression
Completed,
In Progress,
Not started
Features
- Automatic updating ~ The proxy will automatically update your information within seconds without dropping any existing connections on your proxy or all others. Originally using the default configuration there is a high chance of connections being dropped but I know a way around this.
- RESTful API ~ Advanced API allowing you to fetch and put data. For example getting basic statistics real time stats about your proxy or updating your server IP and port remotely. The idea for this was originally going to be for reselling ~ I will likely implement reselling into the panel but will not be used.
- Transparent ~ For some reasons proxy providers have never done this and I don't understand why as the actual clients IP can be used for extra security. The point of a reverse proxy is to provide security, so why would you want to remove existent security to implement it? It also allows you to use the traditional commands like ip ban without having to pull last_ip from database. Most retro cms insert last_ip based on the IP which cloudflare passes in header (over the remote addr), if you don't use cloudflare then you can easily insert a fake header with whatever IP you want.
- Firewall ~ Allowing you to set some basic rules which will drop connections or packets if they meet a bad criteria. For example if a user continually submits the sso check packet then it will drop the connection - stops brute force etc. Personally I just check to follow client to check that they follow the actual handshake but still prevents spam. Can also drop packets if they exceed a length or empty.
- Live statistics ~ Provides live and past data on the proxy for example peaks in connections, etc. Currently I have done a lot such as viewing connections, bandwidth in and out (as well as clean bandwidth), proxy uptime (since last reload) and so on. However, I want to implemented more statistics such as obtaining data based on clients already connected - requires me to do a little research to figure out where it's stored and if it's worth doing. Cron scripts could do with a little bit of work as well though for existing stats.
- Whitelist/Blacklist ~ Allows for you to black list and white list IPs. Those which are white listed will not be passed through the proxy firewall, etc. Those which are black listed will not be able to connect at all ~ instantly dropping the connection. It will be implemented into API so you could possibly run it as ip bans if you don't feel confident on your existing solution. Can use ip ranges as well if needed.
- Interface ~ The actual interface hasn't been started, but will contain everything listed above and will be main form of proxy management. I focus mainly on back end at the moment as front end doesn't really bother me lol. However, I already have a template system, etc. which has been coded.
