ProjectsGeek

MULTICAST DNS RESOLVER

The Project aims at implementing a Name Server Switch Plugin to resolve multicast DNS names.

TCP/IP networking has been deployed in many environments and has been especially successful in large networks such as those in universities, corporations, and government agencies. Operating an IP network requires specialized technical skills. So, IP networking has not been especially well suited for smaller networks (such as in the home, in small businesses, for impromptu networks in conference rooms or construction sites), where capable network administration is not feasible.

Multicast DNS (mDNS) is a DNS like protocol. It uses normal DNS Resource Records, transmitted over multicast (at address 224.0.0.251) to a known port (5353).It doesn’t require configuration and administration like DNS.

We implemented the mDNS protocol, main principle of which is to run a DNS-Like Responder and Resolver (Our Name Service Switch) on every host on the network. This responder speaks the normal DNS protocol, but listens on the UDP port 5353 and bind to multicast address 224.0.0.251. The domain name ‘.local.’ is reserved for mDNS hosts and every host on the network chooses its own name. Like the IPv4 addresses in the prefix 169.254/16, these names are link-local to the network on which the host resides.

When a query for a hostname arrives on the multicast socket, the host responds to that same multicast socket so all the hosts in the network get that information and can cache it if necessary.

In addition to resolve name, the multicast DNS can be used in conjunction with DNS SRV records for service discovery.

The benefits of using multicast responses result in a net lowering of overall multicast traffic for example; one multicast response can update the cache on all machines on the network, in addition to other advantages.

Project Name: Multicast DNS Resolver

As networked devices become smaller, more portable, and more ubiquitous, the ability to operate with less configured infrastructure is increasingly important. When mobile nodes (dynamic hosts) want to communicate with one another in Ad-hoc Networks environments such as battle field and public vehicle (e.g., airplane, bus and boat, conference rooms), they need to construct a temporary and infrastructure less network.

Therefore, a new DNS architecture appropriate for this Ad-hoc Networks, where there is no dedicated DNS server, become necessary.

Multicast DNS (mDNS) is a DNS like protocol with a little version, which specifies architecture of name service system. It provides mobile nodes in Ad-hoc Networks with the name-to-address resolution and auto configuration technology, for easy configuration related to IP address autoconfiguration and name service. It uses normal DNS Resource Records, transmitted over multicast (at address 224.0.0.251) to a known port (5353).

So we have implemented the mDNS protocol (using normal libc calls), main principle of this protocol is to run a DNS-Like Responder and Resolver on every host on the network. This responder speaks the normal DNS protocol, but listens on the UDP port 5353 and bind to multicast address 224.0.0.251.

Our system consists of mDNS Responder that works as DNS name server in Ad-hoc Networks and mDNS Resolver that performs the role of DNS resolver for name-to-Address translation.

This project is to develop a web-based software solution for tracking the various opportunities handled by an employee in a company. It gives an insight into the various stages of an opportunity that the employee has worked on with the duration specified and how efficient the employee has been in his performance. A detailed view of all the meetings done with a particular client with respect to the ongoing opportunity is recorded.

It is an online application accessible to the employees to view as a web page where the employees may view personal as well as business details of any employee of the company. It also provides the facility of updating only his or her own details which are stored temporarily in a secondary database and are left for further evaluation by the administrator. The administrator is the only one who has access rights for making changes or updating of business details of an employee n verification by the supervisor of the concerned employee. These changes are finally reflected in the primary copy if they are valid else the data is rolled back. The personal data can be updated directly into the primary database without requiring any verification by the administrator. The final summary report of every employee is generated based on the efficiency of the employee in completing an opportunity.

It provides the facility to view the opportunity status depending on the following:

Date-based retrieval of the various stages that have been reached

All opportunities associated with an employee both current and committed

A funnel depicting the current stage of all the ongoing opportunities

A list comprising of the opportunities that have been committed

We are creating a Web based application for tracking various opportunities faced by employees in an organization. The application enables the user to view as well as update his personal or business details. It also provides reviews on the performance of the employee.

We have used the .NET Platform along with C# as the coding language. The application is completely based on ASP.NET which runs in the .NET Framework.

The application uses ASP.NET pages with C# as the scripting language for the functionality that takes place behind the Web Forms that are visible to the user as front-end.

SQL Server 2000 is used as back-end, which along with ADO.NET provides easy access to data required for the application.

XML is also used to provide support for updates.

The project uses ASP.NET pages to provide the front-end to the user. The ASP.NET pages consist of Web Forms. These act as the user interface of the application. The functionality embedded in the Web Forms has been provided through C#.

The application provides the user with the following facilities:

• Viewing opportunity data for the organization as a whole.
• Viewing opportunity data for a particular employee.
• Viewing personal details of employees.
• Updating personal details of the employee.
• Updating business details of the employee.
• Provides drill down to view particular opportunity details.

The application uses SQL server 2000 as back end. The data stored on these databases is fetched by the application using ADO.NET. This provides a partially two-tier and partially three-tier architecture to the application. The use of DataSets and DataAdapters allow easy access to the database.

The application also uses XML for business updates to provide double verification before allowing data in the databases to be updated.

The application has been developed in the Visual Studio .NET 1.0 developing environment, which uses the .NET Framework which is provided on Windows.

The backend uses SQL Server 2000 which requires Windows Server 2000 or later.

The application has the following software requirements:-

• IIS server
• NET Framework
• Visual Studio .NET 1.0 developing environment.
• The client requires a web browser.

The application has the following hardware applications:-

• Multimedia PC configuration.

“ Web Issue-manager for distributed teams “

Issue Manager is a web-based application designed to help a workgroup keep track of issues and tasks via a shared central resource. The data is stored centrally on the server, which make it specially suitable for distributed teams who can use just the web browser to access it. No local software needs to be installed on the client and all web browsers are supported.

Strategic issue management is the responsibility of the entire organization. That responsibility crosses all units and all reporting lines. It is the external component of strategic management.

This issue management framework involves three functions:

• Gathering/Monitoring intelligence and information
• Analyzing the information and classifying the issue
• Taking action and evaluating the results

Issues are events that occur outside the control of an organization and that may require the organization to take action.

For effective strategic management , issues need to be classified and ranked.

Classification determines whether the problem is internal pr external and routes it accordingly

Ranking determines the priority order for dealing with and expending resources on an issue.

The purpose of the issue resolution process is to provide a mechanism for organizing ,maintaining and tracking the resolution of issues that cannot be resolved at the “individual” level. The approach consists of issue control mechanism and a well definied Process that enables the project team to identify ,address and prioritize problems and issues. All action items will be tracked until they are resolved.

The issue Manager will report on all open issues at the weekly status meetings. If the list of issues is too long only the new issues will be discussed. At times, it may be advisable to pre-distribute issues information so that the project status group can review the material before the meeting.When the issue of problem has been resolved and verified , the actual date problem was resolved and an approval signature complete the issue resolution process, and the issue is Closed.

Platform:- Windows

• IIS
• Microsoft access
• .NET Framework SDK Beta2/ASP.NET Premium Edition Beta2
• Winzip or similar program

• Local area network configuration

Our goal is to introduce a Package Manager for Source Code Installation in Linux distributions. This Package Manager would itself take care of maintenance of complete system, which so far has been a very cumbersome job for any administrator. This LPM along with a Registry would provide an alternative back-end for various text configuration files.

Thus, instead of each application having its own text-configuration files, our application provides a universal, hierarchical, fast & consistent namespace & infrastructure to access configuration parameters through a key-value pair mechanism.

This would include creation of separate entities:-

• local database for local machine administration & maintenance.
• registry for local as well as remote administration of the machine configuration.

• I386 Architecture Machines.
• Red Hat Linux 9.0 Operating System.

The project has some hardware & software requirements that are described as follows:-

• Red Hat Linux 9.0 with kernel(2.4.23)
• Linux GUI builder package – QT
• A C/C++ IDE for Linux – Anjuta
• Elektra API’s

• Two PC’s with usual configurations (128/256RAM P4 Processors etc.)
• LAN connection b/w the machines.

It has been long desired to have some kind of Package Management system in existing Linux environment. Due to the pre-existing feature of being Open Source, any package can be installed & used, almost anywhere in a Linux system (be it Personal/Server configuration).

Today’s GNU/Linux systems are a sum of independent components collected from Open Source Community. Each of them already has a working, but selfish configuration system.

One of the system (maintained by an administrator X) has an Apache package (say version 1.4) installed from source (instead of RPM distribution).After some time a new administrator (say Y) starts maintaining that system. Suppose he comes to know that Apache (version 1.4) has a serious security flaw and he installs a newer version (2.0). Now to clean the system more efficiently he has to effectively delete all the files (main files as well as support files) from various locations which become a very tedious task itself.

Thus we realize that the overall maintenance of complete Linux system is a highly cumbersome process which any administrator has difficulty in carrying out, both efficiently & effectively.

Now that the problem at hand is very much clear, the next & foremost step is as to how the information about various packages, getting installed on the system, needs to be track down & stored. One of the most important design issues that needs utmost attention is:-

The existing system should not change. It means that we cannot go about changing the entire installation methodology, just for the sake of obtaining the desired information. The reason is if the existing system changes, there is a high probability that the newer system is not at all welcomed by the existing developer & user society.

Thus after considering various other issues, the solution that has been finalized is as follows:-

We need to trap the information when & where it is getting created & moved into the existing system.

This information then has to be stored & later on retrieved in an efficient & effective way that would suite our project requirements.

Thus the complete project now gets divided into 4 different stages. They are:-

• Collection of all the data.
• Extraction of Information.
• Efficient storage of the information.
• Effective retrieval of this information.

The purpose of this document is to collect, analyze and define high-level needs and features of the Source Code Analyzer. It focuses on the capabilities needed by the stakeholders, and the target users, and why these needs exist. 

Input to this source code analyzer will be a windows code and as an output it’ll give us graphical view of amount of portable source code, non-portable source code.

Purpose of Source Code Analyzer

In order to comply with this kinda working knowledge of different operating systems is must because one just can’t simply use the same program for different operating systems. One has to again write that program taking into consideration compatibility issues. This is not always possible. Here idea of porting comes into the picture.

We’ve discovered that there are no tools available to check the compatibility issues; ergo we’ve decided to design software that will analyze a program and give us an information regarding parameters needed to be considered while going for porting. This software is called source code analyzer.

Summary of Capabilities

SCA will be providing a launch pad for a porting project. It will indicate the comparative study of the existing code. SCA will assist management to identify problem areas and gauge staff workload. The reports generated by SCA allow high level review of problem status.

SCA will assist the programmers too as it provides the readymade reverse engineered documents of existing code as well as special guidelines for porting that code on the other platform.

Objectives

Manual analyzing of source code is a very time consuming and tedious. SCA attempts to reduce this process of analyzing the existing code, provides various reports, graphs, suggestions, which are extremely useful not only for developers but for management personnel also to decide the deadline, and number of employees to be assigned.

Platform:

 

• Jdk 1.4
• Software requirements:
• Gel IDE

 

Hardware requirements:

 

• PROCESSOR: PENTIUM III/IV.
• MEMORY: 256MB onwards

Source code analyzer final year project for cse