IP Stack Research Articles

Distributed Intrusion Detection and Research of Fragment Attack Based-on IPv6

IPv6, the address has to aggregation, thus greatly reducing the length of the routing equipment routing table to improve the efficiency of routing and security, but then there is any possibility of network intrusion attack. This paper used to implement IPv6 Snort intrusion detection software, intrusion detection system is proposed as long as the server itself TCP / IP stack on the handling of data packets are different, the packet will bypass the intrusion detection system from the ground to produce a TCP fragment attack.

Survey of network security systems to counter SIP-based denial-of-service attacks

Session Initiation Protocol is a core protocol for coming real time communication networks, including VoIP, IMS and IPTV networks. Based on the open IP stack, it is similarly susceptible to Denial-of-Service Attacks launched against SIP servers. More than 20 different research works have been published to address SIP-related DoS problems. In this survey we explain three different types of DoS attacks on SIP networks, called SIP message payload tampering, SIP message flow tampering and SIP message flooding. We survey different approaches to counter these three types of attacks. We show that there are possible solutions for both payload and flow tampering attacks, and partial solutions for message flooding attacks. We conclude by giving hints how open flooding attacks issues could be addressed.

Performance Comparison of VxWorks, Linux, RTAI, and Xenomai in a Hard Real-Time Application

We report on a set of performance measurements executed on VMEbus MVME5500 boards equipped with MPC7455 PowerPC processor, running four different operating systems: Wind River VxWorks, Linux, RTAI, and Xenomai. Some components of RTAI and Xenomai have been ported to the target architecture. Interrupt latency, rescheduling and inter-process communication times are compared in the framework of a sample real-time application. Performance measurements on Gigabit Ethernet network communication have also been carried out on the target boards. To this purpose, we have considered the Linux IP stack and RTnet, an open-source hard real-time network protocol stack for Xenomai and RTAI, which was ported to the considered architecture. Performance measurements show that the tested open-source software is suitable for hard real-time applications.

Impact of Redhat IPv6 router on heterogeneous host connections

AbstractInternet's popularity has been expanding on dramatic pace and the number of people getting connected to it multiplies regularly. With this high demand, the current Internet Protocol (IPv4) has reached its limits. The next generation Internet Protocol version6 (IPv6) has been incorporated into various operating systems. The motivation behind this work is how well IPv6 co‐operates with various operating systems. The performance of the IP stack, together with the behaviour of the OS greatly affects the efficiency of network applications built on top of it. The acceptance of IPv6 implementations on various operating systems heavily relies on the end‐user performance. In this paper, we propose to analyse these various IPv6 implementations for its host and router‐level supports. In this paper, we investigate the impact of Redhat‐based IPv6 router on IPv6 stacks of three different operating systems namely, Windows2003, Redhat Linux 9.0 (Redhat9.0) and FreeBSD4.9. Copyright © 2006 John Wiley & Sons, Ltd.

Performance comparison of packet transmission over IPv6 network on different platforms

With the increasing popularity in recent years, many popular operating system (OS) vendors worldwide have incorporated Internet Protocol version 6 (IPv6) into their OS. The performance of the IP stack, together with the behaviour of the OS greatly affects the efficiency of network applications built on top of it. Like any other protocols, the acceptance of various IPv6 implementations heavily relies on the end-user performance. Hence, with the availability of a variety of IPv6 implementations, it is essential to evaluate their performance under different operating systems. An investigation of IPv6 stack performance on three different operating systems, namely, Windows 2003, Redhat Linux 9.0 (Redhat 9.0) and FreeBSD 4.9, is discussed. Performance analysis and comparison of the three IPv6 stacks, some interesting points raised by the experimental results are addressed.

On Source-Based Route Computation for Quickest Paths under Dynamic Bandwidth Constraints

Routing in the newer generation of network transmission methods may be performed at various levels of the IP stack such as datagram, TCP stream, and application levels. It is important in the use of these methods to compute the routes that minimize the end-to-end delays for the specific routing mechanism. We formulate an abstract network path computation problem, the dynamic quickest path problem, to encompass a number of message forwarding mechanisms including circuit switching, Internet Protocol, and their variations. This problem deals with the transmission of a message from a source to a destination with the minimum end-to-end delay over a network with propagation delays and dynamic bandwidth constraints on the links. The available bandwidth for each link is specified as a piecewise constant function. We present for each message forwarding mechanism or mode an algorithm to compute a path with the minimum end-to-end delay for a given message size. Our algorithms with suitable network restrictions have polynomial time complexity in the size of the network and total number of segments in the bandwidth list.

Where Internet Service Providers and Telephone Companies Compete: A Guide to the Computer Inquiries, Enhanced Service Providers and Information Service Providers

In 1966, the FCC launched the first of the Computer Inquiries, asking about the difference between computers that run telecommunications networks and computers with which we interact. Even in the late 60s, the FCC perceived the tremendous potential that computer networks promised for economic growth, the highly competitive nature of the computer network market, and the dependency of computer networks upon the underlying telecommunications network monopoly. The end product of the Computer Inquiries has been to distinguished between computer networks classified as enhanced services and basis telecommunications services. The FCC found no need to regulate enhanced services. The Internet falls within this category of enhanced services, with everything above layer 2 in the IP stack falling within this category. However, recognizing the dependency of enhanced services on basic services and the ability of telecommunications monopolies to anticompetitively impact the enhanced services market, the FCC created a series of progressive safeguards. But there is a problem. Some of the Computer Inquiry rules have been codified in the Code of Federal Regulation; some have not. Some rules have been reconsidered by the Commission, appealed in federal court, and reviewed by the Supreme Court. Some rules are currently in effect, some have been vacated, and some are the subject of current open proceedings before the Commission. This makes these rules difficult to comprehend, particularly to a small Internet business. Thus, this paper embarks upon the modest project of setting forth the Computer Inquiries rules as they exist today. All facilities based carriers fall under Computer Inquiry obligations. Facilities based carriers who offer enhanced services must unbundle their basic service from their enhanced services and offer the basic service to independent enhanced services providers (ESPs) on the same terms and conditions. Bell Operating Companies (BOCs), with their greater market power and incentives, have stronger separation safeguards. BOCs who elect to provision enhanced services may do so through a separate subsidiary pursuant to Computer II, or without a separate subsidiary pursuant to Computer III. Computer III requires the posting of a Comparably Efficient Interconnection plan detailing what the BOC is providing to itself and how these elements shall be made available to independent ESPs. Computer III also requires that BOCs, regardless of whether they provision enhanced services (they all do), create Open Network Architecture plans that break their networks down into basic building blocks available for use by ESPs. BOCs are required to file regular reports with the Commission detailing their compliance with these rules. Beyond the separation rules, the FCC created additional safeguards generally aimed at all carriers. These rules included Customer Propriety Network Information (restricting the use of a customer's telecommunications information for non-telecommunications purposes), restrictions on discrimination against independent ESPs, Network Information Disclosure (ensuring that information concerning upgrades to the network is provided to all equally), restrictions against cross subsidization, and accounting safeguards. Service Providers

Terminal independent mobility for IP (TIMIP)

This article presents Terminal Independent Mobility for IP (TIMIP), which is a new architecture for IP mobility in wireless access networks. TIMIP is based on principles similar to those in the CIP and HAWAII architectures proposed at IETF and is equally suited for micromobility scenarios. With TIMIP, terminals with legacy IP stacks have the same degree of mobility as terminals with mobility-aware IP stacks. Nevertheless, it still uses MIP for macromobility scenarios. In order to support seamless handoff, TIMIP uses context-transfer mechanisms compatible with those currently in discussion at the IETF SeaMoby group.

Internet traffic measurement

The Internet's evolution over the past 30 years (1971-2001), has been accompanied by the development of various network applications. These applications range from early text-based utilities such as file transfer and remote login to the more recent advent of the Web, electronic commerce, and multimedia streaming. For most users, the Internet is simply a connection to these applications. They are shielded from the details of how the Internet works, through the-information-hiding principles of the Internet protocol stack, which dictates how user-level data is transformed into network packets for transport across the network and put back together for delivery at the receiving application. For many networking researchers however, the protocols themselves are of interest. Using specialized network measurement hardware or software, these researchers collect information about network packet transmissions. With detailed packet-level measurements and some knowledge of the IP stack, they can use reverse engineering to gather significant information about both the application structure and user behavior, which can be applied to a variety of tasks like network troubleshooting, protocol debugging, workload characterization, and performance evaluation and improvement. Traffic measurement technologies have scaled up to provide insight into fundamental behavior properties of the Internet, its protocols, and its users. The author introduces the tools and methods for measuring Internet traffic and offers highlights from research results.

A pointed look at the point-to-point protocol

While players like TCP and RSVP are usually considered the stars in the theater of Internet protocols, perhaps the most pervasive, extensible, underpublicized, and underappreciated protocol within the IP stack today is the point-to-point protocol (PPP). The author considers the basics of PPP.

Network Dispatcher: a connection router for scalable Internet services

Network Dispatcher (ND) is a TCP connection router that supports load sharing across several TCP servers. Prototypes of Network Dispatcher were used to support several large scale high-load Web sites. Network Dispatcher provides a fast IP packet-forwarding kernel-extension to the TCP IP stack. Load sharing is supported by a user-level manager process that monitors the load on the servers and controls the connection allocation algorithm in the kernel extension. This paper describes the design of Network Dispatcher, outlines Network Dispatcher's performance in the context of http traffic, and presents several of its features including high-availability, support for WANs, and client affinity.