On 19/06/14 18:32, [email protected] wrote:

Hi Jan,

*From:*Jan Just Keijser [mailto:[email protected]]
*Sent:* donderdag 19 juni 2014 16:28
*To:* Witvliet, J, DMO/OPS/I&S/HIN; [email protected]
*Subject:* Re: [Openvpn-users] http-proxy

Hi Hans,

On 19/06/14 16:07, [email protected] <mailto:[email protected]> wrote:

    Hi all,

    Just visited another ministerial department, where the also might
    using or openvpn-set-up.

    As predictable, a whole new list of challenges ...

    One of them is related to the use of http encapsulation:

    At the a client you can configure that all traffic should go to
    proxy.company.org,  port 443

    And that its content should go to vpn_node_22.company.org, tcp
    port 5000.

    But what if you also want:

    Some content should go to vpn_node_22.company.org, tcp port 5010.

    So, Is it possible to configure a reversed-proxy like apache or
    squid to support multiple different destinations?

    What I've seen so far from the docu, is that they sort-off rewrite
    the http-header

I am not sure if I understand your question:

if a http proxy is used to restrict or redirect client access , then the http proxy server can make decisions based on the incoming request, e.g.

1) clientA wants to connect to site www.example.com:443 <http://www.example.com:443> 2) clientA connects to the proxy first, request a 'CONNECT www.example.com <http://www.example.com> 443' 3) http proxy server grants access, or might even direct access to a different host 4) clientA talks via the http proxy with (what it think is) the remote server

OpenVPN works at the routing level, so a similar scheme would have to be achieved using routing. It is not possible to redirect clients to different hosts based on port numbers, but as long as src ip + dest ip are distinguishable then you can route traffic any way you like (on the openvpn server).

Does this answer your question? if not, then please elaborate.

Partly.....

Imagine two clients, client-A and client-B

They BOTH connect to site www.example.com:443 <http://www.example.com:443>
But in the config of client-A it indicates to openvpn server openvn.example.com 1500 tcp and in the config of client-B it indicates to openvpn server openvn.example.com 1510 tcp

So, both users share the same proxy, but should end up on different vpn-servers...


that will work "out of the box" with openvpn - client-A will have something like

remote openvpn.example.com
proto tcp
port 1500
http-proxy  www.example.com 443

and client-B will have
remote openvpn.example.com
proto tcp
port 1510
http-proxy  www.example.com 443

it's the CONNECT string that is sent to the proxy server by OpenVPN itself that will ensure that client-A goes to one instance and client-B to the other.

HTH,

JJK

------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Openvpn-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openvpn-users

Reply via email to