Virtual Private Network (VPN) Project Report

Wireless Communication
Introduction
The term "wireless" has become a generic and all-encompassing word used to describe communications in which electromagnetic waves or RF (rather than some form of wire) carry a signal over part or the entire communication path.
It is the transfer of information over a distance without the use of electrical conductors or "wires".
The distances involved may be short (a few meters as in television remote control) or long (thousands or millions of kilometers for radio communications). When the context is clear, the term is often shortened to "wireless". Wireless communication is generally considered to be a branch of telecommunications.

Examples
It encompasses various types of fixed, mobile, and portable two-way radios, cellular telephones, personal digital assistants (PDAs), and wireless networking. Other examples of wireless technology include GPS units, garage door openers and or garage doors, wireless computer peripherals ( like mice, keyboards and headsets ), satellite television, wireless gaming and cordless telephones.

Modes of Wireless Communication
Wireless communication can be via:
• radio frequency communication,
• microwave communication, for example long-range line-of-sight via highly directional antennas, or short-range communication, or
• infrared (IR) short-range communication, for example from remote controls or via Infrared Data Association (IrDA).

Applications
Applications may involve point-to-point communication, point-to-multipoint communication, broadcasting, cellular networks and other wireless networks.
Download Full Project Report

Project Report on Visual Basic

OBJECTIVE & SCOPE OF PROJECT
The main objective of this project is that to minimize the handwritten work to small as possible and provide user an automated environment in which he/she can work efficiently and also in user friendly environment.

The scope of the project generally lies at the places like schools , colleges & universities where faculties attendance maintenance are major requirement because on basis of this the salary of person can be calculated, this project is on very small basis means to say not on big scale we can implement it on bigger scale in form of maintaining student attendance ,apart from this the same concept can be applied in various business firms (public and private) which are fully automated with computer and the company has to maintain the regularity of employers also at these places it is not possible to maintain large records files which require a separate room for storage so to avoid this we made this software in which database are maintained which cover very less space then the space taken by files etc.

THEORETICAL BACKGROUND
Why VB (Visual Basic)?
Visual basic is one of the most popular programming languages in the market today. Microsoft has positioned it to fit multiple purposes in development. The language ranges from light weight vb script programming, to application specific programming with vb for applications

What is Visual Basic?
The visual part refers to the method used to create GUI.Rather then writing numerous lines of code to describe the appearance and location of interface elements , we simplify add rebuilt objects into place on screens.

VB is high level programming language evolved from earlier DOS version called BASIC. VB is event driven programming VB programs are made up of many sub programs , each has its in own program codes and each can be executed independently and at the sane time each can be linked in one way or another.

VB is designed to deploy applications across the enterprise and to scale of any size needed the ability to develop object mode is databases integration, server components, and Internet/Intranet applications provides an extensive range of capabilities and tools of the developer. In particular VB lets us to add menus, textboxes, command buttons, option buttons, check boxes, scroll bars, and file & directory boxes to blank windows. We can communicate with other window applications and perhaps most importantly we will have an easy method to let users’ control and access database.
Download Full Project Report

Voice Over IP (VOIP) Project Report

LIST OF CONTENTS
1. Introduction: VoIP
2. VoIP Architecture and Protocol Stack
3. VoIP configurations
4. Requirements, Availability, and Service Limitations
5. Introduction: Session Initiation Protocol (SIP)
6. Short History of SIP
7. Overview of Services Provided by SIP Servers
8. SIP Enabled Network
9. Threats and Risks
10. How to Protect Against Risks
11. References

Download Full Project Report

Cooperative DNS Project Report

INTRODUCTION
Translation of names to network addresses is an essential predecessor to communication in networked systems. The Domain Name System (DNS) performs this translation on the Internet and constitutes a critical component of the Internet infrastructure. While the DNS has sustained the growth of the Internet through static, hierarchical partitioning of the namespace and wide-spread caching, recent increases in malicious behavior, explosion in client population, and the need for fast reconfiguration pose difficult problems. The existing DNS architecture is fundamentally unsuitable for addressing these issues. The foremost problem with DNS is that it is susceptible to denial of service (DoS) attacks. This vulnerability stems from limited redundancy in name servers, which pro-vide name-address mappings and whose overload, failure or compromise can lead to low performance, failed lookups and misdirected clients. Approximately 80% of the domain names are served by just two name servers and a surprising 0.8% by only one. At the network level, all servers for 32% of the domain names are connected to the Internet through a single gateway, and can thus be compromised by a single failure. The top levels of the hierarchy are served by a relatively small number of servers, which serve as easy targets for denial of service attacks. A recent DoS attack on the DNS crippled nine of the thirteen root servers at that time, while another recent DoS attack on Microsoft’s DNS servers severely affected the availability of Microsoft’s web services for several hours .DNS name servers are easy targets for malicious agents, partly because approximately 20% of name server implementations contain security flaws that can be exploited to take over the name servers. Second, name-address translation in the DNS incurs long delays. Recent studies have shown that DNS lookup time contributes more than one second for up to 30% of web object retrievals. The explosive growth of the namespace has decreased the effectiveness of DNS caching. The skewed distribution of names under popular domains, such as .com, has attended the name hierarchy and increased load imbalance. The use of short timeouts for popular map-pings, as is commonly employed by content distribution net-works, further reduces DNS cache hit rates. Further, manual configuration errors, such as lame delegations, can introduce latent performance problems. Finally, widespread caching of mappings in the DNS prohibits fast propagation of unanticipated changes. Since the DNS does not keep track of the locations of cached map-pings, but relies on timeout-based invalidations of stale co-pies, it cannot guarantee cache coherency. Lack of cache coherency in the DNS implies that changes may not be visible to clients for long durations, effectively preventing quick service relocation in response to attacks or emergencies.
Fresh design of the legacy DNS provides an opportunity to address these shortcomings. A replacement for the DNS should exhibit the following properties.

High Performance: Decouple the performance of DNS from the number of name servers. Achieve lower latencies than legacy DNS and improve lookup performance in the presence of high loads and unexpected changes in popularity
Resilience to Attacks: Remove vulnerabilities in the system and provide resistance against denial of service attacks through decentralization and dynamic load balancing. Self-organize automatically in response to host and network failures.
Fast Update Propagation: Enable changes in name-address mappings to quickly propagate to clients. Support secure delegation to preserve integrity of DNS records, and prohibit rogue nodes from corrupting the system.
This paper describes Cooperative Domain Name System (CoDoNS), a backwards-compatible replacement for the legacy DNS that achieves these properties. CoDoNS com-bines two recent advances, namely, structured peer-to-peer overlays and analytically informed proactive caching. Structured peer-to-peer overlays, which create and maintain a mesh of cooperating nodes, have been used previously to implement wide-area distributed hash tables (DHTs). While their self organization, scalability, and failure resilience provide a strong foundation for robust large-scale distributed services, their high lookup costs render them inadequate for demanding, latency-sensitive applications such as DNS]. CoDoNS achieve high lookup performance on a structured overlay through an analytically-driven proactive caching layer. This layer, called Beehive, automatically replicates the DNS mappings throughout the network to match anticipated demand and provides a strong performance guarantee. Specially, Beehive achieves targeted average lookup latency with a minimum number of replicas. Overall, the combination of Beehive and structured overlays provides the requisite properties for a large scale name service, suitable for deployment over the Internet.
Download Full Project Report

Project Report on HTML

INTRODUCTION
OVERVIEW:
This is dynamic website which gives all the information about a book store, helps the user to find books of their choice with little bit of introduction about the book with ease.

The website has been developed in HTML, JSP and HTML is a markup language which is in reality a backbone of any site, every site can’t structured without the knowledge of html.

If we make our web page only with the help of html, than we can’t add many of the effective features in a web page, for making a web page more effective we use various platforms such as JSP.

So here we are using these entire features to make our web pages more effective as well as efficient.
And to make our web pages dynamic we are using JSP here.

HTML (HYPERTEXTMARKUP LANGUAGE)
HTML stands for Hypertext Markup Language, and it is the language in which, until recently, virtually all Web pages were written. Now, don’t break out in hives when you hear the word “language.” You don’t need complex logical or mathematical formulas to work with HTML, and you don’t need to think like a programmer to use it. Computer programmers must think through the tasks that they want their programs to perform, and then develop an elaborate (and usually complicated) series of instructions to tell the computer what to do. Although you do need to do some thinking and planning when you use HTML, it is not nearly that difficult.

So, how does Hypertext Markup Language work?
Hypertext refers to the way in which Web pages (HTML documents) are linked together. When you click a link in a Web page, you are using hypertext. It is this system of linking documents that has made the World Wide Web the global phenomenon it has become.

Markup Language describes how HTML works. With a markup language, you simply “mark up” a text document with tags that tell a Web browser how to structure it. HTML originally was developed with the intent of defining the structure of documents (headings, paragraphs, lists, and so forth) to facilitate the sharing of scientific information between researchers. All you need to do to use HTML is to learn what type of markup to use to get the results you want

FOUR KEY CONCEPTS
The first step toward understanding and working with HTML is learning the basic terms that describe most of the functions of this language. You will come across these terms repeatedly as you use HTML and if you understand them, you will have progressed a long way toward comprehending HTML, not to mention XHTML.

ELEMENTS
All HTML pages are made up of elements. Think of an element as a container in which a portion of a page is placed. Whatever is contained inside the element will take on the characteristics of that element. For example, to identify a heading on a page, you would enclose it in a heading element

. If you want to create a table, you put the table information inside the table element . To construct a form, you need the form element

.

TAGS
Often, you’ll find the terms element and tag used interchangeably. It’s fairly common, but not strictly accurate. An element is made up of two tags: an opening tag and a closing tag. Although it might seem somewhat picky to make this distinction, when you begin to work with XHTML (Extensible Hypertext Markup Language), it will be a very important difference to remember. If you get into the habit of distinguishing elements and tags from the very beginning, you’ll save yourself some confusion down the line.

All tags are constructed the same way. The tag begins with a “less than” sign (<), then the element name, followed by a “greater than” sign (>). For example, an opening tag for the paragraph element would look like this:

. The only difference in a closing tag is that the closing tag includes a slash (/) before the element name:

. Your content goes between the tags. A simple paragraph might look like this:

This is an HTML paragraph.

Some elements do not use closing tags because they do not enclose content. These are called empty elements. For example, the line break element
does not require a closing tag. In the case of empty elements, add a closing slash after the element name, like this:
. When a browser sees the slash, it will recognize the element as one that does not need a separate, closing tag.
Download Full Project Report

Grid Computing Project Report

Introduction to Grid Computing
In today's pervasive world of needing information anytime and anywhere, the explosive Grid Computing environments have now proven to be so significant that they are often referred to as being the world's single and most powerful computer solutions.. As a matter of fact the complexity and dynamic nature of industrial problems in today's world are much more intensive to satisfy by the more traditional, single computational platform approaches. Grid computing enables the virtualization of distributed computing and data resources such as processing, network bandwidth and storage capacity to create a single system image, granting users and applications seamless access to vast IT capabilities. Just as an Internet user views a unified instance of content via the Web, a grid user essentially sees a single, large virtual computer.

Grid computing is concerned with "coordinated resource sharing and problem solving in dynamic, multi-institutional virtual organizations." The key concept is the ability to negotiate resource-sharing- arrangements among a set of participating parties (providers and consumers) and then to use thee resulting resource pool for some purpose..

At its core, grid computing is based on an open set of standards and protocols - e.g., Open Grid Services Architecture (OGSA) - that enable communication across heterogeneous, geographically dispersed environments. With grid computing organizations can optimize computing and data resources, pool them for large capacity workloads, share them across networks and enable collaboration.

GRID COMPUTING
Computational Grid is a collection of distributed, possibly heterogeneous resources which can be used as an ensemble to execute large-scale applications

"Grid" computing has emerged as an important new field, distinguished from conventional distributed computing by its focus on large-scale resource sharing, innovative applications, and, in some cases, high-performance orientation. In this article, we define this new field.

Grid computing is a very hot topic these days. Many major IT vendors are promoting and announcing "grid," "on-demand," "adaptive infrastructure" or some closely related initiative. It's likely the buzz will only increase as these firms reorient themselves to this emerging market.

Though it may seem to be yet another "next big thing," grid computing is in fact. bringing real benefits to commercial enterprises. That's why enterprises and the software vendors that serve the analytics/business intelligence (BI) sectors are now partnering with the 'technology specialists in this space - or pushing initiatives of their own. It's particularly relevant in today hyper-competitive yet cost constrained times when companies truly do need to do more with less.

A computational grid is a hardware and software infrastructure that provides dependable, consistent, pervasive, and inexpensive access to high-end computational capabilities. "

grid computing is based on the concept of coordinated shared use of computers grid computing is a way to create a virtual supercomputer by connecting large numbers of pcs in different locations over a shared network grid computing is applying the resources of many computers in a network to a single problem at the same time.

Grid computing is concerned with "coordinated resource sharing and problem solving in dynamic; multi-institutional virtual organizations." The key concept is the ability to negotiate resource-sharing arrangements among a set of participating parties (providers and consumers) and then to use the resulting resource pool for some purpose. We noted: "The sharing that we are concerned with is not primarily file exchange but rather direct access to computers, software, data, and other resources, as is required by a range of collaborative problem-solving and resource-brokering strategies emerging in industry, science, and engineering. This sharing is, necessarily, highly controlled, with resource providers and consumers defining clearly and carefully just what is shared, who is allowed to share, and the conditions under which sharing occurs. A set of individuals and/or institutions defined by such sharing rules form what we call a virtual organization."

A Grid Checklist I suggest that the essence of the definitions above can be captured in a simple checklist, according to which a Grid is a system that:
1. coordinates resources that are NOT subject to centralized control
2. uses standard, open, general purpose protocols and interfaces
3. delivers non-trivial qualities of service

Expansion:
• Coordinates resources that are not subject to centralized control - (A Grid integrates and coordinates resources and users that live within different control domains for example, the user's desktop vs. central computing; different administrative units of the same company; or different companies; and addresses the issues of security, policy, payment, membership, and so forth that arise in these settings. Otherwise, we are dealing with a local management system.).

• Using standard, open, general-purpose protocols and interfaces - (A Grid is built from multi-purpose protocols and interfaces that address such fundamental issues as authentication, authorization, resource discovery, and resource access. As I discuss further below, it is important that these protocols and interfaces be standard and open. Otherwise, we are dealing with an application-specific system.).

• To deliver nontrivial qualities of service - (A Grid allows its constituent resources to be used in a coordinated fashion to deliver various qualities of service, relating for example to response time, throughput, availability, and security, and/or co¬-allocation of multiple resource types to meet complex user demands, so that the 'utility of the combined system is significantly greater than that of the sum of its parts.)
Download Full Project Report