A Multidisciplinary Project Report

8/9/2019 A Multidisciplinary Project Report

1/17

A MULTIDISCIPLINARY

PROJECT REPORT

ONLOCAL AREA

NETWORK(LAN)

UNDER THE GUIDANCE OF

SIR HIMANSU HALOI

&

MADAM BANANI DAS DEKA

(FACULTY OF ITTC OF ICAI)

SUBMITTED IN PARTIAL FULFILLMENT OF THE

REQUIREMENTS FOR QUALIFYING 100 HOURS IT

TRAINING

COMPUTER DEPARTMENT

INSTITUTE OF CHARTERED ACCOUNTANTS OF

INDIA

PANBAZAR, GUWAHATI


2/17

SUBMITTED BY .

-CHINMAY JAIN.

REG.NO.- ERO-0147925

INFORMATION TECHNOLOGY CENTRE

GUWAHATI BRANCH OF EIRC(The Institute Of Chartered Accountants Of India)

3rd Floor, The Institution of Engineers (India)

Panbazar Over bridge, Guwahati: 781001(Assam)

CERTIFICATE

This is to certify that the work presented in the

project is allotted toCHINMAY JAIN,Registration No: ERO-0147925as a part for the

fulfillment of the guidelines lay down by the Institute of Chartered Accountants of India

(I.C.A.I ) regarding the multi-disciplinary projectand partial fulfillment of CAITTComputerTraining Programme of 100 hours.


3/17

Authorized Signatory. .

DATED: 25/02/2010

PLACE: GUWAHATI (ASSAM)

ASSURANCE

I, hereby assure that this project provided to us byInstitute of Chartered Accountants of

India

for

100 hours InformationTechnology Trainingis an authentic work carriedon by me and has not been copied from any other source

other than Internet for necessary elements used in project.

I sincerely thank and express my gratitudetowards Sir Himanshu Haloi and MadamBanani Das Deka, who has devoted their valuable


4/17

time for providing me with the requisite knowledge and

training for preparing the project.

Resemblance of this project with any project shall be

purely co-incidental.Name:CHINMAY JAIN

Reg. No: Ero-

0147925

PREFACE

Chartered Accountants in the present scenario work in an ever-

changing environment. Computerized methods and systemreplace manual operations which demand and in-depth and

critical examination of the processes and procedure.

The Chartered Accountant role is indispensable right from

designing of the system till its successful implementation and

checking of its efficiency. Hence, the Chartered Accountant hasto equip himself of the knowledge of the various systems and

their working. To help the budding professionals acquire such

knowledge, the Chartered Accountant course contains

compulsory computer training program.


5/17

Computers have made great inroad in our everyday life and

thinking. They are to put to use for all sorts of applications

ranging from complex calculations in the field or frontlineresearch, engineering simulations down to teaching, printing

books and recreational games. The cases with which computers

can process data store and retrieve it painlessly have made

them inevitable in office and business environments, so much

that a common man today, at least in any developed society,

finds it difficult to survive without computers awareness and

with computer illiteracy.

-CHINMAY JAIN

ACKNOWLDGEMENT

AT THE VERY OUTSET OF THIS MULTIDISCIPLINARY

PROJECT, I WOULD LIKE TO EXPRESS MY SINCERE

GRATITUDE AND THANKS TO SOME VERY IMPORTANT

PEOPLE WHOM I OWE THIS PROJECT AND WITHOUT

WHOM THIS PROJECT WOULDNT HAVE REACHED ITS

FINAL STAGE.


6/17

THESE INCLUDE OUR VERY HONORABLE FACULTY

MEMBERS MR. HIMANSU HALOI AND MRS. BANANI DAS

DEKA AND Also MY FELLOW FRIENDS WHOSE

GUIDANCE AND SUPPORT PLAYED A CENTRAL ROLE IN

THE COMPLETION OFTHIS PROJECT.

I SHALL ALWAYS BE INDEBTED TO THEM FOR THEIR

KIND SUPPORT AND VALUABLE TIME.

With Regards

-CHINMAY JAIN


7/17

i

Table of Contents

CHAPTER 1: INTRODUCTION ............. ............. ............. ............. .............. ............. ............. ............. 2

1.1.PURPOSE........................................................................................................................................ 2

1.2.SCOPE ........................................................................................................................................... 2

1.3.GLOSSARY..................................................................................................................................... 31.4.REFERENCES .................................................................................................................................. 4

1.5.OVERVIEW OF DOCUMENT ............................................................................................................. 4

CHAPTER 2: TEST PLAN ............ ............. ............. ............. .............. ............. ............. ............. ........... 5

2.1.SCHEDULES AND RESOURCES ......................................................................................................... 5

2.2.TEST RECORDING........................................................................................................................... 5

2.3.TEST REPORTING ........................................................................................................................... 5

2.4.STATIC TESTING ............................................................................................................................ 6

CHAPTER 3: VERIFICATION TESTING........................ ............. .............. ............. ............. ............. 7

3.1.UNIT TESTING................................................................................................................................ 7

3.1.1. Wireless Access Points ........................................................................................................... 7

3.1.2. RADIUS ................................................................................................................................ 73.1.3. M0n0wall .............................................................................................................................. 8

CHAPTER 4: VALIDATION TESTING ............ ............. ............. ............. .............. ............. ............. .. 9

4.1.SYSTEM TESTING ........................................................................................................................... 9

4.2.ACCEPTANCE AND BETA TESTING................................................................................................... 9

APPENDIX A: INDEX ............ .............. ............. ............. .........ERROR! BOOKMARK NOT DEFINED.


8/17

2

Chapter 1: Introduction

1.1. PurposeThe purpose of this document is to overview the major phases of the testing process from unit

testing to system testing, including validating requirements and acceptance testing. This document will

list tested items organized by phases, following the structure of the System Design. This document will

show requirements traceability. This document will show the testing schedule with resource allocation,

test recording procedures, and hardware and software requirements.

The intended audience of this document is a network administrator who wishes to mimic such a

project. This will allow an administrator to skip the hardships that I encountered. By reading this

document and performing activities that I performed, an administrator need not re-invent the wheel.

1.2. ScopeThere are five major testing phases of the process. The first phase is unit testing. Unit testing is

the testing of individual programs. This project, however, is not made up of programs. It is made up of

networking tools. This document will discuss how the different components were tested.

The second phase is module testing. Module testing is testing performed on a subset of a

program. This is relatively not applicable for this project, since object oriented programming was not

used.

The third phase is subsystem testing. Subsystem testing is testing performed on different

sections of the system. Subsystem testing tests how different programs interact. Because there are no

programs in this project, subsystem testing will be tested by how the different networking tools interact.

The fourth phase is system testing. System testing is testing the entire system of programs.

Once again, because this project contains no coding, system testing will be defined as testing the entire

verification system by using false data and mock users. It will test how all different tools use each other.


9/17

3

The fifth phase is acceptance testing. Acceptance testing is conducting any tests required by the

user. This will be done when the wireless access points are in the ceiling and all clients are able to log in

to the captive portal properly. At that time, the project will be operational. At that time, the ultimate

client of this product will recommend further possibilities.

1.3. Glossary

Captive Portal

A technique that forces a HTTP client on a network to see a special Web page

for authentication before surfing the Internet. This is done by intercepting

all HTTP traffic, regardless of address, until the user is allowed to exit the

portal.

DHCP

Dynamic Host Control Protocol. It assigns dynamic IP addresses to devices

on a network, causing a device to possibly have a different IP address every

time it logs on to the network.

Gateway A Computer on a network that servers as an entrance to another network

NAT

Network Address Translation. It enables a local area network to use one set

of private IP addresses for internal traffic and a public address for external

traffic.

NISNetwork Information System. It allows a group of machines to share a

common set of configuration files.

RADIUS

Remote Authentication Dial-In User Service. When you dial in to an ISP, youmust enter your username and password, which is passed to a RADIUS

server, which checks that the information is correct, and then authorizes

access to the ISP system.

RouterA computer that forwards data across networks, connected to at least two

networks


10/17

4

SSID

Service Set Identifier. A unique identifier attached to packets sent over a

wireless local area network. The SSID differentiates one WiLAN from

another, so all access points and all devices attempting to connect to a

specific WiLAN must use the same SSID.

1.4. ReferencesHassell, Jonathan. RADIUS. California: OReilly Associates, Inc., 2001.

Kasper, Manuel. m0n0wall. 2004. The m0n0wall project. 29 September 2004 .

Stair, Ralph M. and George W. Reynolds. Principles of Information Systems.

Massachusetts: Course Technology, 2001.

Whitten, Jeffery L., Lonnie D. Bentley, and Kevin C. Dittman. Systems Analysis &

Design Methods, Sixth Edition. New York: McGraw-Hill/Irwin, 2001.

1.5. Overview of DocumentThe next chapter in this paper will discuss the test plan, including the schedules and resources,

the test recording, test reporting, and static testing. The third chapter will discuss verification testing,

including unit testing and integrative testing. The fourth chapter will discuss validation testing, including

system testing and acceptance and beta testing.


11/17

5

Chapter 2: Test Plan

2.1. Schedules and ResourcesUnit testing will begin the week of November 1, 2004. Unit testing will be performed by the

system administrator. Subsystem testing will begin the week of November 8. Subsystem testing will be

performed by the system administrator. System testing will begin the week of November 15. System

testing will be performed by the system administrator. Acceptance testing will occur the week of

November 22. Acceptance testing will be performed by the user group (the students and faculty of the

Department of Computing Sciences). For each phase of testing, the only resource that is necessary is a

wireless laptop computer with wireless connectivity.

2.2. Test RecordingItem to be tested:

Tester:

Test data:

Expected results:

Date tested:

Person with responsibility to retest:

2.3. Test ReportingTested Unit Pass/Fail Errors Re-test Date


12/17

6

2.4. Static TestingAfter all the machines have been configured, every page and every file of every system will be

proofread to ensure that the alterations will not affect the current running network. This will occur the

week of October 25.


13/17

7

Chapter 3: Verification Testing

3.1. Unit Testing

3.1.1. Wireless Access Points

For this project, each wireless access point will be tested as it is configured individually. It will

originally be connected directly to the Internet and assign an IP address and will not filter packets. If

after the initial configuration, a user can connect to the wireless access point, obtain a 192.168.x.x IP

address, and can connect to any public computer on the World Wide Web. This testing will be

performed by the system administrator and will only ensure that the wireless access point is capable of

passing information from its wireless interface to its WAN interface.

3.1.2. RADIUS

For this project, a RADIUS server will be configured and tested on a test network by the system

administrator. This test will require any computer with an Internet connection. For this project

FreeRADIUS 1.0.1 will be used. Once installed and configured, a client must be added to the file

/usr/local/etc/raddb/clients.conf. The client, who once again can be any computer with an Internet

connection, must download the RADIUS testing utility called NTRadPing.


14/17

8

By entering the IP address of the RADIUS server and the port on which it is communicating, the secret

key, a user that is recognized by that machine, and the users password, then that server works properly.

3.1.3. M0n0wall

For this project m0n0wall will be tested by the system administrator. After the setup of

m0n0wall is complete as per the system design documentation, then testing m0n0wall can begin. A

user will be in the range of an antenna of one of the wireless access points. The tester will click theView

Available Networks button. All available networks will show on the screen, including the SSID of this

network.

The tester will click on this network and click connect. After connecting, the laptop will receive a

private IP address on the 192.168.100.0/24 subnet. Even though the machine has an IP address, much

still must be done. The tester cannot access the Internet in any form until he/she opens a Web browser.

When that happens, the captive portal page will appear requesting username and password. If

the tester enters an incorrect username/password pair, an error page appears. That error page explains

that the tester either did not type either the username or the password correctly or that the

username/password pair does not exist, in which case the page directs the tester to the system

administrator to become a user on the network.

If, however, the username and password are accepted via the RADIUS server, m0n0wall begins a

captive portal session for the length of one hour. During this time, the user can access any part of the

Internet, depending on firewall rules. After that one hour has expired, the user has lost his/her captive

portal session and also the DHCP session. The tester would have to perform the steps above to obtain a

new IP address, open the captive portal page, become re-authorized, and continue Web surfing.


15/17

9

Chapter 4: Validation Testing

4.1. System TestingNow that RADIUS, m0n0wall, and one wireless access point integrate and work well together,

testing must be done for roaming. Roaming is an issue because the surface area covered by each

wireless access point is limited. Since a large area is required than one wireless access point can provide

coverage, more than one wireless access points are necessary. All of these wireless access points will

connect to the same 192.168.100.0/24 subnet that m0n0walls PORTAL interface is connected to.

What if a user wants to roam with his/her laptop, to go from one sector to another? It would be

unacceptable for the user to have to start a new DHCP session and a new captive portal session. We

essentially want one network, not four separate networks.

To test roaming, a notebook computer is needed that has a battery. This notebook computer

must also be equipped with wireless networking capabilities. The system administrator would test

roaming by being in the coverage area of one of the wireless antennas. The tester must complete the

steps above to obtain an IP address and go to the captive portal Web page. The tester now must walk to

an area that he/she knows is outside the coverage area, but in the coverage area of another wireless

access point. This might be on the other side of a door or a cinder block wall.

Depending on the wireless network card, the user should not have to begin a new session.

Newer wireless network cards are smart enough to recognize that a new wireless access point and

dynamically adjust. This would allow the user to retain his/her current captive portal and DHCP session.

Older wireless network cards would make you complete the steps above to obtain a new IP address and

enter the captive portal page.

4.2. Acceptance and Beta TestingBeta testing will be done by the system administrator on a weekend when the user community

will not be around to access the wireless network. A few test users must be invited to the beta test. All


16/17

10

users will test their abilities to complete the steps above to obtain an IP address and complete the

captive portal. All users will test their abilities to roam between wireless access points.

Acceptance testing will occur at that moment when the main client for this project will agree

that this has done what it was intended to do. Acceptance testing will be an ongoing process, since new

users will be constantly using this network for the first time.


17/17

11

Documents

A Multidisciplinary Project Report