[dba-Tech] Extranet VPN for testing customers' web sites/web API solutions

[Gustav Brock]

Hi Shamil

I can't tell about the VPN infrastructure as that must be a courtesy of your hosting provider, but as you have a VM and not just a web server, I guess no ports are blocked.

The only way to find out if the netsh command will work, is to check it out. Even though port 80 is default for the HTTP protocol, I would explicitly specify it as you suggest.

/gustav

-----Oprindelig meddelelse-----
Fra: dba-Tech [mailto:dba-tech-bounces at databaseadvisors.com] På vegne af Salakhetdinov Shamil via dba-Tech
Sendt: 3. august 2017 12:18
Til: Discussion of Hardware and Software issues <dba-tech at databaseadvisors.com>
Cc: Salakhetdinov Shamil <mcp2004 at mail.ru>
Emne: Re: [dba-Tech] Extranet VPN for testing customers' web sites/web API solutions

Hi Gustav --

Thank you for the example you found.

So using netsh and having VPN infrastructure activated and configured for the case

1. Customer #1 would get access to virtual IP 15.27.103.185 referring real IP:Port  123.17.82.45:2337

the Cusomer #1 should run the following netsh command:

netsh interface portproxy add v4tov4 listenport=80 listenaddress= 15.27.103.185 connectport=2337 connectaddress= 123.17.82.45 ?

Not sure about listenport=80 value, not sure about if it works at all what I'd like to get in this case is the Customer #1 typing

http://15.27.103.185

in his browser and accessing web site running on my cloud VM on  http:// 123.17.82.45:2337  (Use sase #1.1)

or the Customer #1 WinForms/WPF/UWP/... application communicating with a RESTFul Web API via 

http://15.27.103.185

and actually getting connected with the RESTFul Web API on http:// 123.17.82.45:2337  (Use sase #1.2)

Do you suppose use cases #1.1 and #1.2 are doable this or that way?

Thank you.

-- Shamil


>Thursday, August  3, 2017 12:41 PM +03:00 from Gustav Brock <gustav at cactus.dk>:
>
>Hi Shamil
>
>I believe the native command netsh is for this (and many other tasks).
>
>I found this example on port forwarding in windows:
>
>     https://stackoverflow.com/a/11535395/3527297
>
>Another option seems to be nginx. 
>
>I haven't tried any of these methods.
>
>/gustav
>
>
>-----Oprindelig meddelelse-----
>Fra: dba-Tech [mailto:dba-tech-bounces at databaseadvisors.com] På vegne af Salakhetdinov Shamil via dba-Tech
>Sendt: 3. august 2017 11:25
>Til: Discussion of Hardware and Software issues < dba-tech at databaseadvisors.com >
>Cc: Salakhetdinov Shamil < mcp2004 at mail.ru >
>Emne: [dba-Tech] Extranet VPN for testing customers' web sites/web API solutions
>
>Hi All --
>
>I have a hosted on a cloud MS Windows Server 2012+ VM and I'd like to setup my customers' testing web sites/web API solutions.
>The hosted VM has its own IP but I'd like to virtualize access to customers' testing web sites by using virtual IPs, which, as I expect could be provided by a VPN infrastructure/software.
>
>For example via VPN:
>
>1. Customer #1 would get access to virtual IP 15.27.103.185 referring real IP:Port  123.17.82.45:2337 2. Customer #2 would get access to virtual IP 15.27.103.142 referring real IP:Port  123.17.82.45:2338 ...
>N. Customer #N would get access to virtual IP 15.27.103.1147 referring real IP:Port  123.17.82.45:2399
>
>(all the IP addresses and ports above are just sample ones not having any real refs) 
>
>Is it possible?
>
>If it's possible what software would you recommened to setup on server side? 
>This one looks good -  https://www.softether.org/1-features ?
>
>I'd prefer free/not very expensive solution on server side and free solution for client/customers side.
>
>NB: I currently prefer to not use MS Azure, AWS etc.
>
>Thank you.
>
>-- Shamil