[ns] [AOC 2014] Last Days - IEEE WoWMoM Workshop on Autonomic and
Opportunistic Communications (AOC 2014)
Message-ID: 532051a5.auv6xtpin5d1mrvc%d.masci...@iit.cnr.it
User-Agent: Heirloom mailx 12.4 7/29/08
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
-
CALL FOR PAPERS
Eighth IEEE WoWMoM Workshop on
Autonomic and Opportunistic Communications (AOC 2014)
June 16, 2014 - Sydney, Australia
http://aoc2014.conference.nicta.com.au
Fast Track on Computer Communication Journal
http://www.elsevier.com/locate/comcom
Extended Submission Deadline --- March 14, 2014
-
The recent proliferation of sensor-rich portable devices is enabling
novel communication paradigms for users and contributing to the
implementation of the ubiquitous computing and networking vision.
Opportunistic networking represents a key communication paradigm for
this vision. Either as a standalone communication mode or as a
complement to infrastructure-based communication, opportunistic
networking leverages the mobility of end users to enhance their ability
to communicate in the absence of reliable end-to-end connectivity.
Opportunistic networking opens up many possibilities but also poses
countless new challenges. The goal of the AOC 2014 workshop is to serve
as a forum for researchers, professionals, application developers, and
other experts from both academia and industry to exchange new ideas,
discuss new solutions, and share their experiences. As with previous
editions, this year's workshop is particularly interested in novel
research directions, such as service composition techniques,
co-existence with infrastructure networks, and insights from game
theory, social networking analysis, and cognitive psychology. The
workshop will solicit original papers addressing theoretical and
practical aspects of autonomic and opportunistic communications as well
as papers describing prototype implementations and deployments.
Topics of interest for AOC 2014 include, but are not limited to:
* Routing, transport, and reliability issues
* Techniques for data dissemination and replication
* Applications and middleware support, mobile social networking
applications
* Mobility models and statistical analysis of mobility traces
* Context and social awareness mechanisms and algorithms
* Co-existence of opportunistic networks with infrastructure mobile
wireless networks
* Service composition in autonomic and opportunistic networks
* Cognition-driven information processing and decision making
* Performance modelling, scaling laws, and fundamental limits for
autonomic and opportunistic communications
* Game-theoretical insights to the operation of autonomic and
opportunistic networks
* Participatory and urban sensing in autonomic and opportunistic
networks
* Trust, security, and reputation
* Autonomic and opportunistic communication testbeds and prototypes,
measurement data from real experiments
* Socio-economic models for autonomic and opportunistic communications
* Mobile Social networks
PAPER SUBMISSION AND PUBLICATION
Papers should neither have been published elsewhere nor being currently
under review by another conference or journal. Manuscripts are limited
to 6 pages, single spacing, double column, and must strictly adhere to
the template format.
Accepted papers will appear in the symposium proceedings published by
IEEE. There will be no separate workshop registration, as one single
registration will cover both conference and workshops participation. At
least one author of each accepted paper is required and present his/her
work at the workshop.
Submissions and reviews will be done through EDAS. Please submit your
manuscript at http://edas.info/N16861. Extended versions of the
selected workshop papers will be considered for possible fast track
publication on the Computer Communications Journal (Elsevier).
IMPORTANT DATES
===
* Register by: March 7, 2014
* Full papers due: March 14, 2014 (Extended)
* Notification: April 15, 2014
* Workshop: June 16, 2014
ORGANIZING COMMITTEE
Workshop Chairs
~~~
* Mohan Kumar, Rochester Institute of Technology, USA
* Peizhao Hu, NICTA, Australia
Steering Committee
~~
* Marco Conti, IIT-CNR, Italy
* Silvia Giordano, SUPSI, Switzerland
* Ioannis Stavrakakis, University of Athens, Greece
Publicity Chairs
* Olivier Mehani, NICTA, Australia
* Davide Mascitti, IIT-CNR, Italy
Webmaster
~
* Christoph Dwertmann, NICTA, Australia
Program Committee (tentative)
=
* Nils Aschenbruck, University of Osnabruck, Germany
[ns] [AOC 2014] Last Days - IEEE WoWMoM Workshop on Autonomic and
Opportunistic Communications (AOC 2014)
Message-ID: 532051a5.vzhwx5sa0callwhr%d.masci...@iit.cnr.it
User-Agent: Heirloom mailx 12.4 7/29/08
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
-
CALL FOR PAPERS
Eighth IEEE WoWMoM Workshop on
Autonomic and Opportunistic Communications (AOC 2014)
June 16, 2014 - Sydney, Australia
http://aoc2014.conference.nicta.com.au
Fast Track on Computer Communication Journal
http://www.elsevier.com/locate/comcom
Extended Submission Deadline --- March 14, 2014
-
The recent proliferation of sensor-rich portable devices is enabling
novel communication paradigms for users and contributing to the
implementation of the ubiquitous computing and networking vision.
Opportunistic networking represents a key communication paradigm for
this vision. Either as a standalone communication mode or as a
complement to infrastructure-based communication, opportunistic
networking leverages the mobility of end users to enhance their ability
to communicate in the absence of reliable end-to-end connectivity.
Opportunistic networking opens up many possibilities but also poses
countless new challenges. The goal of the AOC 2014 workshop is to serve
as a forum for researchers, professionals, application developers, and
other experts from both academia and industry to exchange new ideas,
discuss new solutions, and share their experiences. As with previous
editions, this year's workshop is particularly interested in novel
research directions, such as service composition techniques,
co-existence with infrastructure networks, and insights from game
theory, social networking analysis, and cognitive psychology. The
workshop will solicit original papers addressing theoretical and
practical aspects of autonomic and opportunistic communications as well
as papers describing prototype implementations and deployments.
Topics of interest for AOC 2014 include, but are not limited to:
* Routing, transport, and reliability issues
* Techniques for data dissemination and replication
* Applications and middleware support, mobile social networking
applications
* Mobility models and statistical analysis of mobility traces
* Context and social awareness mechanisms and algorithms
* Co-existence of opportunistic networks with infrastructure mobile
wireless networks
* Service composition in autonomic and opportunistic networks
* Cognition-driven information processing and decision making
* Performance modelling, scaling laws, and fundamental limits for
autonomic and opportunistic communications
* Game-theoretical insights to the operation of autonomic and
opportunistic networks
* Participatory and urban sensing in autonomic and opportunistic
networks
* Trust, security, and reputation
* Autonomic and opportunistic communication testbeds and prototypes,
measurement data from real experiments
* Socio-economic models for autonomic and opportunistic communications
* Mobile Social networks
PAPER SUBMISSION AND PUBLICATION
Papers should neither have been published elsewhere nor being currently
under review by another conference or journal. Manuscripts are limited
to 6 pages, single spacing, double column, and must strictly adhere to
the template format.
Accepted papers will appear in the symposium proceedings published by
IEEE. There will be no separate workshop registration, as one single
registration will cover both conference and workshops participation. At
least one author of each accepted paper is required and present his/her
work at the workshop.
Submissions and reviews will be done through EDAS. Please submit your
manuscript at http://edas.info/N16861. Extended versions of the
selected workshop papers will be considered for possible fast track
publication on the Computer Communications Journal (Elsevier).
IMPORTANT DATES
===
* Register by: March 7, 2014
* Full papers due: March 14, 2014 (Extended)
* Notification: April 15, 2014
* Workshop: June 16, 2014
ORGANIZING COMMITTEE
Workshop Chairs
~~~
* Mohan Kumar, Rochester Institute of Technology, USA
* Peizhao Hu, NICTA, Australia
Steering Committee
~~
* Marco Conti, IIT-CNR, Italy
* Silvia Giordano, SUPSI, Switzerland
* Ioannis Stavrakakis, University of Athens, Greece
Publicity Chairs
* Olivier Mehani, NICTA, Australia
* Davide Mascitti, IIT-CNR, Italy
Webmaster
~
* Christoph Dwertmann, NICTA, Australia
Program Committee (tentative)
=
* Nils Aschenbruck, University of Osnabruck, Germany
[ns] [AOC 2014] Last Days - IEEE WoWMoM Workshop on Autonomic and
Opportunistic Communications (AOC 2014) Message-ID: 53145805.GG+dEqoudYzm3r3/%d.masci...@iit.cnr.it User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit - CALL FOR PAPERS Eighth IEEE WoWMoM Workshop on Autonomic and Opportunistic Communications (AOC 2014) June 16, 2014 - Sydney, Australia http://aoc2014.conference.nicta.com.au Fast Track on Computer Communication Journal http://www.elsevier.com/locate/comcom Submission Deadline --- March 7, 2014 - The recent proliferation of sensor-rich portable devices is enabling novel communication paradigms for users and contributing to the implementation of the ubiquitous computing and networking vision. Opportunistic networking represents a key communication paradigm for this vision. Either as a standalone communication mode or as a complement to infrastructure-based communication, opportunistic networking leverages the mobility of end users to enhance their ability to communicate in the absence of reliable end-to-end connectivity. Opportunistic networking opens up many possibilities but also poses countless new challenges. The goal of the AOC 2014 workshop is to serve as a forum for researchers, professionals, application developers, and other experts from both academia and industry to exchange new ideas, discuss new solutions, and share their experiences. As with previous editions, this year's workshop is particularly interested in novel research directions, such as service composition techniques, co-existence with infrastructure networks, and insights from game theory, social networking analysis, and cognitive psychology. The workshop will solicit original papers addressing theoretical and practical aspects of autonomic and opportunistic communications as well as papers describing prototype implementations and deployments. Topics of interest for AOC 2014 include, but are not limited to: * Routing, transport, and reliability issues * Techniques for data dissemination and replication * Applications and middleware support, mobile social networking applications * Mobility models and statistical analysis of mobility traces * Context and social awareness mechanisms and algorithms * Co-existence of opportunistic networks with infrastructure mobile wireless networks * Service composition in autonomic and opportunistic networks * Cognition-driven information processing and decision making * Performance modelling, scaling laws, and fundamental limits for autonomic and opportunistic communications * Game-theoretical insights to the operation of autonomic and opportunistic networks * Participatory and urban sensing in autonomic and opportunistic networks * Trust, security, and reputation * Autonomic and opportunistic communication testbeds and prototypes, measurement data from real experiments * Socio-economic models for autonomic and opportunistic communications * Mobile Social networks PAPER SUBMISSION AND PUBLICATION Papers should neither have been published elsewhere nor being currently under review by another conference or journal. Manuscripts are limited to 6 pages, single spacing, double column, and must strictly adhere to the template format. Accepted papers will appear in the symposium proceedings published by IEEE. There will be no separate workshop registration, as one single registration will cover both conference and workshops participation. At least one author of each accepted paper is required and present his/her work at the workshop. Submissions and reviews will be done through EDAS. Please submit your manuscript at http://edas.info/N16861. Extended versions of the selected workshop papers will be considered for possible fast track publication on the Computer Communications Journal (Elsevier). IMPORTANT DATES === * Full papers due: March 7, 2014 * Notification: April 15, 2014 * Workshop: June 16, 2014 ORGANIZING COMMITTEE Workshop Chairs ~~~ * Mohan Kumar, Rochester Institute of Technology, USA * Peizhao Hu, NICTA, Australia Steering Committee ~~ * Marco Conti, IIT-CNR, Italy * Silvia Giordano, SUPSI, Switzerland * Ioannis Stavrakakis, University of Athens, Greece Publicity Chairs * Olivier Mehani, NICTA, Australia * Davide Mascitti, IIT-CNR, Italy Webmaster ~ * Christoph Dwertmann, NICTA, Australia Program Committee (tentative) = * Nils Aschenbruck, University of Osnabruck, Germany * Chiara Boldrini, IIT-CNR, Italy * Eleonora Borgia
[ns] [AOC 2014] CFP - IEEE WoWMoM Workshop on Autonomic and Opportunistic Communications (AOC 2014)
- CALL FOR PAPERS Eighth IEEE WoWMoM Workshop on Autonomic and Opportunistic Communications (AOC 2014) June 16, 2014 - Sydney, Australia http://aoc2014.conference.nicta.com.au Fast Track on Computer Communication Journal http://www.elsevier.com/locate/comcom Submission Deadline --- March 7, 2014 - The recent proliferation of sensor-rich portable devices is enabling novel communication paradigms for users and contributing to the implementation of the ubiquitous computing and networking vision. Opportunistic networking represents a key communication paradigm for this vision. Either as a standalone communication mode or as a complement to infrastructure-based communication, opportunistic networking leverages the mobility of end users to enhance their ability to communicate in the absence of reliable end-to-end connectivity. Opportunistic networking opens up many possibilities but also poses countless new challenges. The goal of the AOC 2014 workshop is to serve as a forum for researchers, professionals, application developers, and other experts from both academia and industry to exchange new ideas, discuss new solutions, and share their experiences. As with previous editions, this year's workshop is particularly interested in novel research directions, such as service composition techniques, co-existence with infrastructure networks, and insights from game theory, social networking analysis, and cognitive psychology. The workshop will solicit original papers addressing theoretical and practical aspects of autonomic and opportunistic communications as well as papers describing prototype implementations and deployments. Topics of interest for AOC 2014 include, but are not limited to: * Routing, transport, and reliability issues * Techniques for data dissemination and replication * Applications and middleware support, mobile social networking applications * Mobility models and statistical analysis of mobility traces * Context and social awareness mechanisms and algorithms * Co-existence of opportunistic networks with infrastructure mobile wireless networks * Service composition in autonomic and opportunistic networks * Cognition-driven information processing and decision making * Performance modelling, scaling laws, and fundamental limits for autonomic and opportunistic communications * Game-theoretical insights to the operation of autonomic and opportunistic networks * Participatory and urban sensing in autonomic and opportunistic networks * Trust, security, and reputation * Autonomic and opportunistic communication testbeds and prototypes, measurement data from real experiments * Socio-economic models for autonomic and opportunistic communications * Mobile Social networks PAPER SUBMISSION AND PUBLICATION Papers should neither have been published elsewhere nor being currently under review by another conference or journal. Manuscripts are limited to 6 pages, single spacing, double column, and must strictly adhere to the template format. Accepted papers will appear in the symposium proceedings published by IEEE. There will be no separate workshop registration, as one single registration will cover both conference and workshops participation. At least one author of each accepted paper is required and present his/her work at the workshop. We will use a free submission system for processing the submissions and reviews. Extended versions of the selected workshop papers will be considered for possible fast track publication on the Computer Communications Journal (Elsevier). IMPORTANT DATES === * Full papers due: March 7, 2014 * Notification: April 15, 2014 * Workshop: June 16, 2014 ORGANIZING COMMITTEE Workshop Chairs ~~~ * Mohan Kumar, Rochester Institute of Technology, USA * Peizhao Hu, NICTA, Australia Steering Committee ~~ * Marco Conti, IIT-CNR, Italy * Silvia Giordano, SUPSI, Switzerland * Ioannis Stavrakakis, University of Athens, Greece Publicity Chair ~~~ * Olivier Mehani, NICTA, Australia * Davide Mascitti, IIT-CNR, Italy Webmaster ~ * Christoph Dwertmann, NICTA, Australia Program Committee (tentative) = * Nils Aschenbruck University of Osnabruck, Germany * Chiara Boldrini IIT-CNR, Italy * Eleonora Borgia IIT-CNR, Italy * Vania Conan Thales, France * Serge Fdida UPMC, Paris VI, France * Laura Galluccio University of Catania, Italy * Tristan Henderson University of St. Andrews, UK * Kyunghan Lee North Carolina State University
Re: [ns] ECN enabling
Thanks for the reply, i've just found the problem, i haven't included the Flags header and no error occurs but the results was totally wrong then my module to use ecn have to set the ECN bit in the IP header (can i do the same things that are done by the RED queue management?) kind regards Davide 2008/12/18 Sally Floyd sallyfl...@mac.com: Davide - -- Forwarded message -- From: Davide jimi...@gmail.com Date: 2008/12/17 Subject: ECN enabling To: ns-users ns-users@isi.edu hi, i'm using tcp reno and i want to turn on the ecn_ feature. i'm using all module that don't use this information (the queue are all drop tail) and only one module can set this flag. to enable ecn i used this function Agent/TCP set ecn_ 1 and even if my module don't send any ecn notification the result of the simulation are totally different from the case with disabled ecn there is something else that i have to know? i've also took a look inside the test suite but in that case the ecn notification are generated from the RED queue management any help appreciated One thing to do would be to look at the trace file, and see if any packets have the Congestion Experienced bit set in the ECN field of the IP header. From the manual, the flags in the trace file are as follows: The next field contains the flags, which not used in this example. The flags are defined in the flags[] array in trace.cc. Four of the flags are used for ECN: ``E'' for Congestion Experienced (CE) and ``N'' for ECN-Capable-Transport (ECT) indications in the IP header, and ``C'' for ECN-Echo and ``A'' for Congestion Window Reduced (CWR) in the TCP header. For the other flags, ``P'' is for priority, and ``F'' is for TCP Fast Start. If the Congestion Experienced bit is not being set, the next thing would be to see if TCP is setting the ECN-Echo bit. It is possible that when TCP is ECN-capable, the TCP implementation in ns2 uses ECN-Echo even when Congestion Experienced is never set by any routers along the path - I forget exactly. If so, it could affect TCP performance. It is also the case that different runs of a simulation can get different results because they use different seeds for the random number generator... - Sally http://www.icir.org/floyd/
[ns] get current RTO from TCP agent
how to get current RTO from TCP agent? i haven't found any suitable binded variable and i don't know how to do that any help appreciated Davide
[ns] Trace the sequence number of received TCP packets
I'm using ns2 with nsmiracle extension. i've been already able to trace the congestion window (i'm exploiting some tips coming from nsmiracle samples). now i don't know how to trace the sequence number of received packets at the TCPSink any suggestion? BR Davide
[ns] Segmentation fault
this istruction give to me a Segmentation fault: $data(0) attach-agent $tr(S,0,0) where $data(0) has been just defined as FTP application and $tr(S,0,0) is a TCP Module provided by ns miracle Note that the same scheme has been used in the sample dei80211mr_infrastruct_plus_wired_tcp.tcl in the sample directory of nsmiracle I don't know which is the problem and i've sent this mail to both the ML cheers Davide
[ns] how to replace a line in the routing table
i'm using manual routing but if i use the delete-route command the packet addressed to the $dst will be dropped by the $nullagent how to solve this problem? Davide
[ns] what's appen when you type $ns node
hi @ all, i'm learning to use ns-2 and i need to understand as well as possible how a normal wired node works. i've already read the manual section about nodes but when i'm trying to analize the Simulator instproc node i haven't understood how the node can be created, what is the node_factory_ and then i don't know how to ad another object between the node entry and the classifier thaks in advance Davide
[ns] error using rtproto Manual
With that network topology
#
# Create Network Topology #
#
#
# S(0)
# ME(0)--eNB0 /
#\/
# \ /
# ME(1) R0---S(1)
# \ / \ .
#\ /\ .
# ME(2)--eNB1 \ .
#. / S(val(ser_num))
#. /
# ME(val(ME_num))
using the manual routing protocol with that configuration
# Routing for Server nodes
for {set i 0} {$i $val(ser_num)} {incr i} {
[$S($i) get-module Manual] add-route-to-adj-node -default $R0
}
# Routing for Router node
$R0 add-route [$ME(0) id] $eNB0
for {set i 1} {$i = $val(ME_num)} {incr i} {
$R0 add-route [$ME($i) id] $eNB1
}
for {set i 0} {$i $val(ser_num)} {incr i} {
[$R0 get-module Manual] add-route-to-adj-node $S($i)
}
# Routing for eNodeB nodes
[$eNB0 get-module Manual] add-route-to-adj-node $ME(0)
for {set i 1} {$i = $val(ME_num)} {incr i} {
[$eNB1 get-module Manual] add-route-to-adj-node $ME($i)
}
for {set i 1} {$i $val(ser_num)} {incr i} {
$eNB0 add-route [$S($i) id] $R0
$eNB1 add-route [$S($i) id] $R0
}
# Routing for MEs nodes
[$ME(0) get-module Manual] add-route-to-adj-node -default $eNB0
for {set i 1} {$i = $val(ME_num)} {incr i} {
[$ME($i) get-module Manual] add-route-to-adj-node -default $eNB1
}
i get this error:
ns: _o537 runq 0.001: wrong # args: should be compute-all self class proc
node
(Agent/rtProto init line 1)
invoked from within
compute-all init
(Class create line 1)
invoked from within
Agent/rtProto/Manual create compute-all
(eval body line 1)
invoked from within
eval [list $self] create [list $m] $args
(procedure Agent/rtProto/Manual line 5)
(Class unknown line 5)
invoked from within
Agent/rtProto/$i compute-all
(procedure _o11 line 4)
(RouteLogic notify line 4)
invoked from within
[$ns_ get-routelogic] notify
(procedure _o512 line 6)
(Object next line 6)
invoked from within
$self next
(procedure _o512 line 2)
(rtModel/Manual notify line 2)
invoked from within
$obj notify
(procedure _o537 line 12)
(rtQueue runq line 12)
invoked from within
_o537 runq 0.001
but i don't know wat's the problem
can you help me?
Davide
Re: [ns] recv() function in ns2 !
Thanks again for your time and excuse me if i'm bugging you everyday... if i'm thinking in in the right way i've understood that i have to modify the recv() function of the routing protocol because i want to modify the behaviour of an internal node of a wired network. i'm using the Session routing protocol but i havent found in the list that you've sent to me the class that describe this Tell me the right path to choose Davide 2008/10/25 Mubashir Rehmani [EMAIL PROTECTED] Hi davide, To deal with packet by packet handling when a new packet is received by the node, you need to modify the recv() function, which you can found in the following files: - RECV : WirelessPhyhttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classWirelessPhy.htm#WirelessPhyx3WirelessPhyx1 - recv() : TcpApphttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classTcpApp.htm#TcpAppa2, SimpleTcpAgenthttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classSimpleTcpAgent.htm#SimpleTcpAgenta2, HttpInvalAgenthttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classHttpInvalAgent.htm#HttpInvalAgenta1, TraceFilehttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classTraceFile.htm#TraceFiled0, DequeTracehttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classDequeTrace.htm#DequeTracea2, Tracehttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classTrace.htm#Tracea3, TraceIpMachttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classTraceIpMac.htm#TraceIpMaca1, TraceIphttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classTraceIp.htm#TraceIpa1, CMUTracehttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classCMUTrace.htm#CMUTracea2, toraAgenthttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classtoraAgent.htm#toraAgenta1, TrafficGeneratorhttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classTrafficGenerator.htm#TrafficTracea5, SnoopQueueEDrophttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classSnoopQueueEDrop.htm#SnoopQueueEDropa0, SnoopQueueTaggerhttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classSnoopQueueTagger.htm#SnoopQueueTaggera0, SnoopQueueDrophttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classSnoopQueueDrop.htm#SnoopQueueDropa0, SnoopQueueOuthttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classSnoopQueueOut.htm#SnoopQueueOuta0, SnoopQueueInhttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classSnoopQueueIn.htm#SnoopQueueIna0, MeasureModhttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classMeasureMod.htm#MeasureModb0, LossMonitorhttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classLossMonitor.htm#LossMonitora2, TfrcAgenthttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classTfrcAgent.htm#TfrcAgenta1, TfrcSinkAgenthttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classTfrcSinkAgent.htm#TfrcSinkAgenta1, VegasTcpAgenthttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classVegasTcpAgent.htm#VegasTcpAgenta2, NewRenoTcpAgenthttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classNewRenoTcpAgent.htm#NewRenoTcpFsAgenta12, RenoTcpAgenthttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classRenoTcpAgent.htm#TcpRenoAsymAgenta7, TcpAgenthttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classTcpAgent.htm#TcpSessionAgenta45, DelAckSinkhttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classDelAckSink.htm#DelAckSinka1, TcpSinkhttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classTcpSink.htm#TcpSinka1, TcpSessionAgenthttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classTcpSessionAgent.htm#TcpSessionAgenta17, Sack1TcpAgenthttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classSack1TcpAgent.htm#Sack1TcpAgenta2, SackRHTcpAgenthttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classSackRHTcpAgent.htm#SackRHTcpAgenta2, RFC793eduTcpAgenthttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classRFC793eduTcpAgent.htm#RFC793eduTcpAgenta3, RBPRenoTcpAgenthttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classRBPRenoTcpAgent.htm#RBPRenoTcpAgenta1, RBPVegasTcpAgenthttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classRBPVegasTcpAgent.htm#RBPVegasTcpAgenta1, QSTcpSinkhttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classQSTcpSink.htm#QSTcpSinka2, QSNewRenoTcpAgenthttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classQSNewRenoTcpAgent.htm#QSNewRenoTcpAgenta1, IntTcpAgenthttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classIntTcpAgent.htm#IntTcpAgenta5, FullTcpAgenthttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classFullTcpAgent.htm#TahoeFullTcpAgenta0, FackTcpAgenthttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classFackTcpAgent.htm#FackTcpAgenta2, TcpAsymSinkhttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classTcpAsymSink.htm#TcpAsymSinka1, DropTargetAgenthttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classDropTargetAgent.htm#DropTargetAgenta1, AbsDelAckSinkhttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classAbsDelAckSink.htm#AbsDelAckSinka1, AbsTcpSinkhttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classAbsTcpSink.htm#AbsTcpSinka1, AbsTcpAgenthttp://www-rp.lip6.fr/ns-doc/ns226-doc/html/classAbsTcpAgent.htm
Re: [ns] ADD features to a node
thank you i've already found the files but i haven't found the packet by packet handling to introduce the new features... so, in those files, where can i find the actions that should be done everytime that a new pachet is received by the node? thanks again Davide 2008/10/24 Mubashir Rehmani [EMAIL PROTECTED] Hello Davide I think that you should modify node.cc file to add some features to a node. Regards 2008/10/24 Davide [EMAIL PROTECTED] i've a wired scenario and i want to add some features to a node...which file should i modify? the second question is: is possible to implement a wireless scenario without without implement all the protocol stack? thanks in advance Davide -- Mubashir Husain Rehmani Mobile : 00 33 (0)6 32 00 89 35
[ns] C++ code
hi, Is there a place where i can find some c++ code that can be downloaded and used as trart point for my project i have to implement a WFQ scheduler in a wired node Davide
[ns] wireless simulation considering only higher level
can be done a simulation on a wireless scenario in which only the scheduler is implemented (no mac procedures)? which are the possible parameter of a wireless node?...not only those shown in the webpage of the tutorial http://www.isi.edu/nsnam/ns/tutorial/nsscript5.html thanks Davide
[ns] WFQ implemantation
hi @ all, is it possible to implement the WFQ algorithm in ns2 ? is it possible to make some link dependent each other in terms of service time and bandwidth? i want to implement many queues, each of them goes in the same server...quite like the philosophy of a radio link but I'm interested to the tcp behavior so i cannot use the wireless nude becaus is affected by all the problems of a wireless link thanks in advance Davide
[ns] trace format of queue monitor
hi, i dont understand the queue monitor trace file...somebody help me...the sample is here: q -t 0.0200064 -s 4 -d 6 -l 40 -p 1 q -t 0.0200064 -s 4 -d 6 -l 0 -p 0 q -t 0.0802432 -s 4 -d 6 -l 1040 -p 1 q -t 0.0802432 -s 4 -d 6 -l 0 -p 0 q -t 0.0803264 -s 4 -d 6 -l 1040 -p 1 maybe: -t is time -s is source -d is destination -l is length in byte -p is number of packets Davide
[ns] $ns rtmodel-at $time (down/up) $N1 $N2 ISSUE
hi, I know that with this command i can modify the topology of the network. my problem is that i need to use this command inside a procedure (without define at $time) is there any way to do that? Davide
[ns] problem with NAM
i've installed the all-in-one package, but when i try to exec nam i take: nam: error while loading shared libraries: libstdc++-libc6.2-2.so.3: cannot open shared object file: No such file or directory what can i do to solve the problem? Davide
[ns] modify bitrate of a wired link
Hi guys, how to modify during the simulation the bitrate of a wired link according to a file? BR Davide
