[8525, TyTN, MDA Vario II, JasJam General] tetrakouna:
continue from previous post...

In the directive “serveur-bridge”, at the end, they are indicated the IP of the client remote that will come instradati towards the serveur.

The directive “port” (at the beginning) refers obviously to the door in listens of the serveur. Perche' I have chosen door 443? Perche' is the door of service “HTTPS”, one of the little doors (with to door 80) opened generally on “the limited” logons, like on “Vodafone Internet” (WAP).

In the directory “config” of the client, we create the rows client.ovpn with the following one contained:

client

dev tap

proto tcp

remote myip.dyndns.org 443

resolv-retry infinite

nobind

persist-key

persist-tun

ca “\ \ Card of memory \ \ Programs \ \ OpenVPN \ \ config \ \ ca.crt”

CERT “\ \ Card of memory \ \ Programs \ \ OpenVPN \ \ config \ \ client.crt”

key “\ \ Card of memory \ \ Programs \ \ OpenVPN \ \ config \ \ client.key”

# tls-auth “\ \ Card of memory \ \ Programs \ \ OpenVPN \ \ config \ \ ta.key” 1

cipher AES-256-CBC

comp-lzo

#verb 3 # only for debug

HTTP-proxy-retry 1

HTTP-proxy 10.128.201.76 80

The directive “remote” refers to the address of the remote serveur and to the door (the host name of the serveur verra' correctly “resolved” from the logon originates them from own serveur DNS, before that the client it is connected to the VPN and it begins the instradamento of the traffic). The path of the certificates “ca”, “CERT”, “key”, “tls-auth” it depends obviously from the path in which you have installed OpenVPN on the remote machine (in my case it heads for the card of memory of my PocketPC) and must be the path complete, poiche' the rows of executed configuration verra' from the external GUI.

Last the two lines refer to the serveur proxy on which verra' instradato the traffic in order to exit on Internet, in this example it is the serveur proxy of Vodafone in format IP DOOR. Also the logon towards our serveur on obvious door 443 passera', com'e', through this proxy. For less limitative logons (es: only doors sluices but no proxy, these directives go naturally removed).

Final configurations serveur: door 443 goes forwardata towards the machine where it is in execution the serveur OpenVPN (in this guide: 192.168.0.4). It goes shaped the firewall opportunely on the machine, if present.

Final configurations client: it goes shaped the firewall on the system. In this guide (relative to PocketPC and provider Vodafone) it goes shaped the logon: Start > Formulations > Logons > Advanced Logons > > “Selects Nets”, set up both parameters to: “Net Office”. As modems obviously used the apn “wap.omnitel.it” and not “web.omnitel.it”! IMPORTANT: It goes moreover set up manually the IP of virtual card “TAP: ” (Start > Formulations > Logons > WiFi > Cards of Net > “TAP1: ”), in this guide: 192.168.0.31 and default gateway of the router remote: 192.168.0.1 and DNS remote serveur: 192.168.0.1.

We launch finally () the serveur OpenVPN (skillful key on “server.ovpn” > “OpenVPN Start on this config rows”, if all it has gone well would have to be put in I listen in approximately 10 second ones.

We launch client the OpenVPN (skillful key on “client.ovpn” > “OpenVPN Start on this config rows”), that it would have to be connected to the serveur and being projected in the remote local net. Famous for PocketPC: to the installation of OpenVPN you apparira' the icona of a right PC low, to assign connection manager to the logon to use: tap on icona > utils > the Settings > Settings 2 > “Net Office” (Exclusive), you can use the same one icona in order launch the client: tap icona > start from config > client. In this way WAP logon GPRS would have to leave automatically when OpenVPN tentera' to be connected to the remote net. You can disabilitare from the configuration “Try to ping serveur on connect” poiche' you do not have some way to pingare your serveur before esservi connected.

If all you have gone according to plans (fortunate that you have at least this guide, than “sure works”, I does not sleep from three days in order to make the tests) now yours client is connected to the remote net and all the traffic is instradato through of it (any thing, also demands DNS), yours client therefore uscira' on Internet with the public IP of the ADSL and avra' full functionality of all the applicativi of net (web, email, voip, videoconferenza, remote desktop and quant'altro) all making to pass to the traffic through a single door (the local doors comes shunted correctly to the escape ofthe tunnel, and comes recreated of new to the “return”). It is from holding present that you will have also full access to your domestic net, therefore you will be able “to be annoying” on your local PC (to see film in streaming, to listen to music, collegarvi to the rooms of domestic videosorveglianza, etc).

TODO: to render this guide piu' exaustive, coming down in the details of the configuration, for the moment I do not have time (if someone wanted to take the briga to render it piu' compresibile, to him about it I would be pleasing). To render the configuration piu' snella: I use of the tunnelling with table routing created dynamically through OpenVPN directives. The advantage would be not to have to carry out bridge “a physicist” of the net cards on the serveur, without therefore compromising the architecture of the domestic net.

STEP2: installation of the serveur on router dedicated (OpenWRC) so as to not to have itself to worry of having a PC “always on” that make from serveur. Consultabile to this link: “OpenVPN Installation on Router Asus WL-500G”

--------------------------------------------------------------------------

In a previous post of mine i attached a diagram to be helped with the network configuration. Finally i filled out the diagram myself and here it is.

ATTENTION: I spent two days trying to find what the fault was on this..

If you use an wirelless interface as your primary interface on the server side instead of traditional wired NIC , and try to bridge it with the Virtual ethernet interface (TAP) is more likely the Network bridge you will create will have a faulty functioning due to the compatibility mode of those cards. For the solution refer to http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q302348&ID=KB;EN-US;Q302348&

Another interesting point is that if you try to make it work but you can't , try a soft reset to the ppc... (Microsoft OS...).

And remember to build the bridge First and then start Openvpn server.

That's for now..