helping to makes things easy -- er

Installing Modules in Cygwin Perl

2014-07-06T22:36:00.001-07:00

The following will install "File::Tail"

Run cygwin
Type

cpan
install File::Tail

Change "File::Tail" with the module name you want to install

NB:
If that fails you can try delete ~/.cpan/build directory or just the directory of the module you are trying to install and try again.

If that still fails try going to the downloaded directory of the module and do this

perl Makefile.PL
make
make test
make install

Simple Cross-Domain Service Call via JSONP using JQuery

2013-09-12T01:07:00.000-07:00

Objective:

Retrieve data from a different domain and dynamically display them in your web page.

Introduction:

What if you want to make your web page display data dynamically? You can use AJAX to achieve this. All you have to do is fire up your AJAX, request data from the service which you created, and do some javascript stuff to update your DOM. As simple as that.
Now, what if you were in a situation where your supposedly dynamic web page resides in a different domain from where your data is coming from. Initially you will think AJAX to the rescue, again. That would be nice but it doesn’t work that way.
There is a thing called Same-Origin policy which prevents AJAX from calling a service from a different domain. Sucks doesn’t it? I know I’ve been there. And this is why I want to share a solution and explain it as simple as I can. Please read on.

Procedure:

Server Side

create a php script named server.php. with the following content

Client side:

Create a file named client.html with the following content:

Replace the url with the actual url of the server-side script

I hope it helps

Google Bookmark on Safari

2013-01-29T00:09:00.000-08:00

I like Google bookmark since everywhere I go I get to access my bookmarks. That way I can go to my previously bookmarked page and read it at my convenience. In Safari accessing my bookmarks is not hard. Basically I just go to http://bookmarks.google.com, log in and i'll be presented with my list. However, adding an item into my bookmark is another story. The long way is to go to Google's bookmark page and clicking the Add bookmark link. But this is to tedious since you have to provide the title and the URL of the page you want to bookmark.

Fortunately, there is a way. I had this in my Safari for a long time now (frankly, I can't remember where I got it in the first place) and only came to realize how valuable it is when I needed to add this function on a different Mac. I have searched and I have googled but I can't find a way to add Google Toolbar on Safari to ease the task of adding a bookmark nor adding just only the bookmark function. Thus I am sharing this for those who might need it.

Let's start.

1. Start Safari
2. Click Bookmarks --> Add Bookmark…
3. Type "Google Bookmark" or other label the you deemed more appropriate
4. For the location, select "Bookmarks Bar" from the drop-down list
5. Click Add button
6. Going back to the menu, click Bookmarks (again) then Show All Bookmarks
7. Select "Bookmarks Bar" in the left pane
8. Locate the bookmark item you just recently added
9. Click it then click (again) this time aiming at the address column to put it in edit mode
10. Replace the value of the address with the following (note that this is just one line)

javascript:(function(){var%20a=window,b=document,c=encodeURIComponent,d=a.open(%22https://www.google.com/bookmarks/mark?op=edit&output=popup&bkmk=%22+c(b.location)+%22&title=%22+c(b.title),%22bkmk_popup%22,%22left=%22+((a.screenX||a.screenLeft)+10)+%22,top=%22+((a.screenY||a.screenTop)+10)+%22,height=510px,width=550px,resizable=1,alwaysRaised=1%22);a.setTimeout(function(){d.focus()},300)})();

11. Press return button to save the new address value.

If you typed in the correct address this should give you the convenience of adding the current page to you Google bookmark by just clicking the bookmark item you've just created.

Setting Up An Internet Radio Station

2013-01-17T22:26:00.000-08:00

Objective

This guide aims to provide the steps in creating an Internet radio station.

Overview

In this guide we will run a SHOUTcast Distributed Network Audio Server (DNAS) that will broadcast audio stream coming from a transcoder. Initially we will use the SHOUTcast Transcoder to send audio streams to SHOUTcast DNAS for it to broadcast. Both SHOUTcast DNAS and SHOUTcast Transcoder will reside in one host computer running Linux OS.

After the initial setup is done, we will replace SHOUTcast Transcoder with Winamp+DSP running on Windows. This will give easier control on what audio file to stream or switch to live input from a microphone.

Next we will want other people to know of our Server and give them a way to connect to our service. To do that we will need to register our SHOUTcast DNAS to SHOUTcast directory to be included in SHOUTcast’s list of available servers.

We will then finish this guide with steps on how to configure SHOUTcast DNAS accept multiple input and broadcast these in different streams.

Requirements

Computer running Linux OS

SHOUTcast DNAS 2.0

SHOUTcast Transcoder

For Winamp

Computer running Windows OS

Winamp

DSP Plug-In for Winamp

SHOUTcast DNAS

Installation

We need to download a copy of SHOUTcast DNAS from http://www.shoutcast.com/broadcast-tools, and extract it to its own folder. This copy of SHOUTcast DNAS comes pre-compiled and is ready to run as soon as it’s been extracted.

#cd /usr/src

#mkdir shoutcast

#cd shoutcast

#wget http://download.nullsoft.com/shoutcast/tools/sc_serv2_linux_07_31_2011.tar.gz

for a 64 bit version, download http://download.nullsoft.com/shoutcast/tools/sc_serv2_linux_x64_07_31_2011.tar.gz

#tar -xzvf /sc_serv2_linux_07_31_2011.tar.gz

Configuration

SHOUTcast DNAS comes with several sample configuration files that are ready to use. For our need we just need to change the administrator password for SHOUTcast DNAS’s web interface.

Open sc_serv2_basic.conf and look for the line “adminpassword=changeme”. Replace the value with your desired password. Save and close the file.

Testing

Since we are still not sending audio stream to our Server, we cannot test if our Server is working by using an audio player and listening to it. However, we can still run the Server and test its status by checking its web interface.

In the Server

#cd /usr/src/shoutcast

#./sc_serv sc_serv_basic.conf

In a computer with an Internet browser

Open a browser
In the address bar, type the IP address of our Server followed by port 8000 (e.g. 192.168.1.1:8000)
Use the following for the login credentials

username = admin

password = <the password you provided during the configuration>

You will now then be presented with the Server’s web interface

Do not worry if the status says that the Server is currently down. This is just because we have not yet provided the Server with an audio stream to broadcast.

SHOUTcast Transcoder

Installation

Now we’re ready to install the Transcoder that will provide the Server with audio stream to broadcast. Just like SHOUTcast DNAS, SHOUTcast Transcoder comes pre-compiled so we only need to create another directory then download and extract the Trancoder there.

#mkdir /usr/src/shoutcast/transcoder

#cd /usr/src/shoutcast/transcoder

#wget http://download.nullsoft.com/shoutcast/tools/sc_trans_linux_10_07_2011.tar.gz

for a 64 bit version, download http://download.nullsoft.com/shoutcast/tools/sc_trans_linux_x64_10_07_2011.tar.gz

#tar -xzvf sc_trans_linux_10_07_2011.tar.gz

Configuration

Again, just like SHOUTcast DNAS, SHOUTcast Transcoder comes with sample configuration files that we can use right away. All we need to do now is to copy audio files into /usr/src/shoutcast/transcoder/music folder (or to other location you like as long as it is accessible by the Transcoder).

Open /usr/src/shoutcast/transcoder/playlists/main.lst and add the location of the audio file to include in the stream, one file per line. Just follow the example provided in main.lst (don’t forget to remove this line after you are finished adding your audio files). Save and close main.lst

Start Streaming

To start streaming audio to the server, just run sc_trans with the file name of the configuration file to use

#./sc_trans sc_trans_basic.conf

Make sure the SHOUTcast DNAS is running before you execute the above command

Testing

This time we can use an audio player like Winamp, iTunes, VLC, etc. to see if our Server is indeed broadcasting the audio stream provided to it by the Transcoder.

Do this in another computer that has an Internet browser:

Open an Internet browser
Go to <your Server’s IP address>:8000/listen.pls (e.g. 192.168.1.1:8000/listen.pls)
If your browser is configured to open an application that can handle PLS files it will run and start playing the audio broadcasted from our Server
Otherwise, run your audio player and open the downloaded listen.pls file. This will start playing the audio broadcasted from our Server

Registration to SHOUTcast Directory

By now we have a working Internet radio that is ready to broadcast to the whole world. What is left now is for the whole world to know that our server exists. We can easily let the whole world know our server and give them a easy way to connect to us by registering our server to SHOUTcast directory. So with the Server and Transcoder still running, follow the following instructions.

Open an Internet browser
In the address bar, type the following

<Server IP>:<Port #>/admin.cgi?sid=0

(e.g. 192.168.1.1:8000/admin.cgi?sid=0)

Login
Click on Create Authhash
Fill up the form that follows then click Create Authhash button

This time instead of using sc_serv_basic.conf as the parameter for sc_serv, use sc_serv_public.conf

i.e.

sc_serv sc_serv_public.conf

That’s it! Our server is not included in SHOUTcast directory and ready for the whole world to use.

Winamp

Since SHOUTcast Transcoder does not have a GUI interface it becomes hard to add or remove files to be included in the stream. Also, switching between recorded and live feed. To make is easier to control what is to be included in the stream, we will replace SHOUTcast Transcoder with Winamp with DSP plug-in. DSP plug-in is used for sending live feed into the stream. SHOUTcast DSP Plug-In for Winamp only works on Windows so get a Windows computer and start installing.

Install Winamp

Download Winamp from www.winamp.com
Double-click the downloaded file and follow the installation prompts

Install SHOUTcast DSP Plug-In for Winamp

Download the DSP plug-in from http://www.shoutcast.com/broadcast-tools
Double-click the downloaded file and follow the installation prompts

Configuration

Open Winamp’s preferences window by clicking Options then Preferences
Select DSP/Effect under Plug-ins in the left side list box
In the right side list box, select Nullsoft SHOUTcast Source DSP v2.3.2 [dsp_sc.dll]
Click Configure active plug-in button located at the bottom of the window
In Nullsoft SHOUTcast Source, Open the Output tab then the Login tab
Under Server Address, type in the IP address of our SHOUTcast DNAS (e.g 192.168.1.1)
Under Port, type the port number used by our SHOUTcast DNAS (e.g. 8000)
Keep Stream’s value of 1
Ignore the DJ / User ID
Under password, type in the administrator password you provided for the SHOUTcast DNAS
Select Automatic reconnection on connection failure
Keep Reconnection timeout of 1 second
Unselect Use SHOUTcast v1 mode
Click on the Input tab
Select the Input Device you want to use

Winamp (to send the audio being produced by Winamp when it plays)
Souncard Input (to send the audio being received by the computer’s audio input, like your voice from a microphone)

Testing

Before clicking the Connect button in Nullsoft SHOUTcast Source window, make sure that you have stopped SHOUTcast Transcoder but keep SHOUTcast DNAS running.
If you selected Winamp as the Input Device, add audio files into Winamp’s playlist and click the Winamp’s play button
Re-open Nullsoft SHOUTcast Source window (if it closed) and click the Connect in the Output tab
On a different device, connect an audio player to our SHOUTcast DNAS

Once your done you should hear the audio player playing the broadcast from our SHOUTcast DNAS

Multiple Stream

SHOUTcast DNAS is capable of broadcasting multiple streams, meaning we broadcast more than one audio source from our SHOUTcast DNAS. We are going to reconfigure our Server to allow two Transcoders / sources to send input to our Server for it to broadcast. One source will be coming from SHOUTcast Transcoder and the other from Winamp.

Server Configuration

Open sc_serv_basic.conf
Comment the lines

streamid=1

streampath=/test.aac

and uncomment the following lines

streamid_1=1

streampath_1=/test.aac

streamid_2=2

streampath_2=/test2.aac

Save and close the configuration file (Note: you still start sc_serv using sc_serv_public.conf if you want to make the Server public. sc_serv_public.conf reads and includes the configuration in sc_serv_basic.conf)

Transcoder Configuration

SHOUTcast Transcoder

Open sc_trans_basic.conf
Look for streamid and set its value to 1 to occupy broadcast stream 1 of our Server
Optionally change the value of adminport in case it is being used by other Transcoder or other programs
Save and close the file

Winamp + DSP

Open Nullsoft SHOUTcast Source window
Open Output tab then the Login tab
Set the value of Stream to 2 to occupy broadcast stream 2 of our Server

Registering Stream 2

SHOUTcast DNAS is now ready to broadcast these two input sources. However, we still have not registered stream 2 to SHOUTcast directory. We have to do the registrations steps as instructed in Registration to SHOUTcast Directory section. This time choose Create Authhash for stream 2.

Testing

Start our server using sc_serv_public.conf as the parameter
Start SHOUTcast Transcoder
Start Winamp and click the Connect button in Nullsoft SHOUTcast Source window
Use an audio player to listen to the streams. You can manually input the source and select the stream to listen to by accessing this URL pattern

<Server IP address>:<Port #>/test.aac for stream 1

<Server IP address>:<Port #>/test2.aac for stream 2

e.g.

192.168.1.1:8000/test.aac

OpenWRT + BATMAN + CoovaChilli

2013-01-17T00:49:00.000-08:00

Objective

Build a captive portal on a wireless mesh network

Wireless clients can roam around the mesh network

Requirements

OpenWRT compatible router

OpenWRT

B.A.T.M.A.N.

CoovaChilli

FreeRadius

Topology

OpenWRT

Installation

Download appropriate OpenWRT image from http://downloads.openwrt.org/snapshots/trunk/
Connect your computer to the router
Turn on the router
Follow the router’s manual on upgrading its firmware but instead of using the manufacturer’s upgraded firmware, use the downloaded OpenWRT image

Configuration

For the configuration, we just need to set a password for the root user account

Using Telnet, login to the router. A router with a newly installed OpenWRT has a default IP address of 192.168.1.1. Your telnet command should be

telnet 192.168.1.1

Once logged in type passwd then Enter and provide a password for the root user account
Logout by typing exit then press Enter

Testing

First we test if OpenWRT can access the Internet

Connect the WAN port of the router to the Internet
Login to the router using ssh (use root and the password you just set during configuration respectively)
Now do a ping test to see if the router is indeed connected to the Internet

Now We’ll test the wireless interface of the router

Still logged in to the router, edit /etc/config/wireless
Delete the line that says “option disabled 1”
Optionally set the SSID (This is the line that says option ssid ‘OpenWRT’. Change OpenWRT to your chosen SSID)
Save and close the file
Type wifi and press Enter to reload wifi configuration
Connect to the router through its wireless interface. You should be able to access the Internet

B.A.T.M.A.N.

Installation

Login to the router
Connect the router to the Internet
Execute the following

opkg update

opkg install kmod-batman-adv

Configuration

Create a file /tmp/batman_config.sh and set the content with the following

#!/bin/sh

### Node-specific settings

export HOSTNAME="ROUTERNAME"

export IP="192.168.1.1"

export LAN_IFNAME="eth0 bat0"

### Network-specific settings should be consistent across all nodes with in the mesh network

export PUBLIC_ESSID="OMNISPOT"

export NETMASK="255.255.255.0"

export DNS=""

export GATEWAY=""

export MESH0_BSSID="CA:CA:CA:CA:CA:00"

export MESH0_ESSID="mesh0"

export MESH0_CHANNEL="3"

wifi detect >>/etc/config/wireless

( for i in `seq 0 9` ; do echo "delete wireless.@wifi-iface[]" ; done ) | uci batch -q

uci import -m batman-adv </dev/null

echo "

set system.@system[0].hostname=$HOSTNAME

set batman-adv.bat0=mesh

set batman-adv.bat0.interfaces='mesh0'

set batman-adv.bat0.gw_mode='off'

set network.lan.ipaddr=$IP

set network.lan.netmask=$NETMASK

set network.lan.dns='$DNS'

set network.lan.gateway=$GATEWAY

set network.lan.ifname='$LAN_IFNAME'

set network.bat0=interface

set network.bat0.ifname=bat0

set network.bat0.proto=none

set network.bat0.mtu=1500

set network.mesh0=interface

set network.mesh0.proto=none

set network.mesh0.mtu=1528

set wireless.radio0=wifi-device

set wireless.radio0.channel=$MESH0_CHANNEL

set wireless.radio0.disabled=0

set wireless.radio0.phy=phy0

set wireless.radio0.macaddr=

add wireless wifi-iface

set wireless.@wifi-iface[-1].device=radio0

set wireless.@wifi-iface[-1].encryption=none

set wireless.@wifi-iface[-1].network=lan

set wireless.@wifi-iface[-1].mode=ap

set wireless.@wifi-iface[-1].ssid='$PUBLIC_ESSID'

add wireless wifi-iface

set wireless.@wifi-iface[-1].device=radio0

set wireless.@wifi-iface[-1].encryption=none

set wireless.@wifi-iface[-1].network=mesh0

set wireless.@wifi-iface[-1].mode=adhoc

set wireless.@wifi-iface[-1].bssid=$MESH0_BSSID

set wireless.@wifi-iface[-1].ssid='$MESH0_ESSID'

set wireless.@wifi-iface[-1].mcast_rate=11000

set dhcp.lan.ignore=1

commit" \

| uci batch

Set the values of the node-specific settings for each router

Name	Description
HOSTNAME	Would-be hostname of the router
IP	Would-be IP address of the router
LAN_IFNAME	LAN interface name of the router and bat0 (B.A.T.M.A.N. interface)

Set the network specific-settings. These should be the same for all nodes in the mesh network

Name	Description
PUBLIC_ESSID	The SSID of the wireless network where clients will connect to
NETMASK	Network mask of the mesh network
DNS	The DNS setting
GATEWAY	Internet gateway address
MESH0_BSSID	A common MAC address to enable the nodes of the mesh network to identify each other and communicate
MESH0_ESSID	The SSID for the mesh network
MESH0_CHANNEL	The channel to use for wireless communication

Save and close the file /tmp/batman_config.sh
Run the batman configuration script

sh /tmp/batman_config.sh

Restart the router

Do this for all the routers involve

Testing

Turn on all the routers
Log in to one of the routers
You should be able to ping the other router

CoovaChilli

Installation

Login to the router
Connect the router to the Internet
Execute the following

opkg update

opkg install coova-chilli

Configuration

Execute the following on your computer

wget http://ap.coova.org/chilli/coova-chilli-1.3.0.tar.gz .

tar -xzvf coova-chilli-1.3.0.tar.gz

cd coova-chilli-1.3.0/miniportal

ls *.in | sed 's/$.*$\.in/\1/' | xargs -I {} mv {}.in {}

Substitute the markers @SBINDIR@ and @ETCCHILLI@ with “/usr/sbin” and “/etc/chilli” respectively
Copy the content of miniportal folder to the router

scp * root@192.168.1.1:/etc/chilli/www/

Logon to the router
Open /etc/chilli/defaults and edit the following settings

Key	Recommended Value	Remarks
HS_WANIF	eth1 or eth0.2	The WAN interface Uncomment this and set the value to the name of the WAN of the router Use ifconfig to give you a hint
HS_LANIF	bat0	The LAN interface bat0 is the name of the mesh network interface

Choose either of the two for authentication

RADIUS Authentication

For radius authentication, provide the IP address of the RADIUS server as value for key HS_RADIUS in /etc/chilli/defaults

Local File Authentication

For local file authentication, uncomment the line HS_LOCALUSERS in /etc/chilli/defaults
Create the file /etc/chilli/localusers and add the username and password in the following format

username:password:

Replace the marker username and password for the actual username and password. Use one line for each entry

Restart the router

Testing

Use a tablet or a PC to connect to the mesh network
Open a browser and type in a URL

Conclusion

After you have installed and configured everything, you should have a captive portal working on a wireless mesh network. All DHCP request are handled by the gateway running CoovaChilli. And Internet access is controlled by CoovaChilli.

Running NetBeans using a Mac Network User Account

2012-12-02T20:32:00.000-08:00

I have known this for a long time now. And today, I just happen to need NetBeans again. I am using Mac OSX 10.6 logged in as a network user. You'd think it would be easy to run NetBeans in this environment. Well, think again. I, again, forgot how to start NetBeans.

So I am writing this to share to other, and serve also as a reminder to myself.

Steps to running NetBeans:

1. Open a Terminal

2. Type the following on the Terminal

open <Path to NetBeans.app> --args -J-Dosgi.locking=none

That's it!

CoovaChilli - MAC Address Authentication

2012-11-23T16:36:00.000-08:00

Since it's hard to get a straight answer from CoovaChilli's site, I just decided to post my findings in here.

Today, after so much searching and testing, I discovered how to bypass CoovaChilli's usual login page. In this post you will learn how to allow a device to gain access to the Internet via CoovaChilli based on the devices' MAC address.

I'm not much for words so go to the easy setup.

Go to /etc/chilli or /usr/local/chilli depending on how you installed your CoovaChilli
Open the "defaults" file
Uncomment HS_MACAUTHMODE=local
Also uncomment HS_MACALLOW="..." and edit it to look something like this

HS_MACALLOW="00-25-d3-3f-70-9f"

Change the value part with the MAC address of the device that you want bypass the login process

That's it!

To add more devices in the list, simply add their MAC address separating them with comma. Like:

Again, that's it!

I hope this helps

OpenWRT+CoovaChilli

2012-11-22T22:27:00.000-08:00

Introduction

Today I am going to share my experience in Installing CoovaChilli on a router.

My first attempt with this endeavor ended up with me having a very expensive brick instead of a captive portal. So for those who want to avoid this costly experience I am laying out this simple installation process for you to follow and hopefully succeed. Once you get comfortable with it you can then venture into more riskier approach, like compiling your own OpenWRT.

I am using TP-Link's MR3220 as my router. Though I haven't tried it yet, I hope the same approach will work on other routers based on Altheros AR71xx.
Let's start!

Download required Packages

1. Download openwrt-ar71xx-generic-tl-mr3220-v1-squashfs-factory.bin from http://downloads.openwrt.org/snapshots/trunk/ar71xx/.
2. Download the following from http://downloads.openwrt.org/snapshots/trunk/ar71xx/packages/

coova-chilli_1.2.9-1_ar71xx.ipk
haserl_0.9.29-1_ar71xx.ipk
kmod-tun_3.3.8-1_ar71xx.ipk
libpthread_0.9.33.2-1_ar71xx.ipk
librt_0.9.33.2-1_ar71xx.ipk

Flash OpenWRT for MR3220

Use a LAN cable to connect your computer to one of the LAN ports of the router
Start a browser and go to http://192.168.1.1 (this is the router's default IP address, change this accordingly if you already changed your router's IP address)
Choose System Tools --> Firmware Upgrade
Click the Browse button
Locate and select openwrt-ar71xx-generic-tl-mr3220-v1-squashfs-factory.bin file
Click the Upgrade button
Wait until it says rebooting

In this stage OpenWRT is already installed in your router and you will not be able to access your router’s web interface

Initialize OpenWRT

For first time login, you have to set root’s password. Follow these steps.

Still connected to your router, open telnet and connect to 192.168.1.1
Once logged in you should be see a display similar to this:

  BusyBox v1.19.4 (2012-11-18 23:21:39 EST) built-in shell (ash)
  Enter 'help' for a list of built-in commands.
  
  _______                     ________        __
  |       |.-----.-----.-----.|  |  |  |.----.|  |_
  |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
  |_______||   __|_____|__|__||________||__|  |____|
  |__| W I R E L E S S   F R E E D O M
  -----------------------------------------------------
  BARRIER BREAKER (Bleeding Edge, r34253)
  -----------------------------------------------------
  * 1/2 oz Galliano         Pour all ingredients into
  * 4 oz cold Coffee        an irish coffee mug filled
  * 1 1/2 oz Dark Rum       with crushed ice. Stir.
  * 2 tsp. Creme de Cacao
  -----------------------------------------------------
  root@OpenWrt:~#

To set root’s password type passwd the press return key
Type in root’s new password, press return, then re-type the password for confirmation

After setting the password you should quit telnet and login to the router using ssh

Setup Wireless Configuration


ssh root@192.168.1.1

Edit /etc/config/wireless


vi /etc/config/wireless

Comment or delete the line “option disabled 1” to enable wireless LAN
Optionally change the SSID by changing the value of “option ssid”, from OpenWRT to your choice
Save and close the file
Execute wifi to force the system to re-read the wireless configuration file and start wireless LAN

Install CoovaChilli

Go to your computer’s terminal and copy the rest of the packages to router’s /tmp directory

scp coova-chilli_1.2.9-1_ar71xx.ipk haserl_0.9.29-1_ar71xx.ipk kmod-tun_3.3.8-1_ar71xx.ipk libpthread_0.9.33.2-1_ar71xx.ipk librt_0.9.33.2-1_ar71xx.ipk root@192.168.1.1:/tmp

Log back in to the router

ssh root@192.168.1.1

Go to /tmp and install the packages in the following order


  opkg install librt_0.9.33.2-1_ar71xx.ipk

  opkg install libpthread_0.9.33.2-1_ar71xx.ipk

  opkg install kmod-tun_3.3.8-1_ar71xx.ipk

  opkg install coova-chilli_1.2.9-1_ar71xx.ipk

  opkg install haserl_0.9.29-1_ar71xx.ipk

Setup CoovaChilli

Configuration File

Open /etc/chilli/defaults and change the following lines

  
  from “# HS_WANIF=eth0                      # WAN Interface toward the Internet”
  to “HS_WANIF=eth1                          # WAN Interface toward the Internet”
  
  from “HS_LANIF=eth1                        # Subscriber Interface for client devices”
  to “HS_LANIF=wlan0                         # Subscriber Interface for client devices”
  
  from “HS_RADIUS=locahost”
  to “HS_RADIUS=<your RADIUS IP address>”
  
  from "HS_RADSECRET=testing123              # Set to be your RADIUS shared secret"
  to "HS_RADSECRET=<your RADIUS password>    # Set to be your RADIUS shared secret

Save and close the file

Start-up Script

Now we need to create the startup script for coova-chilli. Coova-chilli package does not provide this so we have to create this by hand
Create a the file /etc/init.d/chilli with the following content

     #!/bin/sh /etc/rc.common
     # - init script for chilli -

     START=60
     STOP=90

     NAME=chilli
     RUN_D=/var/run
     CMDSOCK=$RUN_D/$NAME.sock
     PIDFILE=$RUN_D/$NAME.pid

     option_cb() { [ -n "$2" ] && echo "HS_$(echo $1|tr 'a-z' 'A-Z')=\"$2\"" | sed 's/\$/\\\$/g'; }
     config_load hotspot > /etc/chilli/config

     . /etc/chilli/functions

     start() {
         HS_DNS_DOMAIN=${HS_DNS_DOMAIN:-cap.coova.org}
         HS_DNS1=${HS_DNS1:-$HS_UAMLISTEN}
         HS_DNS2=${HS_DNS2:-$HS_NASIP}
         HS_NASID=${HS_NASID:-$HS_NASMAC}
         HS_MACAUTHMODE=${HS_MACAUTHMODE:-local}
         HS_USELOCALUSERS=${HS_USELOCALUSERS:-off}
         HS_PROXY_TYPE=${HS_PROXY_TYPE:-none}
         HS_RADCONF_URL=${HS_RADCONF_URL:-http://ap.coova.org/config/tos.conf}
         HS_CFRAME_URL=${HS_CFRAME_URL:-http://coova.org/cframe/default/}
         HS_CFRAME_SZ=${HS_CFRAME_SZ:-100}
         HS_DEFSESSIONTIMEOUT=${HS_DEFSESSIONTIMEOUT:-0}
         HS_DEFIDLETIMEOUT=${HS_DEFIDLETIMEOUT:-0}
         HS_DEFINTERIMINTERVAL=${HS_DEFINTERIMINTERVAL:-300}
         HS_LAN_ACCESS=${HS_LAN_ACCESS:-deny}
         HS_CFRAME_POS=${HS_CFRAME_POS:-top}
         HS_PROVIDER=${HS_PROVIDER:-Coova}
         HS_PROVIDER_LINK=${HS_PROVIDER_LINK:-http://coova.org/}
         HS_LOC_NAME=${HS_LOC_NAME:-My HotSpot}
         HS_LOC_NETWORK=${HS_LOC_NETWORK:-Coova}
         HS_OPENIDAUTH=${HS_OPENIDAUTH:-off}
         HS_ANYIP=${HS_ANYIP:-off}

         [ -z "$HS_LANIF" ] && {
             [ -e /tmp/device.hotspot ] && {
                 stop
             }
             HS_LANIF=$(wlanconfig ath create wlandev wifi0 wlanmode ap)
             for i in 0 1 2 3 4; do ifconfig ath$i mtu 1500; done 2>/dev/null
             echo $HS_LANIF > /tmp/device.hotspot
             iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
             iwconfig $HS_LANIF essid ${HS_SSID:-Coova} 2>/dev/null
         }

         writeconfig
         radiusconfig
                                                                                            
         [ -d $RUN_D ] || mkdir -p $RUN_D

         /sbin/insmod tun >&- 2>&-
         /usr/sbin/chilli
     }

     stop() {
         [ -f $PIDFILE ] && kill $(cat $PIDFILE)
         rm -f $PIDFILE $LKFILE $CMDSOCK 2>/dev/null
         iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE
         wlanconfig $(cat /tmp/device.hotspot) destroy
         rm /tmp/device.hotspot
     }

Automatically Start CoovaChilli

Create a symbolic link to /etc/init.d/chilli in /etc/rc.d and name it S60chilli


cd /etc/rc.d

ln -s ../init.d/chilli S60chilli

This will automatically start CoovaChilli everytime you start your router.

Login Page

Lastly we need to create the login pages for CoovaChilli. CoovaChilli's package for OpenWRT does not include this and so we have to download CoovaChilli's source code and copy the contents of the miniportal forder

Back in your computer, download CoovaChilli's source code

wget http://ap.coova.org/chilli/coova-chilli-1.2.9.tar.gz

Untar the package

tar -xzvf coova-chilli-1.2.9.tar.gz

Goto the miniportal folder

cd coova-chilli-1.2.9/miniportal

Edit the files functions.sh.in, config-local.sh.in, uam.sh.in and replace @SBINDIR@ and @ETCCHILLI@ with /usr/sbin and /etc/chilli respectively
Rename the files that end in ".in", removing ".in" part

e.g. functions.sh.in will be renamed to functions.sh

Copy the contents of miniportal folder to your router's /etc/chilli/www

scp * root@192.168.1.1:/etc/chilli/www/

We're done. All you have to do is reboot your router and connect to it once it starts up.

When you open your browser and starts browsing you will be redirected to CoovaChilli's login page.

Enjoy!!!

2012-10-23T21:04:00.000-07:00

Creating a Capture Portal using CoovaChilli, FreeRadius, and MySQL

Objectives

Create a capture portal

Use MySQL database to hold user accounts and accounting data

Limit access/session time per user

Limit access/session time per MAC address

Limiut simultaneous logins

Requirements

Ubuntu 12.04.1 LTS

CoovaChilli

PC with 2 Network Card

Internet Access

Install Ubuntu

Download a copy of Ubuntu 12.04 LTS from http://www.ubuntu.com/download/desktop

Burn the ISO image onto a CD

Insert the CD in the CD Drive

Start the computer

Wait for Ubuntu to boot from the CD

Click “Install Ubuntu”

Click “Continue”

Select the option to erase the content of the disk and install Ubuntu. Click “Continue”

Click “Install Now”

Set your timezone then click “Continue”

Select appropriate keyboard layout then click “Continue”

Type your name, computer name, login name, and password. Click “Continue”

Wait until Ubuntu finishes copying the files

Click “Restart”

Remove CD from Drive then click press Enter

Wait for the computer to restart

Additional Software Installation

Login using the username and password you provided earlier

Click on the Ubunto Icon and type “Terminal” in the search box

Click the Terminal

Update the source packages

sudo apt-get update

Install tasksel

sudo apt-get install tasksel

Run tasksel and select LAMP server then click OK

sudo tasksel

When asked for “New password for the MYSQL ‘root’ user” use mysqlsecret (this password is use for this documentation. Change this for production use)

Enable packet forwarding

Execute the following command

echo 1 > /proc/sys/net/ipv4/ip_forward

To ensure packet forwarding is enable every time you reboot, do the following

Open /etc/sysctl.conf

Uncomment the line

net.ipv4.ip_forward=1

Save and close sysctl.conf

Install and Configure FreeRadius

Install FreeRadius

sudo apt-get install freeradius

Test FreeRadius

Uncomment line 90
"John Doe" Cleartext-Password := "hello"
and line 91
Reply-Message = "Hello, %{User-Name}"
in /etc/freeradius/users

Restart FreeRadius

/etc/init.d/freeradius restart

Use radtest to test FreeRadius

radtest "John Doe" hello 127.0.0.1 0 testing123

The output should be similar to this

Sending Access-Request of id 153 to 127.0.0.1 port 1812

User-Name = "John Doe"

User-Password = "hello"

NAS-IP-Address = 127.0.1.1

NAS-Port = 0

Install CoovaChilli

Create user for CoovaChilli

sudo useradd chilli -s /usr/sbin/nologin

Install required libraries

sudo apt-get install libssl-dev

sudo apt-get install haserl

Download CoovaChilli

cd

mkdir chilli

cd chilli

wget http://ap.coova.org/chilli/coova-chilli-1.3.0.tar.gz

Compile and Install CoovaChilli

tar -xzvf coova-chilli-1.3.0.tar.gz

cd coova-chilli-1.3.0

./configure --prefix= --enable-largelimits --enable-miniportal --with-openssl

make

sudo make install

Configure CoovaChilli

sudo su -

cd /etc/chilli

cp defaults config

echo iptables -I POSTROUTING -t nat -o \$HS_WANIF -j MASQUERADE >> ipup.sh

/etc/init.d/chilli start && /etc/init.d/chilli stop

Test CoovaChilli

Connect eth0 to the LAN or device that has access to the internet

Set the default gateway to the IP of the Internet gateway that is located in eth0’s LAN

Connect eth1 to an access point or switch

Make sure that DHCP service is disabled in the above-mentioned access point

Start CoovaChilli

Using a tablet, phone or a pc, connect to the access point

Open an Internet browser and go to any site

You should be redirected to the capture portal’s login page

When checking who is logged in, sometimes radwho will give this error

radwho: Error reading /var/log/freeradius/sradutmp: No such file or directory

To fix it, uncomment sradutmp in the accounting section of /etc/freeradius/sites-available/default then restart freeradius

Customize Login Page

Use MySQL for FreeRadius User Configuration

Install Required Packages

MySQL is already installed. All we need is to install FreeRadius’s MySQL package

sudo apt-get install freeradius-mysql

Configure MySQL Database for FreeRadius

Create a database for FreeRadius to use

mysqladmin -uroot -pmysqsecret create radius

Create a user that will have access to the radius database. We’ll use one provided in FreeRadius’s MySQL package

mysql -uroot -pmysqlsecret < /etc/freeradius/sql/mysql/admin.sql

Create the tables

mysql -uroot -pmysqlsecret radius < /etc/freeradius/sql/mysql/schema.sql

Add a test user

mysql -uroot -pmysqlsecret radius -e "INSERT INTO radcheck (username, attribute, op, value) VALUES ('testuser', 'Cleartext-Password', ':=', 'password')"

Configure FreeRadius

Uncomment the line

$INCLUDE sql.conf

in /etc/freeradius/radiusd.conf

Uncomment the line

sql

in the authorize section of /etc/freeradius/sites-available/default (by default this is in line 159)

Test FreeRadius MySQL User Configuration

Restart FreeRadius

/etc/init.d/freeradius restart

Use radtest to login as testuser

radtest testuser password 127.0.0.1 0 testing123

The result should look something like

Sending Access-Request of id 199 to 127.0.0.1 port 1812

User-Name = "testuser"

User-Password = "password"

NAS-IP-Address = 127.0.1.1

NAS-Port = 0

rad_recv: Access-Accept packet from host 127.0.0.1 port 1812, id=199, length=20

Limit Access Time Per User

Limiting the time a use can access the Internet is done by basically returning an AVP of Session-Timeout. But using this a user can just log back in again. To prevent this a counter is used.

Since we already have FreeRadius’s MySQL package, we’ll use the sqlcounter. Our counter will reset the count on a daily basis thus a user can again use his account on the next day

Open /etc/freeradius/dictionary and append the lines

ATTRIBUTE Daily-Session-Time 3000 integer
ATTRIBUTE Max-Daily-Session 3001 integer

Uncomment the line

sql

in the accounting section of /etc/freeradius/sites-available/default (by default this is in line 388)

Open /etc/freeradius/sql/mysql/counter.con and change the sql directive of dailycounter from this:

query = "SELECT SUM(acctsessiontime - \
GREATEST((%b - UNIX_TIMESTAMP(acctstarttime)), 0)) \
FROM radacct WHERE username = '%{%k}' AND \
UNIX_TIMESTAMP(acctstarttime) + acctsessiontime > '%b'"

to this:

query = "SELECT IFNULL(SUM(acctsessiontime - \
GREATEST((%b - UNIX_TIMESTAMP(acctstarttime)), 0)),0) \
FROM radacct WHERE username = '%{%k}' AND \
UNIX_TIMESTAMP(acctstarttime) + acctsessiontime > '%b'"

Open /etc/freeradius/sites-available/default and add the line

dailycounter

just below daily in the authorize section (this should be in line 175)

Uncomment the line

$INCLUDE sql/mysql/counter.conf

in /etc/freeradius/radiusd.conf (this is at line 695)

Add a 15minute limit to testuser account

mysql -uroot -pmysqlsecret radius -e "INSERT INTO radcheck (username, attribute, op, value) VALUES ('testuser', 'Max-Daily-Session', ':=', 1800)"

Restart FreeRadius

Test Configuration for Limiting Access Time Per User

Restart FreeRadius

/etc/init.d/freeradius restart

Use radtest to login as testuser

radtest testuser password 127.0.0.1 0 testing123

The result should look something like

Sending Access-Request of id 132 to 127.0.0.1 port 1812

User-Name = "testuser"

User-Password = "password"

NAS-IP-Address = 127.0.1.1

NAS-Port = 0

rad_recv: Access-Accept packet from host 127.0.0.1 port 1812, id=132, length=26

Session-Timeout = 1800

Notice the “Session-Timeout” at the end of FreeRadius reply. This indicates the amount of time (in seconds) a user can access the internet using the capture portal.

To actually test the configuration browse the Internet by logging through the capture portal. Track the time from login up to the given time limit. When the configured time has lapsed you should be directed to the login screen. You should not be able to use the account again until the counter is reset (in this case, until the next day)

Limiting Simultaneous Logins Per User

This time we will limit the number of simultaneous login a user can have. We will use the rlm_sql module since it is faster (according to the notes in the configuration file)

In the /etc/freeradius/sites-available/default

Make sure sql is included in the accouting section (line 389)

Comment radutmp in the session section (line 433)

Uncomment sql in the session section (line 437)

Uncomment the simul_count_query in /etc/freeradius/sql/mysql/dialup.conf (lines 279-282)

Limit testuser to one session

mysql -uroot -pmysqlsecret radius -e "INSERT INTO radcheck (username, attribute, op, value) VALUES ('testuser', 'Simultaneous-Use', ':=', '1')"

Restart FreeRadius

Limit Access Time Per Device (MAC) Address

In this section we will limit the access time of a device base on user and the device’s MAC address

Append the following to /etc/freeradius/dictionary

ATTRIBUTE MY-Counter-Reset-Type 3002 string

ATTRIBUTE MY-Time-Limit 3003 string

ATTRIBUTE MY-Session-Start-Time 3004 integer

ATTRIBUTE MY-Used-Session-Time 3005 string

ATTRIBUTE MY-Avail-Session-Time 3006 string

Create the file /etc/freeradius/modules/set_starttime with the following content

perl set_starttime {

module = ${confdir}/set_starttime.pl

}

Create the file /etc/freeradius/modules/check_time with the following content

perl check_time {

module = ${confdir}/check_time.pl

}

Create the file /etc/freeradius/set_starttime.pl with the following content

#!/usr/bin/perl

use strict;

# use ...

# This is very important ! Without this script will not get the filled hashesh from main.

use vars qw(%RAD_REQUEST %RAD_REPLY %RAD_CHECK);

use Data::Dumper;

# This is hash wich hold original request from radius

#my %RAD_REQUEST;

# In this hash you add values that will be returned to NAS.

#my %RAD_REPLY;

#This is for check items

#my %RAD_CHECK;

#

# This the remapping of return values

#

use constant RLM_MODULE_REJECT=> 0;# /* immediately reject the request */

use constant RLM_MODULE_FAIL=> 1;# /* module failed, don't reply */

use constant RLM_MODULE_OK=> 2;# /* the module is OK, continue */

use constant RLM_MODULE_HANDLED=> 3;# /* the module handled the request, so stop. */

use constant RLM_MODULE_INVALID=> 4;# /* the module considers the request invalid. */

use constant RLM_MODULE_USERLOCK=> 5;# /* reject the request (user is locked out) */

use constant RLM_MODULE_NOTFOUND=> 6;# /* user not found */

use constant RLM_MODULE_NOOP=> 7;# /* module succeeded without doing anything */

use constant RLM_MODULE_UPDATED=> 8;# /* OK (pairs modified) */

use constant RLM_MODULE_NUMCODES=> 9;# /* How many return codes there are */

# Function to handle authorize

sub authorize {

my ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst)=localtime(time);

#Find out when the reset time should be

if($RAD_CHECK{'MY-Counter-Reset-Type'} =~ /monthly/i){

$RAD_CHECK{'MY-Session-Start-Time'} = mktime (0, 0, 0, 1, $mon, $year, 0, 0); #We use this month

}

if($RAD_CHECK{'MY-Counter-Reset-Type'} =~ /weekly/i){

$RAD_CHECK{'MY-Session-Start-Time'} = mktime (0, 0, 0, $mday-$wday, $mon, $year, 0, 0);

}

if($RAD_CHECK{'MY-Counter-Reset-Type'} =~ /daily/i){

$RAD_CHECK{'MY-Session-Start-Time'} = mktime (0, 0, 0, $mday, $mon, $year, 0, 0);

}

if(exists($RAD_CHECK{'MY-Session-Start-Time'})){

return RLM_MODULE_UPDATED;

} else {

return RLM_MODULE_NOOP;

}

}

Create the file /etc/freeradius/check_time.pl with the following content

#!/usr/bin/perl

use strict;

# use ...

# This is very important ! Without this script will not get the filled hashesh from main.

use vars qw(%RAD_REQUEST %RAD_REPLY %RAD_CHECK);

use Data::Dumper;

# This is hash wich hold original request from radius

#my %RAD_REQUEST;

# In this hash you add values that will be returned to NAS.

#my %RAD_REPLY;

#This is for check items

#my %RAD_CHECK;

#

# This the remapping of return values

#

use constant RLM_MODULE_REJECT=> 0;# /* immediately reject the request */

use constant RLM_MODULE_FAIL=> 1;# /* module failed, don't reply */

use constant RLM_MODULE_OK=> 2;# /* the module is OK, continue */

use constant RLM_MODULE_HANDLED=> 3;# /* the module handled the request, so stop. */

use constant RLM_MODULE_INVALID=> 4;# /* the module considers the request invalid. */

use constant RLM_MODULE_USERLOCK=> 5;# /* reject the request (user is locked out) */

use constant RLM_MODULE_NOTFOUND=> 6;# /* user not found */

use constant RLM_MODULE_NOOP=> 7;# /* module succeeded without doing anything */

use constant RLM_MODULE_UPDATED=> 8;# /* OK (pairs modified) */

use constant RLM_MODULE_NUMCODES=> 9;# /* How many return codes there are */

# Function to handle authorize

sub authorize {

if(!exists($RAD_CHECK{'MY-Time-Limit'}) || !exists($RAD_CHECK{'MY-Used-Session-Time'})){

return RLM_MODULE_NOOP;

}

$RAD_CHECK{'MY-Avail-Session-Time'} = $RAD_CHECK{'MY-Time-Limit'} - $RAD_CHECK{'MY-Used-Session-Time'};

if($RAD_CHECK{'MY-Avail-Session-Time'} <= $RAD_CHECK{'MY-Time-Limit'}){

if($RAD_CHECK{'MY-Counter-Reset-Type'} ne 'never'){

$RAD_REPLY{'Reply-Message'} = "Maximum usage exceeded";

}

return RLM_MODULE_REJECT;

}

$RAD_REPLY{'Session-Timeout'} = int($RAD_CHECK{'MY-Avail-Session-Time'});

return RLM_MODULE_UPDATED;

}

Add the following in the authorize section of /etc/freeradius/sites-available/default, just below daily (line 174). Delete or comment dailycounter

if((control:MY-Time-Limit)&&(control:MY-Counter-Reset-Type)){

set_starttime

if(updated){

update control {

MY-Used-Session-Time := "%{sql:SELECT IFNULL(SUM(acctsessiontime), 0) FROM radacct WHERE UNIX_TIMESTAMP(acctstarttime) > %{control:MY-Session-Start-Time} AND username = '%{request:User-Name}' AND IF(username = 'free', callingstationid='%{request:Calling-Station-Id}', TRUE)}"

}

}

else {

update control {

MY-Used-Session-Time := "%{sql:SELECT IFNULL(SUM(acctsessiontime), 0) FROM radacct WHERE username = '%{request:User-Name}' AND IF(username = 'free', callingstationid='%{request:Calling-Station-Id}', TRUE)}"

}

}

check_time

Note that “else {“ must be in a new line

Give testuser a daily access limit of 15 minutes

mysql -uroot -pmysqlsecret radius -e "INSERT INTO radcheck (username, attribute, op, value) VALUES ('testuser', 'MY-Time-Limit', ':=', ‘1800’)"

mysql -uroot -pmysqlsecret radius -e "INSERT INTO radcheck (username, attribute, op, value) VALUES ('testuser', 'MY-Counter-Reset-Type', ':=', 'daily')"

Remove the simultaneous usage limit created in the previous section

mysql -uroot -pmysqlsecret radius -e "DELETE FROM radcheck WHERE username='testuser' and attribute='Simultaneous-Use'"

Stop FreeRadius

/etc/init.d/freeradius stop

Start FreeRadius in debug mode

freeradius -XX

If you get an error like

Can't load '/usr/lib/perl/5.14/auto/Data/Dumper/Dumper.so' for module Data::Dumper: /usr/lib/perl/5.14/auto/Data/Dumper/Dumper.so: undefined symbol: PL_charclass at /usr/share/perl/5.14/XSLoader.pm line 71.

at /usr/lib/perl/5.14/Data/Dumper.pm line 36

Compilation failed in require at /etc/freeradius/set_starttime.pl line 6.

BEGIN failed--compilation aborted at /etc/freeradius/set_starttime.pl line 6.

Thu Oct 25 10:51:37 2012 : Error: rlm_perl: perl_parse failed: /etc/freeradius/set_starttime.pl not found or has syntax errors.

Thu Oct 25 10:51:37 2012 : Error: /etc/freeradius/modules/set_starttime[1]: Instantiation failed for module "set_starttime"

Thu Oct 25 10:51:37 2012 : Error: /etc/freeradius/sites-enabled/default[176]: Failed to load module "set_starttime".

Thu Oct 25 10:51:37 2012 : Error: /etc/freeradius/sites-enabled/default[176]: Failed to parse "set_starttime" entry.

Thu Oct 25 10:51:37 2012 : Error: /etc/freeradius/sites-enabled/default[62]: Errors parsing authorize section.

This means FreeRadius has problems dynamically loading perl modules. A workaround is to set LD_PRELOAD environment variable before starting FreeRadius. Use the following command

LD_PRELOAD=/usr/lib/libperl.so.5.14 /usr/sbin/freeradius -XXX

This Setup will allow simultaneous devices using testuser account to have 15 minute daily access to the Internet using the capture portal

Debugging PHP using NetBeans and x Debug

2012-10-23T21:03:00.002-07:00

Objective:

To be able to debug PHP files

Tested on:

- Windows 7 64 bit

Requirements:

- NetBeans 6.9.1 with PHP package
- Apache 2.2
- PHP 5.3
- xDebug 2.1.0 (php-xdebug-2.1.0-5.3-vc9.dll

Steps:

- Install PHP
- Install Apache
- Configure Apache
- Download xDebug
- Configure php.ini
- Install Netbeans
- Create a test project
- Test

- Install PHP

Get the thread safe windows zip package, php-5.3.3-Win32-VC9-x86.zip, from PHP download site http://windows.php.net/download/

unzip the package to c:\php (you can put this in other location but you have to make adjustments)

- Install Apache

Download Apache HTTP server, httpd-2.2.16-win32-x86-openssl-0.9.8o.msi, from http://httpd.apache.org/download.cgi

Start installing Apache by double clicking httpd-2.2.16-win32-x86-openssl-0.9.8o.msi.

- Configure Apache

- Download xDebug
- Configure php.ini
- Install Netbeans
- Create a test project
- Test

Reference:
http://www.xdebug.org/find-binary.php

Understanding Android SQLite Database

2010-10-06T01:39:00.000-07:00

Because of the limited documentation of Android's database handling, I have spent days trying to understand the inner workings SQLite in an Android application. Debugging here, testing there, but in the end, going no where.

For those who are in a hurry to learn SQLite in Android, I have written this in order to share my discoveries and hope to help those who are impatiently wanting to understand Android's database handling

In order to demonstrate database creation, we will create an An android project that will take the a name and an age data and save it in SQLite database.

Make sure that you already have Eclipse with Android plug-in installed.

Let's start by creating an Android project by clicking File->New-Project.

Select Android Project from the list (you may have to expand Android to see Android Project)

Click the Next button to proceed.

Now fill in the project details using the following values:

Project Name = Android SQLite DemoBuild Target = Android 2.1
Application Name = SQLite Demo
Package Name = com.demo.sqlite
Activity = Main

Click Finish to create the project

Let's start with construction the UI. Open main.xml located in res/layout.

Replace the content with the following:
<?xml version="1.0" encoding="utf-8"?>
<TableLayout xmlns:android="http://schemas.android.com/apk/res/android"
    android:layout_width="fill_parent"
    android:layout_height="fill_parent"
    android:stretchColumns="1">
    <TableRow>
        <TextView android:text="Name" />
        <EditText android:id="@+id/name" />
    </TableRow>
    <TableRow>
        <TextView android:text="Age" />
        <EditText android:id="@+id/age" />
    </TableRow>
    <TableRow>
        <Button android:id="@+id/saveButton"
            android:layout_span="2"
            android:text="Save"
        />
    </TableRow>
</TableLayout>

Save main.xml then open Main.java in src/src/com.demo.sqlite.

Type in the following:

package com.demo.sqlite;

import android.app.Activity;
import android.os.Bundle;
import android.view.View;
import android.view.View.OnClickListener;
import android.widget.Button;
import android.widget.EditText;
import android.widget.Toast;

public class Main extends Activity {
    private EditText name;
    private EditText age;


    private OnClickListener saveButtonClicked = new OnClickListener() {

        public void onClick(View v) {
            DBHandler dbHandler = new DBHandler(v.getContext());
            Long id = dbHandler.insertRow(name.getText().toString(), Integer.parseInt(age.getText().toString()));
            if (id != -1){
                Toast toast = Toast.makeText(v.getContext(), "Your data has been saved, successfully", Toast.LENGTH_SHORT);
                toast.show();
                name.setText("");
                age.setText("");
            }
        }
    };


    /** Called when the activity is first created. */
    @Override
    public void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.main);

        name = (EditText) findViewById(R.id.name);
        age = (EditText) findViewById(R.id.age);
        Button saveButton = (Button) findViewById(R.id.saveButton);
        saveButton.setOnClickListener(saveButtonClicked);
    }
}

Save Main.java.

Now, create a new class under com.demo.sqlite and name it DBHandler.java. Type the following in the newly created class:

package com.demo.sqlite;

import android.content.Context;
import android.database.sqlite.SQLiteDatabase;
import android.database.sqlite.SQLiteOpenHelper;
import android.database.sqlite.SQLiteStatement;

public class DBHandler extends SQLiteOpenHelper {
    private static final int DATABASE_VERSION = 1;
    private static final String DATABASE_NAME = "demo.db";
    private static final String TABLE_NAME = "mytable";
    private static final String QUERY_CREATE_TABLE =
        "CREATE TABLE "
        + TABLE_NAME
        + "(id INTEGER PRIMARY KEY AUTOINCREMENT"
        + ",name TEXT"
        + ",age INTEGER);";
    private static final String QUERY_INSERT_ROW =
        "INSERT INTO "
        + TABLE_NAME
        + "(name, age)"
        + "values (?,?)";



    SQLiteDatabase db;
    SQLiteStatement stmtInsertRow;


    public DBHandler(Context context) {
        super(context, DATABASE_NAME, null, DATABASE_VERSION);
        db = this.getWritableDatabase();
        stmtInsertRow = db.compileStatement(QUERY_INSERT_ROW);
    }


    @Override
    public void onCreate(SQLiteDatabase db) {
        db.execSQL(QUERY_CREATE_TABLE);
    }


    @Override
    public void onUpgrade(SQLiteDatabase db, int oldVersion, int newVersion) {
        db.execSQL("DROP TABLE IF EXISTS " + TABLE_NAME);
        onCreate(db);
    }


    public long insertRow(String name, Integer age){
        stmtInsertRow.bindString(1, name);
        stmtInsertRow.bindLong(2, age);
        return stmtInsertRow.executeInsert();
    }

}

Let's trace the program execution to learn how Android handles SQLite databases first hand. Put breakpoints on the first line of all methods/functions of DBHandler. Now start debugging.

First Run:

Type in your name and age in the input boxes respectively. Click the save button when you are finished.

After clicking the save button the constructor for DBHandler is called when then DBHandler is initialized.

super(context, DATABASE_NAME, null, DATABASE_VERSION), Initializes DBHandler by calling SQLiteOpenHelperConstructor.

When the second line db = this.getWritableDatabase() is executed, the onCreate method is called. onCreate executes a query that will create your table.

After onCreate finishes, execution goes back to the constructor then creates the insert statement. Code continues to save the data that you have provided in the text boxes.

Notice that in this first run the onCreate method is called. It has been advised that you put your table creation query here. Do not worry thinking that every time the constructor is called the table creation query will be executed. You will know why it is best to put your table creation query here later.

Also notice onUpgrade method is not called during program execution.

2nd Run:

You may want to close the emulator and restart Eclipse. This is to demonstrate what will happen when Android phone or your Android application is restarted.

Now start debugging.

On the second run, constructor for DBHandler is again called.

When the second line db = this.getWritableDatabase() is executed, you will notice that onCreate method is NOT called. This just returns a reference to SQLiteDatabase object.

The next line creates the and insert statement and continues to run just like in the first run.

In this second run you will notice that onCreate method is never called. Android knows that the database is already created and thus skips calling the onCreate method.

Again the onUpgrade method is not executed.

3rd Run:

For the third run, edit DBHandler.java. Change the line

private static final int DATABASE_VERSION = 1;

to

private static final int DATABASE_VERSION = 2;

Save DBHandler.java. If you're the doubting kind, you may want to restart Eclipse and close the emulator.

Start the debug.

Step over the code until you reach

db = this.getWritableDatabase();

Notice that when you execute this line you will jump to onUpgrade method instead of onCreate method.

onUpgrade method deletes your table then calls onCreate to re-create your table.

After creating the table, execution goes back to DBHandler constructor. The codes continues to execute, inserting a data to the table and popping a notification the insert procedure went sucessfully.

Here, onCreate is only executed because onUpgrade called it. This is the recommended way of updating the database table.

In summary, the following should be noted:

- your database handler class should extend SQLiteOpenHelper.

- SQLiteOpenHelper's onCreate method is the recommended place to put your table creation query.

- SQLiteOpenHelper's onCreate method is called/executed only when the database is first created. Android ignores this if the database already exist.

- To delete, change, or update the database table structure, it is recommended that you put the code inside SQLiteOpenHelper's onUpgrade function. Note that you have to change the database version to force the execution of onUpgrade function. It does not matter whether you increment or decrement database version as long as the new version number is different from the previous number the application is running on.

I hope this helps. Good luck!

Running Eclipse on a Mac Network User Account

2010-09-25T16:50:00.000-07:00

Original Post Date: Aug 17, 2010

ISSUE:

When running eclipse (galileo) using a Mac network user account a message “Workspace in use or cannot be created, choose a different one” always pops up. Then after clicking "OK", eclipse closes

SOLUTION:

Run eclipse with the following parameters:

-vmargs -Dosgi.locking=java.io

e.g.

./eclipse -vmargs -Dosgi.locking=java.io

OR

Add -Dosgi.locking=java.io in eclipse.ini.

eclipse.ini can be found by right clicking Eclipse.app and choosing "Show Package Content". Then go to Contents -> MacOS

REFERENCE:

http://www.spreendigital.de/blog/2010/03/26/eclipse-on-mac-os-x-workspace-error-on-nfs-mounts/comment-page-1/#comment-4486

Setting Up OpenVPN

2010-09-25T16:45:00.000-07:00

This is a transfer from a blog dated Feb 23, 2009
consolidating...

Goal

To concentrate on getting a VPN up and running. Explanations are cut to the very minimum (for details read the OpenVPN HowTo).
This guide is done using an Ubuntu 8.04 for the server and client. The text in red may be modified to fit your configurations.

Server

Install

- log in to the server
- execute:


# apt-get install openvpn

Create CA

- execute:


# cd /usr/share/doc/openvpn/examples/easy-rsa/2.0
# source ./vars
# ./clean-all
# ./build-ca

[[build-ca will prompt you for some values. Use the following as reference:]]

[[this will create ca.crt and ca.key in /usr/share/doc/openvpn/examples/easy-rsa/2.0/keys/]]

Create Key & Certificate

- execute:
# cd /usr/share/doc/openvpn/examples/easy-rsa/2.0
# ./build-key-server server

[[build-key-server will prompt you for some values. Use the following as reference (leave challenge password and optional company name blank):]]

[[build-key-server will create server.crt and server.key in /usr/share/doc/openvpn/examples/easy-rsa/2.0/keys/]]

Create Diffie Hellman parameters

- execute:


# cd /usr/share/doc/openvpn/examples/easy-rsa/2.0
# ./build-dh

[[build-dh will create dh1024.pem in /usr/share/doc/openvpn/examples/easy-rsa/2.0/keys/]]

Configuration

- execute:

# cp /usr/share/doc/openvpn/examples/sample-config-files/server.conf.gz /etc/openvpn/
# cd /etc/openvpn
# gunzip server.conf.gz

- open /etc/openvpn/server.conf and change the following:

line 78
from ca ca.crt
to ca /usr/share/doc/openvpn/examples/easy-rsa/2.0/keys/ca.crt

line 79
from cert server.crt
to cert /usr/share/doc/openvpn/examples/easy-rsa/2.0/keys/server.crt

line 80
from key server.key
to key /usr/share/doc/openvpn/examples/easy-rsa/2.0/keys/server.key

line 87
from dh dh1024.pem
to dh /usr/share/doc/openvpn/examples/easy-rsa/2.0/keys/dh1024.pem

- save and close /etc/openvpn/server.conf

Test

- execute:


# openvpn /etc/openvpn/server.conf

- the output should look something like (the line "Initialization Sequence Completed" indicates that everything is working):

- press Ctrl+C to stop the test

Run

- execute:


# /etc/init.d/openvpn start

[[the init.d script for OpenVPN will look for .conf file in /etc/openvpn/ and use it as configuration file. This means that everytime you start the server it will start to listen for a vpn connection request.]]

Linux Client

Install

- log in to the linux client
- execute:


# apt-get install openvpn

Create Key & Certificate

- execute:


# cd /usr/share/doc/openvpn/examples/easy-rsa/2.0
# mkdir keys
# chmod 700 keys
# source ./vars
# ./clean-all
# scp user@vpnserver_ip:/usr/share/doc/openvpn/examples/easy-rsa/2.0/keys/ca.key ./keys/.
# scp user@vpnserver_ip:/usr/share/doc/openvpn/examples/easy-rsa/2.0/keys/ca.crt ./keys/.
# ./build-key client

[[the lines
# scp user@vpnserver:/usr/share/doc/openvpn/examples/easy-rsa/2.0/keys/ca.key ./keys/.
# scp user@vpnserver:/usr/share/doc/openvpn/examples/easy-rsa/2.0/keys/ca.crt ./keys/.
aim to copy the certificate authority (ca) key and certificate from the server to the client. you can use other means to copy the files from the server to the client]]

[[build-key will prompt you for some values. Use the following as reference (leave challenge password and optional company name blank):]]

[[make sure CommonName value is different for each client]]
[[this will create client.crt and client.key in /usr/share/doc/openvpn/examples/easy-rsa/2.0/keys/]]

Configuration

- execute:


# cp /usr/share/doc/openvpn/examples/sample-config-files/client.conf /etc/openvpn/
# cd /etc/openvpn

- open /etc/openvpn/client.conf and change the following:

line 42
from remote my-server-1 1194
to remote 111.111.111.101 1194

line 88
from ca ca.crt
to ca /usr/share/doc/openvpn/examples/easy-rsa/2.0/keys/ca.crt

line 89
from cert
client.crt
to cert /usr/share/doc/openvpn/examples/easy-rsa/2.0/keys/client.crt

line 90
from key client.key
to key /usr/share/doc/openvpn/examples/easy-rsa/2.0/keys/client.key

- save and close /etc/openvpn/client.conf

Test

- make sure that UDP port 1194 on the server is open
- execute:


# openvpn /etc/openvpn/client.conf

- the output should look something like (the line "Initialization Sequence Completed" indicates that everything is working):

- press Ctrl+C to stop the test

Run

- execute:


# /etc/init.d/openvpn start

[[the init.d script for OpenVPN will look for .conf file in /etc/openvpn/ and use it as configuration file. This means that everytime you start the client it will establish a vpn with the server.]]

Windows Client

Install

- download OpenVPN's Windows Installer
- run downloaded file to start OpenVPN installation

Create Key & Certificate

- in a command window, execute the following:


C:\> cd "c:\Program Files\OpenVPN\easy-rsa"
C:\> init-config
C:\> vars
C:\> clean-all
C:\> pscp user@vpnserver_ip:/usr/share/doc/openvpn/examples/easy-rsa/2.0/keys/ca.key keys\.
C:\> pscp user@vpnserver_ip:/usr/share/doc/openvpn/examples/easy-rsa/2.0/keys/ca.crt keys\.
C:\> path=%PATH%;c:\Program Files\OpenVPN\bin
C:\> build-key client

[[the lines
C:\> pscp user@vpnserver_ip:/usr/share/doc/openvpn/examples/easy-rsa/2.0/keys/ca.key keys\.
C:\> pscp user@vpnserver_ip:/usr/share/doc/openvpn/examples/easy-rsa/2.0/keys/ca.crt keys\.
aim to copy the certificate authority (ca) key and certificate from the server to the client. you can use other means to copy the files from the server to the client]]

[[build-key will prompt you for some values. Use the following as reference (leave challenge password and optional company name blank):]]

Configuration

- still in the same command window, execute the following:


C:\> cd "c:\Program Files\OpenVPN\config\"
C:\> copy ..\sample-config\client.ovpn .
C:\> edit client.ovpn

change the following:

line 42
from remote my-server-1 1194
to remote 111.111.111.101 1194

line 88
from ca ca.crt
to ca c:/Program\ Files/OpenVPN/easy-rsa/keys/ca.crt

line 89
from cert
client.crt
to cert c:/Program\ Files/OpenVPN/easy-rsa/keys/client.crt

line 90
from key client.key
to key c:/Program\ Files/OpenVPN/easy-rsa/keys/client.key

- save and close "c:\Program Files\OpenVPN\config\client.conf"

Run

- make sure that UDP port 1194 on the server is open
- still in the same command window, execute the following:


C:\> cd "c:\Program Files\OpenVPN"
C:\> bin\openvpn config\client.ovpn

- when you see the line "Initialization Sequence Completed", this indicates that everything is working
- press Ctrl+Pause to stop OpenVPN

Reference

OpenVPN HowTo

Running Eclipse on a Mac Network User Account

2010-08-17T19:51:00.000-07:00

ISSUE:

When running eclipse (galileo) using a Mac network user account a message “Workspace in use or cannot be created, choose a different one” always pops up. Then after clicking "OK", eclipse closes

SOLUTION:

Run eclipse with the following parameters:

-vmargs -Dosgi.locking=java.io

e.g.

./eclipse -vmargs -Dosgi.locking=java.io

OR

Add -Dosgi.locking=java.io in eclipse.ini.

eclipse.ini can be found by right clicking Eclipse.app and choosing "Show Package Content". Then go to Contents -> MacOS

REFERENCE:

http://www.spreendigital.de/blog/2010/03/26/eclipse-on-mac-os-x-workspace-error-on-nfs-mounts/comment-page-1/#comment-4486

Dynamic IP "Road-Warrior" VPN

2009-02-23T21:03:00.000-08:00

Goal

Server

Install

- log in to the server
- execute:


# apt-get install openvpn

Create CA

- execute:


# cd /usr/share/doc/openvpn/examples/easy-rsa/2.0
# source ./vars
# ./clean-all
# ./build-ca

[[build-ca will prompt you for some values. Use the following as reference:]]

[[this will create ca.crt and ca.key in /usr/share/doc/openvpn/examples/easy-rsa/2.0/keys/]]

Create Key & Certificate

[[build-key-server will create server.crt and server.key in /usr/share/doc/openvpn/examples/easy-rsa/2.0/keys/]]

Create Diffie Hellman parameters

- execute:


# cd /usr/share/doc/openvpn/examples/easy-rsa/2.0
# ./build-dh

[[build-dh will create dh1024.pem in /usr/share/doc/openvpn/examples/easy-rsa/2.0/keys/]]

Configuration

- execute:

# cp /usr/share/doc/openvpn/examples/sample-config-files/server.conf.gz /etc/openvpn/
# cd /etc/openvpn
# gunzip server.conf.gz

Test

- execute:


# openvpn /etc/openvpn/server.conf

- the output should look something like (the line "Initialization Sequence Completed" indicates that everything is working):

- press Ctrl+C to stop the test

Run

- execute:


# /etc/init.d/openvpn start

Linux Client

Install

- log in to the linux client
- execute:


# apt-get install openvpn

Create Key & Certificate

- execute:


# cd /usr/share/doc/openvpn/examples/easy-rsa/2.0
# mkdir keys
# chmod 700 keys
# source ./vars
# ./clean-all
# scp user@vpnserver_ip:/usr/share/doc/openvpn/examples/easy-rsa/2.0/keys/ca.key ./keys/.
# scp user@vpnserver_ip:/usr/share/doc/openvpn/examples/easy-rsa/2.0/keys/ca.crt ./keys/.
# ./build-key client

[[make sure CommonName value is different for each client]]
[[this will create client.crt and client.key in /usr/share/doc/openvpn/examples/easy-rsa/2.0/keys/]]

Configuration

- execute:


# cp /usr/share/doc/openvpn/examples/sample-config-files/client.conf /etc/openvpn/
# cd /etc/openvpn

Test

- make sure that UDP port 1194 on the server is open
- execute:


# openvpn /etc/openvpn/client.conf

- the output should look something like (the line "Initialization Sequence Completed" indicates that everything is working):

- press Ctrl+C to stop the test

Run

- execute:


# /etc/init.d/openvpn start

[[the init.d script for OpenVPN will look for .conf file in /etc/openvpn/ and use it as configuration file. This means that everytime you start the client it will establish a vpn with the server.]]

Windows Client

Install

- download OpenVPN's Windows Installer
- run downloaded file to start OpenVPN installation

Create Key & Certificate

- in a command window, execute the following:


C:\> cd "c:\Program Files\OpenVPN\easy-rsa"
C:\> init-config
C:\> vars
C:\> clean-all
C:\> pscp user@vpnserver_ip:/usr/share/doc/openvpn/examples/easy-rsa/2.0/keys/ca.key keys\.
C:\> pscp user@vpnserver_ip:/usr/share/doc/openvpn/examples/easy-rsa/2.0/keys/ca.crt keys\.
C:\> path=%PATH%;c:\Program Files\OpenVPN\bin
C:\> build-key client

Configuration

- still in the same command window, execute the following:


C:\> cd "c:\Program Files\OpenVPN\config\"
C:\> copy ..\sample-config\client.ovpn .
C:\> edit client.ovpn

Run

- make sure that UDP port 1194 on the server is open
- still in the same command window, execute the following:


C:\> cd "c:\Program Files\OpenVPN"
C:\> bin\openvpn config\client.ovpn

- when you see the line "Initialization Sequence Completed", this indicates that everything is working
- press Ctrl+Pause to stop OpenVPN

Reference

OpenVPN HowTo