Port Forking or Connection Broker?

forcedreality

So this is what I'm looking to accomplish and mentally I can't put the pieces of this puzzle together.

I have multiple remote clients that are going to be sitting behind their respective corporate firewalls. I would prefer to use port 443 since it's something I can pretty much guarantee in all cases that I'll be able to use. Naturally, that means I'll have multiple requests coming in from 443, but each of these clients needs to be on their own separate network and they'll each be using an identical IP scheme. The IP scheme isn't much of an issue since I can take care of that situation with NAT, but I need a remote laptop to be able to connect to each respective site and sit on that remote network. Now, I may be overthinking this, but would I need to use a connection broker in this instance since I'll need to have multiple tunnels open on 443? I don't believe that OpenVPN supports port forking, but I'm not 100% sure.

I've done some reading in these forums and I can't pinpoint a post that follows through on what I'm looking to do. If this is a repost, I apologize.

forcedreality

Or I guess the more pertinent question is, is it possible to use an intermediary to listen on a port and based on a ruleset, forward that traffic to a separate server instance that's listening on a different port?

i.e. incoming request from 2.3.4.5 port 443 redirect to 6.7.8.9 port 1180

forcedreality

Also, maybe I'm just thinking about this wrong altogether. Is it possible to have different IP subnets for each client that connects to the server on one tunnel and isolate them from one another while allowing a remote laptop client to access each individual subnet by some sort of ACL?