[8525, TyTN, MDA Vario II, JasJam General] tetrakouna:
Ok after some days of experimentation with the proxy bypass story i finally managed to bypass it in both ways ((a) alikzmo's method putty-cygwin , (b) npole's method openvpn).

The conclusions are that:

with the (a) method the setup is easier (thanks to the excellent tutorial in the first page) BUT it is difficult sometimes even impossible to make all the internet applications running on phone to bypass the proxy.The email application described in the first page is in the "easy side".

with the (b) method the setup is a bit more difficult (no detailed explanations in this topic).BUT if you manage to get this work then 80% of your phone's applications will work INSTANTLY. Hopefully Npole has more detailed explanations in the url: http://arctic-things.blogspot.com/2008/01/wap-openvnp-adsl-internet.html but it is in italian language that i dont understand so i post here the explanation translated in english (via systran :-()...it helped me although the translation is awfull..

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

Guide to the creation of a Tunnel VPN for remote logons firewallate/nattate aka “Like you bypasso the proxy”. Rev.c (update 17/01/2008)

by ARCTiC -

Premised 1: to go around the limitations of a net of third parts could violare policy and the TOS of the manager of the net.

Premised 2: the following guide previews a sure preparation and acquaintance, is not for neophytes, the operations to complete is not complex, but you could trovarvi in difficolta' in points little clear (or not explained at all perche' given for discounted) and not to be able piu' to continue, this could compromise the functionalities of net of your domestic PC and of that remote (no logon to Internet).

To what it serves?

The “tunnel” serves to go around the limitations taxes from the service provider (net under NAT, doors TCP “sluices”), instradando the Internet traffic towards an external gateway. Our remote device will become therefore a client of a connected net to Internet through “a not filtered” public address and sara'.

How it works?

The tunnel is made up of two points, client (that it is the remote device, in this guide our PocketPC), and the serveur (than in this guide sara' our PC of house/office connected to Internet through router an ADSL). The logon happens through OpenVPN (to freeware: www.openvpn.net) in configuration client for the mobile phone, and in serveur-bridged configuration for the fixed PC.

Necessary instruments:

- A connected machine physically to Internet with I KNOW that it allows the installation of OpenVPN (es: Windows, Linux). In this guide the installation and the configuration avverra' on a machine Windows XP Professional.

- An other machine with the same characteristics that functions from “client”. In this guide verra' used a PocketPC with Windows Mobile 6 (HTC P3650).

- The OpenVPN software.

- “A not narrow” Internet logon for the serveur. In this guide verra' used an ADSL Alice 7mbit.

- “A narrow” Internet logon for the client. In this guide verra' used a logon Vodafone WAP Internet (rate 9 euros).

Naturally the instruments listed over are “generic”, are possible to use any Internet logon for the serveur, thus as the guide is adaptable to other managers furnish (with the due adjustments), not being able to make the moment an exaustive guide has preferred to concentrate to me in particular on a configuration. Holding moreover present that the setup demands a minimum of acquaintance of the operation of a net, confido that who is interested this guide sapra' to modify the formulations second own requirements.

Like explained in the introduction: this is not guide “step-step”, therefore me soffermero' on the relative explanation to the installation of the software (in net is not present numerous guides), but passero' directly to the explanation of the configuration of the net and OpenVPN (than finalizzera' in the preparation of the files of configuration).

IP and subnet used (the IP and the subnet is obviously those of my net, goes therefore adapted to yours):

Public IP of the serveur: myip.dyndns.org (is indispensable to use a service of publication IP if the IP, as in the majority of the cases, is not static; I send back to you to www.dyndns.org for the relative configuration)

Physical IP of router/the gateway on the domestic net: 192.168.0.1

Physical IP of the serveur: 192.168.0.3 (after the bridging, to see after)

Physical IP of the client remote: 192.168.0.31 (to notice that it is on the same one sottorete)

Installation and Configuration:

- We install OpenVPN on the serveur;

Al term of the installation verra' created a card of “virtual” net (TAP), rinominiamola “OpenVPN” for comodita'. We select it with to the card of physical net of our PC (selecting them both with the mouse or adding holding them held key CTRL), with both the cards of net selected, we choose from the menu (skillful key) > “Logons with bridging”. Created Verra' a new adapter. To this point bridge diverra' the only controlable member of the net, assegnamo to the same (key destor > proprieta' > Protocol TCP/IP) an IP static (in this 192.168.0.4 guide) with 255.255.255.0 subnet mask, default gateway (in my case the router: 192.168.0.1) and DNS (in my case use the router like serveur DNS, therefore always: 192.168.0.1).

- We create the necessary keys for net VPN. This passage is not essential but highly recommendable! Moreover this guide makes uses of the keys, therefore in the event she is not wanted to be used, the files of configuration go opportunely modified. For to the creation I send back the official guide of OpenVPN, the instruments for their creation are found in the folder “easy-rsa” of OpenVPN (after the installation). At the end we will have 7 files (between certificates and keys), than I have rinominato in this way:

ca.crt

ta.key

server.crt

server.key

client.crt

client.key

dh1024.pem

we copy them in the directory “config” of OpenVPN on the serveur.

- We install OpenVPN on the client;

Al term in the installation (as we have made previously for the bridge) we assign to the card of virtual net as soon as created (in Windows Mobile 6: Start > Formulations > Logons > WiFi > Cards of Net > TAP1:) a static IP (in my case: 192.168.0.31 subnet 255.255.255.0) and serveur DNS (in my case the router of the remote net: 192.168.0.1). Attention the IP must belong to the same one sottorete of the remote net.

- We copy in also in directory “config” of client the certificates and the keys previously created: ca.crt, ca.key, client.crt, client.key, ta.key.

We now go to create the files of OpenVPN configuration for the serveur (server.ovpn) and the client (client.ovpn). I have preferred to insert them in this guide “near” so that they are immediately confrontabili.

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

proto tcp

port 443

dev tap

dev-node OpenVPN # is the name of the TAP *non of the bridge! *

ca ca.crt

CERT server.crt

key server.key

dh dh1024.pem

#tls-auth ta.key 0 # remmata, seems to give problems on PocketPC

ifconfig-pool-persist ipp.txt

serveur-bridge 192.168.0.4 255.255.255.0 192.168.0.31 192.168.0.41

push “dhcp-option DNS 192.168.0.1”

keepalive 10 120

comp-lzo

cipher AES-256-CBC

max-clients 10

persist-key

persist-tun

#status openvpn-status.log # only for debug

#verb 3 # only for debug

to be continued..