Beta

unsorted, untested, random rumbling

install freevo on ubuntu hardy
http://sourceforge.net/mailarchive/message.php?msg_id=901f25b80804040317w5970530pa758688dbd4261b3%40mail.gmail.com

<howto>

Installing Kaa (Revision: 3247) & Freevo rel-1 (Revision: 10605) from
SVN in Ubuntu Hardy

1. Installation method

In this howto the latest Kaa & Freevo sources are downloaded from
the subversion repository. All possible dependencies are installed as
Ubuntu packages from the official repositories (and exception to this
is pyxml). The target operating system is Ubuntu Hardy. As suggested
in the Freevo wiki page SourceSVNInstallation the installations of Kaa
& Freevo are done to ~/freevo-test.

2. Create directories for the svn download & installation

$ mkdir ~/freevo-svn
$ mkdir ~/freevo-test

3. Install common prerequisites

$ sudo apt-get install build-essential python-dev subversion

3. Kaa

3.1 Installing dependencies

$ sudo apt-get install libimlib2-dev libxine-dev libgl1-mesa-dev \
libdvdread-dev python-pysqlite2 libmng-dev librsvg2-dev

NOTE: Replace libgl1-mesa-dev with nvidia-glx-dev if you're using
nvidia-glx. (nvidia-glx is part of the propietary nvidia X.org driver).

3.2 Installing Kaa

$ cd ~/freevo-svn
$ svn co svn://svn.freevo.org/kaa/trunk kaa
$ cd kaa
$ python setup.py install --prefix=~/freevo-test

4. Freevo

4.1 Installing package dependencies

$ sudo apt-get install python-beautifulsoup python-pygame \
python-imaging python-twisted sgmltools-lite

4.2 Installing pyxml

Since ubuntu doesn't seem to have a package which contains pyxml
we have to compile and install it ourselves.

Download pyxml from pyxml.sourceforge.net, unpack it and install it
to the ~/freevo-test directory like this:
$ python setup.py install --prefix=~/freevo-test

4.3 Installing Freevo

$ cd ~/freevo-svn
$ svn co svn://svn.freevo.org/freevo/branches/rel-1 freevo-1.x
$ cd freevo-1.x/freevo
$ ./autogen.sh
$ PYTHONPATH=~/freevo-test/lib/python2.5/site-packages python \
setup.py install --prefix=~/freevo-test

NOTES:
- Running autogen.sh with the "nodoc" parameter like described in the
wiki wasn't enough for "setup.py install"
- The PYTHONPATH needs to be defined for the setup.py to find pyxml

4.4 Installing runtime dependencies

$ sudo apt-get install xmltv mplayer lsdvd xine-ui aumix python-pylirc

5. Running Freevo

Now you can start freevo with these commands (I recommend
you create a script for it):

export PYTHONPATH=~/freevo-test/lib/python2.5/site-packages
export PATH=$PATH:~/freevo-test/bin
freevo

NOTE: The configuration files still need to be created before Freevo
actually starts :)

</howto>

- Jaakko

php random image:
http://www.devlounge.net/articles/random-images-with-php
http://www.alistapart.com/articles/betterrotator
http://www.darrenfauth.com/php/random-image-php.php

pc for cars: http://www.dashpc.com/
http://gnomefiles.org/app.php/DashPC
http://www.gpsdrive.de/
http://gnomefiles.org/app.php/GpsDrive
http://roadmap.sourceforge.net/
http://gnomefiles.org/app.php/RoadMap

vpn-to-vpn-detailed-how-to.

http://www.ipcops.com/modules.php?op=modload&name=PNphpBB2&file=viewtopic&p=55201
http://www.databrokers.net/opensource/ipcop/vpn-to-vpn-detailed-how-to.html

Introduction

I was trying to setup a Net-to-Net VPN between 2 IPCop boxes with no much success. I was using the Short Howto on the X.509 VPN.

The procedure is relatively simple, but sometimes it gets confusing which side is what. If you don't do everything right, it does not work and it is difficult to understand what is wrong.

I had to do it 3 times to get it right. As a result I wrote this detailed step-by-step how-to.

Hope it is useful for other people.

—-
Iassen Hristov

Scenario

We have 2 IPCop boxes, both are running the latest version as of this writing – 1.4.2 (this how-to should work for later 1.4 versions as well)

We want to make an IPSec VPN between the 2 internal networks protected by the 2 IPCop boxes.

Network diagram

GREEN1 — ipcop1 --- Internet ----—- ipcop2 — GREEN2

*

GREEN1 is 192.168.1.0/24
*

ipcop1 has a public IP address of 24.24.24.1 with a public name of ipcop1.ipcop1.org. The specific IP address does not matter as long as both sides resolve it correctly.
*

GREEN2 is 192.168.102.0/24
*

ipcop2 has a public IP address of 24.24.24.2 with a public name of ipcop2.ipcop2.org
*

The hostnames of both IPCop boxes are different. They are NOT ipcop1.ipcop1.org and ipcop2.ipcop2.org.

Detailed step-by-step instructions

Preparation

1.

On ipcop1:

1.

reset VPN settings if necessary (hitting the “Reset” button on the VPN page deletes all certificates and connections that might have been previously created)
2.

set “Local VPN Hostname/IP” to ipcop1.ipcop1.org, check “Enabled” and hit Save
3.

reboot ipcop1 (just in case)

2.

On ipcop2:

1.

reset VPN settings if necessary (hitting the “Reset” button on the VPN page deletes all certificates and connections that might have been previously created)
2.

set “Local VPN Hostname/IP” to ipcop2.ipcop2.org, check “Enabled” and hit Save
3.

reboot ipcop2 (just in case)

Generate Root/Host Certificates

3.

On ipcop1: Hit the “Generate Root/Host Certificates” button and fill the following values:

1.

ipcop1 as the “Organization name”
2.

ipcop1.ipcop1.org as the “IPCop's Hostname” (this will be already filled for you)
3.

Specify your Country
4.

hit the “Generate Root/Host Certificates” button. This will generate the certificates (it might take a while) and will take you back to the VPN configuration page.
5.

Click the “Download Root Certificate” button (icon like a floppy disk). You will be prompted for the file name to save. The default file name is cacert.pem. Just so there is no confusion change the name to cacert.1.pem
6.

Click the “Download Host Certificate” button (the icon below). You will be prompted for the file name to save. The default file name is hostcert.pem. Just so there is no confusion change the name to hostcert.1.pem

4.

On ipcop2: Hit the “Generate Root/Host Certificates” button and fill the following values:

1.

ipcop2 as the “Organization name”
2.

ipcop2.ipcop2.org as the “IPCop's Hostname” (this will be already filled for you)
3.

Specify your Country
4.

hit the “Generate Root/Host Certificates” button. This will generate the certificates (it might take a while) and will take you back to the VPN configuration page.
7.

Click the “Download Root Certificate” button (icon like a floppy disk). You will be prompted for the file name to save. The default file name is cacert.pem. Just so there is no confusion change the name to cacert.2.pem
5.

Click the “Download Host Certificate” button (the icon below). You will be prompted for the file name to save. The default file name is hostcert.pem. Just so there is no confusion change the name to hostcert.2.pem

Upload the CA Certificates

In this step you are letting the 2 IPCop boxes know about the other CA (Certificate Authority), so that they can trust the certificates issued by the other box.

5.

On ipcop1:

1.

Fill ipcop2 as the “CA name”
2.

Browse and select the cacert.2.pem file
3.

hit the “Upload CA Certificate” button. This will upload the CA certificate from ipcop2 to ipcop1 and it will show it as the 3rd row in the “Certificate Authorities” (bottom) section.

6.

On ipcop2:

1.

Fill ipcop1 as the “CA name”
2.

Browse and select the cacert.1.pem file
3.

hit the “Upload CA Certificate” button. This will upload the CA certificate from ipcop1 to ipcop2 and it will show it as the 3rd row in the “Certificate Authorities” (bottom) section.

Create connections

7.

On ipcop1: Hit the “Add” button in the middle panel. On the next screen select “Net-to-Net Virtual Private Network” for the “Connection type” and fill the following values:

1.

ipcop2 as the “Name”
2.

left as the “IPCop side”
3.

192.168.1.0/255.255.255.0 as the “Local subnet”
4.

ipcop2.ipcop2.org as the “Remote Host/IP”
5.

192.168.102.0/255.255.255.0 as the “Remote subnet”
6.

In the “Authentication” section select “ Upload a certificate”. Check “Upload a certificate” and browse to the hostcert.2.pem file.
7.

Finally hit the “Save” button

8.

On ipcop2 (everything is reversed): Hit the “Add” button in the middle panel. On the next screen select “Net-to-Net Virtual Private Network” for the “Connection type” and fill the following values:

1.

ipcop1 as the “Name”
2.

right as the “IPCop side”
3.

192.168.102.0/255.255.255.0 as the “Local subnet”
4.

ipcop1.ipcop1.org as the “Remote Host/IP”
5.

192.168.1.0/255.255.255.0 as the “Remote subnet”
6.

In the “Authentication” section select “ Upload a certificate”. Check “Upload a certificate” and browse to the hostcert.1.pem file.
7.

Finally hit the “Save” button

Done

Important note: As some people have pointed out, it is essential to have your clock synchronized to accurate time on both machines, otherwise you might have issues.
Here is one case

My clock was a few hours ahead, the certs I was generating were yet
to become valid, and I was getting a very uniformative failure that
my CA was not available for my host verification.

Revision history of this document
Description Author Date Version
Initial version IH 13-Feb-2005 0.1
Added note about time synchronization and version table IH 05-Sep-2006 0.2

IPCOP VPN Howto

http://illusioner.dk/blog/?p=18
May 5th, 2006
Note: I will not take responsibility for anything going wrong with your IPCOP. When attempting this. – This is not part of the official release and therefore not supported.
Requierments

* Two IPCOP firewalls running at least RED/GREEN configuration.
* Two Client computers for testing connectivity.
* Switches, cables and so on…

Planning the scenario

Here is the plan regarding the networks, we are going to use:
Network 1 (Left) Red IP: xxx.xxx.xx.xx Red IP: xxx.xxx.xx.xx Red IP: xxx.xxx.xx.xx Green Network: 10.100.151.0/255.255.255.0 Red IP: xxx.xxx.xx.xx Green Network: 10.100.151.0/255.255.255.0 Network 2 (Right) Red IP: yyy.yyy.yy.yy Red IP: yyy.yyy.yy.yy Red IP: yyy.yyy.yy.yy Green Network: 10.100.153.0/255.255.255.0 Red IP: yyy.yyy.yy.yy Green Network: 10.100.153.0/255.255.255.0

Pre-Shared Key: hansen
The Scenario

scenario
Configuration

Before attempting to set up a Net-to-Net VPN, verify your information

Both sites must be on different subnets internally. Example:

Network 1 – 10.100.151.x

Network 2 – 10.100.153.x

You must be able to ping between the networks, when they are setup and configured.

Make sure, port 50 and 51 TCP or 500 UDP are NOT blocked by the ISP or Netadmin.
Setup

Refer to the Scenario illustration for address information.

Log into the IPCop web interface and go to the VPN fan.

Check the box labelled VPN.

Next click on Add.

Select a Net-to-Net Virtual Private Network and click Add

Choose a common name for the VPN. This name plays no role in the VPN’s functionality and is just used for identification.

Use the information from the Scenario illustration for address information.

The remote Host IP address is Network 2’s Red IP Address

Enter any remarks if needed…

Secure the VPN with a Pre-Shared Key. These must match on each of the two firewalls.

Go to the Network 2’s IPCop webpage and repeat the whole thing. Remember to use the Network 2 IP address information.

It should look something like this:
like this

Click SAVE and wait a couple minutes for the connection box to turn green and the connection state will hopefully turn green and state: OPEN.

Otherwise restart the VPN connection from the VPV fan.

status1
Test it!

Use the information from the Scenario illustration for address information on the client setup.

First off try to ping IPCOP to IPCOP.

Ping client 1 To IPCOP 2

Ping Client 1 to Client 2

If successful, then we can continue.

Create a share with some files in them on each client computer.

Just share them for Everyone for now.

Go to STARTàRUN

Type in the desired client.

connected
This could indicate success…

Done.

This setup is on a Windows XP Pro workstation and an IPCop 1.4.10 firewall using OpenVPN addon for IPCop and OpenVPN for the client.

Download OpenVPN from:

http://home.arcor.de/u.altinkaynak/media/ZERINA-0.9.3b-Installer.tar.gz

Copy to your IPCOP using ex. WinSCP.

Extract the archive tar -xzvf ./ZERINA-0.9.3b-Installer.tar.gz

Change directories to the directory created above.

Run the installer with the command: ./install

Will look something like this:

—– Start Shell —-

root@IPCOP:/tmp # tar -xzvf ./ZERINA-0.9.3b-Installer.tar.tar patch.tar.gz _GPL install uninstall _README library.addons
updatefiles root@IPCOP:/tmp # ls _GPL library.addons _README updatefiles install
patch.tar.gz uninstall ZERINA-0.9.3b-Installer.tar.tar root@IPCOP:/tmp # ./install
Welcome to the OpenVPN for IPCop (ZERINA 0.9.3b) Installer! The Installer will
perform the following steps : 1. Looking for older versions of ZERINA 2. Checking for
valid IPCop-version

3. Backing up files for easy uninstall 4. Installing new files 5. Adding entrys to existing files Starting installation process: 1. Looking for older versions of ZERINA . 2. Checking for valid IPCop-version . OK! openvpn.tar.gz

ZERINA-0.9.2b_Perlmodules.tar.gz Compress-Zlib-ipcop1410.tar.gz langs/
langs/de.zerina langs/sv.zerina langs/en.zerina langs/fr.zerina misc/

misc/status misc/rc.firewall.local.stop misc/header.old misc/header
misc/rc.firewall.local.start misc/rc.local.zerina OK! 3. Backing up files for easy uninstall
..OK!

4. Installing new files ….OK! …OK! 5. Adding entrys ……. ZERINA Installer finished

  • You can now access OpenVPN via the IPCop web gui.
  • WARNING: This package is NOT an official IPCop addon. It hasn’t been approved or

reviewed by the IPCop development team. It comes with NO warranty or guarantee, so
use it at your own risk.

  • WARNING: You have to create your own certificates for OpenVPN! *

For support try:
www.openvpn-forum.de * howto : http://home.arcor.de/u.altinkaynak

—- Stop Shell —-

Open your IPCop website under VPNs and verify that OpenVPN has been installed.

Open your IPCop website under VPNs and verify that OpenVPN has been installed. On the OpenVPN fan (look under VPN), enter the red IP address of your IPCop box in the Local VPN Hostname/IP field.

In the OpenVPN Subnet field enter the private IP range that your VPN clients will receive.

NOTE: It is very important, that the subnet differs from the Green subnet

NOTE: Go to advanced setting and press save. Maybe it is a bug, but it will NOT work otherwise. - The serverstatus will remain stopped.
Now Start the OpenVPN server.

Looks like this when up and running:

running
Under the Certificate Authorities heading, click on Generate Root/Host Certificates.

Unless the IPCOP is a powerful machine, this can take a while.

Under Client Status and Control, click Add.

Click on host to net

Fill out the form and make up a password. Remember the password for later use!
Client Setup

Download and install OpenVPN to your client from here :

http://openvpn.net/download.html#stable

After the install, go to your IPCOP and download the Client package (zip) to your client.

download
Extract the files to your OpenVPN\VPNconfig folder.

Right click on the extracted icon and choose to connect. Enter the password from earlier.

On the client a box or a Dos prompt should appear and indicate a successful connection. Something like this:

state
On the server:

open

Done.

Thanks to:

Ben Miller, Ufuk Altinkaynak, OpenVPN and ipcop.org

no right click

http://www.computerhope.com/j20.htm
http://www.hypergurl.com/norightclick.html
http://www.web-wise-wizard.com/javascript-tutorials/disable-right-click.html

<BODY oncontextmenu="return false" onselectstart="return false" ondragstart="return false">
<img src="your.image/url/here.jpg" oncontextmenu="return false">
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License