The ns Manual (formerly ns Notes and Documentation)1 - NM Lab at ...
The ns Manual (formerly ns Notes and Documentation)1 - NM Lab at ... The ns Manual (formerly ns Notes and Documentation)1 - NM Lab at ...
$client log These consist configuration of the Http client. It is attached to a central page pool . Next a random variable is attached to the client that is used by it (client) to generate intervals between two consecutive requests. Lastly the client isattached to a log file for logging its events.$cache log This is part of cache configuration that allows the cache to log its events in a log-file.$client connect $cache connect Once the client, cache, and server are configured, they need to be connected as shown in above commands.$client start-session This starts sending request for a random page from the client to the via .359
Chapter 40Worm ModelIn this chapter, we describe a scalable worm propagation model in ns, namely the detailed-network and abstract-network (DN-AN) model. It combines packet-level simulations with analytic worm spreading model. As shown in Figure 40.1, we modelthe Internet with two parts: detailed, and abstract part. A detailed-network could be an enterprise-network or the networkrun by an ISP. It simulates network connectivity and packet transmission. Users can evaluate worm detection algorithms inthe detailed network. On the other hand, we abstract the rest of the Internet with a mathematical model, namely susceptibleinfectious-removal(SIR) model (refer to [13] for detailed descriptions). Compared to the detailed network, we only trackseveral state variables in the abstract world, such as the number of infected hosts. The interaction between DN and AN isthrough actual packet transmissions, that is, the probing traffic generated by compromised hosts in both parts.For detailed description on DN-AN model, please refer to our draft paper. We implement the worm propagation model asapplications. The source code can be found at ~ns//apps/worm.{cc,h}. There is also a sample script to illustrate the DN-ANmodel under ~ns//tcl/ex/worm.tcl.40.1 OverviewWe implement the worm propagation model with three classes: class WormApp, DnhWormApp, and AnWormApp.class WormAppnd class DnhWormAppre used in the detailed network, representing invulnerable and vulnerable hostsrespectively. class AnWormApps the abstract network. Currently, our model only supports UDP-based worms.An vulnerable host is compromised upon receiving a probing packet. Then, it chooses a target host (randomly or with certainpreference to local neighbors) to scan. Probing packets have no effect on invulnerable hosts. When the abstract networkreceives probing packets, it updates its current states.probingtrafficthe restunprotectedInternetthe protected networkFigure 40.1: The DN-AN model.360
- Page 309 and 310: Chapter 36Agent/SRMThis chapter des
- Page 311 and 312: 36.1.2 Other Configuration Paramete
- Page 313 and 314: 3.6274 n 0 m r 1 type repair servi
- Page 315 and 316: 3.6029 n 3 m r 2 Q NTIMER at 3.730
- Page 317 and 318: 36.4 Loss Detection—The Class SRM
- Page 319 and 320: same packet. The repair objet does
- Page 321 and 322: }hdr_asrm* seh = (hdr_asrm*) p->acc
- Page 323 and 324: set grp [Node allocaddr]$srm set ds
- Page 325 and 326: #set up the multicast routingDM set
- Page 327 and 328: 37.3 Architecture of the PLM Protoc
- Page 329 and 330: We add in void PLMLossMonitor::recv
- Page 331 and 332: Part VIApplication330
- Page 333 and 334: Traffic generatorsApplication/Traff
- Page 335 and 336: • recv(int nbytes)—Announces th
- Page 337 and 338: 1. EXPOO_Traffic—generates traffi
- Page 339 and 340: set src [new Agent/UDP]set sink [ne
- Page 341 and 342: Application FTP FTP objects produce
- Page 343 and 344: send_data(ADU)Application(HttpApp,
- Page 345 and 346: 39.1.4 Transmitting user data over
- Page 347 and 348: and teardown of connections. Only O
- Page 349 and 350: TclObjectPagePoolPagePool/CompMathP
- Page 351 and 352: PagePool/ProxyTrace takes these two
- Page 353 and 354: }int id_; // object IDWebTrafSessio
- Page 355 and 356: An Http/Server object waits for inc
- Page 357 and 358: set tmp [new RandomVariable/Exponen
- Page 359: Object Type Event Type Explaination
- Page 363 and 364: $w local-p 0.5Following are some co
- Page 365 and 366: (nsnode) clientcloudPackM ime(nsnod
- Page 367 and 368: HTTP responsesclients servers Delay
- Page 369 and 370: 41.5 Commands at a GlanceThe follow
- Page 371 and 372: • HTTP response size (bytes)• s
- Page 373 and 374: Chapter 42Session-level Packet Dist
- Page 375 and 376: 42.1.2 Inserting a Loss ModuleWhen
- Page 377 and 378: Delay and Loss Modules Each receive
- Page 379 and 380: Chapter 43Asim: approximate analyti
- Page 381 and 382: set n(1) [$ns node]set link(0:1) [$
- Page 383 and 384: Part VIIIEmulation382
- Page 385 and 386: When using the emulation mode, a sp
- Page 387 and 388: set intf [$pf1 open readonly]puts "
- Page 389 and 390: puts "install nets into taps..."$a0
- Page 391 and 392: Chapter 45Nam45.1 IntroductionNam i
- Page 393 and 394: • Button 6 (Chevron logo) - Close
- Page 395 and 396: Second, when dealing with randomly
- Page 397 and 398: dst_portaddr,seqno,flags,sname);A n
- Page 399 and 400: • up• down• right• left•
- Page 401 and 402: 46.1.7 Agent TracingAgent trace eve
- Page 403 and 404: v -t 1.0 -e node_tclscript 2 "Echo
- Page 405 and 406: If nam ever gets to the end of an e
- Page 407 and 408: l :link-t time-s source id-d des
- Page 409 and 410: E :D :P :a :session enqueue-t time
$client log <strong>The</strong>se co<strong>ns</strong>ist configur<strong>at</strong>ion of the Http client. It is <strong>at</strong>tached to a central page pool . Next a r<strong>and</strong>om variable is <strong>at</strong>tached to the client th<strong>at</strong> is used by it (client) to gener<strong>at</strong>e intervals between two co<strong>ns</strong>ecutive requests. Lastly the client is<strong>at</strong>tached to a log file for logging its events.$cache log This is part of cache configur<strong>at</strong>ion th<strong>at</strong> allows the cache to log its events in a log-file.$client connect $cache connect Once the client, cache, <strong>and</strong> server are configured, they need to be connected as shown in above comm<strong>and</strong>s.$client start-session This starts sending request for a r<strong>and</strong>om page from the client to the via .359
Change language