Linux SSH/SOCKS Proxy Application with SQL Integration

Project Summary
The goal of this project is to create a client application where subscribed users can connect to Linux SSH/SOCKS servers and route specific local ports through the Linux SSH server. The overall goal of the product is to reduce game latency. The servers will be hosted on Amazon, Vultr, and other cloud service providers.

Client Application
• Application GUI may consist of something like a grid view with server location, latency, and other relevant information. May want to add a banner at a later date to promote specials, or other services, products, etc.
• Application GUI is preferably loaded from database so that when new servers are added they are available to subscribed users as soon as the client is relaunched.
• Application must make sure user is current on billing. My primary thought on this is to have static SSH credentials for our servers, but then have some sort of secondary authentication to a billing database. If we could automate the creation and disabling of LDAP credentials in all of our Linux servers and then use 802.1x authentication that may be another route, but seems much more complicated to me.
• Application must limit user to one active connection.
• Application must only forward specified local ports for games like League of Legends, World of Warcraft, Counter Strike, Overwatch, etc. A list of games and ports can be provided at a later date.


Server Side

• Obviously we prefer to use Linux due to performance, costs, and other factors. Any version of Linux that suits you is fine as long as it can be hosted on Vultr, Amazon Web Services, and other cloud hosting services.
• We would like a script to be created that can automate the addition of new servers.
• We would like a way to centrally managed all servers. In the past we have had to login to individual servers on a one by one basis which is cumbersome and inefficient.
• Would like to research the speed between cloud service provider’s data centers. Example: How fast is the connection between Amazon’s Sydney Australia DC and their Eastern Oregon DC? If Amazon is paying for a large pipe between their datacenters it may be beneficial to setup tunnels between nodes and then have subscribers connect to their local servers and have traffic forwarded through that instead of connecting directly to servers in the U.S.
Web/Billing
• Would like to integrate the client login with billing database so that users who aren’t current on their subscription can’t connect.
• Need the ability to securely collect payments yet track the relevant user data.