Presentation of reverse proxy model

In previous article, I have shown issues with standard proxy model. Reverse proxy model gets rid of NAT issues. We have following entities:

NAT device in front of proxy is not configured, meaning only outgoing connections of proxy are allowed. We take the benefit of possibility for proxy to establish outgoing connections; and we create one. But the question is: To where? Answer: To us! Unfortunately, most of networking client-side software does not support "back-connections" or incoming connects - client software usually do not listen for incoming connections, thus we need another software in the middle that would work as a bridge.

Let's assume that the software called RSINT (reverse socks interceptor) might be behind NAT device, which we can configure:

Proxy now connect to RSINT:

And form so called "tunnel". It is a single connection, over which data of multiple connections can be driven. Therefore, it has its own RFC.

Now our client can use proxy, by first connecting to RSINT. RSINT looks to our client as being proxy on itself, but it actually drives all connections over proxy.

It is up to RSINT to properly manage everything. Additionally we can manage accesses and control data flow (since all connections and data is being driven through software controllable by us - RSINT).