Nabble - Network Simulator ns-2

Re: Proposing upgrade of WAF

2009-01-07T14:54:38Z

2009/1/7 raj bhattacharjea <rbhattacharjea@...>

> On Mon, Dec 29, 2008 at 1:06 PM, Gustavo Carneiro <gjcarneiro@...>wrote:
>
>> Yes, I was definitely planning to wait at least a week before merging
>> anything.
>>
>> --
>> Gustavo J. A. M. Carneiro
>> INESC Porto, Telecommunications and Multimedia Unit
>> "The universe is always one step beyond logic." -- Frank Herbert
>>
>
> It has been a week and no one more has commented. The consensus seems to
> be that the proposed changes are good. Do you have any plans for merging?

yes. Sorry, I have been sick, and with some personal time consuming
problems to solve. I'll merge in the next few days.

>
>
> --
> Raj Bhattacharjea
> Georgia Institute of Technology
> School of Electrical and Computer Engineering
> Ph.D. Candidate
> Systems Analyst
> 404.894.2955
>

--
Gustavo J. A. M. Carneiro
INESC Porto, Telecommunications and Multimedia Unit
"The universe is always one step beyond logic." -- Frank Herbert

From forum: ns-developers

ns-3.4 release plans

2009-01-07T14:34:18Z

I wish a happy new year to the ns-3 development community! With the new
year comes new plans, namely those for releasing the next version of ns3,
version 3.4 . This email is lengthy, so you can catch the short version on
the wiki:

http://www.nsnam.org/wiki/index.php/Ns-3.4

Otherwise, read on.

==Release Schedule==
The plan is to have an early merge period through January 27th, during which
proposals for new APIs and features will be reviewed and merged into the
ns-3-dev trunk. Any remaining features which have been proposed but not
fully reviewed, or for which there is no consensus, can be merged in up
until February 10th.

The rest of the month of February will be for maintainance; during this
period only P1 bugs will be fixed, and no API will change. Behavioral
changes to models not affecting API will be allowed.

>From March 1st, release candidates will be released. The bug count should
ideally be zero during this time, and any remaining bugs discovered will be
ironed out by the the 18th of March, when the final release of ns3.4 is
made.

More details follow here:
http://www.nsnam.org/wiki/index.php/Ns-3.4#The_ns-3.4_Release_Schedule

==New Features==

The planned new features for 3.4 are as follows:

1. A new tap net device which will allow ns-3 to create a Linux system
network interface through which ns-3 traffic can flow back and forth with
the real world. It is being adapted by Craig from a prototype version
Mathieu has been utilizing in demonstrations of ns3.
2. A system for assigning names to nodes. Issues of accessing nodes by
name, utilizing names for accessing trace hooks, displaying the names in
trace output, and showing the names in logging output are still being
resolved. Craig is working on this.
3. An upgrade to the waf version used in ns-3, as well as a move to a so
called "allinone" build system. The system will separate the downloading of
"optional" components (such as pybindgen and nsc) from the regular waf build
process of ns-3. Gustavo has something in the works.
4. New API for RandomVariables, adding new seeing API and new default
seeding behavior. Raj is working with Michelle Weigle and Hadi Arbabi on
this.
5. A refactoring of the IPv4 routing API. Tom is working on this.
6. More support for IPv6 (
http://mailman.isi.edu/pipermail/ns-developers/2008-July/004358.html).
Tom is working on this.
7. Behavioral changes in TCP to be RFC compliant in regards to closedown
behavior (correct FINs and RSTs). Raj is working on this.
8. Consistency of trace hooks across NetDevice types. and true PCAP
compatibility (http://www.nsnam.org/bugzilla/show_bug.cgi?id=443). Craig
is working on this.
9. Possible addition of some rigorous ns3 system tests which work without
comparing script output against known traces.

There have been no other proposals for ns-3.4. There are a group of open
issues with no committments from people to work on them. I will be pinging
people to see if they can commit to completing some of these other things.

Thanks for reading this lengthy email. Have a wonderful day everyone,
--
Raj Bhattacharjea
Georgia Institute of Technology
School of Electrical and Computer Engineering
Ph.D. Candidate
Systems Analyst
404.894.2955

From forum: ns-developers

Re: Proposing upgrade of WAF

2009-01-07T11:47:03Z

On Mon, Dec 29, 2008 at 1:06 PM, Gustavo Carneiro <gjcarneiro@...>wrote:

> Yes, I was definitely planning to wait at least a week before merging
> anything.
>
> --
> Gustavo J. A. M. Carneiro
> INESC Porto, Telecommunications and Multimedia Unit
> "The universe is always one step beyond logic." -- Frank Herbert
>

It has been a week and no one more has commented. The consensus seems to be
that the proposed changes are good. Do you have any plans for merging?

--
Raj Bhattacharjea
Georgia Institute of Technology
School of Electrical and Computer Engineering
Ph.D. Candidate
Systems Analyst
404.894.2955

From forum: ns-developers

LAN Layout help

2009-01-07T08:18:00Z

Hi Everybody,

I enclose the NAM layout of a code given as under. I am trying to simulate a LAN with CSMA/MAC/CD. The resulting diagram of the LAN is not very clear. Is there any way to shape it up properly like a LAN. I know only the orient command use with setting duplex links but here the links between the nodes are already set up.
Also, I get a warning the CSMA/MAC/CD is now out of date, what does that mean?

Hope you will write back at the earliest.

Faraz

From forum: ns-users

Re: 802.11 first changesets to comment on.

2009-01-07T06:28:43Z

On Wednesday 07 January 2009 13:40:22 Mathieu Lacage wrote:

> On Wed, 2009-01-07 at 13:35 +0100, Timo Bingmann wrote:
>
> > > > DefaultValue::Bind ("ns3::JakesPropagationLossModel::DopplerFreq",
> > > > StringValue ("0.1"));
> >
> > No, I used only default values until now. I updated my sample program,
> > but used
> > // doppler frequency shift for 5.15 GHz at 100 km/h
> > jakes->SetAttribute("DopplerFreq", DoubleValue(477.9));
>
> Federico's scripts all used 0.1. Don't ask me why.

Well, 0.1 doesn't work for me.

> > Is it correct that the Jakes model is invariant in respect to node
> > distance? Then the new plot shows the following probability density
>
> yes, I believe so.
>
> > function:
> >
> > http://idlebox.net/2008/ns-3-wifi/results/ns-3-main-propagation-loss.pdf?page=4
> >
> >
> Looks good. The key for jakes loss is that you want to see the varying
> loss over time. i.e., you should replace distance by time in your graph.
>
> Mathieu

Updated with two plots by time at different resolutions. The second shows the superimposed oscillators.
Much better this way.

Greetings
Timo

From forum: ns-developers

Re: Mac layer 802.11n

2009-01-07T05:39:17Z

> I've been studying EDCA some time now, and will be implementing it for my thesis.
> We really should somehow coordinate our efforts.

Yeah!At the moment i'm discussing with ns3 developers about the best way
to implement aggregation and blockack features. I think that, for EDCA,
should be great to use DcfManager class. Let me know how you're going
to realize EDCA!

> Not as colorful and detailed, but much more hackish: (temporary screenshot)
> http://idlebox.net/2008/ns-3-wifi/results/snapshot4.png
>
> It just plots time events from debug output. Events are points in time with a duration and some labeling.

This is great!Very useful!My idea to choose AC which a packet belongs is
to use Tags. Your tool should also choose correct AC for a packet? Let
me know!

Regards,

Mirko

--
Mirko Banchi

e-mail: mk.banchi@...
e-mail: mk.banchi@...
id-jabber: mk.banchi@...
id-msn: mb11684@...

PGP key fingerprint:

308F BFB1 4E67 2522 C88E
DC69 7631 52ED 32A5 6456

smime.p7s (4K) Download Attachment

From forum: ns-developers

Re: Mac layer 802.11n

2009-01-07T05:05:47Z

> 1)I agree with you about EdcaTxopN class. Maybe the better way to reuse
> also DcfManager to implement Edca mechanism is write an interface
> DcaTxop and inherit from it.

I've been studying EDCA some time now, and will be implementing it for my thesis.
We really should somehow coordinate our efforts.

Currently I'm developing a small tool to visualize the QoS later on.

Its basic idea is based on this screenshot from Yavista
http://yavista.sourceforge.net/images/e/e5/A_screenshot_of_an_SVG_generated_from_NS%27s_XML_trace.png

Not as colorful and detailed, but much more hackish: (temporary screenshot)
http://idlebox.net/2008/ns-3-wifi/results/snapshot4.png

It just plots time events from debug output. Events are points in time with a duration and some labeling.

Greetings
Timo

From forum: ns-developers

Re: 802.11 first changesets to comment on.

2009-01-07T04:40:22Z

On Wed, 2009-01-07 at 13:35 +0100, Timo Bingmann wrote:

> > > DefaultValue::Bind ("ns3::JakesPropagationLossModel::DopplerFreq",
> > > StringValue ("0.1"));
>
> No, I used only default values until now. I updated my sample program,
> but used
> // doppler frequency shift for 5.15 GHz at 100 km/h
> jakes->SetAttribute("DopplerFreq", DoubleValue(477.9));

Federico's scripts all used 0.1. Don't ask me why.
>
> Is it correct that the Jakes model is invariant in respect to node
> distance? Then the new plot shows the following probability density

yes, I believe so.

> function:
>
> http://idlebox.net/2008/ns-3-wifi/results/ns-3-main-propagation-loss.pdf?page=4
>
>
Looks good. The key for jakes loss is that you want to see the varying
loss over time. i.e., you should replace distance by time in your graph.

Mathieu

From forum: ns-developers

Re: 802.11 first changesets to comment on.

2009-01-07T04:35:46Z

On Tuesday 06 January 2009 15:45:33 Mathieu Lacage wrote:

> On Tue, 2009-01-06 at 15:12 +0100, Mathieu Lacage wrote:
>
> > > - Added samples/main-propagation-loss.cc, which outputs a plot of all
> > > loss models (except Jakes', which I couldnt get to work right or don't
> > > understand it.)
> >
> > I am trying to look at it right now: did you try setting a non-zero
> > doppler frequency ? i.e.,
> >
> > DefaultValue::Bind ("ns3::JakesPropagationLossModel::DopplerFreq",
> > StringValue ("0.1"));

No, I used only default values until now. I updated my sample program, but used
// doppler frequency shift for 5.15 GHz at 100 km/h
jakes->SetAttribute("DopplerFreq", DoubleValue(477.9));

> Ok, the problem in your case comes from the fact that the Jakes
> propagation model relies on simulation time actually going forward to
> calculate the fast fading loss. Since I assume your code is doing a
> single loop calling GetLoss repeatedly, the loss is always a constant
> equal to the first loss and never changes. The following code gets me
> the expected output with the patch from bug 459 applied:
>
> Ptr<PropagationLossModel> model = CreateObject<JakesPropagationLossModel> ();
> Ptr<MobilityModel> a = CreateObject<StaticMobilityModel> ();
> a->SetPosition (Vector (0.0, 0.0, 0.0));
> Ptr<MobilityModel> b = CreateObject<StaticMobilityModel> ();
>
> for (double x = 0; x < 2000; x+= 1)
> {
> b->SetPosition (Vector (x, 0.0, 0.0));
> double loss = model->GetLoss (a, b);
> std::cout << x << " " << loss << std::endl;
> Simulator::Stop (Seconds (1.0));
> Simulator::Run ();
> }
>
> regards,
> Mathieu

Yes, that was the problem: the Jakes model uses Simulator::Now() in it's oscillator calculations.
However Seconds(1.0) were too large time steps, I had to decrease it to 0.01 to get better results.

Is it correct that the Jakes model is invariant in respect to node distance? Then the new plot shows the following probability density function:

http://idlebox.net/2008/ns-3-wifi/results/ns-3-main-propagation-loss.pdf?page=4

I don't know enough about this model to actually verify it's results.

Greetings
Timo

From forum: ns-developers

Re: Mac layer 802.11n

2009-01-07T03:46:04Z

On Wed, 2009-01-07 at 12:25 +0100, Mirko Banchi wrote:

> Use of A-MSDU or A-MPDU should be chosen according to type of traffic.
> The idea is to implement the possibility of choose first, second or
> both.

Ok. Is it the responsability of the MAC layer to choose whether to use
A-MPDUs or is the PHY layer expected to be able to make its own choices
on its own without interference from the MAC ?

> 1)I agree with you about EdcaTxopN class. Maybe the better way to
> reuse
> also DcfManager to implement Edca mechanism is write an interface
> DcaTxop and inherit from it.

You don't need anything special to reuse DcfManager: You should be able
to instance one DcfManager, 4 DcfState, 4 EdcaTxop and associate each
DcfState to one EdcaTxop.

> 2)About BlockAck, you suggest to move storage of packets for which an
> ack hasn't been received yet in DcaTxop and i agree with you.

I think that it should be the EdcaTxop class which should be responsible
for keeping a copy of each outgoing packet to perform a retransmission
if needed. I merely suggested that the MacLow be responsible for sending
a block of packets all in one go. I would expect the MacLow to forget
about each packet as soon as it is sent on the medium, regardless of
whether the packet is acked later or not.

> > a) change the signature of MacLowTransmissionListener::GotAck to
> include
> > the sequence number of the packet we got an ack for:
> > virtual void GotAck (double snr, WifiMode txMode, uint16_t seq) =
> 0;
> > This method will be invoked by the MacLow class to notify the
> EdcaTxop
> > class of each packet whose bit is set in a received BlockAck.
> Changing the signature of
>
> virtual void MacLowTransmissionListener::GotAck(double snr, WifiMode
> txMode, uint16_t seq) = 0;
>
> involves calling it for every corretly received packet that is
> acknowledged with the BlockAck frame. Maybe is better a function like
> this?
>
> virtual void MacLowTrasmissionListener::GotBlockAck(double snr,
> WifiMode
> txMode, uint16_t *p) = 0;
>
> where p array contains sequence numbers indicated in the blockack
> bitmap.

Yes, you could do something like this but the one I suggested:
- allows you to not have to deal with an array of uint16_t (hence, not
have to allocate/deallocate it)
- allows you to not pass around a pointer

I think that both options have probably about the same performance cost
(in one case, you have to do a dynamic allocation and perform a single
function call, in the other case, you don't have to do dynamic
allocation and you perform multiple function calls) but the one I
suggested seems more simple.

> > b) add MacLowTransmissionListener::MissedAck to notify a listener
> that a
> > specific packet has been missed.
> > virtual void MissedAck (uint16_t seq) = 0;
> If we implement the function above there isn't need to add thid
> method.

It seems easier for EdcaTxop to have this method too because it saves
EdcaTxop from having to infer which packets must be retransmitted to
prepare the retransmission.

> > add MacLowTransmissionParameters::AddPacket and m_packets:
> > void AddPacket (Ptr<const Packet> packet,
> > const WifiMacHeader *hdr);
> > std::list<std::pair<Ptr<const Packet>, WifiMacHeader> > m_packets;
> Sorry but i have some problems here :( How is used m_packets? When is
> AddPacket called ?

Sample code:

EdcaTxop::Send (void)
{
MacLowTransmissionParameters params;
params.[...]
params.AddPacket (p1, h1);
params.AddPacket (p2, h2);
m_low->StartTransmission (params, m_listener);
}

MacLowTransmissionParameters contains all the parameters to apply to a
set of packets to transmit. This, of course, will work only if all
packets share the same tx parameters. Will it be the case for you ?

Finally, I wanted to point out that if you really care about merging
your work in ns-3 itself, it is very important to proceed in small steps
and not try to merge/implement all features at once: I would suggest
that you first define a couple of clear milestones with subsets of the
full functionality and that we try to merge each of these incrementally.

regards,
Mathieu

From forum: ns-developers

Re: Mac layer 802.11n

2009-01-07T03:25:11Z

>
> I also looked briefly at the aggregation support and its interaction
> with the rate control code but I have to confess that I am not too
> familiar with the latest 802.11n spec (I did get a copy of draft 7) so,
> I have a question for you too :) What is the difference between MSDU and
> MPDU aggregation ? When do you use one or the other ?
>
> thanks a lot for getting started on this project !
Hi Mathieu,

MSDU aggregation is performed at Mac Layer and MPDU aggregation is
performed at Physical Layer.

A-MSDU:

- at every packet (MSDU), received from LLC that will be part of the
A-MSDU, is added an A-MSDU subframe header.
- all resulting packets are concatenated and is added only one MAC
header. Bit 7 of QoS control field in MAC header indicates the presence
of an A-MSDU.

Obviously all packets must have the same Destination Address and must
belong to the same Access Class (they've same TID).

A-MPDU:

this aggregation consists in concatenate more packets received from Mac
Layer (each of which with own MAC header) in a single packet with a
single PLCP header and a single PLCP preamble.

A-MPDU and A-MSDU can be used togheter at the same time.

Use of A-MSDU or A-MPDU should be chosen according to type of traffic.
The idea is to implement the possibility of choose first, second or both.

--------------------------------------------------------------------------------------------

1)I agree with you about EdcaTxopN class. Maybe the better way to reuse
also DcfManager to implement Edca mechanism is write an interface
DcaTxop and inherit from it.

2)About BlockAck, you suggest to move storage of packets for which an
ack hasn't been received yet in DcaTxop and i agree with you.
> a) change the signature of MacLowTransmissionListener::GotAck to include
> the sequence number of the packet we got an ack for:
> virtual void GotAck (double snr, WifiMode txMode, uint16_t seq) = 0;
> This method will be invoked by the MacLow class to notify the EdcaTxop
> class of each packet whose bit is set in a received BlockAck.
Changing the signature of

virtual void MacLowTransmissionListener::GotAck(double snr, WifiMode
txMode, uint16_t seq) = 0;

involves calling it for every corretly received packet that is
acknowledged with the BlockAck frame. Maybe is better a function like this?

virtual void MacLowTrasmissionListener::GotBlockAck(double snr, WifiMode
txMode, uint16_t *p) = 0;

where p array contains sequence numbers indicated in the blockack bitmap.
> b) add MacLowTransmissionListener::MissedAck to notify a listener that a
> specific packet has been missed.
> virtual void MissedAck (uint16_t seq) = 0;
If we implement the function above there isn't need to add thid method.
> c) add to MacLowTransmissionListener::MissedAck (void) that this method
> is invoked if we missed an ack within ack timeout and that in case of
> block ack transfers, this notifies that the tx side has not received a
> blockack as requested by a block ack req.
Ok!

> d) add a MacLowTransmissionParameters::EnableBlockAck, MustWaitBlockAck,
> and ACK_BLOCK_ACK to m_wait_ack:
> void EnableBlockAck (void);
> bool MustWaitBlockAck (void);
> enum {
> ACK_NONE,
> ACK_NORMAL,
> ACK_FAST,
> ACK_SUPER_FAST,
> ACK_BLOCK_ACK
> } m_waitAck;

Ok!
> add MacLowTransmissionParameters::AddPacket and m_packets:
> void AddPacket (Ptr<const Packet> packet,
> const WifiMacHeader *hdr);
> std::list<std::pair<Ptr<const Packet>, WifiMacHeader> > m_packets;

Sorry but i have some problems here :( How is used m_packets? When is
AddPacket called ?
> f) change the signature of MacLow::CalculateTransmissionTime and
> MacLow::StartTransmission:
>
> Time CalculateTransmissionTime (MacLowTransmissionParameters
> const¶meters) const;
>
> void StartTransmission (MacLowTransmissionParameters parameters,
> MacLowTransmissionListener *listener);
Ok!

I'd like to know what you think about this!
Thank you very much for your consideration and collaboration :-)

Regards,

Mirko

--

Mirko Banchi

e-mail: mk.banchi@...
e-mail: mk.banchi@...
id-jabber: mk.banchi@...
id-msn: mb11684@...

PGP key fingerprint:

308F BFB1 4E67 2522 C88E
DC69 7631 52ED 32A5 6456

smime.p7s (4K) Download Attachment

From forum: ns-developers

Re: output of ./waf --regression

2009-01-06T22:54:44Z

On Tue, 2009-01-06 at 21:43 -0800, Tom Henderson wrote:

> these are artifacts of tutorial scripts second.cc and third.cc being
> added to the regression tests, and these tutorial scripts make use of
> the logging facilities. These could probably be quieted in the
> regression by adding an option to disable logging and plumbing it into
> the regression test-second.py.

even better would be to dump the stdout of each regression script into a
specific regression trace and compare these during waf --regression. I
would suggest that whoever did this change should be responsible for
fixing the output :)

Mathieu

From forum: ns-developers

Re: output of ./waf --regression

2009-01-06T21:43:06Z

Mathieu Lacage wrote:

> hi,
>
> I just noticed that the output of ./waf --regression is a bit more
> verbose than it should be:
>
> [mathieu@localhost ns-3-dev]$ ./waf --regression
> Entering directory `/home/mathieu/code/ns-3-dev/build'
> Compilation finished successfully
> ========== Running Regression Tests ==========
> Synchronizing reference traces using Mercurial.
> Pulling http://code.nsnam.org/ns-3-dev-ref-traces from repo.
> PASS test-csma-bridge
> PASS test-csma-broadcast
> PASS test-csma-multicast
> PASS test-csma-one-subnet
> PASS test-csma-packet-socket
> PASS test-csma-ping
> PASS test-csma-raw-ip-socket
> PASS test-csma-star
> PASS test-dynamic-global-routing
> PASS test-global-routing-slash32
> PASS test-ns2-mob
> PASS test-realtime-udp-echo
> Note the 3 messages below
> Sent 1024 bytes to 10.1.2.4
> Received 1024 bytes from 10.1.1.1
> Received 1024 bytes from 10.1.2.4
> PASS test-second
> PASS test-simple-error-model
> PASS test-simple-global-routing
> PASS test-simple-point-to-point-olsr
> PASS test-static-routing-slash32
> PASS test-tcp-large-transfer
> Skipping tcp-nsc-lfn: NSC not available.
> SKIP test-tcp-nsc-lfn
> And here again
> Sent 1024 bytes to 10.1.2.4
> Received 1024 bytes from 10.1.3.3
> Received 1024 bytes from 10.1.2.4
> PASS test-third
> PASS test-udp-echo
> PASS test-wifi-wired-bridging
> [mathieu@localhost ns-3-dev]$
>
> Did I misconfigure my system or is this expected ? If not, I will file a
> bug.

these are artifacts of tutorial scripts second.cc and third.cc being
added to the regression tests, and these tutorial scripts make use of
the logging facilities. These could probably be quieted in the
regression by adding an option to disable logging and plumbing it into
the regression test-second.py.

Tom

From forum: ns-developers

802.11n MIMO support with ns2

2009-01-06T21:01:38Z

Dear ns2 users,

This is my second post relating to the same topic.
I was wondering if there is some exsistent code or hints to write a
patch to incorporate MIMO support in ns2.

Recently I saw some emails dealing with ns3 and 802.11n
implementation by people from Univeristy of Florance.
When available, it will be a big contribution according to me.

Can somebody please gives some ideas and thoughts.

All help is appreciated.

Regards,
Lochan

From forum: ns-users

Re: how can i change the pause time parameters?

2009-01-06T16:21:12Z

I was just questioning: Will that guy say: "hey, this is the same answer!"?

I tell you: It is not. Read your text and you'll see how rude It was.

I helped him. Twice. And I'm here to help him many more times, to
answer many more questions (if I know the answer).

I will not read your message because probably it doesn't matter. This ends here.

You come from a excelent country, with good schools, and have an well
known, incredible, knowledge of the inside NS-2 and NS-3. So, you can
help people more than anyone.

Please, realize that many students in here had a quarter of your
opportunities. What they need is incentive.

I propose you forget about it, remove the "checking for intelligent
life... not found" from your email sign, and help us.

Sidney Doria

UFCG / BRAZIL

2009/1/6 Hagen Paul Pfeifer <hagen@...>:

> * Sidney Doria | 2009-01-06 20:19:16 [-0300]:
>
>
>>Ok, the answers are here, but I suggest you to google it a bit more! :)
>
> ;-) that was that what I told you some months ago! OK, a little bit more
> unkindly (but that was not my suggestion). But you see, a lot of questions
> here are superfluous and a google search is much more effective as to post
> here (this belongs to a big part of all questions here).
>
> Anyway, I must smile on myself where I read your sentence! ;-)
>
>
> Best regards and have a nice week!
>
> Hagen
>
>
> --
> [...]
> checking for intelligent life... not found
> [...]
> [aus 'configure' von GIMP-1.2.2]
>
>

--
Sidney Doria
Redes ad hoc móveis
Doutorado em Computação
UFCG
Brasil

"Nessa jornada, o conhecimento será o seu escudo..."
(Mestre dos Magos no episódio do grimoire de ouro)

From forum: ns-users

Re: how can i change the pause time parameters?

2009-01-06T15:19:16Z

Ok, the answers are here, but I suggest you to google it a bit more! :)

http://web.syr.edu/~dchen02/FAQ.txt
------------------------------------------------------
Question 6:

How to set up the wireless bandwidth (such as 802.11 a,b,g) in NS2?

Answer:

In ns2.26 and ns2.27, you can change (basicRate_ and dataRate_ ):

Mac/802_11 set basicRate_ 1Mb
Mac/802_11 set dataRate_ 11Mb

in your tcl script.

FHSS (IEEE802.11)
Mac/802_11 set SlotTime_ 0.000050 ;# 50us
Mac/802_11 set SIFS_ 0.000028 ;# 28us
Mac/802_11 set PreambleLength_ 0 ;# no preamble
Mac/802_11 set PLCPHeaderLength_ 128 ;# 128 bits
Mac/802_11 set PLCPDataRate_ 1.0e6 ;# 1Mbps
Mac/802_11 set dataRate_ 1.0e6 ;# 11Mbps
Mac/802_11 set basicRate_ 1.0e6 ;# 1Mbps

DSSS (IEEE802.11b)
Mac/802_11 set SlotTime_ 0.000020 ;# 20us
Mac/802_11 set SIFS_ 0.000010 ;# 10us
Mac/802_11 set PreambleLength_ 144 ;# 144 bit
Mac/802_11 set PLCPHeaderLength_ 48 ;# 48 bits
Mac/802_11 set PLCPDataRate_ 1.0e6 ;# 1Mbps
Mac/802_11 set dataRate_ 11.0e6 ;# 11Mbps
Mac/802_11 set basicRate_ 1.0e6 ;# 1Mbps

Note:

-if using the short preamble option: you can change the line as:
Mac/802_11 set PreambleLength_ 72

- # frequency is 2.4 GHz
Phy/WirelessPhy set freq_ 2.4e+9
# transmit power
Phy/WirelessPhy set Pt_ 3.3962527e-2
# Receive sensitivity.
Phy/WirelessPhy set RXThresh_ 6.309573e-12
Phy/WirelessPhy set CSThresh_ 6.309573e-12

( *** HEY SARYM ***, READ THIS)
Note that the radio range that results from this configuration may or may
not coincide with open field tests. If you want setup a specific range,
use the program ~/indep-utils/propagation/threshold.cc to obtain the
desired RXThresh_ (rx sensitivity) based on the above frequency, transmit
power and your desired range.

802.11g:

#define DSSS_CWMin 15
#define DSSS_CWMax 1023
#define DSSS_SlotTime 0.000009
#define DSSS_CCATime 0.000003
#define DSSS_RxTxTurnaroundTime 0.000002
#define DSSS_SIFSTime 0.000016
#define DSSS_PreambleLength 96
#define DSSS_PLCPHeaderLength 40
#define DSSS_PLCPDataRate 6.0e6 // 6Mbps
#define DSSS_MaxPropagationDelay 0.0000005 // 0.5us

Note: bandwidth is different with achievable throughput.

- In NS ACK are always sent at 1Mbps
- NS use always the long PLCP preamble format sent at 1Mbps
- by default NS uses RTS/CTS handshake
- Packet's size has also an impact in the % of overhead.

All this factor can bound the achievable throughput
---------------------------------------------------------------------------------------------------

Hope to be useful,

Sidney Doria

UFCG / BRAZIL

2009/1/6 sarym binome <binome_ini@...>:

> hi sideny
> please show me exactly where can i do that (about radio range )
> set ns_ [new Simulator]
>
> set topo [new Topography]
>
> set val(chan) Channel/WirelessChannel
> set val(prop) Propagation/TwoRayGround
> set val(ant) Antenna/OmniAntenna
> set val(ll) LL
> set val(ifq) Queue/DropTail/PriQueue
> set val(x) 670 ;# X dimension of the topography
> set val(y) 670 ;# Y dimension of the topography
> set val(ifqlen) 50
> set val(seed) 0.0
> set val(netif) Phy/WirelessPhy
> set val(mac) Mac/802_11
> set val(rp) AODV
> set val(nn) 20
> set val(cp) "cbr-20-test.cbr"
> set val(sc) [lindex $argv 0]
> set val(stop) 200.0
>
>
> for {set i 0} {$i < $val(nn) } { incr i} {
> set node_($i) [$ns_ node]
> $node_($i) random-motion 0
> }
> thanks
>
>> Date: Tue, 6 Jan 2009 18:29:46 -0300
>> From: ssdoria@...
>> To: binome_ini@...
>> Subject: Re: [ns] how can i change the pause time parameters?
>>
>> About the pause time I don't know, but about the radio range 250m is
>> the default. This value is initiated in the TCL file, in a loop to
>> create all nodes (with same parameters).
>>
>> Sidney Doria
>>
>> UFCG / BRAZIL
>>
>> 2009/1/6 sarym binome <binome_ini@...>:
>> >
>> >
>> > hello
>> > how can i change the pause time parameters without creating a lot of
>> > scenario file and change the -p (when we use the setdest) ? is it possible
>> > (how can i do it ?)
>> > how can i set the radio range = 250m , where can i initiate this
>> > variable ?
>> > best regards
>> >
>> > _________________________________________________________________
>> > Glissez - déplacez : c'est si simple de partager vos photos sur Windows
>> > Live™ Photos !
>> > http://www.microsoft.com/windows/windowslive/photos.aspx
>> >
>>
>>
>>
>> --
>> Sidney Doria
>> Redes ad hoc móveis
>> Doutorado em Computação
>> UFCG
>> Brasil
>>
>> "Nessa jornada, o conhecimento será o seu escudo..."
>> (Mestre dos Magos no episódio do grimoire de ouro)
>
> ________________________________
> Tous vos amis discutent sur Messenger, et vous ? Téléchargez Messenger,
> c'est gratuit !

--
Sidney Doria
Redes ad hoc móveis
Doutorado em Computação
UFCG
Brasil

"Nessa jornada, o conhecimento será o seu escudo..."
(Mestre dos Magos no episódio do grimoire de ouro)

From forum: ns-users

Re: Mac layer 802.11n

2009-01-06T15:07:49Z

smime.p7s (4K) Download Attachment

From forum: ns-developers

what the Handoff Attempted error mean

2009-01-06T12:39:43Z

hello
i have this error when i simulate AODV protocol
Client 7: Handoff Attempted
best regards
sarym

_________________________________________________________________
Découvrez Windows Live Spaces et créez votre site Web perso en quelques clics !
http://spaces.live.com/signup.aspx

From forum: ns-users

how can i change the pause time parameters?

2009-01-06T12:35:11Z

hello
how can i change the pause time parameters without creating a lot of scenario file and change the -p (when we use the setdest) ? is it possible (how can i do it ?)
how can i set the radio range = 250m , where can i initiate this variable ?
best regards

_________________________________________________________________
Glissez - déplacez : c'est si simple de partager vos photos sur Windows Live™ Photos !
http://www.microsoft.com/windows/windowslive/photos.aspx

From forum: ns-users

Re: [RFC] Worker Infrastructure - Parallelization in Large

2009-01-06T11:48:26Z

On Tue, 2009-01-06 at 20:33 +0100, Hagen Paul Pfeifer wrote:

> >3) You would be my personal hero if you would modify the waf
> >build/regression system to run the regression suite using a small C++
> >program based on the WorkManager when it is available on the target
> >platform.
>
> An alternative way is something like "if sys.platform == 'win32'". The
> interesting question is _how_ to react for systems where fork(2) is not
> supported.

We support win32 through cygwin so, I am not worried about the lack of
fork.

> Should "WorkManager::Run()" blindly ignores that a parallelized execution is
> not supported and execute all registered task consecutively. This is my
> favorite solution because the simulation file is independent from the platform
> and the only disadvantage is a slower execution. My personal wish is that the
> WorkManager is totally opaque to the user.

This also sounds great.

Mathieu

From forum: ns-developers

Re: [RFC] Worker Infrastructure - Parallelization in Large

2009-01-06T11:33:55Z

* Mathieu Lacage | 2009-01-06 11:41:02 [+0100]:

Point 1 and 2 are brilliant hints, I will commit these changes soon.

>3) You would be my personal hero if you would modify the waf
>build/regression system to run the regression suite using a small C++
>program based on the WorkManager when it is available on the target
>platform.

An alternative way is something like "if sys.platform == 'win32'". The
interesting question is _how_ to react for systems where fork(2) is not
supported.

Should "WorkManager::Run()" blindly ignores that a parallelized execution is
not supported and execute all registered task consecutively. This is my
favorite solution because the simulation file is independent from the platform
and the only disadvantage is a slower execution. My personal wish is that the
WorkManager is totally opaque to the user.

Any hints, ideas?

>thanks again for your code,

You are welcome!

Hagen

From forum: ns-developers

Re: 802.11 first changesets to comment on.

2009-01-06T06:45:33Z

On Tue, 2009-01-06 at 15:12 +0100, Mathieu Lacage wrote:

> > - Added samples/main-propagation-loss.cc, which outputs a plot of all
> > loss models (except Jakes', which I couldnt get to work right or don't
> > understand it.)
>
> I am trying to look at it right now: did you try setting a non-zero
> doppler frequency ? i.e.,
>
> DefaultValue::Bind ("ns3::JakesPropagationLossModel::DopplerFreq",
> StringValue ("0.1"));

Ok, the problem in your case comes from the fact that the Jakes
propagation model relies on simulation time actually going forward to
calculate the fast fading loss. Since I assume your code is doing a
single loop calling GetLoss repeatedly, the loss is always a constant
equal to the first loss and never changes. The following code gets me
the expected output with the patch from bug 459 applied:

Ptr<PropagationLossModel> model = CreateObject<JakesPropagationLossModel> ();
Ptr<MobilityModel> a = CreateObject<StaticMobilityModel> ();
a->SetPosition (Vector (0.0, 0.0, 0.0));
Ptr<MobilityModel> b = CreateObject<StaticMobilityModel> ();

for (double x = 0; x < 2000; x+= 1)
{
b->SetPosition (Vector (x, 0.0, 0.0));
double loss = model->GetLoss (a, b);
std::cout << x << " " << loss << std::endl;
Simulator::Stop (Seconds (1.0));
Simulator::Run ();
}

regards,
Mathieu

From forum: ns-developers

Re: 802.11 first changesets to comment on.

2009-01-06T06:12:25Z

hi timo,

On Thu, 2008-11-27 at 15:53 +0100, Timo Bingmann wrote:

> - Added samples/main-propagation-loss.cc, which outputs a plot of all
> loss models (except Jakes', which I couldnt get to work right or don't
> understand it.)

I am trying to look at it right now: did you try setting a non-zero
doppler frequency ? i.e.,

DefaultValue::Bind ("ns3::JakesPropagationLossModel::DopplerFreq",
StringValue ("0.1"));

Mathieu

From forum: ns-developers

output of ./waf --regression

2009-01-06T04:11:36Z

hi,

I just noticed that the output of ./waf --regression is a bit more
verbose than it should be:

[mathieu@localhost ns-3-dev]$ ./waf --regression
Entering directory `/home/mathieu/code/ns-3-dev/build'
Compilation finished successfully
========== Running Regression Tests ==========
Synchronizing reference traces using Mercurial.
Pulling http://code.nsnam.org/ns-3-dev-ref-traces from repo.
PASS test-csma-bridge
PASS test-csma-broadcast
PASS test-csma-multicast
PASS test-csma-one-subnet
PASS test-csma-packet-socket
PASS test-csma-ping
PASS test-csma-raw-ip-socket
PASS test-csma-star
PASS test-dynamic-global-routing
PASS test-global-routing-slash32
PASS test-ns2-mob
PASS test-realtime-udp-echo
>>>>>>>
Note the 3 messages below
>>>>>>>
Sent 1024 bytes to 10.1.2.4
Received 1024 bytes from 10.1.1.1
Received 1024 bytes from 10.1.2.4
PASS test-second
PASS test-simple-error-model
PASS test-simple-global-routing
PASS test-simple-point-to-point-olsr
PASS test-static-routing-slash32
PASS test-tcp-large-transfer
Skipping tcp-nsc-lfn: NSC not available.
SKIP test-tcp-nsc-lfn
>>>>
And here again
>>>>
Sent 1024 bytes to 10.1.2.4
Received 1024 bytes from 10.1.3.3
Received 1024 bytes from 10.1.2.4
PASS test-third
PASS test-udp-echo
PASS test-wifi-wired-bridging
[mathieu@localhost ns-3-dev]$

Did I misconfigure my system or is this expected ? If not, I will file a
bug.

Mathieu

From forum: ns-developers

storing packets

2009-01-06T03:42:26Z

I want to store all packets send by a source node to destination node, so
that I can resend the missing packets. How can I store the packets sent by
source node.

Thanks for your response.

BR
Ubaid

From forum: ns-users

Re: [RFC] Worker Infrastructure - Parallelization in Large

2009-01-06T02:41:02Z

hi hagen,

Sorry for the very late answer,

On Mon, 2008-12-22 at 14:00 +0100, Hagen Paul Pfeifer wrote:
> under http://code.nsnam.org/pfeifer/ns-3-worker I published a high level
> parallelization approach. Beside a component approach, where some/several
> ns-3 subsystems works in parallel, this worker approach parallelize
> complete ns-3 instances. The major goal is to speed up a *typical
> simulation*
> with more then one successive simulation runs.

I really like the idea and I always wanted to have something like this
so, it would be really nice if we could try to merge something like this
in ns-3 itself (in contrib or core).

> The next few lines show a minimal "hello world" worker application. That
> example is generic enough to utilize all available cores at a system at
> runtime

I went through the example code, API, and implementation. Comments
below.

1) I can't see why ChunkStart/End and GetNumCores are inline so, I would
move them to worker.cc

2) I think that the API is very focused on parallelizing a single for
loop with a fixed number of iterations and the same code executing every
time. It would be nice to try to generalize that. Here is a proposal.

class WorkManager
{
public:
// register a callback which wants to do work.
void AddWork (Callback<void> worker);
// Run one worker on each core, until all workers have run.
void Run (void);
// run one worker on n cores, until all workers have run.
void Run (uint32_t n);
static uint32_t GetNCores (void);
};

class LoopWorkManager
{
public:
// register the loop callback and the total number of iterations.
void SetLoop (Callback<void,uint32_t,uint32_t> worker, uint32_t
iterations);
// run the loop callback on each core until all iterations have run
void Run (void);
// run the loop callback on n cores, until all iterations have run
void Run (uint32_t n);
static uint32_t GetNCores (void);
private:
// implement the loop manager with the work manager.
WorkManager m_manager;
};

Note: I picked WorkManager over Worker because, for me, Worker means a
single guy doing his job while here, the goal is to manage a bunch of
guys doing their job. It could be also WorkerManager but WorkManager
seemed shorter and sufficiently descriptive.

3) You would be my personal hero if you would modify the waf
build/regression system to run the regression suite using a small C++
program based on the WorkManager when it is available on the target
platform.

thanks again for your code,
Mathieu

From forum: ns-developers

Looking for LAN example in NS2

2009-01-06T02:12:20Z

Hello everyone,

I am looking for a simple LAN example in NS 2. I am following the isi tutorial but it seems to have given only the lan command structure. I am looking for a proper syntax to work out at LANs in NS2 environment.

Can some one help please?

Regards,
Faraz

From forum: ns-users

Re: NS installation (Ubuntu)

2009-01-05T23:27:12Z

I use ns-2.33 on ubuntu 8.04.1 . i remember that i solved these error by
installing some packages

Try: sudo apt-get install tcl tk libxt-dev

On Mon, Jan 5, 2009 at 4:28 AM, Bello Lawal <lawalimoriki@...> wrote:

>
> Hello,
>
> Pls. can some one help me i try to install NS2 in Ubuntu during the
> installation it gives me the following error.
>
> tcl8.3.2 configuration failed! Existing ...............
> Tcl is not part of the ns project.
>
>
>
>
>

--
Waleed Tuffaha.

From forum: ns-users

Simulation parameters

2009-01-05T22:43:07Z

Dear All,

Is there any typical or standard simulation parameters for simulating wireless ad hoc networks in ns2?

Thanks

Ghada

From forum: ns-users

Re: (A naive solution) how to set different transmit range for different node

2009-01-05T22:19:17Z

Hi All,

After hacking threshold.cc, I've known the formula used to calculate
receive
threshold (ATTENTION: threshold.cc only generates RXThresh_, NOT Pt_). I
modified
TwoRayGround formula in threshold.cc, as below :

Pr * d^4 * L
Pt = ---------------------------
Gt * Gr * (ht^2 * hr^2)

Pr is replace with RXThresh_ whose value is 3.652e-10.
If a distance is given, Pt can be calculated by above formula.
e.g.
Tx Range Pt_
100m 0.00721383
150m 0.03652
200m 0.115421
250m 0.28179
300m 0.58432
... ...
I attached modified threshold.cc renamed threshold_Pt.cc .
After compiling it, you can use like this:
./threshold_Pt -m TwoRayGround <Required TxRange>

But unluckily, if the tx range is smaller than crossover_dist (always should
be 86.1425m),
the generated Pt_ value is incorrect either using Friis or TwoRay.
If you know why, please let me know.

I've developed a simple tcl script in order to validate transmit range
with different Pt_ value. I attached this script named TxRangeTest.tcl.
The routing protocol used in the script is MFlood, which is just a simple
flooding algorithm. Trace format has been changed a little, like:

s 1.000000000 1 1.00 200.00 AGT --- 0 cbr 512 [0 0 0 0] -------
[1:0 0:0 32 0] [0] 0 0
r 1.004860003 0 0.00 200.00 AGT --- 0 MFlood 532 [mflood 1.000000000
1.00 200.00 ]
The trace format of cbr packet can be referred to NS2 manual. The explain
of trace format about
MFlood packet is below:

event = $1;
curr_time = $2;
curr_node_id = $3;
curr_position_x = $4;
curr_position_y = $5;
trace_type = $6;

pkt_seq = $8;
pkt_type = $9;
pkt_generate_time = $12;

prev_hop_position_x = $13;
prev_hop_position_y = $14;

Finally, a AWT file is used to calculate the transmit range.
#========================================================================
BEGIN {
RecvNum = 0;
final_curr_position_x = 0;
final_curr_position_y = 0;

final_prev_hop_position_x = 0;
final_prev_hop_position_y = 0;
}

{
event = $1;
curr_time = $2;
curr_node_id = $3;
curr_position_x = $4;
curr_position_y = $5;
trace_type = $6;

pkt_seq = $8;
pkt_type = $9;
pkt_generate_time = $12;

prev_hop_position_x = $13;
prev_hop_position_y = $14;

if ( event == "r" && curr_node_id == 0 && trace_type == "AGT" )
{
RecvNum++;
# printf(" %3d [Time : %f] N0(%.2f,%.2f) <---- N1(%.2f,%.2f)\n",
# RecvNum,
# curr_time,
# curr_position_x,
# curr_position_y,
# prev_hop_position_x,
# prev_hop_position_y);

final_curr_position_x = curr_position_x;
final_curr_position_y = curr_position_y;

final_prev_hop_position_x = prev_hop_position_x;
final_prev_hop_position_y = prev_hop_position_y;
}

}

END{
dx = final_prev_hop_position_x - final_curr_position_x ;
dy = final_prev_hop_position_y - final_curr_position_y ;
tx_range = sqrt(dx * dx + dy * dy) ;

printf(" \nNum of Recv pkts : %d \n", RecvNum);
printf(" \nTx Range of Node 1: %f \n", tx_range);
}

This is just a reference. You should do some changes according to
your trace file if you use other routing protocol.

Regards,
Phenix

--------------------------------------------------
From: "kavan sheth" <shethkavan@...>
Sent: Sunday, January 04, 2009 1:24 PM
To: "Phenix" <phenix_yw@...>
Subject: Re: [ns] how to set different transmit range for different node

> Hi Phenix,
>
> As far as I know threshold.cc generates particular transmission
> power(Pt_) based on the propagation model and distance specified by
> you. different propagation model have different equations for
> receiving power based on its characteristics. different equations are
> given in the threshold.cc. you can know more by studying this
> threshold.cc
>
> Kavan
>
> On 1/3/09, Phenix <phenix_yw@...> wrote:
>>
>> Hi Sidney,
>>
>> After times of trials, I've succeeded in letting different nodes own
>> different
>> Tx Range by configuring different value of Pt_ for each node. I get
>> different
>> values of Pt_ from a script:
>> # The transimssion radio range
>> Pt_ 6.9872e-4 ;# ?m
>> Pt_ 8.5872e-4 ;# 40m
>> Pt_ 1.33826e-3 ;# 50m
>> Pt_ 7.214e-3 ;# 100m
>> Pt_ 0.2818 ;# 250m
>>
>> And in my script, I have test range of 250m and 40m. It really works
>> well.
>> But It's a pity that I don't know how to obtain these values. The tool
>> threshold
>> (~ns/lidep-utils/propagation/threshold.cc) only generate RXThresh_ other
>> than Pt_.
>>
>> Is there somebody knowing how to get value of Pt_?
>>
>>
>> [Here is my test script]
>>
>> # ======================================================================
>> # Define options
>> # ======================================================================
>> set val(ifqlen) 50 ;# max packet in ifq
>> set val(nn) 2 ;# number of
>> mobilenodes
>> set val(rp) MFlood ;# routing
>> protocol,DumbAgent
>> set val(chan) Channel/WirelessChannel
>> set val(prop) Propagation/TwoRayGround
>> set val(netif) Phy/WirelessPhy
>> set val(mac) Mac/802_11
>> set val(ifq) Queue/DropTail/PriQueue
>> set val(ll) LL
>> set val(ant) Antenna/OmniAntenna
>> set val(stop) 150
>>
>> # Initialize the SharedMedia interface with parameters to make
>> # it work like the 914MHz Lucent WaveLAN DSSS radio interface
>> Phy/WirelessPhy set CPThresh_ 10.0
>> Phy/WirelessPhy set CSThresh_ 1.559e-11
>> Phy/WirelessPhy set RXThresh_ 3.652e-10
>> Phy/WirelessPhy set Rb_ 2*1e6
>> Phy/WirelessPhy set freq_ 914e+6
>> Phy/WirelessPhy set L_ 1.0
>>
>> # Pt_
>> set txpower_(0) 0.2818 ;# 250m
>> set txpower_(1) 8.5872e-4 ;# 40m
>> set txpower_(2) 7.214e-3 ;# 100m
>>
>> # ======================================================================
>> # Main Program
>> # ======================================================================
>>
>> #ns-random 0
>>
>> # Initialize Global Variables
>> set ns_ [new Simulator]
>> set tracefd [open mflood_txRange.tr w]
>> $ns_ trace-all $tracefd
>>
>> set namtrace [open mflood_txRange.nam w]
>> $ns_ namtrace-all-wireless $namtrace 1000 500
>>
>> # set up topography
>> set topo [new Topography]
>> $topo load_flatgrid 1000 500
>>
>> # Create God
>> create-god $val(nn)
>>
>>
>> # Create the specified number of mobilenodes [$val(nn)] and "attach" them
>> # to the channel.
>> # configure node
>> set channel [new Channel/WirelessChannel]
>> $channel set errorProbability_ 0.0
>>
>> $ns_ node-config -adhocRouting $val(rp) \
>> -llType $val(ll) \
>> -macType $val(mac) \
>> -ifqType $val(ifq) \
>> -ifqLen $val(ifqlen) \
>> -antType $val(ant) \
>> -propType $val(prop) \
>> -phyType $val(netif) \
>> -channel $channel \
>> -topoInstance $topo \
>> -agentTrace ON \
>> -routerTrace OFF\
>> -macTrace OFF \
>> -movementTrace OFF
>>
>> for {set i 0} {$i < $val(nn) } {incr i} {
>> Phy/WirelessPhy set Pt_ $txpower_($i)
>> set node_($i) [$ns_ node]
>> $node_($i) random-motion 0;
>> }
>>
>> # Provide initial (X,Y, for now Z=0) co-ordinates for mobilenodes
>> #
>> # N_0 <-- d ---> N_2
>> # src dst
>>
>> $node_(0) set X_ 0.0
>> $node_(0) set Y_ 200.0
>> $node_(0) set Z_ 0.0
>>
>> $node_(1) set X_ 1.0
>> $node_(1) set Y_ 200.0
>> $node_(1) set Z_ 0.0
>>
>> $ns_ at 1.5 "$node_(1) setdest 255.0 200.0 2.0"
>>
>> # Define node initial position in nam
>> for {set i 0} {$i < $val(nn)} {incr i} {
>> $ns_ initial_node_pos $node_($i) 20
>> }
>>
>> set udp_(0) [new Agent/UDP]
>> set udp_(1) [new Agent/UDP]
>> $ns_ attach-agent $node_(0) $udp_(0)
>> $ns_ attach-agent $node_(1) $udp_(1)
>>
>> set null_(0) [new Agent/Null]
>> set null_(1) [new Agent/Null]
>> $ns_ attach-agent $node_(1) $null_(0)
>> $ns_ attach-agent $node_(0) $null_(1)
>>
>> $ns_ connect $udp_(0) $null_(0)
>> $ns_ connect $udp_(1) $null_(1)
>>
>> for {set i 0} {$i < $val(nn)} {incr i} {
>> set cbr_($i) [new Application/Traffic/CBR]
>> $cbr_($i) set packetSize_ 512
>> $cbr_($i) set interval_ 2
>> $cbr_($i) set random_ 1
>> $cbr_($i) attach-agent $udp_($i)
>>
>> }
>> $ns_ at 1.0 "$cbr_(0) start"
>> $ns_ at 1.1 "$cbr_(1) start"
>>
>> # Tell nodes when the simulation ends
>> for {set i 0} {$i < $val(nn) } {incr i} {
>> $ns_ at $val(stop).0 "$node_($i) reset";
>> }
>> $ns_ at $val(stop).0 "stop"
>> $ns_ at $val(stop).01 "puts \"NS EXITING...\" ; $ns_ halt"
>> proc stop {} {
>> global ns_ tracefd namtrace
>> $ns_ flush-trace
>> close $tracefd
>> close $namtrace
>> }
>>
>> puts "Starting Simulation..."
>> $ns_ run
>>
>>
>>
>>
>> Regards,
>> Phenix
>>
>>
>> From: Sidney Doria
>> Sent: Saturday, January 03, 2009 12:01 AM
>> To: Phenix
>> Subject: Re: [ns] how to set different transmit range for different node
>>
>>
>> Hi Phenix,
>>
>>
>> In the TCL file, there's a loop for node creation. So, you can break this
>> node in a manual creation, each node with specific characteristics.
>>
>>
>> Sidney Doria
>>
>>
>> UFCG / BRAZIL
>>
>>
>> 2009/1/2 Phenix <phenix_yw@...>
>>
>>
>>
>> Hi all,
>>
>> I'd like how to set different transmit range for different node in
>> MANET.
>>
>> eg.
>> Three nodes,N0,N1 and N2 are in a line:
>> (N0) (N1) (N2)
>> |--- 200m -----| ---120m---|
>> The transmit range of N0,N1 and N2 is respectively 250m,150m,200m.
>> So packets can be passed:
>> N0 --> N1 <---> N2
>>
>> Let me know how to set different transmit range please.
>> Thank you in advance!
>>
>> Regards,
>> Phenix
>>
>>
>>
>>
>>
>> --
>> Sidney Doria
>> Redes ad hoc móveis
>> Doutorado em Computação
>> UFCG
>> Brasil
>>
>> "Nessa jornada, o conhecimento será o seu escudo..."
>> (Mestre dos Magos no episódio do grimoire de ouro)
>>
>

From forum: ns-users

Re: AWK programms

2009-01-05T19:46:46Z

Salam Alikm,

About the first point: there are two type of packets ( Data and Control ) packets. control=request+reply messages. Also I am referring you to see the NS-2 manual about Packets in NS-2.

About the second: yes

packet_id = $41; 41 column. also try study the output trace file to get more information

I advise all the beginner into NS-2 to try simple programs and scenarios.

All the best,

Mohammed AbuHajar
Master of Computer Science

________________________________
From: sarym binome <binome_ini@...>
To: mcsist@...
Sent: Monday, January 5, 2009 1:11:46 PM
Subject: RE: [ns] AWK programms

hello, salem
i prepar a simulation for AODV routing protocol, for E2E delay , i saw your example you work in application layer (AGT),

if (( $1 == "r") && ( $35 == "cbr" ) && ( $19=="AGT" )) { end_time[packet_id] = time; }
else { end_time[packet_id] = -1; }

don't we work whith pkt type ( AODV REQUEST and REPLY)??????????(i'm new and i realy don't know )
{ if (($1=="s")&&($25=="(REQUEST)")&&($17=="0]")) { time[$23,$21]=$2 ;printf ("le temps d'émission de requête : %f \n",time[$23,$21] );};

an other question about # CALCULATE DELAY
( packet_id = $41;) whay you choose $41???? is the trace file for DRS has a more than 26 column !?

thanks, best regards.

> Date: Mon, 5 Jan 2009 11:56:37 -0800
> From: mcsist@...
> To: g.hajer@...
> CC: ns-users@...
> Subject: Re: [ns] AWK programms
>
>
> Hi,
>
> About the first point: you need to check your simulation environment and parameters and try to simulate these protocol with simple simulation scenarios.
> About the second point: because I need to remove the size of the packet header from the received packet, so I need exactly to know how the size of header.
>
> All the Successes,
> Mohammed AbuHajar
> Palestine Territory, Occupied.
>
>
>
>
>
> ________________________________
> From: hajer h <g.hajer@...>
> To: mcsist@...
> Sent: Monday, January 5, 2009 1:04:41 AM
> Subject: AWK programms
>
>
> hello i am working with ns2..
> and i am loocking for some awk programme that calculate the average throughput, e-2-e delay, NRL and PDF...for all protcol AODV OLSR DSR DSDV...
> can you help me in this way...
> i have tried http://mailman.isi.edu/pipermail/ns-users/2007-August/060808.html those programme i didn't understand why they gives 0 for such protocol like DSR or DSDV...
> i have anothers questions : about the avearge thtoughut : why did you subtrain 512 ...did you calcul the average throughput for TCP traffic???
> thanks in advance...
>
>
>
>
> --
>
> "Somewhere, something incredible is waiting to be known."
>
>
>

________________________________
Téléchargez le nouveau Windows Live Messenger ! Téléchargez Messenger, c'est gratuit !

From forum: ns-users

Re: ns2 problems with simulation of lan

2009-01-05T18:42:19Z

this is bcoz of the the nam is reading the previous history of the file.
so u must delete the out.tr and out.nam both before re-running the simulation.

pingpingping wrote:

Hello,
recently I use the ns2 simulator to simulate local area network. I
write the tcl code following the manual downloaded from
http://www.isi.edu/nsnam/ns/, but I find that every time I run the
code below, the output is 1.7293548387096773Mb/s,but it shouldn't
be,because I have set the bw of the local area network as 1Mb,how can
it achieve 1.7Mb, I am quite puzzled with it
I don't kown whether there should be some more settings or some
other

the code below just simulate a lan which transmits data from node n1
to node n2,the bw between n1 and n2 is set as 1Mb
is there bugs in the code, please point them out and give me some advice, thanks a lot!
##########################################code########################
set ns [new Simulator]

#Define different colors for data flows (for NAM)
$ns color 1 Blue
$ns color 2 Red

#Open the Trace files
set file1 [open out.tr w]
set winfile [open WinFile w]
$ns trace-all $file1
#Define a 'finish' procedure
proc finish {} {
global ns file1
$ns flush-trace
close $file1
exec nam out.nam &
exit 0
}
set n1 [$ns node]
set n2 [$ns node]
set lan [$ns newLan "$n1 $n2" 1Mb 40ms LL Queue/DropTail MAC/Csma/Cd Channel]
set tcp [new Agent/TCP/Newreno]
$ns attach-agent $n1 $tcp
set sink [new Agent/TCPSink/DelAck]
$ns attach-agent $n2 $sink
$ns connect $tcp $sink
$tcp set fid_ 1
$tcp set window_ 65536
$tcp set packetSize_ 1024

#Setup a FTP over TCP connection
set ftp [new Application/FTP]
$ftp attach-agent $tcp
$ftp set type_ FTP

proc get_throughput { tcp } {
#now calculate the average throughtput (in Mb/s)
puts "[expr [$tcp set ndatapack_]*8.0/1000/124]Mb/s"
}
$ns at 1.0 "$ftp start"
$ns at 124.0 "$ftp stop"
$ns at 124 "get_throughput $tcp"
$ns at 125.0 "finish"
$ns run
########################################################

From forum: ns-users

FLOATING POINT EXECPTION

2009-01-05T18:40:46Z

Hello:I am trying to run a XCP protocol example script as follows:

---------------------------------------------
### XCP EXAMPLE TCLset lrate 0.0
Queue/XCP set tcp_xcp_on 1
Agent/TCP set minrto_ 1
set ns [new Simulator]
$ns color 1 Red
set tr_f [open out.tr w]
set nam_f [open out.nam w]
set record_f1 [open out.data1 w]
$ns trace-all $tr_f$ns namtrace-all $nam_f

### Finish procproc finish {}
{
global ns tr_f record_f1 nam_f
$ns flush-trace close $tr_f
close $record_f1 close $nam_f exec
awk { { print $1, $2 } } out.data1 > temp1.cwnd
exit 0
}
set n0 [$ns node]
set n1 [$ns node]

#### LINK# object from to bandwith delay queue
$ns duplex-link $n0 $n1 5Mb 35ms XCP

#### BOTTLENECK BUFFER
set buffer 43
$ns queue-limit $n0 $n1 [expr $buffer *1]
$ns duplex-link-op $n0 $n1 queuePos 0.5

#### TCP AGENT 1set tcp1 [new Agent/TCP/Reno/XCP]
$ns attach-agent $n0 $tcp1
set sink1 [new Agent/TCPSink/XCPSink]
$ns attach-agent $n1 $sink1
$ns connect $tcp1 $sink1$tcp1 set fid_ 1
$tcp1 set window_ 8000
$tcp1 set packetSize_ 552
set ftp1 [new Application/FTP]
$ftp1 attach-agent $tcp1
$ftp1 set type_ FTP

### Record procproc record {}
{
global ns tcp1 sink1 record_f1
set now [$ns now]
set time 0.15
set cwin1 [$tcp1 set cwnd_]
puts $record_f1 "$now [expr $cwin1*1] "
$ns at [expr $now+$time] "record "
}

$ns at 0.0 "record"
$ns at 0.0 "$ftp1 start"
$ns at 20.0 "$ftp1 stop"
$ns at 20.0 "$ns detach-agent $n0 $tcp1 ; $ns detach-agent $n1 $sink1"
$ns at 20.0 "finish"

$ns run
---------------------------------------------

I got the NS2 version 2.33 installed in Fedora 8. I have no problems with others TCP protocols. The exception normally appears when there is a division by zero. However, in the .tcl code there is nothing that can be associated with this error. How Can be this possible? Can someone help me?

THANKS in advance

DIANA
_________________________________________________________________
Life on your PC is safer, easier, and more enjoyable with Windows Vista®.
http://clk.atdmt.com/MRT/go/127032870/direct/01/

From forum: ns-users

FLOATING POINT EXECPTION

2009-01-05T18:26:04Z

Hello:

I am trying to run a XCP protocol example script as follows:---------------------------------------------### XCP EXAMPLE TCLset lrate 0.0Queue/XCP set tcp_xcp_on 1Agent/TCP set minrto_ 1set ns [new Simulator]$ns color 1 Redset tr_f [open out.tr w]set nam_f [open out.nam w]set record_f1 [open out.data1 w]$ns trace-all $tr_f$ns namtrace-all $nam_f### Finish procproc finish {} { global ns tr_f record_f1 nam_f $ns flush-trace close $tr_f close $record_f1 close $nam_f exec awk { { print $1, $2 } } out.data1 > temp1.cwnd exit 0}set n0 [$ns node]set n1 [$ns node]#### LINK# object from to bandwith delay queue $ns duplex-link $n0 $n1 5Mb 35ms XCP#### BOTTLENECK BUFFERset buffer 43# tamanho del buffer del link n1-n2$ns queue-limit $n0 $n1 [expr $buffer *1]$ns duplex-link-op $n0 $n1 queuePos 0.5#### TCP AGENT 1set tcp1 [new Agent/TCP/Reno/XCP]$ns attach-agent $n0 $tcp1set sink1 [new Agent/TCPSink/XCPSink]$ns attach-agent $n1 $sink1$ns connect $tcp1 $sink1$tcp1 set fid_ 1$tcp1 set window_ 8000$tcp1 set packetSize_ 552set ftp1 [new Application/FTP]$ftp1 attach-agent $tcp1$ftp1 set type_ FTP### Record procproc record {} { global ns tcp1 sink1 record_f1 set now [$ns now] set time 0.15 set cwin1 [$tcp1 set cwnd_] puts $record_f1 "$now [expr $cwin1*1] " $ns at [expr $now+$time] "record "}$ns at 0.0 "record"$ns at 0.0 "$ftp1 start"$ns at 20.0 "$ftp1 stop"$ns at 20.0 "$ns detach-agent $n0 $tcp1 ; $ns detach-agent $n1 $sink1"$ns at 20.0 "finish"$ns run---------------------------------------------I got the NS2 version 2.33 installed in Fedora 8. I have no problems with others TCP protocols. The exception normally appears when there is a division by zero. However, in the .tcl code there is nothing that can be associated with this error. How Can be this possible? Can someone help me? THANKS in advance DIANA
_________________________________________________________________
It’s the same Hotmail®. If by “same” you mean up to 70% faster.
http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_broad1_122008

From forum: ns-users