WISP Coova phpMyPrepaid: Difference between revisions

From WirelessAfrica
Line 52: Line 52:
* Setup coova on Linksys router - [http://coova.org/wiki/index.php/Installation_Help URL]
* Setup coova on Linksys router - [http://coova.org/wiki/index.php/Installation_Help URL]
* Configure Coova WAN settings. (the following points are with assumption that the gateway server settings described here are being used)
* Configure Coova WAN settings. (the following points are with assumption that the gateway server settings described here are being used)
** On Coova administration web portal : Network->WAN.
** On Coova administration web portal : ''Network''->''WAN''.
** Under WAN Configuration, set Connection Type to Static IP.
** Under ''WAN Configuration'', ''set Connection Type'' to ''Static IP''.
** Under IP Settings, set IP address, Netmask and Default Gateway settings (e.g, 192.168.5.4, 255.255.255.0, 192.168.5.1 in this example).
** Under ''IP Settings'', set ''IP address'', ''Netmask'' and ''Default Gateway'' settings (e.g, 192.168.5.4, 255.255.255.0, 192.168.5.1 in this example).
** Under DNS Servers, add Gateway server internal network interface IP address (e.g 192.168.5.1).
** Under ''DNS Servers'', add Gateway server internal network interface IP address (e.g 192.168.5.1).
** Leave the Dyanmic DNS Settings as is. Save changes.
** Leave the ''Dyanmic DNS'' Settings as is. Save changes.
* Configure Coova Wireless Network
* Configure Coova Wireless Network. ''Click on Network''->''Wireless''.
** Under Wireless Configuration, ensure Wireless Network is set to Enabled and Mode is set to Access Point.  Configure Wireless Network to however it suits you. Save changes.
** Under ''Wireless Configuration'', ensure ''Wireless Network'' is set to ''Enabled'' and ''Mode'' is set to ''Access Point''.  Configure Wireless Network to however it suits you. Save changes.
** For the purposes of testing in this case, Wireless Network is not encrypted, with minimal access configuration (ESSID - wifibox, ESSID Broadcast - Show, Channel - Auto, Encryption Type - Disabled).
** For the purposes of testing in this case, Wireless Network is not encrypted, with minimal access configuration (''ESSID'' - wifibox, ''ESSID Broadcast'' - Show, ''Channel'' - Auto, ''Encryption Type'' - Disabled).
* Setup coova to act as a Chillispot-type hotspot, with auto-configuration disabled.  (Setup may be tested later on with WifiDog instead of Chillispot).
* Setup coova to act as a Chillispot-type hotspot, with auto-configuration disabled.  (Setup may be tested later on with WifiDog instead of Chillispot).
** Click on the Hotspot tab. Under HotSpot Configurations
** Click on the ''Hotspot'' tab. Under ''HotSpot Configurations''
*** Set Hotspot type to ChilliSpot UAM
*** Set ''Hotspot type'' to ''ChilliSpot UAM''
*** Set Hotspot Mode to Wireless Only
*** Set ''Hotspot Mode'' to ''Wireless Only''
*** Choose if you prefer to Deny or Allow LAN access through the hotspot.
*** Choose if you prefer to ''Deny'' or ''Allow'' ''LAN access'' through the hotspot.
** Under ChilliSpot Configurations
** Under ''ChilliSpot Configurations''
*** Set Auto Configuration to Disabled
*** Set ''Auto Configuration'' to ''Disabled''
***  
***  
* Fill in UAM Hostname, UAM Secret, NAS Identifer information.
* Fill in UAM Hostname, UAM Secret, NAS Identifer information.

Revision as of 17:01, 11 June 2008


Introduction

This section contains documentation on work done regarding testing of an implementation that would make it as easy as possible for a would-be entrepreneur to deploy an ISP service over a wireless network infrastructure. The entrepreneur should be able to manage, monitor and charge users with ease.

Setup Ingredients

The tools used to setup this testbed:


Setup Recipe

Diagram of initial WISPiab-billing setup using Coova, myPhpPrepaid.

At the moment the intention of this setup is to mainly test billing support, and is more of a wifi-hotspot setup. It will later on be modified to adapt to a wireless mesh network environment. The gateway server has an external network interface (e.g, eth0) that is connected to the Internet, and an internal network interface (e.g, eth3), connected to the Coova Linksys Router (internal network). In this case the external network interface gets its IP address automatically (DHCP). The internal network interface is assigned a static ip address (e.g, 192.168.5.1), therefore the Coova WAN interface is also set to static (e.g, 192.168.5.4). All instructions below are provided with the assumption that this is a fresh install of Ubuntu. Performing these steps on an existing installation does not guarantee proper functionality.






Coova

  • Setup coova on Linksys router - URL
  • Configure Coova WAN settings. (the following points are with assumption that the gateway server settings described here are being used)
    • On Coova administration web portal : Network->WAN.
    • Under WAN Configuration, set Connection Type to Static IP.
    • Under IP Settings, set IP address, Netmask and Default Gateway settings (e.g, 192.168.5.4, 255.255.255.0, 192.168.5.1 in this example).
    • Under DNS Servers, add Gateway server internal network interface IP address (e.g 192.168.5.1).
    • Leave the Dyanmic DNS Settings as is. Save changes.
  • Configure Coova Wireless Network. Click on Network->Wireless.
    • Under Wireless Configuration, ensure Wireless Network is set to Enabled and Mode is set to Access Point. Configure Wireless Network to however it suits you. Save changes.
    • For the purposes of testing in this case, Wireless Network is not encrypted, with minimal access configuration (ESSID - wifibox, ESSID Broadcast - Show, Channel - Auto, Encryption Type - Disabled).
  • Setup coova to act as a Chillispot-type hotspot, with auto-configuration disabled. (Setup may be tested later on with WifiDog instead of Chillispot).
    • Click on the Hotspot tab. Under HotSpot Configurations
      • Set Hotspot type to ChilliSpot UAM
      • Set Hotspot Mode to Wireless Only
      • Choose if you prefer to Deny or Allow LAN access through the hotspot.
    • Under ChilliSpot Configurations
      • Set Auto Configuration to Disabled
  • Fill in UAM Hostname, UAM Secret, NAS Identifer information.
  • Fill in RADIUS server details and secret. (To be inserted into FreeRADIUS configuration on Gateway server.)

Gateway server

  • Install Ubuntu Server (Hardy), with minimum MySQL, FreeRADIUS, Apache webserver. DO NOT Install the DNS Server. This is because I have decided to use dnsmasq instead, as I found it much easier to setup for any user who is not familiar with bind9. Bind9 is the default DNS server that is included with Ubuntu distributions.
  • Install Webmin. Webmin is a great tool with a web-based frontend to administer many important settings under Linux (Startup/Shutdown Scripts, DNS, DHCP, Firewall, NAT; also supports plugins for other tools). (an apparently better alternative is ispconfig, but I've not tested this tool yet.)
  • Setup up network configuration for both network interfaces. [Todo: Should check out the dnsmasq webmin module..]
    • Configure NAT using iptables (can be done using the Webmin interface).
      • Click on Networking -> Linux Firewall on the left panel of the Webmin interface.
      • On the Linux Firewall page, at the top left, there is a list box next to the Showing IPtable: button. Click on this list box and ensure Network address translation (nat) is selected.
      • Click on Showing IPtable: The page will reload with NAT iptable configuration.
      • Under the section Packets after routing (POSTROUTING), click on the Add Rule button. The page reloads with the Add Rule page.
      • In the Chain and action details section, you may fill the Rule comment section with a description of your choice (e.g., Internet access for intranet). Choose Masquerade option in the Action to take field. Leave other fields as is.
      • In the Condition details, select outgoing interface to the external interface (eth0 for the purpose of this document.) Leave other details as is.
      • Click 'the 'Create button.
      • This page will reload the general Linux Firewall page. You should see a rule under the postrouting section to the following effect:
        Action: Masquerade;                        Condition:If output interface is eth0
      • Click on Apply Configuration.
      • Next to the Activate at boot button, select the Yes option. Then click 'Activate at boot.
    • Enable IP forwarding. (In this case we are using IPv4. For IPv6, replace "ipv4" in all the settings below with "ipv6".
      • Open terminal and type the following command in terminal:
        echo 1 > /proc/sys/net/ipv4/ip_forward 
      • Open the /etc/sysctl.conf file with superuser privileges.
        sudo /etc/sysctl.conf
        If nano is not installed, you can type
        sudo apt-get install nano
      • Look for the the term net.ipv4.ip_forward in this file. If it is commented uncomment it. Edit this line as necessary to ensure that it looks like
         net.ipv4.ip_forward=1
    • Install and setup dnsmasq and ipmasq by typing from terminal
      • sudo apt-get install dnsmasq ipmasq
      • sudo /etc/init.d/dnsmasq restart
      • dpkg-reconfigure ipmasq
        This will load a window that requests some configuration steps. Select Yes to the first screen (recompute firewall). Select OK to the second screen. Select After network services have been started on the next screen (when should ipmasq be started) and press OK. Reboot.
    • Setup FreeRADIUS and MySQL. Note: I have had a lot of hassle trying to smoothly set up FreeRADIUS. A lot of issues can be expected during this part of the setup.
      • Ensure that the FreeRADIUS MySQL plugin is installed:
        apt-get install freeradius-mysql

More to follow within the next few days.