Here’s a quick start installation guide to get you up and running with the Google Android Software Development Kit (SDK). This guide will describe how to install the Android SDK and set up your chosen development environments. If you’ haven’t already done so you can download the Android SDK from the link below, then we can get started.
First you’ll need to download the Android SDK source files:
( http://code.google.com/android/download.html )
System Requirements
In order to first use the Android SDK code and tools for development you will of course need a suitable environment develop from.
Currently the following operating systems are supported:
* Windows XP or Vista
* Mac OS X 10.4.8 or later (x86 only)
* Linux (tested on Linux Ubuntu Dapper Drake)
You will also need to install a suitable development environment such as:
* Eclipse
Eclipse 3.2, 3.3 (Europa)
Android Development Tools plugin (optional)
* Other development environments or IDEs
JDK 5 or JDK 6 (JRE alone is not sufficient)
Not compatible with Gnu Compiler for Java (gcj)
Apache Ant 1.6.5 or later for Linux and Mac, 1.7 or later for Windows
Installing The Android SDK
First you will need to download the Android SDK pack .zip archive, once downloaded find a suitable installation location on your machine and extract the zipped files.
Please note: This installation location will be referred to as $SDK_ROOT from now on through this tutorial
Alternatively you can add /tools to your root path which will prevent the need to specify the full path to the tools directory along with enabling you to run Android Debug Bridge (adb) along with other command line tools.
To add /tools:
Linux
1. Edit the ~/.bash_profile or ~/.bashrc files looking for a line that sets the PATH variable.
2. Add the full path location to your $SDK_ROOT/tools location for the PATH variable.
3. If no PATH line exists you can add the line by typing the following:
4. export PATH=${PATH}:
Mac OS X
1. In the home directory locate the .bash_profile and locating the PATH variable add the location to your $SDK_ROOT/tools folder.
Windows XP / Vista
1. Right click on the My Computer icon and select the properties tab.
2. Select the Advanced tab and click the Environment Variables button.
3. In the new dialog box dowble-click on Path (located under System Variables) and type in the full path location to the tools directory.
The Android SDK also requires a suitable development environment to work in, here’s the installation guides for each of the supported environments.
Android Eclipse Plugin (ADT)
If you choose to use the Eclipse IDE as your Android development environment you will have the opportunity to install and run a plug-in called Android Development Tools. ADT comes with a variety of powerful tools and extensions that will make creating, running and debugging your Android applications much easier and faster.
In order to download and install ADT you will first need to configure an Eclipse remote update, this can achieved via the following steps:
1. Start Eclipse, then select Help > Software Updates > Find and Install….
2. In the dialog that appears, select Search for new features to install and press Next.
3. Press New Remote Site.
4. In the resulting dialog box, enter a name for the remote site (e.g. Android Plugin) and enter this as its URL: https://dl-ssl.google.com/android/eclipse/.
5. Press OK.
6. You should now see the new site added to the search list (and checked).
7. Press Finish.
8. In the subsequent Search Results dialog box, select the checkbox for Android Plugin > Eclipse Integration > Android Development Tools and press Next.
9. Read the license agreement and then select Accept terms of the license agreement, if appropriate.
10. Press Next.
11. Press Finish.
12. The ADT plugin is not signed; you can accept the installation anyway by pressing Install All.
13. Restart Eclipse.
14. After restart, update your Eclipse preferences to point to the SDK root directory ($SDK_ROOT):
Select Window > Preferences… to open the Preferences panel. (Mac OS X: Eclipse > Preferences)
Select Android from the left panel.
For the SDK Location in the main panel, press Browse... and find the SDK root directory.
15. Press Apply, then OK
Updating the ADT Plugin
To update the ADT plugin to the latest version, follow these steps:
1. Select Help > Software Updates > Find and Install….
2. Select Search for updates of the currently installed features and press Finish.
3. If any update for ADT is available, select and install.
Alternatively:
1. Select Help > Software Updates > Manage Configuration.
2. Navigate down the tree and select Android Development Tools
3. Select Scan for Updates under Available Tasks.
How-To Use Eclipse To Develop Android Applications
In order to begin development on your Android applications you will first need to create a new Android project and then configure a launch configuration. Once completed you will have the capability to write, run and debug your Android creations.
The following sections below will provide you with the necessary instructions to get you up and running with Android provided you have installed the ADT plugin (as previously mentioned) in your Eclipse environment.
Creating A New Android Project
The Android Development Tools plugins kindly provides a Wizard for setting up new Projects which will allow us to create new Eclipse projects relatively quickly for either new or existing code.
Select File > New > Project
1. Select Android > Android Project, and press Next
2. Select the contents for the project:
* Select Create new project in workspace to start a project for new code. Enter the project name, the base package name, the name of a single Activity class to create as a stub .java file, and a name to use for your application.
* Select Create project from existing source to start a project from existing code. Use this option if you want to build and run any of the sample applications included with the SDK. The sample applications are located in the samples/ directory in the SDK. Browse to the directory containing the existing source code and click OK. If the directory contains a valid Android manifest file, the ADT plugin fills in the package, activity, and application names for you.
Press Finish.
Once completed the ADT plugin will go ahead and create the following files and folders as appropriate for the type of project selected:
* src/ A folder that includes your stub .java Activity file.
* res/ A folder for your resources.
* AndroidManifest.xml The manifest for your project.
Creating A Launch Configuration For Eclipse
In order to be able to run and debug your own Eclipse applications you must first create a launch configuration. Simply, a launch config is used to specify which project to launch, which activity to start and the specific emulation options to use.
To create a launch configuration for the application, please see the following steps:
1. Select Run > Open Run Dialog… or Run > Open Debug Dialog… as appropriate.
2. In the project type list on the left, right-click Android Application and select New.
3. Enter a name for your configuration.
4. On the Android tab, browse for the project and Activity to start.
5. On the Emulator tab, set the desired screen and network properties, as well as any other emulator startup options.
6. You can set additional options on the Common tab as desired.
7. Press Apply to save the launch configuration, or press Run or Debug (as appropriate).
Running and Debugging an Eclipse Application
Once both steps 1 and 2 have been completed and your project and launch configs are up and running you will now be able to run or debug your application.
From the Eclipse main menu, select Run > Run or Run > Debug as appropriate. This command will run or debug the most recently selected application.
To set or change the active launch configuration, use the Run configuration manager, which you can access through Run > Open Run Dialog… or Run > Open Debug Dialog….
Running or debugging the application will trigger the following actions:
* Starts the emulator, if it is not already running.
* Compile the project, if there have been changes since the last build, and installs the application on the emulator.
* Run starts the application.
* Debug starts the application in “Wait for debugger” mode, then opens the Debug perspective and attaches the Eclipse Java debugger to the application.
Developing Android Applications with Other IDEs and Tools
Although it is recommended you use Eclipse with the Android plugin to develop your applications, the SDK also provides tools which will enable you to develop with other IDE’s including intelliJ (alternatively you could just use Eclipse without the plugin).
Creating an Android Project
Bundled with the Android SDK is a program called activityCreatory. activityCreator will generate a number of ‘stub’ files for your chosen project alongside a build file. This can be used to either create an Android project for new code or from existing code.
For Linux and Mac users the Android SDK provides a Python script called activityCreator.py, with Windows users receiving a btach script called activityCreator.bat. The program is used in the same way regardless of operating system.
In order to run activityCreator and create an Android project, follow these steps:
1. In the command line, change to the tools/ directory of the SDK and create a new directory for your project files. If you are creating a project from existing code, change to the root folder of your application instead.
2. Run activityCreator. In the command, you must specify a fully-qualified class name as an argument. If you are creating a project for new code, the class represents the name of a stub class that the script will create. If you are creating a project from existing code, you must specify the name of one Activity class in the package. Command options for the script include:
–out
–ide intellij, which generates IntelliJ IDEA project files in the newly created project
Here’s an example:
/android_linux_sdk/tools$ ./activityCreator.py –out myproject your.package.name.ActivityName
package: your.package.name
out_dir: myproject
activity_name: ActivityName
~/android_linux_sdk/tools$
The activityCreator script generates the following files and directories (but will not overwrite existing ones):
* AndroidManifest.xml The application manifest file, synced to the specified Activity class for the project.
* build.xml An Ant file that you can use to build/package the application.
* src/your/package/name/ActivityName.java The Activity class you specified on input.
* your_activity.iml, your_activity.ipr, your_activity.iws [only with the -ide intelliJ flag] intelliJ project files.
* res/ A directory to hold resources.
* src/ The source directory.
* bin/ The output directory for the build script.
Once complete you will now be able to move your folder wherever you choose for development but you’ll need to bear in mind then you will need to use the adb program in the tools folder in order to send the files to the emulator.
How-To Build An Android Application
Here’s how to use the Ant build.xml file generated by activityCreator to build your application.
1. If you don’t have it, you can obtain Ant from the Apache Ant home page. Install it and make sure it is on your executable path.
2. Before calling Ant, you need to declare the JAVA_HOME environment variable to specify the path to where the JDK is installed.Note: When installing JDK on Windows, the default is to install in the “Program Files” directory. This location will cause ant to fail, because of the space. To fix the problem, you can specify the JAVA_HOME variable like this: set JAVA_HOME=c:\Prora~1\Java\. The easiest solution, however, is to install JDK in a non-space directory, for example: c:\java\jdk1.6.0_02.
3. If you have not done so already, follow the instructions for Creating a New Project above to set up the project.
4. You can now run the Ant build file by simply typing ant in the same folder as the build.xml file for your project. Each time you change a source file or resource, you should run ant again and it will package up the latest version of the application for you to deploy.
How-To Run An Android Application
In order to run a compiled application you will first need to upload the .apk file to the /data/app/ directory in the emulator using the adb tool:
1. Start the emulator (run $SDK_HOME/tools/emulator from the command line)
2. On the emulator, navigate to the home screen (it is best not to have that application running when you reinstall it on the emulator; press the Home key to navigate away from that application).
3. Run adb install myproject/bin/
4. In the emulator, open the list of available applications, and scroll down to select and start your application.
Please Note: When installing an activity for the first time you may need to restart the emulator engine in order for the activity to show up in the application launcher or before any other application can call. This is usually down to the fact that the package manager normally only examines manifests completely on emulator start-up.
How-To Attach a Debugger to Your Application
The following section details how to display debug information directly onto the screen (for example CPU usage). It also shows you how to hook up your IDE to debug running applications on the emulator.
The Eclipse plugin automatically attaches a debugger but you can configure other IDE’s to wait on a debugging port by doing the following:
Start the Dalvik Debug Monitor Server (DDMS) tool , which acts as a port forwarding service between your IDE and the emulator.
1. Set optional debugging configurations on your emulator, such as blocking application startup for an activity until a debugger is attached. Note that many of these debugging options can be used without DDMS, such as displaying CPU usage or screen refresh rate on the emulator.
2. Configure your IDE to attach to port 8700 for debugging. We’ve included information higher up on how to set up Eclipse to debug your project.
How-To Configure Your IDE To Attach To The Debugging Port
DDMS will automatically assign a specific debugging port for every virtual machine that it detects on the emulator. You must either attach your IDE to that port, or use a default port 8700 to connect to whatever application is currently selected on the list of discovered virtual machines.
Ideally your IDE will attach to the application running on the emulator, showing its threads and allowing you to suspend them, inspect them, or set breakpoints. If you choose to “Wait for debugger” in the Development settings panel, this will cause the application to run when Eclipse connects therefore you will need to set any breakpoints you want before connecting. If you change the application being debugged or the “Wait for debugger” then the system will kill the selected currently running application.
This can be handy if your application is in a bad state, you can simply go to the settings and toggle the checkbox to kill it.
Debugging Android
Google Android has a fairly extensive set of tools to help you debug your programs:
* DDMS – A graphical program that supports port forwarding (so you can set up breakpoints in your code in your IDE), screen captures on the emulator, thread and stack information, and many other features. You can also run logcat to retrieve your Log messages. See the linked topic for more information.
* logcat – Dumps a log of system messages. The messages include a stack trace when the emulator throws an error, as well as Log messages. To run logcat, see the linked topic. …
I/MemoryDealer( 763): MemoryDealer (this=0×54bda0): Creating 2621440 bytes heap at 0×438db000
I/Logger( 1858): getView() requesting item number 0
I/Logger( 1858): getView() requesting item number 1
I/Logger( 1858): getView() requesting item number 2
D/ActivityManager( 763): Stopping: HistoryRecord{409dbb20 com.google.android.home.AllApps}
…
* Android Log- A logging class to print out messages to a log file on the emulator. You can read messages in real time if you run logcat on DDMS (covered next). Add a few logging method calls to your code.
To use the Log class, you just call Log.v() (verbose), Log.d() (debug), Log.i() (information), Log.w() (warning) or Log.e (error) depending on the importance you wish to assign the log message.
Log.i(“MyActivity”, “MyClass.getView() — Requesting item number ” + position) You can use logcat to read these messages
* Traceview – Android can save a log of method calls and times to a logging file that you can view in a graphical reader called Traceview. See the linked topic for more information.
* Eclipse plugin – The Eclipse Android plugin incorporates a number of these tools (ADB, DDMS, logcat output, and other functionality). See the linked topic for more information.
Debug and Test Device Settings – Android exposes several settings that expose useful information such as CPU usage and frame rate.
Debug and Test Settings on the Device
Android enables you to set a number of options that will make it far easier to test and debug your applications.
To get to the development settings page on the emulator simply go to Dev Tools > Development Settings. This will in turn open up the development settings page with the following options (among others):
* Debug app Selects the application that will be debugged. You do not need to set this to attach a debugger, but setting this value has two effects:
It will prevent Android from throwing an error if you pause on a breakpoint for a long time while debugging.
It will enable you to select the Wait for Debugger option to pause application startup until your debugger attaches (described next).
* Wait for debugger Blocks the selected application from loading until a debugger attaches. This way you can set a breakpoint in onCreate(), which is important to debug the startup process of an Activity. When you change this option, any currently running instances of the selected application will be killed. In order to check this box, you must have selected a debug application as described in the previous option. You can do the same thing by adding waitForDebugger() to your code.
* Immediately destroy activities Tells the system to destroy an activity as soon as it is stopped (as if Android had to reclaim memory). This is very useful for testing the onFreeze(Bundle) / onCreate(android.os.Bundle) code path, which would otherwise be difficult to force. Choosing this option will probably reveal a number of problems in your application due to not saving state.
* Show screen updates Flashes a momentary pink rectangle on any screen sections that are being redrawn. This is very useful for discovering unnecessary screen drawing.
* Show CPU usage Displays CPU meters at the top of the screen, showing how much the CPU is being used. The top red bar shows overall CPU usage, and the green bar underneath it shows the CPU time spent in compositing the screen. Note: You cannot turn this feature off once it is on, without restarting the emulator.
* Show screen FPS Displays the current frame rate. Mostly useful for games to see the overall frame rate they are achieving. Note: You cannot turn this feature off once it is on without restarting the emulator.
* Show background Displays a background pattern when no activity screens are visible. This typically does not happen, but can happen during debugging.
How to install android in windows xp
Tips Meningkatkan Alexa Rank
1. Alexa Traffic
Langkah yang paling dasar : Get lot of site traffic! Karena ide awal dari Alexa rank adalah untuk menentukan website mana yang memiliki traffic paling banyak dengan asumsi, banyak traffic = lebih populer. Yep, Alexa pada dasarnya adalah ranking popularistas suatu website.
2. Alexa Toolbar
Menggunakan browser yang terinstall toolbar Alexa bisa ningkatin ranking website kamu. Sebenarnya bukan hanya websitemu, setiap website yang dikunjungi browser yang terinstall toolbar Alexa juga mendapat “nilai” yang akan diperhitungkan dalam ranking. Lalu, bukankah pengunjung pasti dari websitemu adalah dirimu sendiri? So, kalau browsermu sudah terinstall toolbar, maka penambahan point ranking akan terjadi secara otomatis! Nah, toolbar Alexa tersebut bisa di install melalui link berikut :
3. Alexa Widget
Pasang Alexa site stat widget di websitemu. Alexa site stat ini mengandung javascript yang mengantarkan setiap data pengunjung (ping) ke server Alexa sehingga statistik Alexa menjadi lebih akurat. Scriptnya bisa diambil di sini. Tinggal copy paste. Ga perlu malu pasang Alexa widget yang gede, untuk mencapai hasil yang diinginkan tentunya ada harga yang harus dibayar kan? Siapa sangka dulunya ranking 3 juta-an sekarang ranking 300 ribuan?
4. Alexa Redirection
Gunakan Alexa redirection setiap berkunjung ke websitemu. Formatnya seperti berikut:
http://redirect.alexa.com/redirect?www.resep.web.id
(Ganti www.www.resep.web.id dengan URL websitemu)
Alexa Redirection sudah tidak berfungsi lagi. Setiap loading page dengan link ini akan muncul pesan 404.
404 Not Found
The requested URL /redirect was not found on this server.
5. Alexa Blog/Content
Tulis/blog tentang Alexa di blogmu. Webmaster dan Blogger suka cara-cara untuk meningkatkan ranking Alexa. Ya… mungkin seperti yang dibaca sekarang ini.
Mengapa Alexa penting ?
Jawabannya, karena ada beberapa website layanan iklan komersil yang memberikan syarat ranking Alexa dalam batasan tertentu. ReviewMe, Text Link Ads dan Sponsored Reviews adalah 3 diantaranya dan masih banyak lagi. Jikapun kita tidak berkeinginan menggunakan layanan iklan komersil atau tidak ingin menjadikan blog kita sebagai monetize blog, peningkatan ranking Alexa bisa dipandang sebagai upaya untuk melakukan sedikit optimasi yang bisa bermanfaat bagi kwalitas blog.
source www.nadasumbang.com
IP Hotspot 2
Menu is designed to manage HotSpot servers of the router. It is possible to run HotSpot on Ethernet, wireless, VLAN and bridge interfaces. One HotSpot server is allowed per interface. When HotSpot is configured on bridge interface, set HotSpot interface as bridge interface not as bridge port, do not add public interfaces to bridge ports. You can add HotSpot servers manually to /ip hotspot menu, but it is advised to run /ip hotspot setup, that adds all necessary settings.
* name (text) : HotSpot server's name or identifier
* address-pool (name / none; default: none) : address space used to change HotSpot client any IP address to a valid address. Useful for providing public network access to mobile clients that are not willing to change their networking settings
* idle-timeout (time / none; default: 5m) : period of inactivity for unauthorized clients. When there is no traffic from this client (literally client computer should be switched off), once the timeout is reached, user is dropped from the HotSpot host list, its used address becomes available
* interface (name of interface) : interface to run HotSpot on
* addresses-per-mac (integer / unlimited; default: 2) : number of IP addresses allowed to be bind with the MAC address, when multiple HotSpot clients connected with one MAC-address
* profile (name; default: default) - HotSpot server default HotSpot profile, which is located in /ip hotspot profile
ip hotspot profile
HotSpot profile used for common settings of the HotSpot server, which are applied for all users connected to HotSpot server. Profile allows to specify HotSpot server login options, whether to use RADIUS server for clients and much more.
* name (text) : HotSpot profile name or identifier
* dns-name (text) : DNS name of the HotSpot server, it appears as the location of the login page in the web browser. Fully qualified domain name is required, like www.myhotspot.com not www.hotspot
* hotspot-address (IP address; default: 0.0.0.0) : IP address for the HotSpot server ?!
* html-directory (text; default: hotspot) : HotSpot HTML pages are stored in the particular directory, for example login page, status page, etc. To change HotSpot login page, connect to the router with FTP and download hotspot folder contents. Basic HTML skills required to change HotSpot login page.
* http-cookie-lifetime (time; default: 3d) : HTTP cookie validity time, the option is related to cookie HotSpot login method
* http-proxy (IP address; default: 0.0.0.0) : address of the proxy server for HotSpot service, when default value is used all request are resolved by the local /ip proxy
* login-by (multiple choice: cookie / http-chap / http-pap / https / mac / mac / trial; default: http-chap, cookie) : used HotSpot authentication method
o cookie - may only be used with other HTTP authentication method. HTTP cookie is generated, when user authenticates in HotSpot for the first time. User is not asked for the login/password and authenticated automatically, until cookie-lifetime is active
o http-chap - login/password is required for the user to authenticate in HotSpot. CHAP challenge-response method with MD5 hashing algorithm is used for protecting passwords.
o http-pap - login/password is required for user to authenticate in HotSpot. Username and password are sent over network in plain text.
o https - login/password is required for user to authenticate in HotSpot. Client login/password exchange between client and server is encrypted with SSL tunnel
o mac - client is authenticated without asking login form. Client MAC-address is added to /ip hotspot user database, client is authenticated as soon as connected to the HotSpot
o trial - client is allowed to use internet without HotSpot login for the specified amount of time
* mac-auth-password (text) : used together with MAC authentication, field used to specify password for the users to be authenticated by their MAC addresses. The following option is required, when specific RADIUS server rejects authentication for the clients with blank password
* nas-port-time (text; default: wireless-802.11) : NAS-Port-Type value to be sent to RADIUS server, NAS-Port-Type values are described in the RADIUS RFC. This optional value attribute indicates the type of the physical port of the HotSpot server
* radius-accounting (yes / no; default: yes) : send RADIUS server accounting information for each user, when yes is used
* radius-default-domain (text) : default domain to use for RADIUS requests. Allows to use separate RADIUS server per /ip hotspot profile
* radius-interim-update (time / received) : how often to send accounting updates. When received is configured, interim-time is used from RADIUS server
* radius-location-name (text) : RADIUS-Location-Id to be sent to RADIUS server. To identify location of the HotSpot server during the communication with RADIUS server. Value is optional and used together with RADIUS server
* smtp-server (IP address; default: 0.0.0.0) : SMTP server address to be used to redirect HotSpot users SMTP requests
* split-user-domain (yes / no; default: no) : Split username from domain name when the username is given in "user@domain" or in "domain\user" format from RADIUS server
* ssl-certificate (name / none; default: none) : name of the SSL certificate on the router to use only for HTTPS authentication
* trial-uptime (time / time; default: 30m / 1d) : used only with trial authentication method. First time specifies, how long trial user identified by MAC address can use access to public networks without HotSpot authentication. Second time specifies amount of time, that has to pass that user is allowed to use trial again
* trial-user-profile (name; default: default) : specifies ip hotspot user profile for trial users
* use-radius (yes / no; default: no) : whether to use RADIUS server of authorization and accounting. When yes RADIUS server should be added to radius menu, firstly local ip hotspot user database is used, only then information is sent to RADIUS server
to be continued....
Mikrotik Hotspot 1
Labels: mikrotikHotSpot
The MikroTik HotSpot Gateway provides authentication for clients before access to public networks .
HotSpot Gateway features:
* different authentication methods of clients using local client database on the router, or remote RADIUS server;
* users accounting in local database on the router, or on remote RADIUS server;
* walled-garden system, access to some web pages without authorization;
* login page modification, where you can put information about the company;
* automatic and transparent change any IP address of a client to a valid address;
ip hotspot setup
The simplest way to setup HotSpot server on a router, by
/ip hotspot setup
Router will ask you the questions, when successfully finished default configuration will be added for HotSpot server. Once your run setup command, you will be asked for the particular questions,
* hotspot interface (name of the interface) : interface name to run HotSpot on. To run HotSpot on bridge interface, make sure public interfaces are not included to the bridge
* local address of network (IP address; default: 10.5.50.1/24) : HotSpot gateway address
* masquerade network (yes / no; default: yes) : Whether to masquerade HotSpot network, when yes rule is added to /ip firewall nat with action=masquerade
* address pool of network (name) : Address pool for HotSpot network, which is used to change user IP address to a valid address. Useful for providing network access to mobile clients that are not willing to change their networking settings
* select certificate (none / import-other-certificate) : choose SSL certificate, when HTTPS authorization method is required
* ip address of smtp server (IP address; default: 0.0.0.0) : IP address of the SMTP server, where to redirect HotSpot's network SMTP requests (25 TCP port)
* dns servers (IP address) : DNS server addresses used for HotSpot clients, configuration taken from /ip dns menu of the HotSpot gateway
* dns name (name; default: blank) : domain name of the HotSpot server, full quality domain name is required, for example www.example.com
* name of local hotspot user (name; default: admin) : username of one automatically created HotSpot user, added to /ip hotspot user
* password for the user (name) : password for automatically created HotSpot user
to be continue.....
Setting up a basic MikroTik hotspot
Labels: mikrotikMikrotik RouterOS includes an excellent hotspot solution. Read on for details on getting a basic hotspot going using RouterOS on any standard x86 PC hardware or a RouterBOARD.
The RouterOS hotspot solution is very powerful and only the very basics of the solution are covered here; just enough to get you started.
Introduction
This article assumes you want to set up a basic hotspot as shown in the diagram below. If you have a DNS server integrated into your router the same rule applies, just use the router IP for your DNS server as well.
To help get you started MikroTik now include a combined RADIUS server and simple web administration package for RouterOS called the User Manager. This provides a much simpler means of user administration then the command line or Winbox. The User Manager package is included standard with all versions of RouterOS from about 2.9.35 onwards.
Advanced users might wish to provide their own RADIUS server, however this is outside the scope of this article.
Getting the Hotspot to Work
First of all you will need to have a copy of RouterOS. You can purchase a license or download a 24-hour trial from Mikrotik. RouterBOARDs also usually come with RouterOS pre-licensed and installed. You will also need a computer with at least a 100MHz CPU, 32MB RAM and an IDE hard disk, or a RouterBOARD. Either method you choose will need a compatible wireless card and Ethernet adapter, or two Ethernet adapters with one connected to a standard wireless access point. You should check your hardware against the RouterOS compatibility list.
If you are installing RouterOS for the first time, download the ISO image from Mikrotik and burn it to CD. Note that installation of RouterOS will completely wipe the contents of the hard disk! Boot the PC off this CD and install the following packages:
* System
* DHCP
* Wireless
* Hotspot
* Proxy
* User Manager (optional)
* Security (optional - recommended)
* Advanced tools (optional)
Now to get started. Log onto the PC as admin with no password. If this box intended for deployment, change set a password by typing in password at the prompt. Change the hostname by typing in name.
Assign an IP address to each interface. As this is going to be set up as a router, they will need to be on a different subnet. Substitute wlan1 with ether2 if you have a separate access point.
[admin@Mikrotik] > ip address add address=192.168.24.3/24 interface=ether1
[admin@Mikrotik] > ip address add address=192.168.30.1/24 interface=wlan1
Now we need to add a default route to the IP of the internet router.
[admin@MikroTik] > ip route add gateway 192.168.24.1
Enable the wireless interface and set it to run as an access point as below. If you have an access point instead, ignore the command below, make sure it is running with no security enabled, use a suitable SSID and channel and change its admin password.
[admin@Mikrotik]> interface wireless set wlan1 ssid="My HotSpot" band=2.4ghz-b mode=ap-bridge
Run the hotspot setup as below. Substitute the values in italics to suit your network. The user account bears no relation to the admin account and is used for the hotspot service only. You may also need to add a host record to your DNS server for the hostname of the hotspot box. Make sure the address pool does not conflict with any devices using static IPs, such as access points.
[admin@MikroTik] > ip hotspot setup
hotspot interface: wlan1
local address of network: 192.168.30.1/24
masquerade network: yes
address pool of network: 192.168.30.2-192.168.30.99
select certificate: none
ip address of smtp server: 0.0.0.0
dns servers: 192.168.24.2
dns name: hotspot.mydomain.net (or leave this blank)
name of local hotspot user: user
password for the user: password
That’s the guts of it there. Fire up your laptop, associate to the network and try to access a web page. You should be redirected to the hotspot login page instead where you can enter the user credentials you set up earlier. Click the thumbnails for a full view of the default page.
You should now be able to access the web normally and a pop-up window will display your connection time and data usage as you go.
Bear in mind I have left out the certificate so usernames and passwords will be sent as plain text. If you intend on deploying the hotspot, you should install a certificate on it and set up SSL to protect account data from being sniffed.
Setting up User Manager
The User Manager is a nice and simple web administration for setting up user account for the MikroTik hotspot and other services. It can be hosted on either the same box as the hotspot or located in a separate box on the same local network. One User Manager package can control multiple hotspots.
Before getting the User Manager set up, check for any existing hotspot account and remove them. To do this, run the following command:
[admin@MikroTik] > ip hotspot user print
Flags: X - disabled, D - dynamic
# SERVER NAME ADDRESS PROFILE UPTIME
0 fred default 0s
If any items are listed (in this case bob), run the following command to remove them:
[admin@MikroTik] > ip hotspot user remove 0
You can delete multiple items at the same time, simply separate each item number with a comma.
To get the User Manager working we first need to add a customer login. This is used to access the UM web administration. Make sure you substitute the values in italics to suit.
[admin@MikroTik] > tool user-manager customer add login=hs_admin password=password
Now we need to add the hotspot as a RADIUS client to the user manager. This is done under the user manager router section. The shared secret can be any string of text and should be reasonably long and complex. If you are setting the user manager up on the same box as the hotspot, use 127.0.0.1 for the IP address.
[admin@MikroTik] > tool user-manager router add ip-address=hotspot-ip shared-secret=12345 subscriber=hs_admin
In return, we need to set up the hotspot to use RADIUS for user authentication. First this involves creating a RADIUS client to communicate with the UM. Remember that if you have both services on the same box, the IP address should be set to 127.0.0.1. The secret should be the same as you set up above.
[admin@MikroTik] > radius add service=hotspot address=ip-address secret=12345
Now we tell the hotspot itself to use a RADIUS client. First bring up a list of hotspot profiles:
admin@MikroTik] > ip hotspot profile print
Locate the profile in use and type the following command where 1 is the number of the profile to configure:
[admin@MikroTik] > ip hotspot profile set 1 use-radius=yes
Now we are done with configuration. Browse to http://router-ip/userman where router-ip is the IP address of the box you are configuring UM on. Login using the customer username and password created earlier.
Click on the User menu and select Add. Enter in a username, password and any other details you wish. You can limit the speed the client can access the internet by selecting the Rate limits checkbox and typing in a suitable speed (e.g. for a flat 128kBps download/64kBps upload speed limit simply type in 128k in the RX field and 64k in the TX field).
Click Add and you should be able to now access the hotspot using the username and password you specified. If you want to generate a printable ticket for the users you set up, click on the Users link, select the users to make a ticket for, click Generate and select the number of tickets per page.
======
source : http://www.marlwifi.org.nz
TIPS : How To Find Cheap DSL Connection
Today, there are different types of low-cost DSL Internet connections on the market with different rates depending on the needs of users, for example, ADSL, R-ADSL, HDSL, SDSL, and VDSL. The monthly rate of ADSL depends on your connection speed and download or upload traffic allows. DSL provider, data traffic up to 1 GB database from 128 kbit / s connection to the Internet. But if you want to play online, download audio or video files and data retrieval, and then allowed the movement (1 GB) per month with DSL providers will be the biggest problem for you. Visit the market for the best rate DSL-May, some providers offer DSL up to 2 GB or more traffic allows, with the same rates. Almost all of the provider of DSL service in the month compared with the same rhythm, but you can use your DSL connection is the cost of many computers using any Internet-sharing software. Typically, DSL connection is available in the unrestricted use, but you can also buy a connection for some time, or packages per hour at the monthly cost. Finally, you can ask your DSL share of the costs of business connection to the Internet from your home if your business or home nearby.
Read More......
About DSL Modem
Labels: NetworkModem, which is used to transmit and receive data and digital phone line, for example, ISDN and DSL modems. These modems send and receive digital signals and digital lines. These modems are available in the market with USB and Ethernet ports only team with a USB modem, is the best option, but if you want to share the DSL connection in more than two computers, then you should try the modem to Ethernet-port. DSL modems use digital signal because these modems convert the digital signal to analog. DSL modems provide high speed Internet up to 24 Mbps downstream and 3.5 Mbps upstream. Price range of DSL modems from $ 60 to $ 225, but some DSL providers offer more advantages you have with ADSL connections in competition with other suppliers of services, like free modem with a year warranty. If you want your DSL is working with good speed and error-free is available, make sure that there is no tower of a telephone line and modem line. Your DSL modem to the heat of May, freezes and slow, if your DSL modem continuously for 24 hours, and then restart to solve this problem.
Read More......
