Configuring DLink DSL-500G

• Step 1) Connect network cable (UTP) to the DSL-500G unit’s Ethernet port and the other end of the cable to any PC or notebook’s Ethernet port. Please also ensure that the provided power supply is connect to the DSL-500G unit.
• Step 2) Initiate Internet Explorer and enter the address http://10.1.1.1/ in the address bar field. A login screen will next appear as shown in fig. 2.
  Please enter the following :
  User name : admin
  Password : admin
  Click on the OK button next.
• Step 3) As shown in fig. 3, on the left menu of the display screen click on Home .. Quick Configuration.
  Also as shown below, on the main option page in the left of the screen, alter the following fields to the values as stated:
  1) Connection Type : 1483 Bridge IP VC-Mux
  2) Bridge : Enable
  3) Default route : Disabled
  Complete configuration by next clicking on Submit button.

This guide describes the installation and configuration of the Cisco Service Control Management Suite (SCMS) Collection Manager (CM). This preface describes who should read the Cisco Service Control Management Suite Collection Manager User Guide, how it is organized, its document conventions, and how to obtain documentation and technical assistance.

This guide is intended for the networking or computer technician responsible for the onsite installation and configuration of the Cisco Service Control Management Suite (SCMS) Collection Manager (CM). It is also intended for the operator responsible for the daily operations of the CM, allowing the Service Provider operator to make enhancements in a subscriber-oriented environment. This guide assumes a basic familiarity with the concept of the Cisco Service Control solution, the Service Control Engine (SCE) platforms, and related components.

Introduction

This preface describes who should read the Cisco Service Control Application for Broadband Reference Guide, how it is organized, its document conventions, and how to obtain documentation and technical assistance. This guide assumes a basic familiarity with the concept of the Cisco Service Control solution, the Service Control Engine (SCE) platforms, and related components.

This guide provides information about the data structures created and used by SCA BB. It is intended for:

• The administrator who is responsible for daily operation of the Cisco Service Control solution
• Integrators who are developing applications on top of SCA BB

Information About Protocols

Protocols are divided into four groups:

• Generic Protocols—These protocols are used for transactions that were not mapped to a service by one of the more specific protocol types.
• Signature-Based Protocols—Protocols classified according to a Layer 7 application signature. This group includes the most common protocols, such as HTTP and FTP, and a large group of popular P2P protocols.

System Architecture and Working Flows of PPLive

The PPLive software, running in user computers (peers), has two major communication protocols: (i) a registration and peer discovery protocol; and (ii) a P2P chunk distribution protocol. Figure 1 depicts an overview of the registration and peer discovery protocol [5]. When an end-user starts the PPLive software, it joins the PPLive network and becomes a PPLive peer node. The first action (step 1) is an exchange with the PPLiveWeb site to retrieve a list of channels distributed by PPLive. Once the user selects a channel, the peer node registers with the bootstrap root servers (trackers) and requests a list of peers that are currently watching the channel (step 2). The peer node then communicates with the peers in the list to obtain additional lists (step 3), which it aggregates with its existing list. In this manner, each peer maintains a list of other peers watching the channel.

Packet Capture
In this article, we shall cover the basic working of a sniffer, to capture packets for analyzing the traffic. If an analyst does not have working skills of a packet sniffer to a certain level, it is really hard to defend intrusions. This article would help the analyst to prepare to the level of what is required for basic packet collection and basic analysis, but not everything about sniffers. An in depth article on sniffer’s using packet crafting and packet capture will be coming soon. In this document we are using Wireshark Version 0.99.5 (SVN Rev 20677).

What you will learn…

• Introduction to Sniffer
• Capturing Traffic
• Wireshark basics: The different panes

The fork-and-do-something latency on my notebook on Linux 2.6 is 200
microseconds. That means my notebook can create 5.000 processes per second. Thus my notebook can handle about 13 billion forks per month. My Athlon XP 2000+ desktop can do 10.000 processes per second, or 26 billion per month. Heise Online, the biggest German site, had 118 million page impressions in September.

Scheduling
Why does the fork benchmark include writing to the pipe? Because having many processes not only makes creating more processes more difficult, it also makes choosing which process to run more difficult. The part of the operating system that chooses which process to run next is called the scheduler. A typical workload is having two dozen processes, with one or two of them actually having something to do (they are runnable).