- First
approach: The sender must transmit an IP datagram of size as same as that
of the first hop’s MTU.
- Second
approach: Running the path MTU discovery algorithm.
Thursday, September 19, 2013
What is fragmentation?
Posted by
Sunflower
at
9/19/2013 03:41:00 PM
0
comments
Labels: Data, Datagrams, Destination, Fragmentation, Fragments, Host, Hosts, IP, Layers, Messages, Packets, Paths, Protocols, Receiver, Router, Sender, Source, Techniques, transmission, Transport
![]() | Subscribe by Email |
|
Tuesday, September 10, 2013
What are the differences between bridges and repeaters?
- LAN
address of the node
- Bridge
interface
- Time
stamp
- Stale
table entries
Posted by
Sunflower
at
9/10/2013 03:20:00 PM
0
comments
Labels: Address, Analog, Bridges, Data, Devices, Differences, Forward, Frames, Hosts, Information, Interface, Layers, Network, Networking, Packets, Physical, Repeaters, Signals, Store, Telecommunications
![]() | Subscribe by Email |
|
Friday, August 9, 2013
What are applications of flooding algorithm?
Applications of Flooding Algorithm
Posted by
Sunflower
at
8/09/2013 03:07:00 PM
0
comments
Labels: Address, Algorithms, Applications, Data, files, Flood, Flooding Algorithm, Graph, Hosts, Links, Messages, Nodes, Packets, Parameters, Receiver, Route, Routing, Schema, Similarity Algorithm, Transmitter
![]() | Subscribe by Email |
|
Saturday, July 20, 2013
What are data gram sub-nets?
- Layer
1: chip (CDMA)
- Layer
2: frames (IEEE 802.3 and IEEE 802.11), cell (ATM)
- Layer
3: data packet
- Layer
4: data segment
Posted by
Sunflower
at
7/20/2013 03:16:00 PM
0
comments
Labels: Advantages, Communication, Connection, Datagram Subnets, Destination, Disadvantages, Hosts, Information, Layers, Network, Operate, OSI, Packets, Protocols, Source, Subnets, Switch, User
![]() | Subscribe by Email |
|
Wednesday, July 17, 2013
What are network layer design issues?
- Services
provided to the layer 4 i.e., the transport layer.
- Implementation
of the services that are connection oriented.
- Store
– and - forward packet switching
- Implementation
of the services that are not connection oriented.
- Comparison
of the data-gram sub-nets and the virtual circuits.
- They
should be independent of the router technology.
- Shielding
from the type, number and topology of the routers must be provided to the
transport layer.
- The
network addresses that are provided to the transport layer must exhibit a
uniform numbering plan irrespective of whether it’s a LAN or a WAN.
Posted by
Sunflower
at
7/17/2013 05:30:00 PM
0
comments
Labels: Communication, Connection, Data, Datagram, Design, Hosts, Issues, Layers, Model, Network, Network layer, OSI, Packets, Processes, Routes, Routing, subnet, Tasks, Transport layer, Virtual Circuits
![]() | Subscribe by Email |
|
Tuesday, July 9, 2013
Explain CSMA with collision detection?
- Contention
- Transmission
- Idle
Posted by
Sunflower
at
7/09/2013 01:30:00 PM
0
comments
Labels: Algorithms, Carrier, Channels, Collision, Collision Detection, CSMA, CSMA/CD, Data, Frames, Host, Hosts, Listen, Packets, Processes, Protocols, Sense, States, Stations, transmission, Transmitter
![]() | Subscribe by Email |
|
Sunday, July 7, 2013
Differentiate between persistent and non-persistent CSMA?
- The length of the packets is
constant.
- The errors can only be
caused by collisions except which there are no errors.
- Capture effect is absent.
- The transmissions made by
all the other hosts can be sensed by each of the hosts.
- The transmission time is
always greater than the propagation delay.
Posted by
Sunflower
at
7/07/2013 12:58:00 PM
0
comments
Labels: Behavior, Carrier, Carrier Sense Multiple Access, Channel, Collisions, CSMA, Data, Differences, Errors, Frames, Hosts, Non-persistent, Packets, Persistent, Protocols, Station, Technology, Throughput, transmission
![]() | Subscribe by Email |
|
Saturday, July 21, 2012
What is meant by DNS? What does it contain?
- Computers
- Services
- Resources that
are connected to some private network or internet and so on.
What does DNS contain?
Posted by
Sunflower
at
7/21/2012 10:56:00 AM
0
comments
Labels: Address, Communication, Distributed system, Domain, Domain Name, Domain Name System, End users, Functionality, Hosts, Information, Internet, IP address, Network, Protocol, Queries, Register, Resources, Servers, URL
![]() | Subscribe by Email |
|
Friday, March 9, 2012
What is meant by storm worm?
Storm worm? You may not recognize this worm at the first instance since you might be knowing it by one of the following other names:
1. Small. Dam
2. Trojan- downloader. Win 32. Small. Dam
3. F secure as dubbed by the finnish company.
4. W32/ Numwar@MM
5. Downloader BAI (McAfee’s specific variant)
6. Trojan. DL. Tibs. Gen! Pact13
7. Trojan. Peacomm (Symantec)
8. Win32/ Nuwar (ESET)
9. W32/ Zhelatin (kaspersky, F secure)
10. Trojan. Peed (Bit Defender)
11. Trojan. Tibs (Bit Defender)
12. Win32/ Nuwar. N@MM! CME- 711 (windows live one care)
13. TROJ_SMALL. EDW (trend micro)
14. Trojan. Downloader – 647
15. Loland Mal/ Dorf (sophos)
16. CME- 711 (mitre)
Evolution of Storm Worm
- It was recognized as a back door Trojan horse that had most of its impact on the computer systems that use the Microsoft operating systems or applications or extensions.
- This worm was first observed on the date of 17th January in the year of 2007.
- The storm worm first took its affect in the countries of the United States and Europe infecting millions of computer systems starting on the date of 19th January 2007.
- It was usually sent to the users as an e-mail message having the subject as a headline about the recent weather disaster like “230 dead as storm batters Europe”.
- At the starting of this cyber epidemic, there were around 6 waves of attack subsequently.
- At the end of the January 2007, the storm worm was said to account for 8 percent of all the world wide malware infections.
- According to the PC world, the history or origin of the storm worm can be traced back to a Russian business network.
- Mostly the European wind storm “kyrill” was used as the subject of the infected e- mails.
- This email usually had an attachment accompanying it which when opened, automatically installed this malware on to the system of the users.
Steps involved in installing the Malware
The malware was installed via the following steps:
1. Installation of the wincom32 service
2. Injection of payload
3. Passing of the packets to destinations as mentioned in the malware code.
4. Download and run the W32. Mixor. Q@mm worm and Trojan. Abwiz. F Trojan.
These downloaded Trojans then attached themselves to spam like flashcard.exe, postcard.exe and so on. Other changes regarding the original attack wave were made as the mutation of the attack carried on. Below mentioned are some other prominent spam attachments:
1. Ecard.exe
2. Fullstory.exe
3. Read more. Exe
4. Greeting postcard.exe
5. Read more.exe
6. Full news.exe
7. Arcade world.exe
8. Fullvideo.exe
9. Video.exe
10. Full clip.exe
11. More here.exe
12. Click here.exe
13. Nfl stat tracker.exe
14. Arcade world game.exe
Later the storm worm came to be spread by subjects regarding love such as “touched by love”, “love birds” and so on. These e- mails had the links referring to the malicious web sites containing virus like:
1. With love.exe
2. With_love.exe
3. From me to you.exe
4. Fck2008.exe
5. Fck2009.exe
6. Love.exe
7. Iheart you.exe
The storm worm has an exceptional ability to stay resilient. The affected machine or system used to become a part of botnet networks which was controlled through a central server. A botnet is seeded by the storm worm that acts as a P2P network without any control. The connected systems then act as a host and share the list of other hosts. One peculiarity was observed in the working of these machines which is that none of them shared the whole list of botnets.
Posted by
Sunflower
at
3/09/2012 10:57:00 PM
0
comments
Labels: Application, Computer system, Connected systems, Control, Destination, Hosts, Impact, Infection, Installation, Machines, Malware, Network, Packets, Security, Source, Storm Worm, Trojan Horse, Users
![]() | Subscribe by Email |
|
Thursday, July 8, 2010
What are different terminologies used in LoadRunner ?
Application performance testing requirements are divided into scenarios using LoadRunner.
- A scenario defines the events that occur during each testing sessions.
- A scenario defines and controls the number of users to emulate, the actions that they perform, and the machines on which they run their emulations.
Vusers
LoadRunner works by creating virtual users who take the place of real users operating client software. LoadRunner works by creating virtual users who take the place of real users operating client software. Vusers emulate the actions of human users working with your application. A scenario can contain tens, hundreds, or even thousands of
Vusers.
Vusers Scripts
The actions that a Vuser performs during the scenario are described in a
Vuser script. When you run a scenario, each Vuser executes a Vuser script. Vuser scripts include functions that measure and record the performance of the server during the scenario.
Transactions
Transactions are defined to measure the performance of the server. Transactions measure the time that it takes for the server to respond to tasks submitted by Vusers.
Rendezvous Points
Rendezvous points are inserted into Vuser scripts to emulate heavy user load on the server. Rendezvous points instruct multiple Vusers to perform tasks at exactly the same time.
Controller
LoadRunner Controller is used to manage and maintain your scenarios. Using the Controller, you control all the Vusers in a scenario from a single workstation.
Hosts
The LoadRunner Controller distributes each Vuser in the scenario to a host when the scenario is executed. The host is the machine that executes the Vuser script, enabling the Vuser to emulate the actions of a human user.
Performance Analysis
Vuser scripts include functions that measure and record system performance during load-testing sessions. During a scenario run, you can monitor the network and server resources. Following a scenario run, you can view performance analysis data in reports and graphs.
Posted by
Sunflower
at
7/08/2010 01:26:00 PM
0
comments
Labels: Automated Testing, Controller, Hosts, LoadRunner, Machines, Manual Testing, Performance testing, Scenarios, Terminology, Transaction, Vuser script, Vusers
![]() | Subscribe by Email |
|