[ns] Topology control in WSN
Can anyone send me examples of topology control implemented in the NS-2? Thanks in advance! [ ] -- === Dalton Cézane - Voip UFCG: 1075-2005 Mestrando em Ciência da Computação (UFCG) Bacharel em Ciência da Computação (UFCG) Técnico em Informática (ETER)
[ns] invalid command name -adhocRouting
Hello all，
It‘s a problem of Mobile IP example .The code is in the end.
When I tried run the script-infra.tcl in NS2 ,I got errors look that
[r...@redhat9 examples]# ns script-infra.tcl
num_nodes is set 3
invalid command name -adhocRouting
while executing
-adhocRouting DSDV \
(file script-infra.tcl line 191)
What should I do ? I running it both in ns.2.28 and ns.2.33 . Thanks for your
help …..
code
[TCL script--infra.tcl]
# Copyright (c) 1997 Regents of the University of California.
# All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
# 1. Redistributions of source code must retain the above copyright
#notice, this list of conditions and the following disclaimer.
# 2. Redistributions in binary form must reproduce the above copyright
#notice, this list of conditions and the following disclaimer in the
#documentation and/or other materials provided with the distribution.
# 3. All advertising materials mentioning features or use of this software
#must display the following acknowledgement:
# This product includes software developed by the Computer Systems
# Engineering Group at LawrenceBerkeley Laboratory.
# 4. Neither the name of the University nor of the Laboratory may be used
#to endorse or promote products derived from this software without
#specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
# ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
# FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
# OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
# OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
# SUCH DAMAGE.
# ==
# Options
# ==
set opt(nn) 1 ;# 1個MH
set num_wired_nodes 2 ;# 2個有線節點
set opt(x) 670 ;# x coordinate of topology
set opt(y) 670 ;# y coordinate of topology
set opt(ftp1-start) 100.0 ;#開始傳送ftp
set opt(stop) 250 ;# 模擬結束
set opt(tr-ns)infra-out.tr ;#設定trace file名稱
set opt(tr-nam) infra-out.nam ;#設定nam名稱
# ==
# MAC
# ==
Mac/802_11 set dataRate_2.0e6 ;# 傳送速度2Mbps
Mac/802_11 set RTSThreshold_3000 ;# 不使用RTS/CTS
# ==
# Nodes
# ==
set ns_ [new Simulator]
$ns_ node-config -addressType hierarchical ;# 使用階層式的定址方式
AddrParams set domain_num_ 3 ;# 設定3個domain: wired, wireless, wireless
lappendcluster_num 2 1 1 ;# 設定2個clusters for wired
domain,1個給wireless 1, 1個給wireless 2
AddrParams set cluster_num_ $cluster_num
lappendeilastlevel 1 1 2 1;# 設定一個節點給wired domain, cluster 1, 一個節點給
wired domain, cluster 2
;# 設定兩個節點給wireless 1, cluster 1, 一個節點給wireless
2, cluster 1
AddrParams set nodes_num_ $eilastlevel ; # of each domain
set tracefd [open $opt(tr-ns) w]
set namtrace [open $opt(tr-nam) w]
$ns_ trace-all $tracefd
$ns_ namtrace-all-wireless $namtrace $opt(x) $opt(y)
set topo [new Topography]
$topoload_flatgrid $opt(x) $opt(y)
create-god [expr $opt(nn) + 2]
# 2 for HA and FA
#---
# wired nodes
#---
#設定有線節點
set temp {0.0.0 0.1.0} ;# hierarchical addresses
for {set i 0} {$i $num_wired_nodes} {incri} {
set W($i) [$ns_ node [lindex $temp $i]]
}
#---
# hybrid and wireless nodes
#---
$ns_ node-config-mobileIP ON \
-adhocRouting DSDV \
-llType LL \
-macType Mac/802_11 \
-ifqType Queue/DropTail/PriQueue \
[ns] Generation of packets with spoofed source address
Hi there, Does anyone know how to generate packets with spoofed source IP addresses (used in DDoS attacks) in ns-2? If so, please share your knowledge.
[ns] IPv6-QoS and NS2 and NS3
Dear all, I am in the stage of choosing a simulator software however I need to consult with the experttes in this case and open up the discussion on IPv6 QoS.. Is any one of you aware of how much we can rely on NS2 for simulating the IPV6 QOS issues? is there so many limitations and bugs for develpping some new model in this environment (from your point of view)? I FORFOT TO ASK HOW ABOUT NS3? BECAUSE WHEN iREVIED NS3, IT SEEMS THAT THEY ADD SOME COMPONENT FOR IPV6 ALREADY..ANY ONE HAVE ANY IDEA? Thank you and looking forward to hear your valuable comments on this Best regards Bahareh
[ns] multi channel multi interface for 802.11 by Prof. Ramon
Hi All,
I made the modifications in the Ns2.33 as given in the PDF by Prof.Ramon.
But after successful compilation when i run a simple tcl script it gives
error as listed. I am not able to find out the reason for the error.
INITIALIZE THE LIST xListHead
(_o19 cmd line 1)
invoked from within
_o19 cmd if-queue 0 _o22
invoked from within
catch $self cmd $args ret
invoked from within
if [catch $self cmd $args ret] {
set cls [$self info class]
global errorInfo
set savedInfo $errorInfo
error error when calling class $cls: $args $...
(procedure _o19 line 2)
(SplitObject unknown line 2)
invoked from within
$agent if-queue $i [$self set ifq_($i)]
(procedure _o16 line 27)
(Node/MobileNode add-target line 27)
invoked from within
$self add-target $agent $port
(procedure _o16 line 15)
(Node attach line 15)
invoked from within
$node attach $ragent [Node set rtagent_port_]
(procedure _o3 line 82)
(Simulator create-wireless-node line 82)
invoked from within
_o3 create-wireless-node
(eval body line 1)
invoked from within
eval $self create-wireless-node $args
(procedure _o3 line 23)
(Simulator node line 23)
invoked from within
$ns_ node
invoked from within
set node0 [$ns_ node]
(file multi.tcl line 52)
Please help to resolve the problem.
Thanks.
Regards
Kiran
Re: [ns] multi channel multi interface for 802.11 by Prof. Ramon
Thanks Sir, I modified the command method for AODV. Now when I run the
example I do not get any error, but nothing gets written in the trace
file/nam file.
On command window what I get is
num_nodes is set 8
INITIALIZE THE LIST xListHead
Starting Simulation...
channel.cc:sendUp - Calc highestAntennaZ_ and distCST_
highestAntennaZ_ = 1.5, distCST_ = 212.8
SORTING LISTS ...DONE!
*Scheduler: attempt to schedule an event with a NULL handler. Don't DO
that.
*Any suggestions !! Thanks for your help
Regards
Kiran
On Thu, Apr 9, 2009 at 4:34 PM, Ramon Aguero ra...@tlmat.unican.es wrote:
Hi Kiran,
I think you need to modify the command method of the AODV routing agent. I
did not include that in the AODV specific information, but you need to
make the changes as shown in the corresponding Listing for the generic
routing agent class (I am not currently looking at the howto, but I think
it was Listing 5.2).
Hope it helps,
Ramón
Hi All,
I made the modifications in the Ns2.33 as given in the PDF by Prof.Ramon.
But after successful compilation when i run a simple tcl script it gives
error as listed. I am not able to find out the reason for the error.
INITIALIZE THE LIST xListHead
(_o19 cmd line 1)
invoked from within
_o19 cmd if-queue 0 _o22
invoked from within
catch $self cmd $args ret
invoked from within
if [catch $self cmd $args ret] {
set cls [$self info class]
global errorInfo
set savedInfo $errorInfo
error error when calling class $cls: $args $...
(procedure _o19 line 2)
(SplitObject unknown line 2)
invoked from within
$agent if-queue $i [$self set ifq_($i)]
(procedure _o16 line 27)
(Node/MobileNode add-target line 27)
invoked from within
$self add-target $agent $port
(procedure _o16 line 15)
(Node attach line 15)
invoked from within
$node attach $ragent [Node set rtagent_port_]
(procedure _o3 line 82)
(Simulator create-wireless-node line 82)
invoked from within
_o3 create-wireless-node
(eval body line 1)
invoked from within
eval $self create-wireless-node $args
(procedure _o3 line 23)
(Simulator node line 23)
invoked from within
$ns_ node
invoked from within
set node0 [$ns_ node]
(file multi.tcl line 52)
Please help to resolve the problem.
Thanks.
Regards
Kiran
--
Every footstep in life is full of possibilities we just need to know our
ability to explore them
[ns] Wireless trace analysis
Can anyone tell me how to analyze wireles trace files? if some one come across any good tutorial or manual regarding wireless trace analysis using awk, perl or gnuplot, plz let me know as early as possible. Thanks!
[ns] multi channel multi interface for 802.11 by Prof. Ramon
Hi All,
I made the modifications in the Ns2.33 as given in the PDF by Prof.Ramon.
But after successful compilation when i run a simple tcl script it gives
error as listed.
INITIALIZE THE LIST xListHead
(_o18 cmd line 1)
invoked from within
_o18 cmd if-queue 0 _o21
invoked from within
catch $self cmd $args ret
invoked from within
if [catch $self cmd $args ret] {
set cls [$self info class]
global errorInfo
set savedInfo $errorInfo
error error when calling class $cls: $args $...
(procedure _o18 line 2)
(SplitObject unknown line 2)
invoked from within
$agent if-queue $i [$self set ifq_($i)]
(procedure _o15 line 27)
(Node/MobileNode add-target line 27)
invoked from within
$self add-target $agent $port
(procedure _o15 line 15)
(Node attach line 15)
invoked from within
$node attach $ragent [Node set rtagent_port_]
(procedure _o3 line 82)
(Simulator create-wireless-node line 82)
invoked from within
_o3 create-wireless-node
(eval body line 1)
invoked from within
eval $self create-wireless-node $args
(procedure _o3 line 23)
(Simulator node line 23)
invoked from within
$ns_ node
invoked from within
set node_(0) [$ns_ node]
(file test.tcl line 73)
Please help to resolve the problem.
Thanks.
Regards
Kiran
--
Every footstep in life is full of possibilities we just need to know our
ability to explore them
Re: [ns] Error : Scheduler: attempt to schedule an event with a NULL handler. Don't DO that.
Hi, Did you find the solution for the mentioned problem? plz let me know the solution, if you found it. Thanks Kiran Saikat Kundu wrote: I am new to ns and have added a new protocol in NS using the guide Adding a new unicast manet protocol in ns-2. After a lot of struggle , I managed to compile the protocol successfully. I wrote a tcl script for testing the protocol. On running the tcl script I got the following error. Scheduler: attempt to schedule an event with a NULL handler. Don't DO that. Can anyone tell me what is the cause of the error and how to solve it. Thanks in advance. -- View this message in context: http://www.nabble.com/Error-%3A-Scheduler%3A-attempt-to-schedule-an-event-with-a-NULL-handler.--Don%27t-DO-that.-tp22735986p22969949.html Sent from the ns-users mailing list archive at Nabble.com.
Re: [ns] multi channel multi interface for 802.11 by Prof. Ramon
Hi All,
The problem of NULL handler was occuring due to the forward method. In this
method Iface is not defined. If we define it in the method then it gives the
error mentioned. I replaced the Iface with rt_interface and it worked
without error.
Prof Ramon, Please correct me if I am wrong.
Thanks
Kiran
On Thu, Apr 9, 2009 at 5:09 PM, Kiran K Chauhan kiran.c...@gmail.comwrote:
Thanks Sir, I modified the command method for AODV. Now when I run the
example I do not get any error, but nothing gets written in the trace
file/nam file.
On command window what I get is
num_nodes is set 8
INITIALIZE THE LIST xListHead
Starting Simulation...
channel.cc:sendUp - Calc highestAntennaZ_ and distCST_
highestAntennaZ_ = 1.5, distCST_ = 212.8
SORTING LISTS ...DONE!
*Scheduler: attempt to schedule an event with a NULL handler. Don't DO
that.
*Any suggestions !! Thanks for your help
Regards
Kiran
On Thu, Apr 9, 2009 at 4:34 PM, Ramon Aguero ra...@tlmat.unican.eswrote:
Hi Kiran,
I think you need to modify the command method of the AODV routing agent. I
did not include that in the AODV specific information, but you need to
make the changes as shown in the corresponding Listing for the generic
routing agent class (I am not currently looking at the howto, but I think
it was Listing 5.2).
Hope it helps,
Ramón
Hi All,
I made the modifications in the Ns2.33 as given in the PDF by
Prof.Ramon.
But after successful compilation when i run a simple tcl script it gives
error as listed. I am not able to find out the reason for the error.
INITIALIZE THE LIST xListHead
(_o19 cmd line 1)
invoked from within
_o19 cmd if-queue 0 _o22
invoked from within
catch $self cmd $args ret
invoked from within
if [catch $self cmd $args ret] {
set cls [$self info class]
global errorInfo
set savedInfo $errorInfo
error error when calling class $cls: $args $...
(procedure _o19 line 2)
(SplitObject unknown line 2)
invoked from within
$agent if-queue $i [$self set ifq_($i)]
(procedure _o16 line 27)
(Node/MobileNode add-target line 27)
invoked from within
$self add-target $agent $port
(procedure _o16 line 15)
(Node attach line 15)
invoked from within
$node attach $ragent [Node set rtagent_port_]
(procedure _o3 line 82)
(Simulator create-wireless-node line 82)
invoked from within
_o3 create-wireless-node
(eval body line 1)
invoked from within
eval $self create-wireless-node $args
(procedure _o3 line 23)
(Simulator node line 23)
invoked from within
$ns_ node
invoked from within
set node0 [$ns_ node]
(file multi.tcl line 52)
Please help to resolve the problem.
Thanks.
Regards
Kiran
--
Every footstep in life is full of possibilities we just need to know our
ability to explore them
--
Every footstep in life is full of possibilities we just need to know our
ability to explore them
Re: [ns] [Ns-developers] transmission range in wifi network
Hi all, Thank you Mathieu. * * 2009/4/9 Mathieu Lacage mathieu.lac...@sophia.inria.fr On Mon, 2009-04-06 at 19:34 +0200, ichrak amdouni wrote: Hi all, I need to fix the transmission range for access points and mobile stations in an infrastructure wifi network. I mean, how to manage to let communication restricted to a given distance? I know that in the ns3.3 version, this parameter is not explicitly set, but affected by others like the TxPower and the channel loss model, but actually, I experimented multiple matching between those parameters but I have always stange results (a sta can affiliate with an APdistant of thousands of meters!!). I doubt that is the case with the default values of all parameters. Maybe you changed some parameters ? Yes, it is the case, the mac association succeed between an access point and one mobile station distant of 3000m, connectivity is however not maintained. Note that my nodes simulates vehicles running at 50km/h. Having distinct results from those of the wifi-phy-test.cc example, I wonder if this issue has a relation with other layers other than the Physical one? No, it's all a PHY layer thing. I find the hypothesis very stange but I really reproduced the same scenario as in wifi-phy-test.cc. What kind of scenario ? Could you be more explicit about what you, what you get, and what you expect from wifi-phy-test ? I am expecting to have nodes that can't see each other beyond the theoretical coverage area. For example I used the following setting: *channel.AddPropagationLoss(ns3::LogDistancePropagationLossModel,Exponent, DoubleValue(1.70)); channel.SetPropagationDelay (ns3::ConstantSpeedPropagationDelayModel); PtrYansWifiChannel chan = channel.Create (); ** wifiPhy.SetChannel (chan);* * wifiPhy.SetErrorRateModel (ns3::ErrorRateModel); wifiPhy.Set (TxPowerStart,DoubleValue(5)); wifiPhy.Set (TxPowerEnd,DoubleValue(5)); wifiPhy.Set (TxPowerLevels,UintegerValue (1)); wifiPhy.Set (TxGain,DoubleValue (2)); wifiPhy.Set (RxGain,DoubleValue (2)); *This make connection impossible beyond 250m, but the problem now is that packet transfert failure is important due to the condition:* (m_random.GetValue () snrPer.per** ) *at the physical layer when sending probe responses.* * May I missing something? - Did someone experiment this issue especially in high mobiliy network? or have an idea to deal with it differently? - Is the transmission range explicitly set in ns 3.4? If yes, which files were modified? No, ns-3.4 has no support for this. A patch to add a range-based PHY model would be welcome. Mathieu Best Regards. Ichrak.
[ns] how to interpret file output setdest for to generate graphs of simulation
I need to demonstrate trough graphs the rate of delivery of protocols AODV and DSR (x axis of graphs) compared with pause time (y axis of graphs) generate by commands setdest. How I make this? I already have the output of setdest but I don't know to interpret. Thanks.
Re: [ns] [Ns-developers] transmission range in wifi network
On Thu, 2009-04-09 at 15:59 +0200, ichrak amdouni wrote: I doubt that is the case with the default values of all parameters. Maybe you changed some parameters ? Yes, it is the case, the mac association succeed between an access point and one mobile station distant of 3000m, connectivity is however not maintained. Note that my nodes simulates vehicles running at 50km/h. As I said, I don't believe that the default parameter values allow any kind of packet reception at 3000m. Here is what I get with ns-3-dev from today: [mlac...@diese ns-3-dev]$ ./build/debug/src/devices/wifi/wifi-phy-test Psr --PacketSize=40 --TxMode=wifia-6mbs --Distance=3000 0 or: [mlac...@diese ns-3-dev]$ ./build/debug/src/devices/wifi/wifi-phy-test SizeVsRange --TargetPsr=0.0001 --TxMode=wifia-6mbs 10 199.125 50 189.214 90 182.218 130 177.554 170 174.639 210 171.918 250 172.307 290 170.947 330 169.586 370 168.226 ... To summmarize, the default parameter setup and values ensure that the probability of successful reception of packets 10bytes-long by the PHY with mode 6mbs is close to zero after 200m. If you don't get this, then, either you have a very broken version of ns-3 or you have changed some default parameter, but I have no idea which. Or, I could be wrong, but I don't have enough information to reproduce the behavior you are describing. Having distinct results from those of the wifi-phy-test.cc example, I wonder if this issue has a relation with other layers other than the Physical one? No, it's all a PHY layer thing. I find the hypothesis very stange but I really reproduced the same scenario as in wifi-phy-test.cc. What kind of scenario ? Could you be more explicit about what you, what you get, and what you expect from wifi-phy-test ? I am expecting to have nodes that can't see each other beyond the theoretical coverage area. For example I used the following setting: what is the 'theoretical' coverage area ? channel.AddPropagationLoss(ns3::LogDistancePropagationLossModel,Exponent, DoubleValue(1.70)); channel.SetPropagationDelay (ns3::ConstantSpeedPropagationDelayModel); PtrYansWifiChannel chan = channel.Create (); wifiPhy.SetChannel (chan); wifiPhy.SetErrorRateModel (ns3::ErrorRateModel); wifiPhy.Set (TxPowerStart,DoubleValue(5)); wifiPhy.Set (TxPowerEnd,DoubleValue(5)); wifiPhy.Set (TxPowerLevels,UintegerValue (1)); wifiPhy.Set (TxGain,DoubleValue (2)); wifiPhy.Set (RxGain,DoubleValue (2)); This make connection impossible beyond 250m, but the problem now is that packet transfert failure is important due to the condition: (m_random.GetValue () snrPer.per ) at the physical layer when sending probe responses. I am not sure what you are trying to achieve. Theoretically, all you need to do to adjust the transmission range is to change the tx power. Mathieu
[ns] cygwin installation problem
Hi, After installing cygwin,when i open the cygwin window,i am getting as bash 3.2$. I am not getting root or administrator.Do anyone know what the problem is? If so,please help me. Thanks in advance.
[ns] Getting the same trace file over and over?
Hi, I have very simple scenario, 5 nodes sending CBR traffic to a sink (I am only looikng at MAC layer). Every time I run the tcl file, I get the exact same trace file. However, this should not be the case since 802.11 chooses random backoff value, and, therefore, the trace should be differnt at every run. Does anyone have an idea what I am doing wrong? Thanks.
[ns] nam error urgent help needed
hi all,
whenever i m running followin simple tcl file:-
#Create a simulator object
set ns [new Simulator]
#Open the nam trace file
set nf [open out.nam w]
$ns namtrace-all
$nf
#Define a 'finish' procedure
proc finish {} {
global ns nf
$ns flush-trace
#Close the trace file
close $nf
#Execute nam on the trace file
exec nam out.nam
exit 0
}
# Insert your own code for topology creation
# and agent definitions, etc. here
#Call the finish procedure after 5 seconds simulation time
$ns at 5.0 finish
#Run the simulation
$ns run
i got nam error/ message :
bash-3.2$ nam:
[code omitted because of length]
: no event type or button # or keysym
while executing
bind Listbox MouseWheel {
%W yview scroll [expr {- (%D/120)*4}] units
}
invoked from within
if {[tk windowingsystem] eq classic || [tk windowingsystem] eq aqua} {
bind Listbox MouseWheel {
%W yview scroll [expr {- (%D)}] units
}
bind Li...
how to solve this problem please tell me as soon as possible
thanx in advance
[ns] ACCESS QUEUE LENGTH IN MAC.802.11.CC
Hi all, I am trying to access queue length in mac.802.11.cc. I tried to find an answer in the archive following : http://mailman.isi.edu/pipermail/ns-users/2003-January/028602.html but none of these proposals seems to work. Can someone guide me through this process? What am I doing wrong and what should I change? Thank you, Stratos
[ns] [Fwd: Re: big delay by MAC-802_11 bug]
Hi again Anas, I have moved this back to ns-users as it does not belong on ns-developers. Yes, that is much more informative - I'm no DSR expert, but the previous lines in the trace say you have lost the link from 25 to node 10: SSendFailure 202.663960039 _25_ 585 2 9:1 10:1 25-43 2 2 2 3 [|25 43 10 ] Ssalv 202.66396 _25_ salvaging 9 - 10 --- 585 with [(25) 30 10 ] D 202.663960039 _25_ MAC RET 585 cbr 576 [13a 2b 19 800] --- [9:1 10:1 25 43] [17] 7 2 f 202.663960039 _25_ RTR --- 585 cbr 576 [13a 2b 19 800] --- [9:1 10:1 25 30] [17] 7 2 Congestion? Out of range? You will need to investigate from here. - David Ross. QUT, Australia. (UTC+10hours) anas wrote: dear David, I have done what you have said, but I figured out that there is no packets in the queue may be there is another reason as you will see in the trace file of node 25, it works regularly and it received many data and control packets and forward it normally within the period which packet 585 is still waiting ( 202-358) I send you the trace file of 585 packet . Regards -- From: David Ross david.r...@isrc.qut.edu.au Sent: Thursday, April 09, 2009 2:04 AM To: anas saba717...@hotmail.com Subject: Re: [ns] big delay by MAC-802_11 bug Anas, if you grep out all the _25_ entries, you should be able to work out how many packets it has queued at 202 seconds (all the ones the RTR has sent less the ones the MAC has sent on) to see if this really is the problem. Like if the MAC just sent packet 100, but the RTR just queued 585, look back to see what other packet IDs are in this node and count them until you get to the one the MAC just sent at 202 seconds. Hope that helps - David Ross. anas wrote: thank you so much David so what I will try to minimize the queue length to improve my end to end delay is it right -- From: David Ross david.r...@isrc.qut.edu.au Sent: Thursday, April 09, 2009 1:35 AM To: anas saba717...@hotmail.com Cc: ns ns-users@ISI.EDU Subject: Re: [ns] big delay by MAC-802_11 bug Anas, the delay is not the MAC, it is the RTR to the MAC, which is the IFQ. The only time I see these delays is with lots of nodes and lots of queued packets, say 50 queued and each takes 3 seconds to win contention = 150 seconds for the packet to get out. - David Ross QUT, Australia. (UTC+10hours) anas wrote: Dear all, I have encountered a large delay end to end delay and when I checked the out put file I see some of the packets have a very large delay at MAC layer as shown below: f 202.663960039 _25_ RTR --- 585 cbr 576 [13a 2b 19 800] --- [9:1 10:1 25 30] [17] 7 2 s 358.840523771 _25_ MAC --- 585 cbr 634 [13a 1e 19 800] --- [9:1 10:1 25 30] [17] 7 2 as it appears there is about 150 second at MAC layer what is the bug here I used NS2.33 under both Linux and sygwin all of them have the same bug please help me best regards Anas
