http://wiki.webos-internals.org/api.php?action=feedcontributions&user=Papa4narchia&feedformat=atomWebOS Internals - User contributions [en]2024-03-29T11:00:20ZUser contributionsMediaWiki 1.35.1http://wiki.webos-internals.org/index.php?title=Tutorials_Linux_DDNS_Update_Client_INADYN&diff=11626Tutorials Linux DDNS Update Client INADYN2010-09-30T16:00:26Z<p>Papa4narchia: /* Configuration of inadyn service */</p>
<hr />
<div>The Dynamic DNS client [http://linux.die.net/man/8/inadyn INADYN] is well used around the world. It is typically found on OpenWRT, DD-WRT Routers, and now can be on your Palm Pre. The INADYN service maintain your IP address in relation to the DNS hosting of your choice.<br />
This should help friends reach services you may run in the future. Services such as Dropbear, lighttpd and SFTP. It's assumed that firewall configuration on WiFi connections will need attention.<br />
<br />
Authentication through DNS matching can now be achieved.<br />
<br />
[http://www.dd-wrt.com/wiki/index.php/DDNS_-_How_to_setup_Custom_DDNS_settings_using_embedded_inadyn_-_HOWTO Configuration details for DDNS services listed below]:<br />
*[http://www.dyndns.com dyndns]<br />
*[http://www.easydns.com easydns]<br />
*[http://freedns.afraid.org afraid]<br />
*[http://www.no-ip.com no-ip]<br />
*[http://www.tzo.com tzo]<br />
*[http://www.zoneedit.com zoneedit]<br />
*[http://www.ChangeIP.com changeip]<br />
*[http://www.regfish.de regfish]<br />
*[http://www.dnsomatic.com dnsomatic]<br />
<br />
Below are simple get-to syntax & conf examples.<br />
<br />
==Installing inadyn backend service==<br />
<pre><nowiki><br />
/opt/bin/ipkg-opt update<br />
/opt/bin/ipkg-opt install inadyn<br />
</nowiki></pre><br />
<br />
==Configuration of inadyn service==<br />
The available options of inadyn are documented on the website in the [http://www.inatech.eu/inadyn/readme.html readme]. All options can be given via the commandline (directly in the upstart script, or via a dedicated configuration file.)<br><br />
The following is a sample configuration for inadyn to update a host under a freedns.afraid.org account. Adapt this for your dns service.<br />
'''/var/opt/etc/inadyn.conf'''<br />
<pre><nowiki><br />
dyndns_system default@freedns.afraid.org<br />
alias palmpre.evilvho.st<br />
dyndns_server_name freedns.afraid.org<br />
dyndns_server_url /dynamic/update.php?**<inserted afraid.org hash here>**<br />
update_period_sec 400<br />
verbose 0<br />
</nowiki></pre><br />
The following is a sample call of inadyn on the commandline, providing options for No-IP.com:<br />
<pre><nowiki><br />
inadyn --dyndns_system default@no-ip.com -u <your no-ip account> -p <your no-ip password> -a <the no-ip host you want to update><br />
</nowiki></pre><br />
'''Note'''<br><br />
WiFi (eth0) may/will override Evdo (ppp0) DNS settings with the above code. Services on <1024 may/will be firewalled. However if UPnP is enabled we can utilize //libupnp// (The Universal Plug and Play (UPnP) SDK for Linux provides support for building UPnP-compliant control points, devices, and bridges)<br />
==Running inadyn==<br />
See [[Tutorials_Linux_DDNS_Update_Client_wget]] if your dynamic DNS supports URL based updates (i.e. freedns.afraid.org) to ensure updates are always with your device's radio IP. This method also doesn't require an always-on daemon, and updates only when your IP changes.<br />
===Alternative 1: run inadyn in the background upon system start===<br />
The following is a sample upstart script to run inadyn on system start:<br />
'''/etc/event.d/webos-inadyn'''<br />
<pre><nowiki><br />
description "inadyn Daemon for WebOS"<br />
author "oc80z"<br />
start on started<br />
nice 5<br />
respawn<br />
exec /opt/bin/inadyn --input_file /var/opt/etc/inadyn.conf<br />
</nowiki></pre><br />
===Alternative 2: run inadyn when your ppp0 (3G) IP changes===<br />
If you want to only run updates with inadyn when 3G (EVDO, UMTS ..) connects, you can use the --iterations option, and set it up like the previous method which will keep the memory free when it's not updating. If you do this, make sure to turn off the auto start described above in Alternative 1 by removing /etc/event.d/webos-inadyn.<br />
<br />
Add a script to /etc/ppp/ip-up.d called 09update-ddns. Here are the contents of that /etc/ppp/ip-up.d/09update-ddns:<br />
<pre><nowiki><br />
#!/bin/sh<br />
/opt/bin/inadyn --input_file /var/opt/etc/inadyn.conf --iterations 1 > /dev/null 2>&1 || /bin/true<br />
</nowiki></pre><br />
<br />
Make this script executable:<br />
<pre><nowiki><br />
chmod 755 /etc/ppp/ip-up.d/09update-ddns<br />
</nowiki></pre></div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=Tutorials_Linux_DDNS_Update_Client_INADYN&diff=11624Tutorials Linux DDNS Update Client INADYN2010-09-30T15:55:57Z<p>Papa4narchia: /* Configuration of inadyn service */</p>
<hr />
<div>The Dynamic DNS client [http://linux.die.net/man/8/inadyn INADYN] is well used around the world. It is typically found on OpenWRT, DD-WRT Routers, and now can be on your Palm Pre. The INADYN service maintain your IP address in relation to the DNS hosting of your choice.<br />
This should help friends reach services you may run in the future. Services such as Dropbear, lighttpd and SFTP. It's assumed that firewall configuration on WiFi connections will need attention.<br />
<br />
Authentication through DNS matching can now be achieved.<br />
<br />
[http://www.dd-wrt.com/wiki/index.php/DDNS_-_How_to_setup_Custom_DDNS_settings_using_embedded_inadyn_-_HOWTO Configuration details for DDNS services listed below]:<br />
*[http://www.dyndns.com dyndns]<br />
*[http://www.easydns.com easydns]<br />
*[http://freedns.afraid.org afraid]<br />
*[http://www.no-ip.com no-ip]<br />
*[http://www.tzo.com tzo]<br />
*[http://www.zoneedit.com zoneedit]<br />
*[http://www.ChangeIP.com changeip]<br />
*[http://www.regfish.de regfish]<br />
*[http://www.dnsomatic.com dnsomatic]<br />
<br />
Below are simple get-to syntax & conf examples.<br />
<br />
==Installing inadyn backend service==<br />
<pre><nowiki><br />
/opt/bin/ipkg-opt update<br />
/opt/bin/ipkg-opt install inadyn<br />
</nowiki></pre><br />
<br />
==Configuration of inadyn service==<br />
The available options of inadyn are documented on the website in the [http://www.inatech.eu/inadyn/readme.html readme]. All options can be given via the commandline (directly in the upstart script, or via a dedicated configuration file.)<br><br />
The following is a sample configuration for inadyn to update a host under a freedns.afraid.org account. Adapt this for your dns service.<br />
'''/var/opt/etc/inadyn.conf'''<br />
<pre><nowiki><br />
dyndns_system default@freedns.afraid.org<br />
alias palmpre.evilvho.st<br />
dyndns_server_name freedns.afraid.org<br />
dyndns_server_url /dynamic/update.php?**<inserted afraid.org hash here>**<br />
update_period_sec 400<br />
verbose 0<br />
</nowiki></pre><br />
The following is a sample call of inadyn on the commandline, providing options for No-IP.com:<br />
<pre><nowiki><br />
inadyn --dyndns_system default@no-ip.com -u <your no-ip account> -p <your no-ip password> -a <the no-ip host you want to update><br />
</nowiki></pre><br />
'''Note'''<br><br />
WiFi (eth0) may/will override Evdo (ppp0) DNS settings with the above code. Services on <1024 may/will be firewalled. However if UPnP is enabled we can utilize //libupnp// (The Universal Plug and Play (UPnP) SDK for Linux provides support for building UPnP-compliant control points, devices, and bridges)<br />
==Running inadyn==<br />
See [[Tutorials_Linux_DDNS_Update_Client_wget]] if your dynamic DNS supports URL based updates (i.e. freedns.afraid.org) to ensure updates are always with your device's radio IP. This method also doesn't require an always-on daemon, and updates only when your IP changes.<br />
===Alternative 1: run inadyn in the background upon system start===<br />
The following is a sample upstart script to run inadyn on system start:<br />
'''/etc/event.d/webos-inadyn'''<br />
<pre><nowiki><br />
description "inadyn Daemon for WebOS"<br />
author "oc80z"<br />
start on started<br />
nice 5<br />
respawn<br />
exec /opt/bin/inadyn --input_file /var/opt/etc/inadyn.conf<br />
</nowiki></pre><br />
<br />
If you want to only run updates with inadyn when the EVDO connects, you can use the --iterations option, and set it up like the previous method which will keep the memory free when it's not updating. <br />
<br />
You can do this by adding a script to /etc/ppp/ip-up.d called 09update-ddns. Here are the contents of that /etc/ppp/ip-up.d/09update-ddns:<br />
#!/bin/sh<br />
/opt/bin/inadyn --input_file /var/opt/etc/inadyn.conf --iterations 1 > /dev/null 2>&1 || /bin/true<br />
<br />
<br />
Make this script executable:<br />
chmod 755 /etc/ppp/ip-up.d/09update-ddns<br />
<br />
If you do this, make sure to turn off the auto start described above by removing /etc/event.d/webos-inadyn.</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=Tutorials_Linux_DDNS_Update_Client_INADYN&diff=11623Tutorials Linux DDNS Update Client INADYN2010-09-30T15:54:54Z<p>Papa4narchia: /* Installing inadyn backend service */</p>
<hr />
<div>The Dynamic DNS client [http://linux.die.net/man/8/inadyn INADYN] is well used around the world. It is typically found on OpenWRT, DD-WRT Routers, and now can be on your Palm Pre. The INADYN service maintain your IP address in relation to the DNS hosting of your choice.<br />
This should help friends reach services you may run in the future. Services such as Dropbear, lighttpd and SFTP. It's assumed that firewall configuration on WiFi connections will need attention.<br />
<br />
Authentication through DNS matching can now be achieved.<br />
<br />
[http://www.dd-wrt.com/wiki/index.php/DDNS_-_How_to_setup_Custom_DDNS_settings_using_embedded_inadyn_-_HOWTO Configuration details for DDNS services listed below]:<br />
*[http://www.dyndns.com dyndns]<br />
*[http://www.easydns.com easydns]<br />
*[http://freedns.afraid.org afraid]<br />
*[http://www.no-ip.com no-ip]<br />
*[http://www.tzo.com tzo]<br />
*[http://www.zoneedit.com zoneedit]<br />
*[http://www.ChangeIP.com changeip]<br />
*[http://www.regfish.de regfish]<br />
*[http://www.dnsomatic.com dnsomatic]<br />
<br />
Below are simple get-to syntax & conf examples.<br />
<br />
==Installing inadyn backend service==<br />
<pre><nowiki><br />
/opt/bin/ipkg-opt update<br />
/opt/bin/ipkg-opt install inadyn<br />
</nowiki></pre><br />
<br />
==Configuration of inadyn service==<br />
The available options of inadyn are documented on the website in the [http://www.inatech.eu/inadyn/readme.html readme]. All options can be given via the commandline (directly in the upstart script, or via a dedicated configuration file.)<br><br />
The following is a sample configuration for inadyn to update a host under a freedns.afraid.org account. Adapt this for your dns service.<br />
'''/var/opt/etc/inadyn.conf'''<br />
<pre><nowiki><br />
dyndns_system default@freedns.afraid.org<br />
alias palmpre.evilvho.st<br />
dyndns_server_name freedns.afraid.org<br />
dyndns_server_url /dynamic/update.php?**<inserted afraid.org hash here>**<br />
update_period_sec 400<br />
verbose 0<br />
</nowiki></pre><br />
The following is a sample call of inadyn on the commandline, providing options for No-IP.com:<br />
<pre><nowiki><br />
inadyn --dyndns_system default@no-ip.com -u <your no-ip account> -p <your no-ip password> -a <the no-ip host you want to update><br />
</nowiki></pre><br />
'''Note'''<br><br />
WiFi (eth0) may/will override Evdo (ppp0) DNS settings with the above code. Services on <1024 may/will be firewalled. However if UPnP is enabled we can utilize //libupnp// (The Universal Plug and Play (UPnP) SDK for Linux provides support for building UPnP-compliant control points, devices, and bridges)<br />
<br />
See [[Tutorials_Linux_DDNS_Update_Client_wget]] if your dynamic DNS supports URL based updates (i.e. freedns.afraid.org) to ensure updates are always with your device's radio IP. This method also doesn't require an always-on daemon, and updates only when your IP changes.<br />
<br />
===Alternative 2: run inadyn when ppp0 (3G) IP address changes===<br />
If you want to only run updates with inadyn when the EVDO connects, you can use the --iterations option, and set it up like the previous method which will keep the memory free when it's not updating. <br />
<br />
You can do this by adding a script to /etc/ppp/ip-up.d called 09update-ddns. Here are the contents of that /etc/ppp/ip-up.d/09update-ddns:<br />
#!/bin/sh<br />
/opt/bin/inadyn --input_file /var/opt/etc/inadyn.conf --iterations 1 > /dev/null 2>&1 || /bin/true<br />
<br />
<br />
Make this script executable:<br />
chmod 755 /etc/ppp/ip-up.d/09update-ddns<br />
<br />
If you do this, make sure to turn off the auto start described above by removing /etc/event.d/webos-inadyn.</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=Tutorials_Linux_DDNS_Update_Client_INADYN&diff=11622Tutorials Linux DDNS Update Client INADYN2010-09-30T15:54:27Z<p>Papa4narchia: /* Configuration of inadyn service */</p>
<hr />
<div>The Dynamic DNS client [http://linux.die.net/man/8/inadyn INADYN] is well used around the world. It is typically found on OpenWRT, DD-WRT Routers, and now can be on your Palm Pre. The INADYN service maintain your IP address in relation to the DNS hosting of your choice.<br />
This should help friends reach services you may run in the future. Services such as Dropbear, lighttpd and SFTP. It's assumed that firewall configuration on WiFi connections will need attention.<br />
<br />
Authentication through DNS matching can now be achieved.<br />
<br />
[http://www.dd-wrt.com/wiki/index.php/DDNS_-_How_to_setup_Custom_DDNS_settings_using_embedded_inadyn_-_HOWTO Configuration details for DDNS services listed below]:<br />
*[http://www.dyndns.com dyndns]<br />
*[http://www.easydns.com easydns]<br />
*[http://freedns.afraid.org afraid]<br />
*[http://www.no-ip.com no-ip]<br />
*[http://www.tzo.com tzo]<br />
*[http://www.zoneedit.com zoneedit]<br />
*[http://www.ChangeIP.com changeip]<br />
*[http://www.regfish.de regfish]<br />
*[http://www.dnsomatic.com dnsomatic]<br />
<br />
Below are simple get-to syntax & conf examples.<br />
<br />
==Installing inadyn backend service==<br />
<pre><nowiki><br />
/opt/bin/ipkg-opt update<br />
/opt/bin/ipkg-opt install inadyn<br />
</nowiki></pre><br />
<br />
The following is a sample upstart script to run inadyn on system start:<br />
'''/etc/event.d/webos-inadyn'''<br />
<pre><nowiki><br />
description "inadyn Daemon for WebOS"<br />
author "oc80z"<br />
start on started<br />
nice 5<br />
respawn<br />
exec /opt/bin/inadyn --input_file /var/opt/etc/inadyn.conf<br />
</nowiki></pre><br />
==Configuration of inadyn service==<br />
The available options of inadyn are documented on the website in the [http://www.inatech.eu/inadyn/readme.html readme]. All options can be given via the commandline (directly in the upstart script, or via a dedicated configuration file.)<br><br />
The following is a sample configuration for inadyn to update a host under a freedns.afraid.org account. Adapt this for your dns service.<br />
'''/var/opt/etc/inadyn.conf'''<br />
<pre><nowiki><br />
dyndns_system default@freedns.afraid.org<br />
alias palmpre.evilvho.st<br />
dyndns_server_name freedns.afraid.org<br />
dyndns_server_url /dynamic/update.php?**<inserted afraid.org hash here>**<br />
update_period_sec 400<br />
verbose 0<br />
</nowiki></pre><br />
The following is a sample call of inadyn on the commandline, providing options for No-IP.com:<br />
<pre><nowiki><br />
inadyn --dyndns_system default@no-ip.com -u <your no-ip account> -p <your no-ip password> -a <the no-ip host you want to update><br />
</nowiki></pre><br />
'''Note'''<br><br />
WiFi (eth0) may/will override Evdo (ppp0) DNS settings with the above code. Services on <1024 may/will be firewalled. However if UPnP is enabled we can utilize //libupnp// (The Universal Plug and Play (UPnP) SDK for Linux provides support for building UPnP-compliant control points, devices, and bridges)<br />
<br />
See [[Tutorials_Linux_DDNS_Update_Client_wget]] if your dynamic DNS supports URL based updates (i.e. freedns.afraid.org) to ensure updates are always with your device's radio IP. This method also doesn't require an always-on daemon, and updates only when your IP changes.<br />
<br />
===Alternative 2: run inadyn when ppp0 (3G) IP address changes===<br />
If you want to only run updates with inadyn when the EVDO connects, you can use the --iterations option, and set it up like the previous method which will keep the memory free when it's not updating. <br />
<br />
You can do this by adding a script to /etc/ppp/ip-up.d called 09update-ddns. Here are the contents of that /etc/ppp/ip-up.d/09update-ddns:<br />
#!/bin/sh<br />
/opt/bin/inadyn --input_file /var/opt/etc/inadyn.conf --iterations 1 > /dev/null 2>&1 || /bin/true<br />
<br />
<br />
Make this script executable:<br />
chmod 755 /etc/ppp/ip-up.d/09update-ddns<br />
<br />
If you do this, make sure to turn off the auto start described above by removing /etc/event.d/webos-inadyn.</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=Tutorials_Linux_DDNS_Update_Client_INADYN&diff=11620Tutorials Linux DDNS Update Client INADYN2010-09-30T15:46:54Z<p>Papa4narchia: </p>
<hr />
<div>The Dynamic DNS client [http://linux.die.net/man/8/inadyn INADYN] is well used around the world. It is typically found on OpenWRT, DD-WRT Routers, and now can be on your Palm Pre. The INADYN service maintain your IP address in relation to the DNS hosting of your choice.<br />
This should help friends reach services you may run in the future. Services such as Dropbear, lighttpd and SFTP. It's assumed that firewall configuration on WiFi connections will need attention.<br />
<br />
Authentication through DNS matching can now be achieved.<br />
<br />
[http://www.dd-wrt.com/wiki/index.php/DDNS_-_How_to_setup_Custom_DDNS_settings_using_embedded_inadyn_-_HOWTO Configuration details for DDNS services listed below]:<br />
*[http://www.dyndns.com dyndns]<br />
*[http://www.easydns.com easydns]<br />
*[http://freedns.afraid.org afraid]<br />
*[http://www.no-ip.com no-ip]<br />
*[http://www.tzo.com tzo]<br />
*[http://www.zoneedit.com zoneedit]<br />
*[http://www.ChangeIP.com changeip]<br />
*[http://www.regfish.de regfish]<br />
*[http://www.dnsomatic.com dnsomatic]<br />
<br />
Below are simple get-to syntax & conf examples.<br />
<br />
==Installing inadyn backend service==<br />
<pre><nowiki><br />
/opt/bin/ipkg-opt update<br />
/opt/bin/ipkg-opt install inadyn<br />
</nowiki></pre><br />
<br />
The following is a sample upstart script to run inadyn on system start:<br />
'''/etc/event.d/webos-inadyn'''<br />
<pre><nowiki><br />
description "inadyn Daemon for WebOS"<br />
author "oc80z"<br />
start on started<br />
nice 5<br />
respawn<br />
exec /opt/bin/inadyn --input_file /var/opt/etc/inadyn.conf<br />
</nowiki></pre><br />
==Configuration of inadyn service==<br />
The available options of inadyn are documented on the website in the [http://www.inatech.eu/inadyn/readme.html readme]. All options can be given via the commandline (directly in the upstart script, or via a dedicated configuration file.<br />
The following is a sample configuration for inadyn to update a host under a freedns.afraid.org account. Adapt this for your dns service.<br />
'''/var/opt/etc/inadyn.conf'''<br />
<pre><nowiki><br />
dyndns_system default@freedns.afraid.org<br />
alias palmpre.evilvho.st<br />
dyndns_server_name freedns.afraid.org<br />
dyndns_server_url /dynamic/update.php?**<inserted afraid.org hash here>**<br />
update_period_sec 400<br />
verbose 0<br />
</nowiki></pre><br />
THe following is a sample call of inadyn on the commandline, providing options for No-IP.com:<br />
<pre><nowiki><br />
inadyn --dyndns_system default@no-ip.com -u <your no-ip account> -p <your no-ip password> -a <the no-ip host you want to update><br />
</nowiki></pre><br />
Note: WiFi (eth0) may/will override Evdo (ppp0) DNS settings with the above code. Services on <1024 may/will be firewalled. However if UPnP is enabled we can utilize //libupnp// (The Universal Plug and Play (UPnP) SDK for Linux provides support for building UPnP-compliant control points, devices, and bridges)<br />
<br />
See [[Tutorials_Linux_DDNS_Update_Client_wget]] if your dynamic DNS supports URL based updates (i.e. freedns.afraid.org) to ensure updates are always with your device's radio IP. This method also doesn't require an always-on daemon, and updates only when your IP changes.<br />
<br />
===Make inadyn run whenever your ppp0 (EV-DO) IP address changes:===<br />
If you want to only run updates with inadyn when the EVDO connects, you can use the --iterations option, and set it up like the previous method which will keep the memory free when it's not updating. <br />
<br />
You can do this by adding a script to /etc/ppp/ip-up.d called 09update-ddns. Here are the contents of that /etc/ppp/ip-up.d/09update-ddns:<br />
#!/bin/sh<br />
/opt/bin/inadyn --input_file /var/opt/etc/inadyn.conf --iterations 1 > /dev/null 2>&1 || /bin/true<br />
<br />
<br />
Make this script executable:<br />
chmod 755 /etc/ppp/ip-up.d/09update-ddns<br />
<br />
If you do this, make sure to turn off the auto start described above by removing /etc/event.d/webos-inadyn.</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11610OpenVPN for Palm Pre2010-09-30T11:54:34Z<p>Papa4narchia: /* Further resources */</p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to another available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, openvpn is easily installable on your palm devices via ipkg. An application scenario could be to connect your Palm device via 3G to your home network, accessing data and services hosted by a NAS, for example.<br />
<br />
==OpenVPN client installation==<br />
To setup a connection to an available OpenVPN endpoint, you need the appropriate kernel module (tun.ko) on your Palm device and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN client configuration==<br />
OpenVPN is deployed quickly and easily. The [http://openvpn.net/ OpenVPN.net] website and source installations contain configuration scripts that can make OpenVPN connect to your home or work when WiFi is activated. The following excerpt assumes that you already have available the following things: <br />
*a certificate for yourself / your device (in the example, called palmpre.crt)<br />
*the issuing certificate authority (ca.crt)<br />
*a key-file (palmpre.key)<br />
*a client configuration for your Palm device (palmpre.ovpn)<br />
Be aware, that the abovementioned filenames are only examples. Most likely, you would create these files yourself.<br><br />
'''It is highly suggested that you make yourself familiar in creating your own keys (and certificates), in case you are not provided with from a very trusted source!'''<br> As you create certificates, keys, and certificate signing requests yourself, understand that only .key files should be kept confidential. .crt and .csr files can be sent over insecure channels such as plaintext email.You should never need to copy a .key file between computers. Normally each computer will have its own certificate/key pair.<br><br />
Have a look at the wiki [http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#Telnet_Management_Interface Setup optware OpenVPN on a NAS], giving you exact instructions how to. For easy key management, the package easy-rsa provides necessary tools. It is also available via optware and well documented on the OpenVPN website.<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
<br />
==Starting OpenVPN==<br />
For a first connection test, you should start openvpn on your Palm device allowing it to write to standard out. Thereby, you will be able to follow allong, if anything goes awry during the initialization sequence:<br />
<pre><nowiki><br />
openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
If it connects successfully , you could start it as a background task (adding &), redirecting output to /dev/null. (You could write an upstart script, see the example for the Hamachi VPN in the resources below.)<br />
<pre><nowiki><br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
</nowiki></pre><br />
<br />
==Testing connection==<br />
When testing access to your openvpn endpoint (server) from your Palm device, it can be benefitial if both can connect only via the openvpn tunnel (and not reach each other via an alternate route in your home network). The following scenario assumes, that a Palm device connects via openvpn to a private network (possibly your home network) from outside, using 3G (EVDO, UMTS). You can test this by turning off wifi and ssh to your Palm device using a Bluetooth PAN. See if your Palm device still has internet access over 3G, when turning off wifi. (While pinging google, drop wifi and monitor via SSH over Bluetooth PAN):<br />
<pre><nowiki><br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
</nowiki></pre><br />
If you ping IPs in your home network now (the openvpn endpoint/gateway or other IPs behind), traffic to your private network is routed through the encrypted tunnel:<br />
<pre><nowiki><br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
</nowiki></pre><br />
<br />
==OpenVPN IRC channel==<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]<br />
==Further resources==<br />
#[http://openvpn.net/ OpenVPN.net] The official website of OpenVPN. See the excellent Documentation! (Community software > Documentation > Howto)<br />
#[http://openvpn.net/easyrsa.html Easy-RSA] Key management tool for OpenVPN<br />
#[http://www.webos-internals.org/wiki/HamachiVPN Hamachi on Pre]. Use the popular, proprietary Hamachi for VPN on your Palm device.<br />
#[http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#OpenVPN_GUI Optware OpenVPN on a QNAP Nas] gives you a good example of a complete configuration.</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11609OpenVPN for Palm Pre2010-09-30T11:53:30Z<p>Papa4narchia: /* Further resources */</p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to another available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, openvpn is easily installable on your palm devices via ipkg. An application scenario could be to connect your Palm device via 3G to your home network, accessing data and services hosted by a NAS, for example.<br />
<br />
==OpenVPN client installation==<br />
To setup a connection to an available OpenVPN endpoint, you need the appropriate kernel module (tun.ko) on your Palm device and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN client configuration==<br />
OpenVPN is deployed quickly and easily. The [http://openvpn.net/ OpenVPN.net] website and source installations contain configuration scripts that can make OpenVPN connect to your home or work when WiFi is activated. The following excerpt assumes that you already have available the following things: <br />
*a certificate for yourself / your device (in the example, called palmpre.crt)<br />
*the issuing certificate authority (ca.crt)<br />
*a key-file (palmpre.key)<br />
*a client configuration for your Palm device (palmpre.ovpn)<br />
Be aware, that the abovementioned filenames are only examples. Most likely, you would create these files yourself.<br><br />
'''It is highly suggested that you make yourself familiar in creating your own keys (and certificates), in case you are not provided with from a very trusted source!'''<br> As you create certificates, keys, and certificate signing requests yourself, understand that only .key files should be kept confidential. .crt and .csr files can be sent over insecure channels such as plaintext email.You should never need to copy a .key file between computers. Normally each computer will have its own certificate/key pair.<br><br />
Have a look at the wiki [http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#Telnet_Management_Interface Setup optware OpenVPN on a NAS], giving you exact instructions how to. For easy key management, the package easy-rsa provides necessary tools. It is also available via optware and well documented on the OpenVPN website.<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
<br />
==Starting OpenVPN==<br />
For a first connection test, you should start openvpn on your Palm device allowing it to write to standard out. Thereby, you will be able to follow allong, if anything goes awry during the initialization sequence:<br />
<pre><nowiki><br />
openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
If it connects successfully , you could start it as a background task (adding &), redirecting output to /dev/null. (You could write an upstart script, see the example for the Hamachi VPN in the resources below.)<br />
<pre><nowiki><br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
</nowiki></pre><br />
<br />
==Testing connection==<br />
When testing access to your openvpn endpoint (server) from your Palm device, it can be benefitial if both can connect only via the openvpn tunnel (and not reach each other via an alternate route in your home network). The following scenario assumes, that a Palm device connects via openvpn to a private network (possibly your home network) from outside, using 3G (EVDO, UMTS). You can test this by turning off wifi and ssh to your Palm device using a Bluetooth PAN. See if your Palm device still has internet access over 3G, when turning off wifi. (While pinging google, drop wifi and monitor via SSH over Bluetooth PAN):<br />
<pre><nowiki><br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
</nowiki></pre><br />
If you ping IPs in your home network now (the openvpn endpoint/gateway or other IPs behind), traffic to your private network is routed through the encrypted tunnel:<br />
<pre><nowiki><br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
</nowiki></pre><br />
<br />
==OpenVPN IRC channel==<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]<br />
==Further resources==<br />
#[http://openvpn.net/ OpenVPN.net] The official website of OpenVPN. See the excellent Documentation! (Community software > Documentation > Howto)<br />
#[http://openvpn.net/index.php/open-source/documentation/miscellaneous/77-rsa-key-management.html Easy-RSA] Key management tool for OpenVPN<br />
#[http://www.webos-internals.org/wiki/HamachiVPN Hamachi on Pre]. Use the popular, proprietary Hamachi for VPN on your Palm device.<br />
#[http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#OpenVPN_GUI Optware OpenVPN on a QNAP Nas] gives you a good example of a complete configuration.</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11608OpenVPN for Palm Pre2010-09-30T11:52:49Z<p>Papa4narchia: /* Further resources */</p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to another available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, openvpn is easily installable on your palm devices via ipkg. An application scenario could be to connect your Palm device via 3G to your home network, accessing data and services hosted by a NAS, for example.<br />
<br />
==OpenVPN client installation==<br />
To setup a connection to an available OpenVPN endpoint, you need the appropriate kernel module (tun.ko) on your Palm device and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN client configuration==<br />
OpenVPN is deployed quickly and easily. The [http://openvpn.net/ OpenVPN.net] website and source installations contain configuration scripts that can make OpenVPN connect to your home or work when WiFi is activated. The following excerpt assumes that you already have available the following things: <br />
*a certificate for yourself / your device (in the example, called palmpre.crt)<br />
*the issuing certificate authority (ca.crt)<br />
*a key-file (palmpre.key)<br />
*a client configuration for your Palm device (palmpre.ovpn)<br />
Be aware, that the abovementioned filenames are only examples. Most likely, you would create these files yourself.<br><br />
'''It is highly suggested that you make yourself familiar in creating your own keys (and certificates), in case you are not provided with from a very trusted source!'''<br> As you create certificates, keys, and certificate signing requests yourself, understand that only .key files should be kept confidential. .crt and .csr files can be sent over insecure channels such as plaintext email.You should never need to copy a .key file between computers. Normally each computer will have its own certificate/key pair.<br><br />
Have a look at the wiki [http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#Telnet_Management_Interface Setup optware OpenVPN on a NAS], giving you exact instructions how to. For easy key management, the package easy-rsa provides necessary tools. It is also available via optware and well documented on the OpenVPN website.<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
<br />
==Starting OpenVPN==<br />
For a first connection test, you should start openvpn on your Palm device allowing it to write to standard out. Thereby, you will be able to follow allong, if anything goes awry during the initialization sequence:<br />
<pre><nowiki><br />
openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
If it connects successfully , you could start it as a background task (adding &), redirecting output to /dev/null. (You could write an upstart script, see the example for the Hamachi VPN in the resources below.)<br />
<pre><nowiki><br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
</nowiki></pre><br />
<br />
==Testing connection==<br />
When testing access to your openvpn endpoint (server) from your Palm device, it can be benefitial if both can connect only via the openvpn tunnel (and not reach each other via an alternate route in your home network). The following scenario assumes, that a Palm device connects via openvpn to a private network (possibly your home network) from outside, using 3G (EVDO, UMTS). You can test this by turning off wifi and ssh to your Palm device using a Bluetooth PAN. See if your Palm device still has internet access over 3G, when turning off wifi. (While pinging google, drop wifi and monitor via SSH over Bluetooth PAN):<br />
<pre><nowiki><br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
</nowiki></pre><br />
If you ping IPs in your home network now (the openvpn endpoint/gateway or other IPs behind), traffic to your private network is routed through the encrypted tunnel:<br />
<pre><nowiki><br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
</nowiki></pre><br />
<br />
==OpenVPN IRC channel==<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]<br />
==Further resources==<br />
#[http://openvpn.net/ OpenVPN.net] The official website of OpenVPN. See the excellent Documentation! (Community software > Documentation > Howto)<br />
#[http://openvpn.net/index.php/open-source/documentation/miscellaneous/77-rsa-key-management.html Easy-RSA| Key management tool for OpenVPN<br />
#[http://www.webos-internals.org/wiki/HamachiVPN Hamachi on Pre]. Use the popular, proprietary Hamachi for VPN on your Palm device.<br />
#[http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#OpenVPN_GUI Optware OpenVPN on a QNAP Nas] gives you a good example of a complete configuration.</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11607OpenVPN for Palm Pre2010-09-30T11:51:40Z<p>Papa4narchia: /* OpenVPN client configuration */</p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to another available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, openvpn is easily installable on your palm devices via ipkg. An application scenario could be to connect your Palm device via 3G to your home network, accessing data and services hosted by a NAS, for example.<br />
<br />
==OpenVPN client installation==<br />
To setup a connection to an available OpenVPN endpoint, you need the appropriate kernel module (tun.ko) on your Palm device and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN client configuration==<br />
OpenVPN is deployed quickly and easily. The [http://openvpn.net/ OpenVPN.net] website and source installations contain configuration scripts that can make OpenVPN connect to your home or work when WiFi is activated. The following excerpt assumes that you already have available the following things: <br />
*a certificate for yourself / your device (in the example, called palmpre.crt)<br />
*the issuing certificate authority (ca.crt)<br />
*a key-file (palmpre.key)<br />
*a client configuration for your Palm device (palmpre.ovpn)<br />
Be aware, that the abovementioned filenames are only examples. Most likely, you would create these files yourself.<br><br />
'''It is highly suggested that you make yourself familiar in creating your own keys (and certificates), in case you are not provided with from a very trusted source!'''<br> As you create certificates, keys, and certificate signing requests yourself, understand that only .key files should be kept confidential. .crt and .csr files can be sent over insecure channels such as plaintext email.You should never need to copy a .key file between computers. Normally each computer will have its own certificate/key pair.<br><br />
Have a look at the wiki [http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#Telnet_Management_Interface Setup optware OpenVPN on a NAS], giving you exact instructions how to. For easy key management, the package easy-rsa provides necessary tools. It is also available via optware and well documented on the OpenVPN website.<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
<br />
==Starting OpenVPN==<br />
For a first connection test, you should start openvpn on your Palm device allowing it to write to standard out. Thereby, you will be able to follow allong, if anything goes awry during the initialization sequence:<br />
<pre><nowiki><br />
openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
If it connects successfully , you could start it as a background task (adding &), redirecting output to /dev/null. (You could write an upstart script, see the example for the Hamachi VPN in the resources below.)<br />
<pre><nowiki><br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
</nowiki></pre><br />
<br />
==Testing connection==<br />
When testing access to your openvpn endpoint (server) from your Palm device, it can be benefitial if both can connect only via the openvpn tunnel (and not reach each other via an alternate route in your home network). The following scenario assumes, that a Palm device connects via openvpn to a private network (possibly your home network) from outside, using 3G (EVDO, UMTS). You can test this by turning off wifi and ssh to your Palm device using a Bluetooth PAN. See if your Palm device still has internet access over 3G, when turning off wifi. (While pinging google, drop wifi and monitor via SSH over Bluetooth PAN):<br />
<pre><nowiki><br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
</nowiki></pre><br />
If you ping IPs in your home network now (the openvpn endpoint/gateway or other IPs behind), traffic to your private network is routed through the encrypted tunnel:<br />
<pre><nowiki><br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
</nowiki></pre><br />
<br />
==OpenVPN IRC channel==<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]<br />
==Further resources==<br />
#[http://openvpn.net/ OpenVPN.net] The official website of OpenVPN. See the excellent Documentation! (Community software > Documentation > Howto)<br />
#[http://www.webos-internals.org/wiki/HamachiVPN Hamachi on Pre]. Use the popular, proprietary Hamachi for VPN on your Palm device.<br />
#[http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#OpenVPN_GUI Optware OpenVPN on a QNAP Nas] gives you a good example of a complete configuration.</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11606OpenVPN for Palm Pre2010-09-30T11:50:33Z<p>Papa4narchia: </p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to another available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, openvpn is easily installable on your palm devices via ipkg. An application scenario could be to connect your Palm device via 3G to your home network, accessing data and services hosted by a NAS, for example.<br />
<br />
==OpenVPN client installation==<br />
To setup a connection to an available OpenVPN endpoint, you need the appropriate kernel module (tun.ko) on your Palm device and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN client configuration==<br />
OpenVPN is deployed quickly and easily. The [http://openvpn.net/ OpenVPN.net] website and source installations contain configuration scripts that can make OpenVPN connect to your home or work when WiFi is activated. The following excerpt assumes that you already have available the following things: <br />
*a certificate for yourself / your device (in the example, called palmpre.crt)<br />
*the issuing certificate authority (ca.crt)<br />
*a key-file (palmpre.key)<br />
*a client configuration for your Palm device (palmpre.ovpn)<br />
Be aware, that the abovementioned filenames are only examples. Most likely, you would create these files yourself.<br><br />
'''It is highly suggested that you make yourself familiar in creating your own keys (and certificates), in case you are not provided with from a very trusted source!'''<br> As you create certificates, keys, and certificate signing requests yourself, understand that only .key files should be kept confidential. .crt and .csr files can be sent over insecure channels such as plaintext email.You should never need to copy a .key file between computers. Normally each computer will have its own certificate/key pair.<br><br />
Have a look at the wiki [http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#Telnet_Management_Interface Setup optware OpenVPN on a NAS], giving you exact instructions how to.<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
<br />
==Starting OpenVPN==<br />
For a first connection test, you should start openvpn on your Palm device allowing it to write to standard out. Thereby, you will be able to follow allong, if anything goes awry during the initialization sequence:<br />
<pre><nowiki><br />
openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
If it connects successfully , you could start it as a background task (adding &), redirecting output to /dev/null. (You could write an upstart script, see the example for the Hamachi VPN in the resources below.)<br />
<pre><nowiki><br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
</nowiki></pre><br />
<br />
==Testing connection==<br />
When testing access to your openvpn endpoint (server) from your Palm device, it can be benefitial if both can connect only via the openvpn tunnel (and not reach each other via an alternate route in your home network). The following scenario assumes, that a Palm device connects via openvpn to a private network (possibly your home network) from outside, using 3G (EVDO, UMTS). You can test this by turning off wifi and ssh to your Palm device using a Bluetooth PAN. See if your Palm device still has internet access over 3G, when turning off wifi. (While pinging google, drop wifi and monitor via SSH over Bluetooth PAN):<br />
<pre><nowiki><br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
</nowiki></pre><br />
If you ping IPs in your home network now (the openvpn endpoint/gateway or other IPs behind), traffic to your private network is routed through the encrypted tunnel:<br />
<pre><nowiki><br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
</nowiki></pre><br />
<br />
==OpenVPN IRC channel==<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]<br />
==Further resources==<br />
#[http://openvpn.net/ OpenVPN.net] The official website of OpenVPN. See the excellent Documentation! (Community software > Documentation > Howto)<br />
#[http://www.webos-internals.org/wiki/HamachiVPN Hamachi on Pre]. Use the popular, proprietary Hamachi for VPN on your Palm device.<br />
#[http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#OpenVPN_GUI Optware OpenVPN on a QNAP Nas] gives you a good example of a complete configuration.</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11578OpenVPN for Palm Pre2010-09-27T20:13:00Z<p>Papa4narchia: /* Further Resources */</p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to another available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, openvpn is easily installable on your palm devices via ipkg. An application scenario could be to connect your Palm device via 3G to your home network, accessing data and services hosted by a NAS, for example.<br />
<br />
==OpenVPN client installation==<br />
To setup a connection to an available OpenVPN endpoint, you need the appropriate kernel module (tun.ko) on your Palm device and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN client configuration==<br />
OpenVPN is deployed quickly and easily. The [http://openvpn.net/ OpenVPN.net] website and source installations contain scripts that can make OpenVPN connect to your home or work when WiFi is activated. The following excerpt assumes that you already have available the following things: <br />
*a certificate for yourself / your device (in the example, called palmpre.crt)<br />
*the issuing certificate authority (ca.crt)<br />
*a key-file (palmpre.key)<br />
*a client configuration for your Palm device (palmpre.ovpn)<br />
Be aware, that the abovementioned filenames are only examples. Most likely, you would create these files yourself.<br><br />
'''It is highly suggested that you make yourself familiar in creating your own keys (and certificates), in case you are not provided with from a very trusted source!'''<br><br />
Have a look at the wiki [http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#Telnet_Management_Interface Setup optware OpenVPN on a NAS], giving you exact instructions how to.<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
<br />
==Starting OpenVPN==<br />
For a first connection test, you should start openvpn on your Palm device allowing it to write to standard out. Thereby, you will be able to follow allong, if anything goes awry during the initialization sequence:<br />
<pre><nowiki><br />
openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
If it connects successfully , you could start it as a background task (adding &), redirecting output to /dev/null. (You could write an upstart script, see the example for the Hamachi VPN in the resources below.)<br />
<pre><nowiki><br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
</nowiki></pre><br />
<br />
==Testing connection==<br />
When testing access to your openvpn endpoint (server) from your Palm device, it can be benefitial if both can connect only via the openvpn tunnel (and not reach each other via an alternate route in your home network). The following scenario assumes, that a Palm device connects via openvpn to a private network (possibly your home network) from outside, using 3G (EVDO, UMTS). You can test this by turning off wifi and ssh to your Palm device using a Bluetooth PAN. See if your Palm device still has internet access over 3G, when turning off wifi. (While pinging google, drop wifi and monitor via SSH over Bluetooth PAN):<br />
<pre><nowiki><br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
</nowiki></pre><br />
If you ping IPs in your home network now (the openvpn endpoint/gateway or other IPs behind), traffic to your private network is routed through the encrypted tunnel:<br />
<pre><nowiki><br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
</nowiki></pre><br />
<br />
==OpenVPN IRC channel==<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]<br />
==Further resources==<br />
#[http://openvpn.net/ OpenVPN.net] The official website of OpenVPN. See the excellent Documentation! (Community software > Documentation > Howto)<br />
#[http://www.webos-internals.org/wiki/HamachiVPN Hamachi on Pre]. Use the popular, proprietary Hamachi for VPN on your Palm device.<br />
#[http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#OpenVPN_GUI Optware OpenVPN on a QNAP Nas] gives you a good example of a complete configuration.</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11577OpenVPN for Palm Pre2010-09-27T20:12:40Z<p>Papa4narchia: /* Further Resources */</p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to another available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, openvpn is easily installable on your palm devices via ipkg. An application scenario could be to connect your Palm device via 3G to your home network, accessing data and services hosted by a NAS, for example.<br />
<br />
==OpenVPN client installation==<br />
To setup a connection to an available OpenVPN endpoint, you need the appropriate kernel module (tun.ko) on your Palm device and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN client configuration==<br />
OpenVPN is deployed quickly and easily. The [http://openvpn.net/ OpenVPN.net] website and source installations contain scripts that can make OpenVPN connect to your home or work when WiFi is activated. The following excerpt assumes that you already have available the following things: <br />
*a certificate for yourself / your device (in the example, called palmpre.crt)<br />
*the issuing certificate authority (ca.crt)<br />
*a key-file (palmpre.key)<br />
*a client configuration for your Palm device (palmpre.ovpn)<br />
Be aware, that the abovementioned filenames are only examples. Most likely, you would create these files yourself.<br><br />
'''It is highly suggested that you make yourself familiar in creating your own keys (and certificates), in case you are not provided with from a very trusted source!'''<br><br />
Have a look at the wiki [http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#Telnet_Management_Interface Setup optware OpenVPN on a NAS], giving you exact instructions how to.<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
<br />
==Starting OpenVPN==<br />
For a first connection test, you should start openvpn on your Palm device allowing it to write to standard out. Thereby, you will be able to follow allong, if anything goes awry during the initialization sequence:<br />
<pre><nowiki><br />
openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
If it connects successfully , you could start it as a background task (adding &), redirecting output to /dev/null. (You could write an upstart script, see the example for the Hamachi VPN in the resources below.)<br />
<pre><nowiki><br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
</nowiki></pre><br />
<br />
==Testing connection==<br />
When testing access to your openvpn endpoint (server) from your Palm device, it can be benefitial if both can connect only via the openvpn tunnel (and not reach each other via an alternate route in your home network). The following scenario assumes, that a Palm device connects via openvpn to a private network (possibly your home network) from outside, using 3G (EVDO, UMTS). You can test this by turning off wifi and ssh to your Palm device using a Bluetooth PAN. See if your Palm device still has internet access over 3G, when turning off wifi. (While pinging google, drop wifi and monitor via SSH over Bluetooth PAN):<br />
<pre><nowiki><br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
</nowiki></pre><br />
If you ping IPs in your home network now (the openvpn endpoint/gateway or other IPs behind), traffic to your private network is routed through the encrypted tunnel:<br />
<pre><nowiki><br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
</nowiki></pre><br />
<br />
==OpenVPN IRC channel==<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]<br />
==Further Resources==<br />
#[http://openvpn.net/ OpenVPN.net] The official website of OpenVPN. See the excellent Documentation! (Community software > Documentation > Howto)<br />
#[http://www.webos-internals.org/wiki/HamachiVPN Hamachi on Pre]. Use the popular, proprietary Hamachi for VPN on your Palm device.<br />
#[http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#OpenVPN_GUI Optware OpenVPN on a QNAP Nas] gives you a good example of a complete configuration.</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11576OpenVPN for Palm Pre2010-09-27T20:10:37Z<p>Papa4narchia: /* OpenVPN client configuration */</p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to another available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, openvpn is easily installable on your palm devices via ipkg. An application scenario could be to connect your Palm device via 3G to your home network, accessing data and services hosted by a NAS, for example.<br />
<br />
==OpenVPN client installation==<br />
To setup a connection to an available OpenVPN endpoint, you need the appropriate kernel module (tun.ko) on your Palm device and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN client configuration==<br />
OpenVPN is deployed quickly and easily. The [http://openvpn.net/ OpenVPN.net] website and source installations contain scripts that can make OpenVPN connect to your home or work when WiFi is activated. The following excerpt assumes that you already have available the following things: <br />
*a certificate for yourself / your device (in the example, called palmpre.crt)<br />
*the issuing certificate authority (ca.crt)<br />
*a key-file (palmpre.key)<br />
*a client configuration for your Palm device (palmpre.ovpn)<br />
Be aware, that the abovementioned filenames are only examples. Most likely, you would create these files yourself.<br><br />
'''It is highly suggested that you make yourself familiar in creating your own keys (and certificates), in case you are not provided with from a very trusted source!'''<br><br />
Have a look at the wiki [http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#Telnet_Management_Interface Setup optware OpenVPN on a NAS], giving you exact instructions how to.<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
<br />
==Starting OpenVPN==<br />
For a first connection test, you should start openvpn on your Palm device allowing it to write to standard out. Thereby, you will be able to follow allong, if anything goes awry during the initialization sequence:<br />
<pre><nowiki><br />
openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
If it connects successfully , you could start it as a background task (adding &), redirecting output to /dev/null. (You could write an upstart script, see the example for the Hamachi VPN in the resources below.)<br />
<pre><nowiki><br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
</nowiki></pre><br />
<br />
==Testing connection==<br />
When testing access to your openvpn endpoint (server) from your Palm device, it can be benefitial if both can connect only via the openvpn tunnel (and not reach each other via an alternate route in your home network). The following scenario assumes, that a Palm device connects via openvpn to a private network (possibly your home network) from outside, using 3G (EVDO, UMTS). You can test this by turning off wifi and ssh to your Palm device using a Bluetooth PAN. See if your Palm device still has internet access over 3G, when turning off wifi. (While pinging google, drop wifi and monitor via SSH over Bluetooth PAN):<br />
<pre><nowiki><br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
</nowiki></pre><br />
If you ping IPs in your home network now (the openvpn endpoint/gateway or other IPs behind), traffic to your private network is routed through the encrypted tunnel:<br />
<pre><nowiki><br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
</nowiki></pre><br />
<br />
==OpenVPN IRC channel==<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]<br />
==Further Resources==<br />
#[http://www.webos-internals.org/wiki/HamachiVPN Hamachi on Pre]. Use the popular, proprietary Hamachi for VPN on your Palm device.<br />
#[http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#OpenVPN_GUI Optware OpenVPN on a QNAP Nas] gives you a good example of a complete configuration.</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11575OpenVPN for Palm Pre2010-09-27T20:10:18Z<p>Papa4narchia: /* OpenVPN client configuration */</p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to another available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, openvpn is easily installable on your palm devices via ipkg. An application scenario could be to connect your Palm device via 3G to your home network, accessing data and services hosted by a NAS, for example.<br />
<br />
==OpenVPN client installation==<br />
To setup a connection to an available OpenVPN endpoint, you need the appropriate kernel module (tun.ko) on your Palm device and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN client configuration==<br />
OpenVPN is deployed quickly and easily. The [http://openvpn.net/ | OpenVPN.net] website and source installations contain scripts that can make OpenVPN connect to your home or work when WiFi is activated. The following excerpt assumes that you already have available the following things: <br />
*a certificate for yourself / your device (in the example, called palmpre.crt)<br />
*the issuing certificate authority (ca.crt)<br />
*a key-file (palmpre.key)<br />
*a client configuration for your Palm device (palmpre.ovpn)<br />
Be aware, that the abovementioned filenames are only examples. Most likely, you would create these files yourself.<br><br />
'''It is highly suggested that you make yourself familiar in creating your own keys (and certificates), in case you are not provided with from a very trusted source!'''<br><br />
Have a look at the wiki [http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#Telnet_Management_Interface Setup optware OpenVPN on a NAS], giving you exact instructions how to.<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
<br />
==Starting OpenVPN==<br />
For a first connection test, you should start openvpn on your Palm device allowing it to write to standard out. Thereby, you will be able to follow allong, if anything goes awry during the initialization sequence:<br />
<pre><nowiki><br />
openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
If it connects successfully , you could start it as a background task (adding &), redirecting output to /dev/null. (You could write an upstart script, see the example for the Hamachi VPN in the resources below.)<br />
<pre><nowiki><br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
</nowiki></pre><br />
<br />
==Testing connection==<br />
When testing access to your openvpn endpoint (server) from your Palm device, it can be benefitial if both can connect only via the openvpn tunnel (and not reach each other via an alternate route in your home network). The following scenario assumes, that a Palm device connects via openvpn to a private network (possibly your home network) from outside, using 3G (EVDO, UMTS). You can test this by turning off wifi and ssh to your Palm device using a Bluetooth PAN. See if your Palm device still has internet access over 3G, when turning off wifi. (While pinging google, drop wifi and monitor via SSH over Bluetooth PAN):<br />
<pre><nowiki><br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
</nowiki></pre><br />
If you ping IPs in your home network now (the openvpn endpoint/gateway or other IPs behind), traffic to your private network is routed through the encrypted tunnel:<br />
<pre><nowiki><br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
</nowiki></pre><br />
<br />
==OpenVPN IRC channel==<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]<br />
==Further Resources==<br />
#[http://www.webos-internals.org/wiki/HamachiVPN Hamachi on Pre]. Use the popular, proprietary Hamachi for VPN on your Palm device.<br />
#[http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#OpenVPN_GUI Optware OpenVPN on a QNAP Nas] gives you a good example of a complete configuration.</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11574OpenVPN for Palm Pre2010-09-27T20:04:00Z<p>Papa4narchia: /* Testing connection */</p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to another available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, openvpn is easily installable on your palm devices via ipkg. An application scenario could be to connect your Palm device via 3G to your home network, accessing data and services hosted by a NAS, for example.<br />
<br />
==OpenVPN client installation==<br />
To setup a connection to an available OpenVPN endpoint, you need the appropriate kernel module (tun.ko) on your Palm device and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN client configuration==<br />
OpenVPN is deployed quickly and easily. The OpenVPN.net website and source installations contain scripts that can make OpenVPN connect to your home or work when WiFi is activated. The following excerpt assumes that you already have available the following things: <br />
*a certificate for yourself / your device (in the example, called palmpre.crt)<br />
*the issuing certificate authority (ca.crt)<br />
*a key-file (palmpre.key)<br />
It is highly suggested that you make yourself familiar in creating your own keys (and certificates), in case you are not provided with from a trusted source. Have a look at the following wiki page, explaining in detail how to [http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#Telnet_Management_Interface Setup optware OpenVPN on a NAS], giving you exact instructions how to setup an endpoint you could connect your Palm device to.<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
==Starting OpenVPN==<br />
For a first connection test, you should start openvpn on your Palm device allowing it to write to standard out. Thereby, you will be able to follow allong, if anything goes awry during the initialization sequence:<br />
<pre><nowiki><br />
openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
If it connects successfully , you could start it as a background task (adding &), redirecting output to /dev/null. (You could write an upstart script, see the example for the Hamachi VPN in the resources below.)<br />
<pre><nowiki><br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
</nowiki></pre><br />
<br />
==Testing connection==<br />
When testing access to your openvpn endpoint (server) from your Palm device, it can be benefitial if both can connect only via the openvpn tunnel (and not reach each other via an alternate route in your home network). The following scenario assumes, that a Palm device connects via openvpn to a private network (possibly your home network) from outside, using 3G (EVDO, UMTS). You can test this by turning off wifi and ssh to your Palm device using a Bluetooth PAN. See if your Palm device still has internet access over 3G, when turning off wifi. (While pinging google, drop wifi and monitor via SSH over Bluetooth PAN):<br />
<pre><nowiki><br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
</nowiki></pre><br />
If you ping IPs in your home network now (the openvpn endpoint/gateway or other IPs behind), traffic to your private network is routed through the encrypted tunnel:<br />
<pre><nowiki><br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
</nowiki></pre><br />
<br />
==OpenVPN IRC channel==<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]<br />
==Further Resources==<br />
#[http://www.webos-internals.org/wiki/HamachiVPN Hamachi on Pre]. Use the popular, proprietary Hamachi for VPN on your Palm device.<br />
#[http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#OpenVPN_GUI Optware OpenVPN on a QNAP Nas] gives you a good example of a complete configuration.</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11573OpenVPN for Palm Pre2010-09-27T20:03:01Z<p>Papa4narchia: /* Starting OpenVPN */</p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to another available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, openvpn is easily installable on your palm devices via ipkg. An application scenario could be to connect your Palm device via 3G to your home network, accessing data and services hosted by a NAS, for example.<br />
<br />
==OpenVPN client installation==<br />
To setup a connection to an available OpenVPN endpoint, you need the appropriate kernel module (tun.ko) on your Palm device and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN client configuration==<br />
OpenVPN is deployed quickly and easily. The OpenVPN.net website and source installations contain scripts that can make OpenVPN connect to your home or work when WiFi is activated. The following excerpt assumes that you already have available the following things: <br />
*a certificate for yourself / your device (in the example, called palmpre.crt)<br />
*the issuing certificate authority (ca.crt)<br />
*a key-file (palmpre.key)<br />
It is highly suggested that you make yourself familiar in creating your own keys (and certificates), in case you are not provided with from a trusted source. Have a look at the following wiki page, explaining in detail how to [http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#Telnet_Management_Interface Setup optware OpenVPN on a NAS], giving you exact instructions how to setup an endpoint you could connect your Palm device to.<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
==Starting OpenVPN==<br />
For a first connection test, you should start openvpn on your Palm device allowing it to write to standard out. Thereby, you will be able to follow allong, if anything goes awry during the initialization sequence:<br />
<pre><nowiki><br />
openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
If it connects successfully , you could start it as a background task (adding &), redirecting output to /dev/null. (You could write an upstart script, see the example for the Hamachi VPN in the resources below.)<br />
<pre><nowiki><br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
</nowiki></pre><br />
<br />
==Testing connection==<br />
When testing access to your openvpn endpoint (server) from your Palm device, it can be benefitial if both can connect only via the openvpn tunnel (and not reach each other via an alternate route in your home network). The following scenario assumes, that a Palm device connects via openvpn to a private network (possibly your home network) from outside, using 3G (EVDO, UMTS). You can test this by turning off wifi and ssh to your Palm device using a Bluetooth PAN. See if your Palm device still has internet access over 3G, when turning off wifi. (While pinging google, drop wifi and monitor via SSH over Bluetooth PAN):<br />
<pre><nowiki><br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
</nowiki></pre><br />
If you ping an IP in your home network now, traffic to your private network is routed through the encrypted tunnel:<br />
<pre><nowiki><br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
</nowiki></pre><br />
<br />
==OpenVPN IRC channel==<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]<br />
==Further Resources==<br />
#[http://www.webos-internals.org/wiki/HamachiVPN Hamachi on Pre]. Use the popular, proprietary Hamachi for VPN on your Palm device.<br />
#[http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#OpenVPN_GUI Optware OpenVPN on a QNAP Nas] gives you a good example of a complete configuration.</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11572OpenVPN for Palm Pre2010-09-27T19:57:19Z<p>Papa4narchia: /* Further Resources */</p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to another available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, openvpn is easily installable on your palm devices via ipkg. An application scenario could be to connect your Palm device via 3G to your home network, accessing data and services hosted by a NAS, for example.<br />
<br />
==OpenVPN client installation==<br />
To setup a connection to an available OpenVPN endpoint, you need the appropriate kernel module (tun.ko) on your Palm device and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN client configuration==<br />
OpenVPN is deployed quickly and easily. The OpenVPN.net website and source installations contain scripts that can make OpenVPN connect to your home or work when WiFi is activated. The following excerpt assumes that you already have available the following things: <br />
*a certificate for yourself / your device (in the example, called palmpre.crt)<br />
*the issuing certificate authority (ca.crt)<br />
*a key-file (palmpre.key)<br />
It is highly suggested that you make yourself familiar in creating your own keys (and certificates), in case you are not provided with from a trusted source. Have a look at the following wiki page, explaining in detail how to [http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#Telnet_Management_Interface Setup optware OpenVPN on a NAS], giving you exact instructions how to setup an endpoint you could connect your Palm device to.<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
==Starting OpenVPN==<br />
For a first connection test, you should start openvpn on your Palm device allowing it to write to standard out. Thereby, you will be able to follow allong, if anything goes awry during the initialization sequence:<br />
<pre><nowiki><br />
openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
If it connects successfully , you could start it as a background task (adding &), redirecting output to /dev/null:<br />
<pre><nowiki><br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
</nowiki></pre><br />
==Testing connection==<br />
When testing access to your openvpn endpoint (server) from your Palm device, it can be benefitial if both can connect only via the openvpn tunnel (and not reach each other via an alternate route in your home network). The following scenario assumes, that a Palm device connects via openvpn to a private network (possibly your home network) from outside, using 3G (EVDO, UMTS). You can test this by turning off wifi and ssh to your Palm device using a Bluetooth PAN. See if your Palm device still has internet access over 3G, when turning off wifi. (While pinging google, drop wifi and monitor via SSH over Bluetooth PAN):<br />
<pre><nowiki><br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
</nowiki></pre><br />
If you ping an IP in your home network now, traffic to your private network is routed through the encrypted tunnel:<br />
<pre><nowiki><br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
</nowiki></pre><br />
<br />
==OpenVPN IRC channel==<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]<br />
==Further Resources==<br />
#[http://www.webos-internals.org/wiki/HamachiVPN Hamachi on Pre]. Use the popular, proprietary Hamachi for VPN on your Palm device.<br />
#[http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#OpenVPN_GUI Optware OpenVPN on a QNAP Nas] gives you a good example of a complete configuration.</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11571OpenVPN for Palm Pre2010-09-27T19:56:35Z<p>Papa4narchia: /* Resources */</p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to another available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, openvpn is easily installable on your palm devices via ipkg. An application scenario could be to connect your Palm device via 3G to your home network, accessing data and services hosted by a NAS, for example.<br />
<br />
==OpenVPN client installation==<br />
To setup a connection to an available OpenVPN endpoint, you need the appropriate kernel module (tun.ko) on your Palm device and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN client configuration==<br />
OpenVPN is deployed quickly and easily. The OpenVPN.net website and source installations contain scripts that can make OpenVPN connect to your home or work when WiFi is activated. The following excerpt assumes that you already have available the following things: <br />
*a certificate for yourself / your device (in the example, called palmpre.crt)<br />
*the issuing certificate authority (ca.crt)<br />
*a key-file (palmpre.key)<br />
It is highly suggested that you make yourself familiar in creating your own keys (and certificates), in case you are not provided with from a trusted source. Have a look at the following wiki page, explaining in detail how to [http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#Telnet_Management_Interface Setup optware OpenVPN on a NAS], giving you exact instructions how to setup an endpoint you could connect your Palm device to.<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
==Starting OpenVPN==<br />
For a first connection test, you should start openvpn on your Palm device allowing it to write to standard out. Thereby, you will be able to follow allong, if anything goes awry during the initialization sequence:<br />
<pre><nowiki><br />
openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
If it connects successfully , you could start it as a background task (adding &), redirecting output to /dev/null:<br />
<pre><nowiki><br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
</nowiki></pre><br />
==Testing connection==<br />
When testing access to your openvpn endpoint (server) from your Palm device, it can be benefitial if both can connect only via the openvpn tunnel (and not reach each other via an alternate route in your home network). The following scenario assumes, that a Palm device connects via openvpn to a private network (possibly your home network) from outside, using 3G (EVDO, UMTS). You can test this by turning off wifi and ssh to your Palm device using a Bluetooth PAN. See if your Palm device still has internet access over 3G, when turning off wifi. (While pinging google, drop wifi and monitor via SSH over Bluetooth PAN):<br />
<pre><nowiki><br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
</nowiki></pre><br />
If you ping an IP in your home network now, traffic to your private network is routed through the encrypted tunnel:<br />
<pre><nowiki><br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
</nowiki></pre><br />
<br />
==OpenVPN IRC channel==<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]<br />
==Further Resources==<br />
#[[http://www.webos-internals.org/wiki/HamachiVPN | Hamachi on Pre]]. Use the popular, proprietary Hamachi for VPN on your Palm device.<br />
#[http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#OpenVPN_GUI Optware OpenVPN on a QNAP Nas] gives you a good example of a complete configuration.</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11570OpenVPN for Palm Pre2010-09-27T19:48:33Z<p>Papa4narchia: /* OpenVPN IRC channel */</p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to another available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, openvpn is easily installable on your palm devices via ipkg. An application scenario could be to connect your Palm device via 3G to your home network, accessing data and services hosted by a NAS, for example.<br />
<br />
==OpenVPN client installation==<br />
To setup a connection to an available OpenVPN endpoint, you need the appropriate kernel module (tun.ko) on your Palm device and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN client configuration==<br />
OpenVPN is deployed quickly and easily. The OpenVPN.net website and source installations contain scripts that can make OpenVPN connect to your home or work when WiFi is activated. The following excerpt assumes that you already have available the following things: <br />
*a certificate for yourself / your device (in the example, called palmpre.crt)<br />
*the issuing certificate authority (ca.crt)<br />
*a key-file (palmpre.key)<br />
It is highly suggested that you make yourself familiar in creating your own keys (and certificates), in case you are not provided with from a trusted source. Have a look at the following wiki page, explaining in detail how to [http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#Telnet_Management_Interface Setup optware OpenVPN on a NAS], giving you exact instructions how to setup an endpoint you could connect your Palm device to.<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
==Starting OpenVPN==<br />
For a first connection test, you should start openvpn on your Palm device allowing it to write to standard out. Thereby, you will be able to follow allong, if anything goes awry during the initialization sequence:<br />
<pre><nowiki><br />
openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
If it connects successfully , you could start it as a background task (adding &), redirecting output to /dev/null:<br />
<pre><nowiki><br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
</nowiki></pre><br />
==Testing connection==<br />
When testing access to your openvpn endpoint (server) from your Palm device, it can be benefitial if both can connect only via the openvpn tunnel (and not reach each other via an alternate route in your home network). The following scenario assumes, that a Palm device connects via openvpn to a private network (possibly your home network) from outside, using 3G (EVDO, UMTS). You can test this by turning off wifi and ssh to your Palm device using a Bluetooth PAN. See if your Palm device still has internet access over 3G, when turning off wifi. (While pinging google, drop wifi and monitor via SSH over Bluetooth PAN):<br />
<pre><nowiki><br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
</nowiki></pre><br />
If you ping an IP in your home network now, traffic to your private network is routed through the encrypted tunnel:<br />
<pre><nowiki><br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
</nowiki></pre><br />
<br />
==OpenVPN IRC channel==<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]<br />
==Resources==<br />
Using Hamachi for VPN on your Pre[[http://www.webos-internals.org/wiki/HamachiVPN]]</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11569OpenVPN for Palm Pre2010-09-27T19:39:19Z<p>Papa4narchia: /* Testing connection */</p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to another available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, openvpn is easily installable on your palm devices via ipkg. An application scenario could be to connect your Palm device via 3G to your home network, accessing data and services hosted by a NAS, for example.<br />
<br />
==OpenVPN client installation==<br />
To setup a connection to an available OpenVPN endpoint, you need the appropriate kernel module (tun.ko) on your Palm device and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN client configuration==<br />
OpenVPN is deployed quickly and easily. The OpenVPN.net website and source installations contain scripts that can make OpenVPN connect to your home or work when WiFi is activated. The following excerpt assumes that you already have available the following things: <br />
*a certificate for yourself / your device (in the example, called palmpre.crt)<br />
*the issuing certificate authority (ca.crt)<br />
*a key-file (palmpre.key)<br />
It is highly suggested that you make yourself familiar in creating your own keys (and certificates), in case you are not provided with from a trusted source. Have a look at the following wiki page, explaining in detail how to [http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#Telnet_Management_Interface Setup optware OpenVPN on a NAS], giving you exact instructions how to setup an endpoint you could connect your Palm device to.<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
==Starting OpenVPN==<br />
For a first connection test, you should start openvpn on your Palm device allowing it to write to standard out. Thereby, you will be able to follow allong, if anything goes awry during the initialization sequence:<br />
<pre><nowiki><br />
openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
If it connects successfully , you could start it as a background task (adding &), redirecting output to /dev/null:<br />
<pre><nowiki><br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
</nowiki></pre><br />
==Testing connection==<br />
When testing access to your openvpn endpoint (server) from your Palm device, it can be benefitial if both can connect only via the openvpn tunnel (and not reach each other via an alternate route in your home network). The following scenario assumes, that a Palm device connects via openvpn to a private network (possibly your home network) from outside, using 3G (EVDO, UMTS). You can test this by turning off wifi and ssh to your Palm device using a Bluetooth PAN. See if your Palm device still has internet access over 3G, when turning off wifi. (While pinging google, drop wifi and monitor via SSH over Bluetooth PAN):<br />
<pre><nowiki><br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
</nowiki></pre><br />
If you ping an IP in your home network now, traffic to your private network is routed through the encrypted tunnel:<br />
<pre><nowiki><br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
</nowiki></pre><br />
<br />
==OpenVPN IRC channel==<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11568OpenVPN for Palm Pre2010-09-27T19:36:30Z<p>Papa4narchia: /* Testing connection */</p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to another available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, openvpn is easily installable on your palm devices via ipkg. An application scenario could be to connect your Palm device via 3G to your home network, accessing data and services hosted by a NAS, for example.<br />
<br />
==OpenVPN client installation==<br />
To setup a connection to an available OpenVPN endpoint, you need the appropriate kernel module (tun.ko) on your Palm device and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN client configuration==<br />
OpenVPN is deployed quickly and easily. The OpenVPN.net website and source installations contain scripts that can make OpenVPN connect to your home or work when WiFi is activated. The following excerpt assumes that you already have available the following things: <br />
*a certificate for yourself / your device (in the example, called palmpre.crt)<br />
*the issuing certificate authority (ca.crt)<br />
*a key-file (palmpre.key)<br />
It is highly suggested that you make yourself familiar in creating your own keys (and certificates), in case you are not provided with from a trusted source. Have a look at the following wiki page, explaining in detail how to [http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#Telnet_Management_Interface Setup optware OpenVPN on a NAS], giving you exact instructions how to setup an endpoint you could connect your Palm device to.<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
==Starting OpenVPN==<br />
For a first connection test, you should start openvpn on your Palm device allowing it to write to standard out. Thereby, you will be able to follow allong, if anything goes awry during the initialization sequence:<br />
<pre><nowiki><br />
openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
If it connects successfully , you could start it as a background task (adding &), redirecting output to /dev/null:<br />
<pre><nowiki><br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
</nowiki></pre><br />
==Testing connection==<br />
When testing access to your openvpn endpoint (server) from your Palm device, it can be benefitial if both can connect only via the openvpn tunnel (and not reach each other via an alternate route in your home network). The following scenario assumes, that a Palm device connects via openvpn to a private network (possibly your home network) from outside, using 3G (EVDO, UMTS). You can test this by turing of wifi and ssh to your Palm device using a Bluetooth PAN.<br />
(...While pinging google, dropped wifi and monitored via SSH over Bluetooth PAN)<br />
<pre><nowiki><br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
</nowiki></pre><br />
Traffic to your connected private network in the example is routed through the encrypted tunnel, when pinging an IP in the private network.<br />
<pre><nowiki><br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
</nowiki></pre><br />
<br />
==OpenVPN IRC channel==<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11567OpenVPN for Palm Pre2010-09-27T19:24:34Z<p>Papa4narchia: </p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to another available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, openvpn is easily installable on your palm devices via ipkg. An application scenario could be to connect your Palm device via 3G to your home network, accessing data and services hosted by a NAS, for example.<br />
<br />
==OpenVPN client installation==<br />
To setup a connection to an available OpenVPN endpoint, you need the appropriate kernel module (tun.ko) on your Palm device and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN client configuration==<br />
OpenVPN is deployed quickly and easily. The OpenVPN.net website and source installations contain scripts that can make OpenVPN connect to your home or work when WiFi is activated. The following excerpt assumes that you already have available the following things: <br />
*a certificate for yourself / your device (in the example, called palmpre.crt)<br />
*the issuing certificate authority (ca.crt)<br />
*a key-file (palmpre.key)<br />
It is highly suggested that you make yourself familiar in creating your own keys (and certificates), in case you are not provided with from a trusted source. Have a look at the following wiki page, explaining in detail how to [http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#Telnet_Management_Interface Setup optware OpenVPN on a NAS], giving you exact instructions how to setup an endpoint you could connect your Palm device to.<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
==Starting OpenVPN==<br />
For a first connection test, you should start openvpn on your Palm device allowing it to write to standard out. Thereby, you will be able to follow allong, if anything goes awry during the initialization sequence:<br />
<pre><nowiki><br />
openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn<br />
</nowiki></pre><br />
If it connects successfully , you could start it as a background task (adding &), redirecting output to /dev/null:<br />
<pre><nowiki><br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
</nowiki></pre><br />
==Testing connection==<br />
When testing access to your openvpn endpoint (server) from your Palm device, it can be benefitial if both can connect only via the openvpn tunnel (and not reach each other via an alternate route in your home network). The following example assumes, that a Palm device is connected via openvpn to a network providing internet access (pinging google). When now turning off other potential access routes to the internet (dropping wifi access to an accesspoint) traffic could be routed through the tunnel to the internet.<br />
(...While pinging google, dropped wifi and monitored via SSH over Bluetooth PAN)<br />
<br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
<br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
<br />
</nowiki></pre><br />
<br />
==OpenVPN IRC channel==<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11566OpenVPN for Palm Pre2010-09-27T19:04:28Z<p>Papa4narchia: /* OpenVPN client configuration */</p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to another available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, openvpn is easily installable on your palm devices via ipkg. An application scenario could be to connect your Palm device via 3G to your home network, accessing data and services hosted by a NAS, for example.<br />
<br />
==OpenVPN client installation==<br />
To setup a connection to an available OpenVPN endpoint, you need the appropriate kernel module (tun.ko) on your Palm device and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN client configuration==<br />
OpenVPN is deployed quickly and easily. The OpenVPN.net website and source installations contain scripts that can make OpenVPN connect to your home or work when WiFi is activated. The following excerpt assumes that you already have available the following things: <br />
*a certificate for yourself / your device (in the example, called palmpre.crt)<br />
*the issuing certificate authority (ca.crt)<br />
*a key-file (palmpre.key)<br />
It is highly suggested that you make yourself familiar in creating your own keys (and certificates), in case you are not provided with from a trusted source. Have a look at the following wiki page, explaining in detail how to [http://wiki.nas-portal.org/index.php/Install_OpenVPN_on_QNAP#Telnet_Management_Interface Setup optware OpenVPN on a NAS], giving you exact instructions how to setup an endpoint you could connect your Palm device to.<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
<br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
<br />
(...While pinging google, dropped wifi and monitored via SSH over Bluetooth PAN)<br />
<br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
<br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
<br />
</nowiki></pre><br />
<br />
==OpenVPN IRC channel==<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11565OpenVPN for Palm Pre2010-09-27T19:01:55Z<p>Papa4narchia: /* OpenVPN client configuration */</p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to another available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, openvpn is easily installable on your palm devices via ipkg. An application scenario could be to connect your Palm device via 3G to your home network, accessing data and services hosted by a NAS, for example.<br />
<br />
==OpenVPN client installation==<br />
To setup a connection to an available OpenVPN endpoint, you need the appropriate kernel module (tun.ko) on your Palm device and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN client configuration==<br />
OpenVPN is deployed quickly and easily. The OpenVPN.net website and source installations contain scripts that can make OpenVPN connect to your home or work when WiFi is activated. The following excerpt assumes that you already have available the following things: <br />
*a certificate for yourself / your device (in the example, called palmpre.crt)<br />
*the issuing certificate authority (ca.crt)<br />
*a key-file (palmpre.key)<br />
It is highly suggested that you make yourself familiar in creating your own keys (and certificates), in case you are not provided with from a trusted source.<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
<br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
<br />
(...While pinging google, dropped wifi and monitored via SSH over Bluetooth PAN)<br />
<br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
<br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
<br />
</nowiki></pre><br />
<br />
==OpenVPN IRC channel==<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11564OpenVPN for Palm Pre2010-09-27T18:54:19Z<p>Papa4narchia: /* Introduction */</p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to another available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, openvpn is easily installable on your palm devices via ipkg. An application scenario could be to connect your Palm device via 3G to your home network, accessing data and services hosted by a NAS, for example.<br />
<br />
==OpenVPN client installation==<br />
To setup a connection to an available OpenVPN endpoint, you need the appropriate kernel module (tun.ko) on your Palm device and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN client configuration==<br />
OpenVPN is deployed quickly and easily. The OpenVPN.net website and source installations contain scripts that can make OpenVPN connect to your home or work when WiFi is activated. oc80z<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
<br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
<br />
(...While pinging google, dropped wifi and monitored via SSH over Bluetooth PAN)<br />
<br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
<br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
<br />
</nowiki></pre><br />
==OpenVPN IRC channel==<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11563OpenVPN for Palm Pre2010-09-27T18:51:51Z<p>Papa4narchia: /* OpenVPN client installation */</p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to another available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, openvpn is easily installable on your palm devices via ipkg.<br />
<br />
==OpenVPN client installation==<br />
To setup a connection to an available OpenVPN endpoint, you need the appropriate kernel module (tun.ko) on your Palm device and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN client configuration==<br />
OpenVPN is deployed quickly and easily. The OpenVPN.net website and source installations contain scripts that can make OpenVPN connect to your home or work when WiFi is activated. oc80z<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
<br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
<br />
(...While pinging google, dropped wifi and monitored via SSH over Bluetooth PAN)<br />
<br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
<br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
<br />
</nowiki></pre><br />
==OpenVPN IRC channel==<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11562OpenVPN for Palm Pre2010-09-27T18:50:34Z<p>Papa4narchia: /* Introduction */</p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to another available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, openvpn is easily installable on your palm devices via ipkg.<br />
<br />
==OpenVPN client installation==<br />
To setup a connection to your OpenVPN server, you need the appropriate kernel module (tun.ko) and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN client configuration==<br />
OpenVPN is deployed quickly and easily. The OpenVPN.net website and source installations contain scripts that can make OpenVPN connect to your home or work when WiFi is activated. oc80z<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
<br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
<br />
(...While pinging google, dropped wifi and monitored via SSH over Bluetooth PAN)<br />
<br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
<br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
<br />
</nowiki></pre><br />
==OpenVPN IRC channel==<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11561OpenVPN for Palm Pre2010-09-27T18:46:08Z<p>Papa4narchia: /* Introduction */</p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to an available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, the openvpn-client is easily installable on your palm device.<br />
<br />
==OpenVPN client installation==<br />
To setup a connection to your OpenVPN server, you need the appropriate kernel module (tun.ko) and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN client configuration==<br />
OpenVPN is deployed quickly and easily. The OpenVPN.net website and source installations contain scripts that can make OpenVPN connect to your home or work when WiFi is activated. oc80z<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
<br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
<br />
(...While pinging google, dropped wifi and monitored via SSH over Bluetooth PAN)<br />
<br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
<br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
<br />
</nowiki></pre><br />
==OpenVPN IRC channel==<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11560OpenVPN for Palm Pre2010-09-27T07:48:45Z<p>Papa4narchia: /* OpenVPN-client installation */</p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to an available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using either the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, the openvpn-client is easily installable on your palm device.<br />
<br />
==OpenVPN client installation==<br />
To setup a connection to your OpenVPN server, you need the appropriate kernel module (tun.ko) and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN client configuration==<br />
OpenVPN is deployed quickly and easily. The OpenVPN.net website and source installations contain scripts that can make OpenVPN connect to your home or work when WiFi is activated. oc80z<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
<br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
<br />
(...While pinging google, dropped wifi and monitored via SSH over Bluetooth PAN)<br />
<br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
<br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
<br />
</nowiki></pre><br />
==OpenVPN IRC channel==<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11559OpenVPN for Palm Pre2010-09-27T07:48:27Z<p>Papa4narchia: /* OpenVPN client configuration */</p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to an available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using either the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, the openvpn-client is easily installable on your palm device.<br />
<br />
==OpenVPN-client installation==<br />
To setup a connection to your OpenVPN server, you need the appropriate kernel module (tun.ko) and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN client configuration==<br />
OpenVPN is deployed quickly and easily. The OpenVPN.net website and source installations contain scripts that can make OpenVPN connect to your home or work when WiFi is activated. oc80z<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
<br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
<br />
(...While pinging google, dropped wifi and monitored via SSH over Bluetooth PAN)<br />
<br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
<br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
<br />
</nowiki></pre><br />
==OpenVPN IRC channel==<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11558OpenVPN for Palm Pre2010-09-27T07:48:03Z<p>Papa4narchia: /* OpenVPN IRC channel */</p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to an available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using either the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, the openvpn-client is easily installable on your palm device.<br />
<br />
==OpenVPN-client installation==<br />
To setup a connection to your OpenVPN server, you need the appropriate kernel module (tun.ko) and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN client configuration==<br />
OpenVPN is deployed quickly and easily. The OpenVPN.net website and source installations contain scripts that can make OpenVPN connect to your home or work when WiFi is activated. oc80z<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
<br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
<br />
(...While pinging google, dropped wifi and monitored via SSH over Bluetooth PAN)<br />
<br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
<br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
<br />
</nowiki></pre></div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11557OpenVPN for Palm Pre2010-09-27T07:47:52Z<p>Papa4narchia: /* OpenVPN client configuration */</p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to an available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using either the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, the openvpn-client is easily installable on your palm device.<br />
<br />
==OpenVPN-client installation==<br />
To setup a connection to your OpenVPN server, you need the appropriate kernel module (tun.ko) and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN IRC channel==<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]<br />
<br />
==OpenVPN client configuration==<br />
OpenVPN is deployed quickly and easily. The OpenVPN.net website and source installations contain scripts that can make OpenVPN connect to your home or work when WiFi is activated. oc80z<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
<br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
<br />
(...While pinging google, dropped wifi and monitored via SSH over Bluetooth PAN)<br />
<br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
<br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
<br />
</nowiki></pre></div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11556OpenVPN for Palm Pre2010-09-27T07:47:36Z<p>Papa4narchia: /* OpenVPN-client installation */</p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to an available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using either the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, the openvpn-client is easily installable on your palm device.<br />
<br />
==OpenVPN-client installation==<br />
To setup a connection to your OpenVPN server, you need the appropriate kernel module (tun.ko) and build a client-configuration depending and what type of connection you want to create (bridged or routed). The optware OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre/Pixi Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
<br />
==OpenVPN IRC channel==<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]<br />
<br />
==OpenVPN client configuration==<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
<br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
<br />
(...While pinging google, dropped wifi and monitored via SSH over Bluetooth PAN)<br />
<br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
<br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
<br />
</nowiki></pre></div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11555OpenVPN for Palm Pre2010-09-27T07:38:59Z<p>Papa4narchia: </p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to an available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using either the [http://en.wikipedia.org/wiki/TUN/TAP TUN/TAP] kernel drivers. With optware, the openvpn-client is easily installable on your palm device.<br />
<br />
==OpenVPN-client installation==<br />
The OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre's Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]<br />
<br />
OpenVPN is deployed quickly and easily. The OpenVPN.net website and source installations contain scripts that can make OpenVPN connect to your home or work when WiFi is activated. oc80z<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
==OpenVPN client configuration==<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
<br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
<br />
(...While pinging google, dropped wifi and monitored via SSH over Bluetooth PAN)<br />
<br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
<br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
<br />
</nowiki></pre></div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=OpenVPN_for_Palm_Pre&diff=11554OpenVPN for Palm Pre2010-09-27T07:38:17Z<p>Papa4narchia: </p>
<hr />
<div>==Introduction==<br />
OpenVPN enables you to build a secure virtual private network (VPN) connection from your Palm device to an available OpenVPN server, over an encrypted TLS connection. For encryption, it uses the libraries of the OpenSSL program. On the transport layer, it can use TCP or UDP. The secure connection, or "tunnel", between client and server is created using virtual network devices, using either the [[http://en.wikipedia.org/wiki/TUN/TAP|TUN/TAP]] kernel drivers. With optware, the openvpn-client is easily installable on your palm device.<br />
<br />
==OpenVPN-client installation==<br />
The OpenVPN ipkg is a clean installation as the clipboard below proves. The Palm Pre's Linux OS is compiled with the /dev/tun driver built in, so you can ignore the module dependency warning. There is a project to create a GUI for the pre [http://gitorious.org/pre-openvpn].<br />
<br />
The OpenVPN IRC channel ##OpenVPN exists on the same Freenode server #WebOS-Internals is located on. Please stop by either channel with questions after visiting [http://openvpn.net]<br />
<br />
OpenVPN is deployed quickly and easily. The OpenVPN.net website and source installations contain scripts that can make OpenVPN connect to your home or work when WiFi is activated. oc80z<br />
<br />
note: oinstall is alias oinstall="sudo ipkg-opt install"<br />
<pre><nowiki><br />
┌─(box@castle)-(09:28:44)-><br />
└─(~)--> $ oinstall openvpn<br />
Installing openvpn (2.1_rc15-1) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/openvpn_2.1_rc15-1_arm.ipk<br />
openvpn: unsatisfied recommendation for kernel-module-tun<br />
Installing lzo (1.08-2) to root...<br />
Downloading http://ipkg.nslu2-linux.org/feeds/optware/cs08q1armel/cross/unstable/lzo_1.08-2_arm.ipk<br />
Configuring lzo<br />
Configuring openvpn<br />
Successfully terminated.<br />
</nowiki></pre><br />
==OpenVPN client configuration==<br />
<pre><nowiki><br />
┌─(root@castle)-(10:17:05)-><br />
└─(/opt/etc/openvpn)--> # unzip palmpre.zip<br />
Archive: palmpre.zip<br />
creating: palmpre/<br />
inflating: palmpre/ca.crt<br />
inflating: palmpre/palmpre.key<br />
inflating: palmpre/palmpre.crt<br />
inflating: palmpre/palmpre.conf<br />
inflating: palmpre/dh2048.pem<br />
inflating: palmpre/palmpre.ovpn<br />
<br />
┌─(root@castle)-(10:19:33)-><br />
└─(/opt/etc/openvpn)--> # openvpn --config /opt/etc/openvpn/palmpre/palmpre.ovpn >>/dev/null&<br />
<br />
(...While pinging google, dropped wifi and monitored via SSH over Bluetooth PAN)<br />
<br />
64 bytes from 74.125.67.100: seq=5 ttl=52 time=46.505 ms<br />
64 bytes from 74.125.67.100: seq=6 ttl=52 time=45.603 ms<br />
64 bytes from 74.125.67.100: seq=7 ttl=52 time=49.132 ms<br />
64 bytes from 74.125.67.100: seq=8 ttl=52 time=101.013 ms <br />
64 bytes from 74.125.67.100: seq=9 ttl=52 time=1556.213 ms <-- cutover wifi to evdo<br />
64 bytes from 74.125.67.100: seq=10 ttl=52 time=561.371 ms<br />
64 bytes from 74.125.67.100: seq=11 ttl=52 time=54.932 ms<br />
64 bytes from 74.125.67.100: seq=12 ttl=50 time=109.436 ms<br />
64 bytes from 74.125.67.100: seq=13 ttl=50 time=105.896 ms<br />
64 bytes from 74.125.67.100: seq=14 ttl=50 time=104.523 ms<br />
<br />
┌─(root@castle)-(10:33:54)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.1.10<br />
PING 192.218.1.10 (192.218.1.10): 56 data bytes<br />
64 bytes from 192.218.1.10: seq=0 ttl=42 time=456.665 ms<br />
64 bytes from 192.218.1.10: seq=1 ttl=42 time=260.773 ms<br />
64 bytes from 192.218.1.10: seq=2 ttl=42 time=268.189 ms<br />
<br />
┌─(root@castle)-(10:35:13)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.1<br />
PING 192.218.0.1 (192.218.0.1): 56 data bytes<br />
64 bytes from 192.218.0.1: seq=0 ttl=64 time=259.552 ms<br />
64 bytes from 192.218.0.1: seq=1 ttl=64 time=114.898 ms<br />
64 bytes from 192.218.0.1: seq=2 ttl=64 time=118.958 ms<br />
<br />
┌─(root@castle)-(10:35:40)-><br />
└─(/opt/etc/openvpn/palmpre)--> # ping 192.218.0.218<br />
PING 192.218.0.218 (192.218.0.218): 56 data bytes<br />
64 bytes from 192.218.0.218: seq=0 ttl=64 time=502.137 ms<br />
64 bytes from 192.218.0.218: seq=1 ttl=64 time=182.556 ms<br />
64 bytes from 192.218.0.218: seq=2 ttl=64 time=123.016 ms<br />
<br />
</nowiki></pre></div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=Setup_Bash&diff=11550Setup Bash2010-09-25T19:31:10Z<p>Papa4narchia: /* Setting up bash as a replacment shell for /bin/sh */</p>
<hr />
<div>= Setting up bash as a replacment shell for /bin/sh=<br />
The Palm webOS devices like Pre and Pixi come with the [http://en.wikipedia.org/wiki/Bash_%28Unix_shell Bourne shell] as the default stock shell. The [http://en.wikipedia.org/wiki/Bash_(Unix_shell) Bourne-Again Shell], or bash, is available via optware. This is how you can set it up.<br />
<br />
== Preliminaries==<br />
# Gain [[Portal:Accessing_Linux | root access]].<br />
# Setup the [[Next_steps | Optware Feed]].<br />
# Open the root file system to read/write with rootfs_open. If you haven't yet altered your PATH (see below) use the following:<br />
<pre><nowiki>/usr/sbin/rootfs_open -w</nowiki></pre><br />
<br />
== Install bash==<br />
<pre><nowiki>ipkg-opt install bash</nowiki></pre><br />
<br />
'''Super Important:''' Before you switch your login shell in /etc/passwd, you MUST create /etc/shells and add /opt/bin/bash and /bin/sh to it. If you do not, you will lock yourself out of the Pre on anything but novacom term if you switch your default shell.<br />
<br />
<pre><nowiki>echo -e "# /etc/shells: valid login shells\n/opt/bin/bash\n/bin/sh" >/etc/shells</nowiki></pre><br />
<br />
now you can vi/nano whatever /etc/passwd and replace your unprivileged user shell with /opt/bin/bash.<br />
<br />
Before:<br />
<br />
> youruser:yourpasswordhash:1001:1001:Linux User,,,:/var/home/youruser:/bin/sh<br />
<br />
After:<br />
<br />
> youruser:yourpasswordhash:1001:1001:Linux User,,,:/var/home/youruser:/opt/bin/bash<br />
<br />
Try to SSH in with that user and be sure you can access the machine. Change root as well if you desire. Since you will probably 'sudo su' to root to perform larger tasks, you will want to stay in consistent shell.<br />
==Setup your bash profile==<br />
When a user logs in, the shell provides a certain environment for the programs running in your users context. This is achieved by setting environment variables in scripts, stored in multiple locations. That includes /etc/profile (for all users) and all the files in the /etc/profile.d directory. (Other linux distributions often add ~/.bash_profile and ~/.bashrc as well to the home directories of users.)<br />
<br />
/etc/profile.d/ is a good place to put your application specific setups and thereby setting up custom aliases, paths, editors etc.<br />
Additionally, we can append aliases and logout scripts into this [[profile-d | /etc/profile.d]] folder.<br />
<br />
1. Create the directory:<br />
<pre><nowiki>mkdir /etc/profile.d</nowiki></pre><br />
<br />
2. Add your rc file (name doesn't matter as long as it isn't a .file):<br />
<pre><nowiki>vi/nano/etc /etc/profile.d/profile.custom</nowiki></pre><br />
3) Add aliases and PATH options. Here is what I have:<br />
<pre><nowiki><br />
alias nano='nano -zwc'<br />
alias ls='ls -aF'<br />
alias ll='ls -alF'<br />
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin::/opt/bin:/opt/sbin<br />
EDITOR='nano'<br />
export PATH EDITOR<br />
</nowiki></pre><br />
<br />
nano -zwc will allow nano to suspend with ctl-z and not wordwrap by default as well as show you the line numbers that your cursor is on (avoid having to hit ctrl-c looking for line numbers).<br />
<br />
These are my preferred ls cmds (yours may vary):<br />
<br />
'''PATH''' is adding the /opt/bin and /opt/sbin paths so your optware binaries work easily. This is a complete overwrite of the PATH set by default and applies to your unprivileged user as well as root. Keep that in mind if you try to run stuff out of /sbin dirs...<br />
<br />
'''EDITOR''' is setting your editor of choice for things like crontab edits or subversion if you were using that on the Pre. If you are happy with vi, you can skip the EDITOR set. If you're reading this guide, you probably want nano...<br />
<br />
nano is easily installed with <br />
<pre><nowiki>ipkg-opt install nano</nowiki></pre><br />
<br />
Okay. You are done...remount the root file system as readonly:<br />
<pre><nowiki>mount -o remount,ro /</nowiki></pre><br />
<br />
There's no need to reboot, but if you logout and log back in you can make sure you are in bash... Type some gibberish:<br />
<br />
> root@castle:/etc# asdf<br />
> bash: asdf: command not found<br />
<br />
Mmm, bashalicious...<br />
<br />
'''NOTE''' The 2nd command from the top was adding /bin/bash to /etc/shells, NOT /bin/sh. I fixed it. Also, I wasn't able to get /etc/profile.d/profile.custom to work, so I used ~/.bashrc instead. -hopspitfire<br />
<br />
= Credits=<br />
Submitted by retry.<br />
Tested to work by hopspitfire (see '''NOTE''' above).</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=Setup_Bash&diff=11549Setup Bash2010-09-25T19:29:57Z<p>Papa4narchia: /* Setting up bash as a replacment shell for /bin/sh */</p>
<hr />
<div>= Setting up bash as a replacment shell for /bin/sh=<br />
The Palm webOS devices like Pre and Pixi come with the [http://en.wikipedia.org/wiki/Bash_%28Unix_shell Bourne shell] as the default stock shell. The he [http://en.wikipedia.org/wiki/Bash_Unix_shell Bourne-Again Shell], or bash, is available via optware. This is how you can set it up.<br />
<br />
== Preliminaries==<br />
# Gain [[Portal:Accessing_Linux | root access]].<br />
# Setup the [[Next_steps | Optware Feed]].<br />
# Open the root file system to read/write with rootfs_open. If you haven't yet altered your PATH (see below) use the following:<br />
<pre><nowiki>/usr/sbin/rootfs_open -w</nowiki></pre><br />
<br />
== Install bash==<br />
<pre><nowiki>ipkg-opt install bash</nowiki></pre><br />
<br />
'''Super Important:''' Before you switch your login shell in /etc/passwd, you MUST create /etc/shells and add /opt/bin/bash and /bin/sh to it. If you do not, you will lock yourself out of the Pre on anything but novacom term if you switch your default shell.<br />
<br />
<pre><nowiki>echo -e "# /etc/shells: valid login shells\n/opt/bin/bash\n/bin/sh" >/etc/shells</nowiki></pre><br />
<br />
now you can vi/nano whatever /etc/passwd and replace your unprivileged user shell with /opt/bin/bash.<br />
<br />
Before:<br />
<br />
> youruser:yourpasswordhash:1001:1001:Linux User,,,:/var/home/youruser:/bin/sh<br />
<br />
After:<br />
<br />
> youruser:yourpasswordhash:1001:1001:Linux User,,,:/var/home/youruser:/opt/bin/bash<br />
<br />
Try to SSH in with that user and be sure you can access the machine. Change root as well if you desire. Since you will probably 'sudo su' to root to perform larger tasks, you will want to stay in consistent shell.<br />
==Setup your bash profile==<br />
When a user logs in, the shell provides a certain environment for the programs running in your users context. This is achieved by setting environment variables in scripts, stored in multiple locations. That includes /etc/profile (for all users) and all the files in the /etc/profile.d directory. (Other linux distributions often add ~/.bash_profile and ~/.bashrc as well to the home directories of users.)<br />
<br />
/etc/profile.d/ is a good place to put your application specific setups and thereby setting up custom aliases, paths, editors etc.<br />
Additionally, we can append aliases and logout scripts into this [[profile-d | /etc/profile.d]] folder.<br />
<br />
1. Create the directory:<br />
<pre><nowiki>mkdir /etc/profile.d</nowiki></pre><br />
<br />
2. Add your rc file (name doesn't matter as long as it isn't a .file):<br />
<pre><nowiki>vi/nano/etc /etc/profile.d/profile.custom</nowiki></pre><br />
3) Add aliases and PATH options. Here is what I have:<br />
<pre><nowiki><br />
alias nano='nano -zwc'<br />
alias ls='ls -aF'<br />
alias ll='ls -alF'<br />
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin::/opt/bin:/opt/sbin<br />
EDITOR='nano'<br />
export PATH EDITOR<br />
</nowiki></pre><br />
<br />
nano -zwc will allow nano to suspend with ctl-z and not wordwrap by default as well as show you the line numbers that your cursor is on (avoid having to hit ctrl-c looking for line numbers).<br />
<br />
These are my preferred ls cmds (yours may vary):<br />
<br />
'''PATH''' is adding the /opt/bin and /opt/sbin paths so your optware binaries work easily. This is a complete overwrite of the PATH set by default and applies to your unprivileged user as well as root. Keep that in mind if you try to run stuff out of /sbin dirs...<br />
<br />
'''EDITOR''' is setting your editor of choice for things like crontab edits or subversion if you were using that on the Pre. If you are happy with vi, you can skip the EDITOR set. If you're reading this guide, you probably want nano...<br />
<br />
nano is easily installed with <br />
<pre><nowiki>ipkg-opt install nano</nowiki></pre><br />
<br />
Okay. You are done...remount the root file system as readonly:<br />
<pre><nowiki>mount -o remount,ro /</nowiki></pre><br />
<br />
There's no need to reboot, but if you logout and log back in you can make sure you are in bash... Type some gibberish:<br />
<br />
> root@castle:/etc# asdf<br />
> bash: asdf: command not found<br />
<br />
Mmm, bashalicious...<br />
<br />
'''NOTE''' The 2nd command from the top was adding /bin/bash to /etc/shells, NOT /bin/sh. I fixed it. Also, I wasn't able to get /etc/profile.d/profile.custom to work, so I used ~/.bashrc instead. -hopspitfire<br />
<br />
= Credits=<br />
Submitted by retry.<br />
Tested to work by hopspitfire (see '''NOTE''' above).</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=Setup_Bash&diff=11548Setup Bash2010-09-25T19:28:53Z<p>Papa4narchia: /* Setting up bash as a replacment shell for /bin/sh */</p>
<hr />
<div>= Setting up bash as a replacment shell for /bin/sh=<br />
The Palm webOS devices like Pre and Pixi come with the [http://en.wikipedia.org/wiki/Bourne_shell Bourne shell] as the default stock shell. The he [http://en.wikipedia.org/wiki/Bash_Unix_shell Bourne-Again Shell], or bash, is available via optware. This is how you can set it up.<br />
<br />
== Preliminaries==<br />
# Gain [[Portal:Accessing_Linux | root access]].<br />
# Setup the [[Next_steps | Optware Feed]].<br />
# Open the root file system to read/write with rootfs_open. If you haven't yet altered your PATH (see below) use the following:<br />
<pre><nowiki>/usr/sbin/rootfs_open -w</nowiki></pre><br />
<br />
== Install bash==<br />
<pre><nowiki>ipkg-opt install bash</nowiki></pre><br />
<br />
'''Super Important:''' Before you switch your login shell in /etc/passwd, you MUST create /etc/shells and add /opt/bin/bash and /bin/sh to it. If you do not, you will lock yourself out of the Pre on anything but novacom term if you switch your default shell.<br />
<br />
<pre><nowiki>echo -e "# /etc/shells: valid login shells\n/opt/bin/bash\n/bin/sh" >/etc/shells</nowiki></pre><br />
<br />
now you can vi/nano whatever /etc/passwd and replace your unprivileged user shell with /opt/bin/bash.<br />
<br />
Before:<br />
<br />
> youruser:yourpasswordhash:1001:1001:Linux User,,,:/var/home/youruser:/bin/sh<br />
<br />
After:<br />
<br />
> youruser:yourpasswordhash:1001:1001:Linux User,,,:/var/home/youruser:/opt/bin/bash<br />
<br />
Try to SSH in with that user and be sure you can access the machine. Change root as well if you desire. Since you will probably 'sudo su' to root to perform larger tasks, you will want to stay in consistent shell.<br />
==Setup your bash profile==<br />
When a user logs in, the shell provides a certain environment for the programs running in your users context. This is achieved by setting environment variables in scripts, stored in multiple locations. That includes /etc/profile (for all users) and all the files in the /etc/profile.d directory. (Other linux distributions often add ~/.bash_profile and ~/.bashrc as well to the home directories of users.)<br />
<br />
/etc/profile.d/ is a good place to put your application specific setups and thereby setting up custom aliases, paths, editors etc.<br />
Additionally, we can append aliases and logout scripts into this [[profile-d | /etc/profile.d]] folder.<br />
<br />
1. Create the directory:<br />
<pre><nowiki>mkdir /etc/profile.d</nowiki></pre><br />
<br />
2. Add your rc file (name doesn't matter as long as it isn't a .file):<br />
<pre><nowiki>vi/nano/etc /etc/profile.d/profile.custom</nowiki></pre><br />
3) Add aliases and PATH options. Here is what I have:<br />
<pre><nowiki><br />
alias nano='nano -zwc'<br />
alias ls='ls -aF'<br />
alias ll='ls -alF'<br />
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin::/opt/bin:/opt/sbin<br />
EDITOR='nano'<br />
export PATH EDITOR<br />
</nowiki></pre><br />
<br />
nano -zwc will allow nano to suspend with ctl-z and not wordwrap by default as well as show you the line numbers that your cursor is on (avoid having to hit ctrl-c looking for line numbers).<br />
<br />
These are my preferred ls cmds (yours may vary):<br />
<br />
'''PATH''' is adding the /opt/bin and /opt/sbin paths so your optware binaries work easily. This is a complete overwrite of the PATH set by default and applies to your unprivileged user as well as root. Keep that in mind if you try to run stuff out of /sbin dirs...<br />
<br />
'''EDITOR''' is setting your editor of choice for things like crontab edits or subversion if you were using that on the Pre. If you are happy with vi, you can skip the EDITOR set. If you're reading this guide, you probably want nano...<br />
<br />
nano is easily installed with <br />
<pre><nowiki>ipkg-opt install nano</nowiki></pre><br />
<br />
Okay. You are done...remount the root file system as readonly:<br />
<pre><nowiki>mount -o remount,ro /</nowiki></pre><br />
<br />
There's no need to reboot, but if you logout and log back in you can make sure you are in bash... Type some gibberish:<br />
<br />
> root@castle:/etc# asdf<br />
> bash: asdf: command not found<br />
<br />
Mmm, bashalicious...<br />
<br />
'''NOTE''' The 2nd command from the top was adding /bin/bash to /etc/shells, NOT /bin/sh. I fixed it. Also, I wasn't able to get /etc/profile.d/profile.custom to work, so I used ~/.bashrc instead. -hopspitfire<br />
<br />
= Credits=<br />
Submitted by retry.<br />
Tested to work by hopspitfire (see '''NOTE''' above).</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=Setup_Bash&diff=11547Setup Bash2010-09-25T19:25:29Z<p>Papa4narchia: /* Setting up Bash as a Replacment Shell for /bin/sh */</p>
<hr />
<div>= Setting up bash as a replacment shell for /bin/sh=<br />
The Palm webOS devices like Pre and Pixi come with the [http://en.wikipedia.org/wiki/Bourne_shell|Bourne shell] as the default stock shell. The he [[http://en.wikipedia.org/wiki/Bash_%28Unix_shell%29|Bourne-Again Shell}], or bash, is available via optware. This is how you can set it up.<br />
<br />
== Preliminaries==<br />
# Gain [[Portal:Accessing_Linux | root access]].<br />
# Setup the [[Next_steps | Optware Feed]].<br />
# Open the root file system to read/write with rootfs_open. If you haven't yet altered your PATH (see below) use the following:<br />
<pre><nowiki>/usr/sbin/rootfs_open -w</nowiki></pre><br />
<br />
== Install bash==<br />
<pre><nowiki>ipkg-opt install bash</nowiki></pre><br />
<br />
'''Super Important:''' Before you switch your login shell in /etc/passwd, you MUST create /etc/shells and add /opt/bin/bash and /bin/sh to it. If you do not, you will lock yourself out of the Pre on anything but novacom term if you switch your default shell.<br />
<br />
<pre><nowiki>echo -e "# /etc/shells: valid login shells\n/opt/bin/bash\n/bin/sh" >/etc/shells</nowiki></pre><br />
<br />
now you can vi/nano whatever /etc/passwd and replace your unprivileged user shell with /opt/bin/bash.<br />
<br />
Before:<br />
<br />
> youruser:yourpasswordhash:1001:1001:Linux User,,,:/var/home/youruser:/bin/sh<br />
<br />
After:<br />
<br />
> youruser:yourpasswordhash:1001:1001:Linux User,,,:/var/home/youruser:/opt/bin/bash<br />
<br />
Try to SSH in with that user and be sure you can access the machine. Change root as well if you desire. Since you will probably 'sudo su' to root to perform larger tasks, you will want to stay in consistent shell.<br />
==Setup your bash profile==<br />
When a user logs in, the shell provides a certain environment for the programs running in your users context. This is achieved by setting environment variables in scripts, stored in multiple locations. That includes /etc/profile (for all users) and all the files in the /etc/profile.d directory. (Other linux distributions often add ~/.bash_profile and ~/.bashrc as well to the home directories of users.)<br />
<br />
/etc/profile.d/ is a good place to put your application specific setups and thereby setting up custom aliases, paths, editors etc.<br />
Additionally, we can append aliases and logout scripts into this [[profile-d | /etc/profile.d]] folder.<br />
<br />
1. Create the directory:<br />
<pre><nowiki>mkdir /etc/profile.d</nowiki></pre><br />
<br />
2. Add your rc file (name doesn't matter as long as it isn't a .file):<br />
<pre><nowiki>vi/nano/etc /etc/profile.d/profile.custom</nowiki></pre><br />
3) Add aliases and PATH options. Here is what I have:<br />
<pre><nowiki><br />
alias nano='nano -zwc'<br />
alias ls='ls -aF'<br />
alias ll='ls -alF'<br />
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin::/opt/bin:/opt/sbin<br />
EDITOR='nano'<br />
export PATH EDITOR<br />
</nowiki></pre><br />
<br />
nano -zwc will allow nano to suspend with ctl-z and not wordwrap by default as well as show you the line numbers that your cursor is on (avoid having to hit ctrl-c looking for line numbers).<br />
<br />
These are my preferred ls cmds (yours may vary):<br />
<br />
'''PATH''' is adding the /opt/bin and /opt/sbin paths so your optware binaries work easily. This is a complete overwrite of the PATH set by default and applies to your unprivileged user as well as root. Keep that in mind if you try to run stuff out of /sbin dirs...<br />
<br />
'''EDITOR''' is setting your editor of choice for things like crontab edits or subversion if you were using that on the Pre. If you are happy with vi, you can skip the EDITOR set. If you're reading this guide, you probably want nano...<br />
<br />
nano is easily installed with <br />
<pre><nowiki>ipkg-opt install nano</nowiki></pre><br />
<br />
Okay. You are done...remount the root file system as readonly:<br />
<pre><nowiki>mount -o remount,ro /</nowiki></pre><br />
<br />
There's no need to reboot, but if you logout and log back in you can make sure you are in bash... Type some gibberish:<br />
<br />
> root@castle:/etc# asdf<br />
> bash: asdf: command not found<br />
<br />
Mmm, bashalicious...<br />
<br />
'''NOTE''' The 2nd command from the top was adding /bin/bash to /etc/shells, NOT /bin/sh. I fixed it. Also, I wasn't able to get /etc/profile.d/profile.custom to work, so I used ~/.bashrc instead. -hopspitfire<br />
<br />
= Credits=<br />
Submitted by retry.<br />
Tested to work by hopspitfire (see '''NOTE''' above).</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=Setup_Bash&diff=11546Setup Bash2010-09-25T19:24:56Z<p>Papa4narchia: /* Setting up Bash as a Replacment Shell for /bin/sh */</p>
<hr />
<div>= Setting up Bash as a Replacment Shell for /bin/sh=<br />
The Palm webOS devices like Pre and Pixi come with the [http://en.wikipedia.org/wiki/Bourne_shell|Bourne shell] as the default stock shell. The he [[http://en.wikipedia.org/wiki/Bash_%28Unix_shell%29|Bourne-Again Shell}], or bash, is available via optware. This is how you can set it up.<br />
<br />
== Preliminaries==<br />
# Gain [[Portal:Accessing_Linux | root access]].<br />
# Setup the [[Next_steps | Optware Feed]].<br />
# Open the root file system to read/write with rootfs_open. If you haven't yet altered your PATH (see below) use the following:<br />
<pre><nowiki>/usr/sbin/rootfs_open -w</nowiki></pre><br />
<br />
== Install bash==<br />
<pre><nowiki>ipkg-opt install bash</nowiki></pre><br />
<br />
'''Super Important:''' Before you switch your login shell in /etc/passwd, you MUST create /etc/shells and add /opt/bin/bash and /bin/sh to it. If you do not, you will lock yourself out of the Pre on anything but novacom term if you switch your default shell.<br />
<br />
<pre><nowiki>echo -e "# /etc/shells: valid login shells\n/opt/bin/bash\n/bin/sh" >/etc/shells</nowiki></pre><br />
<br />
now you can vi/nano whatever /etc/passwd and replace your unprivileged user shell with /opt/bin/bash.<br />
<br />
Before:<br />
<br />
> youruser:yourpasswordhash:1001:1001:Linux User,,,:/var/home/youruser:/bin/sh<br />
<br />
After:<br />
<br />
> youruser:yourpasswordhash:1001:1001:Linux User,,,:/var/home/youruser:/opt/bin/bash<br />
<br />
Try to SSH in with that user and be sure you can access the machine. Change root as well if you desire. Since you will probably 'sudo su' to root to perform larger tasks, you will want to stay in consistent shell.<br />
==Setup your bash profile==<br />
When a user logs in, the shell provides a certain environment for the programs running in your users context. This is achieved by setting environment variables in scripts, stored in multiple locations. That includes /etc/profile (for all users) and all the files in the /etc/profile.d directory. (Other linux distributions often add ~/.bash_profile and ~/.bashrc as well to the home directories of users.)<br />
<br />
/etc/profile.d/ is a good place to put your application specific setups and thereby setting up custom aliases, paths, editors etc.<br />
Additionally, we can append aliases and logout scripts into this [[profile-d | /etc/profile.d]] folder.<br />
<br />
1. Create the directory:<br />
<pre><nowiki>mkdir /etc/profile.d</nowiki></pre><br />
<br />
2. Add your rc file (name doesn't matter as long as it isn't a .file):<br />
<pre><nowiki>vi/nano/etc /etc/profile.d/profile.custom</nowiki></pre><br />
3) Add aliases and PATH options. Here is what I have:<br />
<pre><nowiki><br />
alias nano='nano -zwc'<br />
alias ls='ls -aF'<br />
alias ll='ls -alF'<br />
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin::/opt/bin:/opt/sbin<br />
EDITOR='nano'<br />
export PATH EDITOR<br />
</nowiki></pre><br />
<br />
nano -zwc will allow nano to suspend with ctl-z and not wordwrap by default as well as show you the line numbers that your cursor is on (avoid having to hit ctrl-c looking for line numbers).<br />
<br />
These are my preferred ls cmds (yours may vary):<br />
<br />
'''PATH''' is adding the /opt/bin and /opt/sbin paths so your optware binaries work easily. This is a complete overwrite of the PATH set by default and applies to your unprivileged user as well as root. Keep that in mind if you try to run stuff out of /sbin dirs...<br />
<br />
'''EDITOR''' is setting your editor of choice for things like crontab edits or subversion if you were using that on the Pre. If you are happy with vi, you can skip the EDITOR set. If you're reading this guide, you probably want nano...<br />
<br />
nano is easily installed with <br />
<pre><nowiki>ipkg-opt install nano</nowiki></pre><br />
<br />
Okay. You are done...remount the root file system as readonly:<br />
<pre><nowiki>mount -o remount,ro /</nowiki></pre><br />
<br />
There's no need to reboot, but if you logout and log back in you can make sure you are in bash... Type some gibberish:<br />
<br />
> root@castle:/etc# asdf<br />
> bash: asdf: command not found<br />
<br />
Mmm, bashalicious...<br />
<br />
'''NOTE''' The 2nd command from the top was adding /bin/bash to /etc/shells, NOT /bin/sh. I fixed it. Also, I wasn't able to get /etc/profile.d/profile.custom to work, so I used ~/.bashrc instead. -hopspitfire<br />
<br />
= Credits=<br />
Submitted by retry.<br />
Tested to work by hopspitfire (see '''NOTE''' above).</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=Setup_Bash&diff=11545Setup Bash2010-09-25T19:20:57Z<p>Papa4narchia: /* Setup your bash profile */</p>
<hr />
<div>= Setting up Bash as a Replacment Shell for /bin/sh=<br />
<br />
== Preliminaries==<br />
# Gain [[Portal:Accessing_Linux | root access]].<br />
# Setup the [[Next_steps | Optware Feed]].<br />
# Open the root file system to read/write with rootfs_open. If you haven't yet altered your PATH (see below) use the following:<br />
<pre><nowiki>/usr/sbin/rootfs_open -w</nowiki></pre><br />
<br />
== Install bash==<br />
<pre><nowiki>ipkg-opt install bash</nowiki></pre><br />
<br />
'''Super Important:''' Before you switch your login shell in /etc/passwd, you MUST create /etc/shells and add /opt/bin/bash and /bin/sh to it. If you do not, you will lock yourself out of the Pre on anything but novacom term if you switch your default shell.<br />
<br />
<pre><nowiki>echo -e "# /etc/shells: valid login shells\n/opt/bin/bash\n/bin/sh" >/etc/shells</nowiki></pre><br />
<br />
now you can vi/nano whatever /etc/passwd and replace your unprivileged user shell with /opt/bin/bash.<br />
<br />
Before:<br />
<br />
> youruser:yourpasswordhash:1001:1001:Linux User,,,:/var/home/youruser:/bin/sh<br />
<br />
After:<br />
<br />
> youruser:yourpasswordhash:1001:1001:Linux User,,,:/var/home/youruser:/opt/bin/bash<br />
<br />
Try to SSH in with that user and be sure you can access the machine. Change root as well if you desire. Since you will probably 'sudo su' to root to perform larger tasks, you will want to stay in consistent shell.<br />
==Setup your bash profile==<br />
When a user logs in, the shell provides a certain environment for the programs running in your users context. This is achieved by setting environment variables in scripts, stored in multiple locations. That includes /etc/profile (for all users) and all the files in the /etc/profile.d directory. (Other linux distributions often add ~/.bash_profile and ~/.bashrc as well to the home directories of users.)<br />
<br />
/etc/profile.d/ is a good place to put your application specific setups and thereby setting up custom aliases, paths, editors etc.<br />
Additionally, we can append aliases and logout scripts into this [[profile-d | /etc/profile.d]] folder.<br />
<br />
1. Create the directory:<br />
<pre><nowiki>mkdir /etc/profile.d</nowiki></pre><br />
<br />
2. Add your rc file (name doesn't matter as long as it isn't a .file):<br />
<pre><nowiki>vi/nano/etc /etc/profile.d/profile.custom</nowiki></pre><br />
3) Add aliases and PATH options. Here is what I have:<br />
<pre><nowiki><br />
alias nano='nano -zwc'<br />
alias ls='ls -aF'<br />
alias ll='ls -alF'<br />
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin::/opt/bin:/opt/sbin<br />
EDITOR='nano'<br />
export PATH EDITOR<br />
</nowiki></pre><br />
<br />
nano -zwc will allow nano to suspend with ctl-z and not wordwrap by default as well as show you the line numbers that your cursor is on (avoid having to hit ctrl-c looking for line numbers).<br />
<br />
These are my preferred ls cmds (yours may vary):<br />
<br />
'''PATH''' is adding the /opt/bin and /opt/sbin paths so your optware binaries work easily. This is a complete overwrite of the PATH set by default and applies to your unprivileged user as well as root. Keep that in mind if you try to run stuff out of /sbin dirs...<br />
<br />
'''EDITOR''' is setting your editor of choice for things like crontab edits or subversion if you were using that on the Pre. If you are happy with vi, you can skip the EDITOR set. If you're reading this guide, you probably want nano...<br />
<br />
nano is easily installed with <br />
<pre><nowiki>ipkg-opt install nano</nowiki></pre><br />
<br />
Okay. You are done...remount the root file system as readonly:<br />
<pre><nowiki>mount -o remount,ro /</nowiki></pre><br />
<br />
There's no need to reboot, but if you logout and log back in you can make sure you are in bash... Type some gibberish:<br />
<br />
> root@castle:/etc# asdf<br />
> bash: asdf: command not found<br />
<br />
Mmm, bashalicious...<br />
<br />
'''NOTE''' The 2nd command from the top was adding /bin/bash to /etc/shells, NOT /bin/sh. I fixed it. Also, I wasn't able to get /etc/profile.d/profile.custom to work, so I used ~/.bashrc instead. -hopspitfire<br />
<br />
= Credits=<br />
Submitted by retry.<br />
Tested to work by hopspitfire (see '''NOTE''' above).</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=Setup_Bash&diff=11544Setup Bash2010-09-25T19:20:27Z<p>Papa4narchia: /* Setup your bash profile */</p>
<hr />
<div>= Setting up Bash as a Replacment Shell for /bin/sh=<br />
<br />
== Preliminaries==<br />
# Gain [[Portal:Accessing_Linux | root access]].<br />
# Setup the [[Next_steps | Optware Feed]].<br />
# Open the root file system to read/write with rootfs_open. If you haven't yet altered your PATH (see below) use the following:<br />
<pre><nowiki>/usr/sbin/rootfs_open -w</nowiki></pre><br />
<br />
== Install bash==<br />
<pre><nowiki>ipkg-opt install bash</nowiki></pre><br />
<br />
'''Super Important:''' Before you switch your login shell in /etc/passwd, you MUST create /etc/shells and add /opt/bin/bash and /bin/sh to it. If you do not, you will lock yourself out of the Pre on anything but novacom term if you switch your default shell.<br />
<br />
<pre><nowiki>echo -e "# /etc/shells: valid login shells\n/opt/bin/bash\n/bin/sh" >/etc/shells</nowiki></pre><br />
<br />
now you can vi/nano whatever /etc/passwd and replace your unprivileged user shell with /opt/bin/bash.<br />
<br />
Before:<br />
<br />
> youruser:yourpasswordhash:1001:1001:Linux User,,,:/var/home/youruser:/bin/sh<br />
<br />
After:<br />
<br />
> youruser:yourpasswordhash:1001:1001:Linux User,,,:/var/home/youruser:/opt/bin/bash<br />
<br />
Try to SSH in with that user and be sure you can access the machine. Change root as well if you desire. Since you will probably 'sudo su' to root to perform larger tasks, you will want to stay in consistent shell.<br />
==Setup your bash profile==<br />
When a user logs in, the shell provides a certain environment for the programs running in your users context. This is achieved by setting environment variables in scripts, stored in multiple locations. That includes /etc/profile (for all users) and all the files in the /etc/profile.d directory. (Other linux distributions often add ~/.bash_profile and ~/.bashrc as well to the home directories of users.)<br />
<br />
/etc/profile.d/ is a good place to put your application specific setups and thereby setting up custom aliases, paths, editors etc.<br />
Additionally, we can append aliases and logout scripts into this [[profile-d | /etc/profile.d]] folder.<br />
<br />
1. Create the directory:<br />
<pre><nowiki>mkdir /etc/profile.d</nowiki></pre><br />
<br />
2. Add your rc file (name doesn't matter as long as it isn't a .file):<br />
<pre><nowiki>vi/nano/etc /etc/profile.d/profile.custom</nowiki></pre><br />
3) Add aliases and PATH options. Here is what I have:<br />
<pre><nowiki><br />
alias nano='nano -zwc'<br />
alias ls='ls -aF'<br />
alias ll='ls -alF'<br />
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin::/opt/bin:/opt/sbin<br />
EDITOR='nano'<br />
export PATH EDITOR<br />
</nowiki></pre><br />
<br />
nano -zwc will allow nano to suspend with ctl-z and not wordwrap by default as well as show you the line numbers that your cursor is on (avoid having to hit ctrl-c looking for line numbers).<br />
<br />
These are my preferred ls cmds (yours may vary):<br />
<br />
PATH is adding the /opt/bin and /opt/sbin paths so your optware binaries work easily. This is a complete overwrite of the PATH set by default and applies to your unprivileged user as well as root. Keep that in mind if you try to run stuff out of /sbin dirs...<br />
<br />
EDITOR is setting your editor of choice for things like crontab edits or subversion if you were using that on the Pre. If you are happy with vi, you can skip the EDITOR set. If you're reading this guide, you probably want nano...<br />
<br />
nano is easily installed with <br />
<pre><nowiki>ipkg-opt install nano</nowiki></pre><br />
<br />
Okay. You are done...remount the root file system as readonly:<br />
<pre><nowiki>mount -o remount,ro /</nowiki></pre><br />
<br />
There's no need to reboot, but if you logout and log back in you can make sure you are in bash... Type some gibberish:<br />
<br />
> root@castle:/etc# asdf<br />
> bash: asdf: command not found<br />
<br />
Mmm, bashalicious...<br />
<br />
'''NOTE''' The 2nd command from the top was adding /bin/bash to /etc/shells, NOT /bin/sh. I fixed it. Also, I wasn't able to get /etc/profile.d/profile.custom to work, so I used ~/.bashrc instead. -hopspitfire<br />
<br />
= Credits=<br />
Submitted by retry.<br />
Tested to work by hopspitfire (see '''NOTE''' above).</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=Setup_Bash&diff=11543Setup Bash2010-09-25T18:51:17Z<p>Papa4narchia: /* Setup your bash profile */</p>
<hr />
<div>= Setting up Bash as a Replacment Shell for /bin/sh=<br />
<br />
== Preliminaries==<br />
# Gain [[Portal:Accessing_Linux | root access]].<br />
# Setup the [[Next_steps | Optware Feed]].<br />
# Open the root file system to read/write with rootfs_open. If you haven't yet altered your PATH (see below) use the following:<br />
<pre><nowiki>/usr/sbin/rootfs_open -w</nowiki></pre><br />
<br />
== Install bash==<br />
<pre><nowiki>ipkg-opt install bash</nowiki></pre><br />
<br />
'''Super Important:''' Before you switch your login shell in /etc/passwd, you MUST create /etc/shells and add /opt/bin/bash and /bin/sh to it. If you do not, you will lock yourself out of the Pre on anything but novacom term if you switch your default shell.<br />
<br />
<pre><nowiki>echo -e "# /etc/shells: valid login shells\n/opt/bin/bash\n/bin/sh" >/etc/shells</nowiki></pre><br />
<br />
now you can vi/nano whatever /etc/passwd and replace your unprivileged user shell with /opt/bin/bash.<br />
<br />
Before:<br />
<br />
> youruser:yourpasswordhash:1001:1001:Linux User,,,:/var/home/youruser:/bin/sh<br />
<br />
After:<br />
<br />
> youruser:yourpasswordhash:1001:1001:Linux User,,,:/var/home/youruser:/opt/bin/bash<br />
<br />
Try to SSH in with that user and be sure you can access the machine. Change root as well if you desire. Since you will probably 'sudo su' to root to perform larger tasks, you will want to stay in consistent shell.<br />
==Setup your bash profile==<br />
When a user logs in, the shell provides a certain environment for the programs running in your users context. This is achieved by setting environment variables in scripts, stored in multiple locations. That includes /etc/profile (for all users) and all the files in the /etc/profile.d directory. (Other linux distributions often add ~/.bash_profile and ~/.bashrc as well to the home directories of users.)<br />
<br />
/etc/profile.d/ is a good place to put your application specific setups and thereby setting up custom aliases, paths, editors etc.<br />
Additionally, we can append aliases and logout scripts into this [[profile-d | /etc/profile.d]] folder.<br />
<br />
1. Create the directory:<br />
<pre><nowiki>mkdir /etc/profile.d</nowiki></pre><br />
<br />
2. Add your rc file (name doesn't matter as long as it isn't a .file):<br />
<pre><nowiki>vi/nano/etc /etc/profile.d/profile.custom</nowiki></pre><br />
3) Add aliases and PATH options. Here is what I have:<br />
<pre><nowiki><br />
alias nano='nano -zwc'<br />
alias ls='ls -aF'<br />
alias ll='ls -alF'<br />
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin::/opt/bin:/opt/sbin<br />
EDITOR='nano'<br />
export PATH EDITOR<br />
</nowiki></pre><br />
<br />
nano -zwc will allow nano to suspend with ctl-z and not wordwrap by default as well as show you the line numbers that your cursor is on (avoid having to hit ctrl-c looking for line numbers).<br />
<br />
These are my preferred ls cmds (yours may vary):<br />
<br />
PATH is adding the /opt/bin and /opt/sbin paths so your optware binaries work easily. This is a complete overwrite of the PATH set by default and applies to your unprivileged user as well as root. Keep that in mind if you try to run stuff out of /sbin dirs...<br />
<br />
EDITOR is setting your editor of choice for things like crontab edits or subversion if you were using that on the Pre. If you are happy with vi, you can skip the EDITOR set. If you're reading this guide, you probably want nano...<br />
<br />
nano is easily installed with ipkg-opt install nano...<br />
<br />
Okay. You are done...remount the root file system as readonly:<br />
<pre><nowiki>mount -o remount,ro /</nowiki></pre><br />
<br />
There's no need to reboot, but if you logout and log back in you can make sure you are in bash... Type some gibberish:<br />
<br />
> root@castle:/etc# asdf<br />
> bash: asdf: command not found<br />
<br />
Mmm, bashalicious...<br />
<br />
'''NOTE''' The 2nd command from the top was adding /bin/bash to /etc/shells, NOT /bin/sh. I fixed it. Also, I wasn't able to get /etc/profile.d/profile.custom to work, so I used ~/.bashrc instead. -hopspitfire<br />
<br />
= Credits=<br />
Submitted by retry.<br />
Tested to work by hopspitfire (see '''NOTE''' above).</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=Setup_Bash&diff=11542Setup Bash2010-09-25T18:42:06Z<p>Papa4narchia: /* Bash profile */</p>
<hr />
<div>= Setting up Bash as a Replacment Shell for /bin/sh=<br />
<br />
== Preliminaries==<br />
# Gain [[Portal:Accessing_Linux | root access]].<br />
# Setup the [[Next_steps | Optware Feed]].<br />
# Open the root file system to read/write with rootfs_open. If you haven't yet altered your PATH (see below) use the following:<br />
<pre><nowiki>/usr/sbin/rootfs_open -w</nowiki></pre><br />
<br />
== Install bash==<br />
<pre><nowiki>ipkg-opt install bash</nowiki></pre><br />
<br />
'''Super Important:''' Before you switch your login shell in /etc/passwd, you MUST create /etc/shells and add /opt/bin/bash and /bin/sh to it. If you do not, you will lock yourself out of the Pre on anything but novacom term if you switch your default shell.<br />
<br />
<pre><nowiki>echo -e "# /etc/shells: valid login shells\n/opt/bin/bash\n/bin/sh" >/etc/shells</nowiki></pre><br />
<br />
now you can vi/nano whatever /etc/passwd and replace your unprivileged user shell with /opt/bin/bash.<br />
<br />
Before:<br />
<br />
> youruser:yourpasswordhash:1001:1001:Linux User,,,:/var/home/youruser:/bin/sh<br />
<br />
After:<br />
<br />
> youruser:yourpasswordhash:1001:1001:Linux User,,,:/var/home/youruser:/opt/bin/bash<br />
<br />
Try to SSH in with that user and be sure you can access the machine. Change root as well if you desire. Since you will probably 'sudo su' to root to perform larger tasks, you will want to stay in consistent shell.<br />
==Setup your bash profile==<br />
'''Add custom aliases/paths/editor etc with /etc/profile.d dir'''<br />
<br />
//Additionally, we can append aliases and logout scripts into this [[profile-d | /etc/profile.d]] folder :-)//<br />
<br />
1. Create the directory:<br />
<pre><nowiki>mkdir /etc/profile.d</nowiki></pre><br />
<br />
2. Add your rc file (name doesn't matter as long as it isn't a .file):<br />
<pre><nowiki>vi/nano/etc /etc/profile.d/profile.custom</nowiki></pre><br />
3) Add aliases and PATH options. Here is what I have:<br />
<pre><nowiki><br />
alias nano='nano -zwc'<br />
alias ls='ls -aF'<br />
alias ll='ls -alF'<br />
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin::/opt/bin:/opt/sbin<br />
EDITOR='nano'<br />
export PATH EDITOR<br />
</nowiki></pre><br />
<br />
nano -zwc will allow nano to suspend with ctl-z and not wordwrap by default as well as show you the line numbers that your cursor is on (avoid having to hit ctrl-c looking for line numbers).<br />
<br />
These are my preferred ls cmds (yours may vary):<br />
<br />
PATH is adding the /opt/bin and /opt/sbin paths so your optware binaries work easily. This is a complete overwrite of the PATH set by default and applies to your unprivileged user as well as root. Keep that in mind if you try to run stuff out of /sbin dirs...<br />
<br />
EDITOR is setting your editor of choice for things like crontab edits or subversion if you were using that on the Pre. If you are happy with vi, you can skip the EDITOR set. If you're reading this guide, you probably want nano...<br />
<br />
nano is easily installed with ipkg-opt install nano...<br />
<br />
Okay. You are done...remount the root file system as readonly:<br />
<pre><nowiki>mount -o remount,ro /</nowiki></pre><br />
<br />
There's no need to reboot, but if you logout and log back in you can make sure you are in bash... Type some gibberish:<br />
<br />
> root@castle:/etc# asdf<br />
> bash: asdf: command not found<br />
<br />
Mmm, bashalicious...<br />
<br />
'''NOTE''' The 2nd command from the top was adding /bin/bash to /etc/shells, NOT /bin/sh. I fixed it. Also, I wasn't able to get /etc/profile.d/profile.custom to work, so I used ~/.bashrc instead. -hopspitfire<br />
<br />
= Credits=<br />
Submitted by retry.<br />
Tested to work by hopspitfire (see '''NOTE''' above).</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=Setup_Bash&diff=11541Setup Bash2010-09-25T18:41:24Z<p>Papa4narchia: /* Install bash */</p>
<hr />
<div>= Setting up Bash as a Replacment Shell for /bin/sh=<br />
<br />
== Preliminaries==<br />
# Gain [[Portal:Accessing_Linux | root access]].<br />
# Setup the [[Next_steps | Optware Feed]].<br />
# Open the root file system to read/write with rootfs_open. If you haven't yet altered your PATH (see below) use the following:<br />
<pre><nowiki>/usr/sbin/rootfs_open -w</nowiki></pre><br />
<br />
== Install bash==<br />
<pre><nowiki>ipkg-opt install bash</nowiki></pre><br />
<br />
'''Super Important:''' Before you switch your login shell in /etc/passwd, you MUST create /etc/shells and add /opt/bin/bash and /bin/sh to it. If you do not, you will lock yourself out of the Pre on anything but novacom term if you switch your default shell.<br />
<br />
<pre><nowiki>echo -e "# /etc/shells: valid login shells\n/opt/bin/bash\n/bin/sh" >/etc/shells</nowiki></pre><br />
<br />
now you can vi/nano whatever /etc/passwd and replace your unprivileged user shell with /opt/bin/bash.<br />
<br />
Before:<br />
<br />
> youruser:yourpasswordhash:1001:1001:Linux User,,,:/var/home/youruser:/bin/sh<br />
<br />
After:<br />
<br />
> youruser:yourpasswordhash:1001:1001:Linux User,,,:/var/home/youruser:/opt/bin/bash<br />
<br />
Try to SSH in with that user and be sure you can access the machine. Change root as well if you desire. Since you will probably 'sudo su' to root to perform larger tasks, you will want to stay in consistent shell.<br />
==Bash profile==<br />
'''Add custom aliases/paths/editor etc with /etc/profile.d dir'''<br />
<br />
//Additionally, we can append aliases and logout scripts into this [[profile-d | /etc/profile.d]] folder :-)//<br />
<br />
1. Create the directory:<br />
<pre><nowiki>mkdir /etc/profile.d</nowiki></pre><br />
<br />
2. Add your rc file (name doesn't matter as long as it isn't a .file):<br />
<pre><nowiki>vi/nano/etc /etc/profile.d/profile.custom</nowiki></pre><br />
3) Add aliases and PATH options. Here is what I have:<br />
<pre><nowiki><br />
alias nano='nano -zwc'<br />
alias ls='ls -aF'<br />
alias ll='ls -alF'<br />
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin::/opt/bin:/opt/sbin<br />
EDITOR='nano'<br />
export PATH EDITOR<br />
</nowiki></pre><br />
<br />
nano -zwc will allow nano to suspend with ctl-z and not wordwrap by default as well as show you the line numbers that your cursor is on (avoid having to hit ctrl-c looking for line numbers).<br />
<br />
These are my preferred ls cmds (yours may vary):<br />
<br />
PATH is adding the /opt/bin and /opt/sbin paths so your optware binaries work easily. This is a complete overwrite of the PATH set by default and applies to your unprivileged user as well as root. Keep that in mind if you try to run stuff out of /sbin dirs...<br />
<br />
EDITOR is setting your editor of choice for things like crontab edits or subversion if you were using that on the Pre. If you are happy with vi, you can skip the EDITOR set. If you're reading this guide, you probably want nano...<br />
<br />
nano is easily installed with ipkg-opt install nano...<br />
<br />
Okay. You are done...remount the root file system as readonly:<br />
<pre><nowiki>mount -o remount,ro /</nowiki></pre><br />
<br />
There's no need to reboot, but if you logout and log back in you can make sure you are in bash... Type some gibberish:<br />
<br />
> root@castle:/etc# asdf<br />
> bash: asdf: command not found<br />
<br />
Mmm, bashalicious...<br />
<br />
'''NOTE''' The 2nd command from the top was adding /bin/bash to /etc/shells, NOT /bin/sh. I fixed it. Also, I wasn't able to get /etc/profile.d/profile.custom to work, so I used ~/.bashrc instead. -hopspitfire<br />
<br />
= Credits=<br />
Submitted by retry.<br />
Tested to work by hopspitfire (see '''NOTE''' above).</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=Setup_Bash&diff=11540Setup Bash2010-09-25T18:40:17Z<p>Papa4narchia: /* Preliminaries */</p>
<hr />
<div>= Setting up Bash as a Replacment Shell for /bin/sh=<br />
<br />
== Preliminaries==<br />
# Gain [[Portal:Accessing_Linux | root access]].<br />
# Setup the [[Next_steps | Optware Feed]].<br />
# Open the root file system to read/write with rootfs_open. If you haven't yet altered your PATH (see below) use the following:<br />
<pre><nowiki>/usr/sbin/rootfs_open -w</nowiki></pre><br />
<br />
== Install bash==<br />
<pre><nowiki>ipkg-opt install bash</nowiki></pre><br />
<br />
'''Super Important:''' Before you switch your login shell in /etc/passwd, you MUST create /etc/shells and add /opt/bin/bash and /bin/sh to it. If you do not, you will lock yourself out of the Pre on anything but novacom term if you switch your default shell.<br />
<br />
<pre><nowiki>echo -e "# /etc/shells: valid login shells\n/opt/bin/bash\n/bin/sh" >/etc/shells</nowiki></pre><br />
<br />
now you can vi/nano whatever /etc/passwd and replace your unprivileged user shell with /opt/bin/bash.<br />
<br />
Before:<br />
<br />
> youruser:yourpasswordhash:1001:1001:Linux User,,,:/var/home/youruser:/bin/sh<br />
<br />
After:<br />
<br />
> youruser:yourpasswordhash:1001:1001:Linux User,,,:/var/home/youruser:/opt/bin/bash<br />
<br />
Try to SSH in with that user and be sure you can access the machine. Change root as well if you desire. Since you will probably 'sudo su' to root to perform larger tasks, you will want to stay in consistent shell.<br />
<br />
'''Add custom aliases/paths/editor etc with /etc/profile.d dir'''<br />
<br />
//Additionally, we can append aliases and logout scripts into this [[profile-d | /etc/profile.d]] folder :-)//<br />
<br />
1. Create the directory:<br />
<pre><nowiki>mkdir /etc/profile.d</nowiki></pre><br />
<br />
2. Add your rc file (name doesn't matter as long as it isn't a .file):<br />
<pre><nowiki>vi/nano/etc /etc/profile.d/profile.custom</nowiki></pre><br />
3) Add aliases and PATH options. Here is what I have:<br />
<pre><nowiki><br />
alias nano='nano -zwc'<br />
alias ls='ls -aF'<br />
alias ll='ls -alF'<br />
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin::/opt/bin:/opt/sbin<br />
EDITOR='nano'<br />
export PATH EDITOR<br />
</nowiki></pre><br />
<br />
nano -zwc will allow nano to suspend with ctl-z and not wordwrap by default as well as show you the line numbers that your cursor is on (avoid having to hit ctrl-c looking for line numbers).<br />
<br />
These are my preferred ls cmds (yours may vary):<br />
<br />
PATH is adding the /opt/bin and /opt/sbin paths so your optware binaries work easily. This is a complete overwrite of the PATH set by default and applies to your unprivileged user as well as root. Keep that in mind if you try to run stuff out of /sbin dirs...<br />
<br />
EDITOR is setting your editor of choice for things like crontab edits or subversion if you were using that on the Pre. If you are happy with vi, you can skip the EDITOR set. If you're reading this guide, you probably want nano...<br />
<br />
nano is easily installed with ipkg-opt install nano...<br />
<br />
Okay. You are done...remount the root file system as readonly:<br />
<pre><nowiki>mount -o remount,ro /</nowiki></pre><br />
<br />
There's no need to reboot, but if you logout and log back in you can make sure you are in bash... Type some gibberish:<br />
<br />
> root@castle:/etc# asdf<br />
> bash: asdf: command not found<br />
<br />
Mmm, bashalicious...<br />
<br />
'''NOTE''' The 2nd command from the top was adding /bin/bash to /etc/shells, NOT /bin/sh. I fixed it. Also, I wasn't able to get /etc/profile.d/profile.custom to work, so I used ~/.bashrc instead. -hopspitfire<br />
<br />
= Credits=<br />
Submitted by retry.<br />
Tested to work by hopspitfire (see '''NOTE''' above).</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=Setup_Bash&diff=11539Setup Bash2010-09-25T18:39:57Z<p>Papa4narchia: /* Preliminaries */</p>
<hr />
<div>= Setting up Bash as a Replacment Shell for /bin/sh=<br />
<br />
== Preliminaries==<br />
# Gain [[Portal:Accessing_Linux | root access]].<br />
# Setup the [[Next_steps | Optware Feed]].<br />
# Open the root file system to read/write with rootfs_open. If you haven't yet altered your PATH (see below) use the following:<br />
<pre><nowiki>/usr/sbin/rootfs_open -w</nowiki><pre><br />
<br />
== Install bash==<br />
<pre><nowiki>ipkg-opt install bash</nowiki></pre><br />
<br />
'''Super Important:''' Before you switch your login shell in /etc/passwd, you MUST create /etc/shells and add /opt/bin/bash and /bin/sh to it. If you do not, you will lock yourself out of the Pre on anything but novacom term if you switch your default shell.<br />
<br />
<pre><nowiki>echo -e "# /etc/shells: valid login shells\n/opt/bin/bash\n/bin/sh" >/etc/shells</nowiki></pre><br />
<br />
now you can vi/nano whatever /etc/passwd and replace your unprivileged user shell with /opt/bin/bash.<br />
<br />
Before:<br />
<br />
> youruser:yourpasswordhash:1001:1001:Linux User,,,:/var/home/youruser:/bin/sh<br />
<br />
After:<br />
<br />
> youruser:yourpasswordhash:1001:1001:Linux User,,,:/var/home/youruser:/opt/bin/bash<br />
<br />
Try to SSH in with that user and be sure you can access the machine. Change root as well if you desire. Since you will probably 'sudo su' to root to perform larger tasks, you will want to stay in consistent shell.<br />
<br />
'''Add custom aliases/paths/editor etc with /etc/profile.d dir'''<br />
<br />
//Additionally, we can append aliases and logout scripts into this [[profile-d | /etc/profile.d]] folder :-)//<br />
<br />
1. Create the directory:<br />
<pre><nowiki>mkdir /etc/profile.d</nowiki></pre><br />
<br />
2. Add your rc file (name doesn't matter as long as it isn't a .file):<br />
<pre><nowiki>vi/nano/etc /etc/profile.d/profile.custom</nowiki></pre><br />
3) Add aliases and PATH options. Here is what I have:<br />
<pre><nowiki><br />
alias nano='nano -zwc'<br />
alias ls='ls -aF'<br />
alias ll='ls -alF'<br />
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin::/opt/bin:/opt/sbin<br />
EDITOR='nano'<br />
export PATH EDITOR<br />
</nowiki></pre><br />
<br />
nano -zwc will allow nano to suspend with ctl-z and not wordwrap by default as well as show you the line numbers that your cursor is on (avoid having to hit ctrl-c looking for line numbers).<br />
<br />
These are my preferred ls cmds (yours may vary):<br />
<br />
PATH is adding the /opt/bin and /opt/sbin paths so your optware binaries work easily. This is a complete overwrite of the PATH set by default and applies to your unprivileged user as well as root. Keep that in mind if you try to run stuff out of /sbin dirs...<br />
<br />
EDITOR is setting your editor of choice for things like crontab edits or subversion if you were using that on the Pre. If you are happy with vi, you can skip the EDITOR set. If you're reading this guide, you probably want nano...<br />
<br />
nano is easily installed with ipkg-opt install nano...<br />
<br />
Okay. You are done...remount the root file system as readonly:<br />
<pre><nowiki>mount -o remount,ro /</nowiki></pre><br />
<br />
There's no need to reboot, but if you logout and log back in you can make sure you are in bash... Type some gibberish:<br />
<br />
> root@castle:/etc# asdf<br />
> bash: asdf: command not found<br />
<br />
Mmm, bashalicious...<br />
<br />
'''NOTE''' The 2nd command from the top was adding /bin/bash to /etc/shells, NOT /bin/sh. I fixed it. Also, I wasn't able to get /etc/profile.d/profile.custom to work, so I used ~/.bashrc instead. -hopspitfire<br />
<br />
= Credits=<br />
Submitted by retry.<br />
Tested to work by hopspitfire (see '''NOTE''' above).</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=Portal:Accessing_Linux&diff=11536Portal:Accessing Linux2010-09-25T12:26:35Z<p>Papa4narchia: </p>
<hr />
<div>@<br />
__notoc__<br />
{{portal-one-column-blue<br />
|header=Accessing Linux on the Pre or the Pre Emulator<br />
|column1=<br />
The Palm Pre is a Linux based device. Palm provides a simple method to access Linux running on the Pre or the Pre Emulator. A terminal program called ''novaterm'' is bundled with the freely available SDK, enabling command line access to your device (see below for instructions).<br />
<br />
Once you have command line access to Linux, everything else is a process of installing a ''community standard library'' of Linux programs so that users have the same tools and options available to them. (For example, you can [[OpenSSH_Install|install openssh]] or [[Dropbear_Install|dropbear]] enabling shell access to your device.) Once this is process is completed, pretty much anything you can do on a Linux box you can also do on the Pre or the Pre Emulator. <br />
<br />
Notice, that the described procedure below is not compulsorily necessary for you to just install further linux software packages to your device. The [[Application:Preware|Preware]] application manager (an app you install to your device) is capable of installing these as well.<br />
<br />
The following procedures will walk you through the process of obtaining initial command line access to Linux via novaterm on the Pre or the Pre Emulator, and installing the community standard software packages. The same instructions apply to the Pixi as well.<br />
<br />
}}<br />
<br />
{{portal-two-columns<br />
|column1=<br />
== Before you start == <br />
<br />
Please make a note of this page: [[How To Recover]]<br />
<br />
If you are unfamiliar with basic Linux command usage, you should visit this page: [[Basic_Linux_Use|Basic Linux Use]]<br />
<br />
===Disclaimer===<br />
Enacting any set of instructions from this site has the (remote, but greater than zero) potential to void your warranty. Our intention and the specific design of all instructions is such that you should be able to recover using the [http://www.palm.com/ROM webOS Doctor] should anything go wrong, and put your Pre back to a state which is indistinguishable from a factory-new Pre, but we give no guarantee. Use any information from this site at your own risk. At the very least, you should be prepared to lose all data on your phone at any time. We cannot tell you what you should do - we provide the information, but it's up to your own sense of personal responsibility to determine what you do with that information. '''We require you to use the [http://www.palm.com/ROM webOS Doctor] to put your Pre back to factory condition before contacting Palm or your cellular carrier for service or support.'''<br />
<br />
You might also want to consider backing up any files you have in the usb drive portion of the Pre. <br />
|column2=<br />
== Procedure: ==<br />
<br />
In general, simply installing the Palm SDK gives you everything you need for full access to the Linux operating system on the Pre or Pixi. There is no special "rooting" or "jailbreaking" process. Simply installing the SDK provides you with unlimited access to the Linux operating system logged in as the root user. Palm does not see this as a bad thing. '''Palm''' provides all these tools for download by anyone, anytime, for free. <br />
<br />
# Download the [http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1788&Itemid=321# Palm SDK].<br />
# Install it using the installation instructions for [http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1545&Itemid=55 Mac], [http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1585&Itemid=55 Linux], or [http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1661&Itemid=55 Windows].<br />
# Enable dev mode on your Pre:<br />
## In Card view or in the Launcher application, type the following: webos20090606<br />
## Tap the resulting Developer Mode Enabler icon.<br />
## In the application, move the Developer Mode slider to the On position.<br />
## Tap Reset the Device . <br />
##* When reset is complete, Developer mode is enabled.<br />
# Plug the device into the computer via the USB cable, and select "Charge only." <br />
# The next step varies: <br />
#* On Mac or Linux, type '''novaterm''' in a command (terminal) window to directly access the Linux command line.<br />
#* On Windows you will need to download and install a novaterm program. <br />
#** On 32 bit Windows download [http://tkgeisel.com/stuff/novaterm-1.zip novaterm1.zip] and unzip it into the \program files\palm\sdk\bin directory. <br />
#** On 64 bit Windows download [http://vocshop.com/stuff/novaterm64.zip novaterm64.zip] and unzip it into the \program files\palm\sdk\bin directory. <br />
#**Then, just like the Mac and Linux users you can just type '''novaterm'''.<br />
<br />
'''At this point you will have a window with a prompt that says root@webos-device: or something similar. <br />
<br />
You are now logged in as root on your webOS device and can do anything you would normally do on a Linux device. <br />
<br />
Please be careful, you can seriously bork your phone now. '''<br />
<br />
'''IMPORTANT NOTE:''' <br />
With the addition of the ability to install Optware packages to Preware, unless you have a need or desire to type commands into the native Linux shell of your Palm device, there is no need to use the novaterm terminal to log into your devices. ''' Webos Quick Install''' (a java program for your desktop) and '''Preware''' (an app to run on your device) '''are fully capable of installing any Optware IPK (including *.patch and *.diff) to Palm devices'''. Linux command line access is needed by very few people. If you came here from a web page that talked about "root access" or "rooting your Pre" be aware that most of the instructions which require root access have been superseded. <br />
<br />
<br />
}}<br />
{{portal-two-columns<br />
|column1=<br />
== Advanced Topics ==<br />
<br />
* [[Adding Disks to the Emulator]]<br />
* [[Backing_Up_via_Rsync|Backing Up via Rsync]]<br />
<br />
|column2=<br />
== Next Steps ==<br />
<br />
* [[Tutorials_Linux_DDNS_for_EVDO|DDNS for EVDO]]<br />
* [[Next_steps|Set up users, Optware, and access]] '''DEPRECATED'''<br />
* [[Applying_Patches|Applying Patches]] '''DEPRECATED''' <br />
* [[Setup_SFTP|Setup SFTP]] '''DEPRECATED'''<br />
<br />
<br />
}}</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=Portal:Accessing_Linux&diff=11535Portal:Accessing Linux2010-09-25T12:23:08Z<p>Papa4narchia: </p>
<hr />
<div>@<br />
__notoc__<br />
{{portal-one-column-blue<br />
|header=Accessing Linux on the Pre or the Pre Emulator<br />
|column1=<br />
The Palm Pre is a Linux based device. Palm provides a simple method to access Linux running on the Pre or the Pre Emulator. A terminal program called ''novaterm'' is bundled with the freely available SDK, enabling commandline access to your device (see below for instructions).<br />
<br />
Once you have commandline access to Linux, everything else is a process of installing a ''community standard library'' of Linux programs so that users have the same tools and options available to them. (For example, you can [[OpenSSH_Install|install openssh]] or [[Dropbear_Install|dropbear]] enabling shell access to your device.) Once this is process is completed, pretty much anything you can do on a Linux box you can also do on the Pre or the Pre Emulator. <br />
<br />
Notice, that the described procedure below is not compulsorily necessary for you to just install further linux software packages to your device. The [[Application:Preware|Preware]] application manager (an app you install to your device) is capable of installing these as well.<br />
<br />
The following procedures will walk you through the process of obtaining initial commandline access to Linux via novaterm on the Pre or the Pre Emulator, and installing the community standard software packages. The same instructions apply to the Pixi as well.<br />
<br />
}}<br />
<br />
{{portal-two-columns<br />
|column1=<br />
== Before you start == <br />
<br />
Please make a note of this page: [[How To Recover]]<br />
<br />
If you are unfamiliar with basic Linux command usage, you should visit this page: [[Basic_Linux_Use|Basic Linux Use]]<br />
<br />
===Disclaimer===<br />
Enacting any set of instructions from this site has the (remote, but greater than zero) potential to void your warranty. Our intention and the specific design of all instructions is such that you should be able to recover using the [http://www.palm.com/ROM webOS Doctor] should anything go wrong, and put your Pre back to a state which is indistinguishable from a factory-new Pre, but we give no guarantee. Use any information from this site at your own risk. At the very least, you should be prepared to lose all data on your phone at any time. We cannot tell you what you should do - we provide the information, but it's up to your own sense of personal responsibility to determine what you do with that information. '''We require you to use the [http://www.palm.com/ROM webOS Doctor] to put your Pre back to factory condition before contacting Palm or your cellular carrier for service or support.'''<br />
<br />
You might also want to consider backing up any files you have in the usb drive portion of the Pre. <br />
|column2=<br />
== Procedure: ==<br />
<br />
In general, simply installing the Palm SDK gives you everything you need for full access to the Linux operating system on the Pre or Pixi. There is no special "rooting" or "jailbreaking" process. Simply installing the SDK provides you with unlimited access to the Linux operating system logged in as the root user. Palm does not see this as a bad thing. '''Palm''' provides all these tools for download by anyone, anytime, for free. <br />
<br />
# Download the [http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1788&Itemid=321# Palm SDK].<br />
# Install it using the installation instructions for [http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1545&Itemid=55 Mac], [http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1585&Itemid=55 Linux], or [http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1661&Itemid=55 Windows].<br />
# Enable dev mode on your Pre:<br />
## In Card view or in the Launcher application, type the following: webos20090606<br />
## Tap the resulting Developer Mode Enabler icon.<br />
## In the application, move the Developer Mode slider to the On position.<br />
## Tap Reset the Device . <br />
##* When reset is complete, Developer mode is enabled.<br />
# Plug the device into the computer via the USB cable, and select "Charge only." <br />
# The next step varies: <br />
#* On Mac or Linux, type '''novaterm''' in a command (terminal) window to directly access the Linux command line.<br />
#* On Windows you will need to download and install a novaterm program. <br />
#** On 32 bit Windows download [http://tkgeisel.com/stuff/novaterm-1.zip novaterm1.zip] and unzip it into the \program files\palm\sdk\bin directory. <br />
#** On 64 bit Windows download [http://vocshop.com/stuff/novaterm64.zip novaterm64.zip] and unzip it into the \program files\palm\sdk\bin directory. <br />
#**Then, just like the Mac and Linux users you can just type '''novaterm'''.<br />
<br />
'''At this point you will have a window with a prompt that says root@webos-device: or something similar. <br />
<br />
You are now logged in as root on your webOS device and can do anything you would normally do on a Linux device. <br />
<br />
Please be careful, you can seriously bork your phone now. '''<br />
<br />
'''IMPORTANT NOTE:''' <br />
With the addition of the ability to install Optware packages to Preware, unless you have a need or desire to type commands into the native Linux of the Pre, there is no need to use the novaterm terminal to log into your devices. ''' Webos Quick Install''' (a java program for your desktop) and '''Preware''' (an App to run on your device) '''are fully capable of installing any Optware IPK to Palm devices'''. This Linux command line access is needed by very few people. If you came here from a web page that talked about "root access" or "rooting your Pre" be aware that most of the instructions which require root access have been superseded. <br />
<br />
<br />
}}<br />
{{portal-two-columns<br />
|column1=<br />
== Advanced Topics ==<br />
<br />
* [[Adding Disks to the Emulator]]<br />
* [[Backing_Up_via_Rsync|Backing Up via Rsync]]<br />
<br />
|column2=<br />
== Next Steps ==<br />
<br />
* [[Tutorials_Linux_DDNS_for_EVDO|DDNS for EVDO]]<br />
* [[Next_steps|Set up users, Optware, and access]] '''DEPRECATED'''<br />
* [[Applying_Patches|Applying Patches]] '''DEPRECATED''' <br />
* [[Setup_SFTP|Setup SFTP]] '''DEPRECATED'''<br />
<br />
<br />
}}</div>Papa4narchiahttp://wiki.webos-internals.org/index.php?title=Portal:Accessing_Linux&diff=11534Portal:Accessing Linux2010-09-25T12:14:27Z<p>Papa4narchia: </p>
<hr />
<div>@<br />
__notoc__<br />
{{portal-one-column-blue<br />
|header=Accessing Linux on the Pre or the Pre Emulator<br />
|column1=<br />
The Palm Pre is a Linux based device. Palm provides a simple method to access Linux running on the Pre or the Pre Emulator. A terminal program called ''novaterm'' is bundled with the freely available SDK, enabling commandline access to your device (see below for instructions).<br />
<br />
Once you have commandline access to Linux, everything else is a process of installing a ''community standard library'' of Linux programs so that users have the same tools and options available to them. (For example, you can [[OpenSSH_Install|install openssh]] or [[Dropbear_Install|dropbear]] enabling shell access to your device.) Once this is process is completed, pretty much anything you can do on a Linux box you can also do on the Pre or the Pre Emulator.<br />
<br />
The following procedures will walk you through the process of obtaining initial commandline access to Linux via novaterm on the Pre or the Pre Emulator, and installing the community standard software packages. The same instructions apply to the Pixi as well.<br />
<br />
}}<br />
<br />
{{portal-two-columns<br />
|column1=<br />
== Before you start == <br />
<br />
Please make a note of this page: [[How To Recover]]<br />
<br />
If you are unfamiliar with basic Linux command usage, you should visit this page: [[Basic_Linux_Use|Basic Linux Use]]<br />
<br />
===Disclaimer===<br />
Enacting any set of instructions from this site has the (remote, but greater than zero) potential to void your warranty. Our intention and the specific design of all instructions is such that you should be able to recover using the [http://www.palm.com/ROM webOS Doctor] should anything go wrong, and put your Pre back to a state which is indistinguishable from a factory-new Pre, but we give no guarantee. Use any information from this site at your own risk. At the very least, you should be prepared to lose all data on your phone at any time. We cannot tell you what you should do - we provide the information, but it's up to your own sense of personal responsibility to determine what you do with that information. '''We require you to use the [http://www.palm.com/ROM webOS Doctor] to put your Pre back to factory condition before contacting Palm or your cellular carrier for service or support.'''<br />
<br />
You might also want to consider backing up any files you have in the usb drive portion of the Pre. <br />
|column2=<br />
== Procedure: ==<br />
<br />
In general, simply installing the Palm SDK gives you everything you need for full access to the Linux operating system on the Pre or Pixi. There is no special "rooting" or "jailbreaking" process. Simply installing the SDK provides you with unlimited access to the Linux operating system logged in as the root user. Palm does not see this as a bad thing. '''Palm''' provides all these tools for download by anyone, anytime, for free. <br />
<br />
# Download the [http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1788&Itemid=321# Palm SDK].<br />
# Install it using the installation instructions for [http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1545&Itemid=55 Mac], [http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1585&Itemid=55 Linux], or [http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1661&Itemid=55 Windows].<br />
# Enable dev mode on your Pre:<br />
## In Card view or in the Launcher application, type the following: webos20090606<br />
## Tap the resulting Developer Mode Enabler icon.<br />
## In the application, move the Developer Mode slider to the On position.<br />
## Tap Reset the Device . <br />
##* When reset is complete, Developer mode is enabled.<br />
# Plug the device into the computer via the USB cable, and select "Charge only." <br />
# The next step varies: <br />
#* On Mac or Linux, type '''novaterm''' in a command (terminal) window to directly access the Linux command line.<br />
#* On Windows you will need to download and install a novaterm program. <br />
#** On 32 bit Windows download [http://tkgeisel.com/stuff/novaterm-1.zip novaterm1.zip] and unzip it into the \program files\palm\sdk\bin directory. <br />
#** On 64 bit Windows download [http://vocshop.com/stuff/novaterm64.zip novaterm64.zip] and unzip it into the \program files\palm\sdk\bin directory. <br />
#**Then, just like the Mac and Linux users you can just type '''novaterm'''.<br />
<br />
'''At this point you will have a window with a prompt that says root@webos-device: or something similar. <br />
<br />
You are now logged in as root on your webOS device and can do anything you would normally do on a Linux device. <br />
<br />
Please be careful, you can seriously bork your phone now. '''<br />
<br />
'''NOTE:''' with the addition of the ability to install Optware packages to Preware, unless you have a need or desire to type commands into the native Linux of the Pre, there is no need to do this. Webos Quick Install and Preware are fully capable of installing any Optware IPK to the Pre. This Linux command line access is needed by very few people. If you came here from a web page that talked about "root access" or "rooting your Pre" be aware that most of the instructions which require root access have been superceded. <br />
<br />
<br />
}}<br />
{{portal-two-columns<br />
|column1=<br />
== Advanced Topics ==<br />
<br />
* [[Adding Disks to the Emulator]]<br />
* [[Backing_Up_via_Rsync|Backing Up via Rsync]]<br />
<br />
|column2=<br />
== Next Steps ==<br />
<br />
* [[Tutorials_Linux_DDNS_for_EVDO|DDNS for EVDO]]<br />
* [[Next_steps|Set up users, Optware, and access]] '''DEPRECATED'''<br />
* [[Applying_Patches|Applying Patches]] '''DEPRECATED''' <br />
* [[Setup_SFTP|Setup SFTP]] '''DEPRECATED'''<br />
<br />
<br />
}}</div>Papa4narchia