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 ...
40.2 ConfigurationTo set up simulation scenario, we first build the detailed network. We also need to create one extra node to represent theabstract network, and connect it to the detailed network.For nodes in the detailed network, we first attach a MessagePassing agent to each node:set a [new Agent/MessagePassing]$n attach $a $probing_portIf the node represents a vulnerable host, we use class DnhWormAppset w [new Application/Worm/Dnh]$w attach-agent $aOtherwise, we configure the node as invulnerable:set w [new Application/Worm]$w attach-agent $aWe configure the abstract network as:set a [new Agent/MessagePassing]$na attach $a $probing_portset w [new Application/Worm/An]$w attach-agent $aIn order for the abstract network to receive probing packets generated by nodes within the detailed networks, we need to usemanual routing. There are some extra configuration for the abstract-network node:set p [$na set dmux_]$p defaulttarget $a[$na entry] defaulttarget $p40.3 Commands at a glanceSome common parameters can be configured through TCL script:ScanRate # the rate that a compromised host sends probing packetsScanPort # the vulnerable service port numberScanPacketSize # the size of worm probing packetsBy default, compromised hosts scan the Internet randomly. We can also simulate local-scanning worm by setting the localscanningprobability:361
$w local-p 0.5Following are some commands to configure parameters for the abstract network:$w beta 0.1 # infection parameter$w gamma 0 # removal parameter$w addr-range 2000 200000 # the address space of the abstract network$w dn-range 0 1999 # the address space of the detailed network$w v_percent 0.01 # the percentage of vulnerable hosts in the abstract network362
- 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 and 360: Object Type Event Type Explaination
- Page 361: Chapter 40Worm ModelIn this chapter
- 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
- Page 411 and 412: v :V :N :W :g :A :c :q :execute tcl
40.2 Configur<strong>at</strong>ionTo set up simul<strong>at</strong>ion scenario, we first build the detailed network. We also need to cre<strong>at</strong>e one extra node to represent theabstract network, <strong>and</strong> connect it to the detailed network.For nodes in the detailed network, we first <strong>at</strong>tach a MessagePassing agent to each node:set a [new Agent/MessagePassing]$n <strong>at</strong>tach $a $probing_portIf the node represents a vulnerable host, we use class DnhWormAppset w [new Applic<strong>at</strong>ion/Worm/Dnh]$w <strong>at</strong>tach-agent $aOtherwise, we configure the node as invulnerable:set w [new Applic<strong>at</strong>ion/Worm]$w <strong>at</strong>tach-agent $aWe configure the abstract network as:set a [new Agent/MessagePassing]$na <strong>at</strong>tach $a $probing_portset w [new Applic<strong>at</strong>ion/Worm/An]$w <strong>at</strong>tach-agent $aIn order for the abstract network to receive probing packets gener<strong>at</strong>ed by nodes within the detailed networks, we need to usemanual routing. <strong>The</strong>re are some extra configur<strong>at</strong>ion for the abstract-network node:set p [$na set dmux_]$p defaulttarget $a[$na entry] defaulttarget $p40.3 Comm<strong>and</strong>s <strong>at</strong> a glanceSome common parameters can be configured through TCL script:ScanR<strong>at</strong>e # the r<strong>at</strong>e th<strong>at</strong> a compromised host sends probing packetsScanPort # the vulnerable service port numberScanPacketSize # the size of worm probing packetsBy default, compromised hosts scan the Internet r<strong>and</strong>omly. We can also simul<strong>at</strong>e local-scanning worm by setting the localscanningprobability:361