[ns] a talk in Berkeley reporting on the ns-3 simulator

[Sally Floyd]

Mathieu Lacage will give a talk in Berkeley this Wednesday,
May 21, with a progress report on the ns-3 simulator:


A talk by Mathieu Lacage at ICSI on Wednesday, May 21, at 2 PM.

Title:
A Progress Report on the ns-3 Network Simulator

Speaker:
Mathieu Lacage is one of the main developers for the ns-3 simulator.
He works at INRIA (the French National Institute for Research in
Computer Science and Control), and is visiting the University of
Washington for six months.

Abstract:
Intended to eventually replace the popular ns-2 simulator, ns-3 aims to
retain the successful features of ns-2, while remedying some complaints
about it. In this presentation, we will describe the design of ns-3 and
how it relates to some of its long-term goals, such as improving the
integration of simulation tools with real-world applications and
experimentation testbeds.

Location of ICSI in Berkeley:
http://www.icsi.berkeley.edu/about/location.html

- Sally
http://www.icir.org/floyd/

Re: [ns] Why routing is performed on layer 2 in IEEE 802.11s wireless mesh networks standard

[Arturo Servin]

I remember something similar with Frame Relay and mostly with ATM,  
which in deed had its own routing protocol PNNI. I do not know about  
IEEE 802.11s but with ATM you need to switch the cells independently  
from the L3 protocol (then it came MPLS and we forgot about ATM), I  
imagine that 802.11s has some needs about meshing topologies, roaming,  
etc. that require that independent routing from the L3.

Regards,
-as

On 19 May 2008, at 22:24, Ghada Al-Mashaqbeh wrote:

>
>  Dear all,
>
>  I just want to find a reasonable justfications of why the IEEE  
> 802.11s standard have specified that routing must take place at  
> layer 2 of the protocol stack not layer 3? and which is better  
> routing on layer 2 or layer 3 of the protocol stack?
>
>  Thanks,
>
>  Ghada
>
>
>
>

[ns] Why routing is performed on layer 2 in IEEE 802.11s wireless mesh networks standard

[Ghada Al-Mashaqbeh]

  Dear all,
   
  I just want to find a reasonable justfications of why the IEEE 802.11s 
standard have specified that routing must take place at layer 2 of the protocol 
stack not layer 3? and which is better routing on layer 2 or layer 3 of the 
protocol stack?
   
  Thanks,
   
  Ghada
  


   

Re: [ns] Fwd: installing underwatermiracle module

[Marco Miozzo]

Hi,

you may find documentation on how to installl miracle and its related
packages at the following link:
http://telecom.dei.unipd.it/pages/read/16/
http://www.dei.unipd.it/~baldo/nsmiracle-dei80211mr-howto.html

For further information, let me suggest you to use the miracle-users
mailing list, you can find it at the following link:
https://mail.dei.unipd.it/mailman/listinfo/nsmiracle-users

Best regards,
Marco Miozzo



On Mon, May 19, 2008 at 5:12 PM, Dewald Nolte <[EMAIL PROTECTED]> wrote:
>
> -- Forwarded message --
> From: Dewald Nolte <[EMAIL PROTECTED]>
> Date: Mon, May 19, 2008 at 4:28 PM
> Subject: installing underwatermiracle module
> To: ns-users@isi.edu
>
>
> Hi all
>
> I have a very simple problem, but just not sure how to go about it.
>
> I want to install the underwater moduel for ns-miracle, but im not
> sure how to do this?
>
> Can anyone please help. Im sure it'll be similar to installing nsmiracle?
>
> Thanx alot
>
> Dewald
>
>

[ns] Fwd: installing underwatermiracle module

[Dewald Nolte]

-- Forwarded message --
From: Dewald Nolte <[EMAIL PROTECTED]>
Date: Mon, May 19, 2008 at 4:28 PM
Subject: installing underwatermiracle module
To: ns-users@isi.edu


Hi all

I have a very simple problem, but just not sure how to go about it.

I want to install the underwater moduel for ns-miracle, but im not
sure how to do this?

Can anyone please help. Im sure it'll be similar to installing nsmiracle?

Thanx alot

Dewald

[ns] How to export NS 2.26 to a linux distribution with GCC 4.2.1

[Cristiano Zema]

Hi all,
   I have NS version 2.26 installed on Linux (Mandrake 10 distribution) since 
some years. During these years the original version of NS2 was developed with 
new modules and stuffs needed for work, so I have to use that version of NS2 
and all the modified things. Now I need to export NS2 2.26 to another Linux 
distribution (Open Suse 10.3), that uses GCC version 4.2.1.
I made a backup of NS2 modified version and I tried, together witm some 
collegues, to run the NS2 installer. We had some compatibility problems with 
GCC 4.2.1 and we modified the code where needed. One of the last problems we 
had is a problem concerning some standard libreries header files. Here attached 
you can find the installer output.
Is there someone that can help us to export NS2 2.26 using the GCC 4.2.1 ??
Is it possible? Or do we need to use another version of GCC ?
Can someone tell us please which is the latest version of CGG compatible with 
NS2 2.26?

Thank you in advance for your kind answers. 

* Build ns-2.26

loading cache ./config.cache
No .configure file found in current directory
Continuing with default options...
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
checking for gcc... (cached) gcc
checking whether the C compiler (gcc  ) works... yes
checking whether the C compiler (gcc  ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for c++... (cached) c++
checking whether the C++ compiler (c++  ) works... yes
checking whether the C++ compiler (c++  ) is a cross-compiler... no
checking whether we are using GNU C++... (cached) yes
checking whether c++ accepts -g... (cached) yes
checking how to run the C preprocessor... (cached) gcc -E
checking for ANSI C header files... (cached) yes
checking for string.h... (cached) yes
checking for main in -lXbsd... (cached) no
checking for socket in -lsocket... (cached) no
checking for gethostbyname in -lnsl... (cached) yes
checking for dcgettext in -lintl... (cached) no
checking for getnodebyname in -ldnet_stub... (cached) no
checking that c++ can handle -O2... no
checking if STL works without any namespace... no
checking if STL works with namespace std... yes
checking will use STL... yes
checking for tcl.h... -I../include
checking for libtcl8.3... -L../lib -ltcl8.3
checking for init.tcl... ../lib/tcl8.3
checking for tclsh8.3.2... (cached) ../bin/tclsh8.3
checking for tk.h... -I../include
checking for libtk8.3... -L../lib -ltk8.3
checking for tk.tcl... ../lib/tk8.3
checking for otcl.h... -I../otcl-1.0a8
checking for libotcl1.0a8... -L../otcl-1.0a8 -lotcl
checking for tclcl.h... -I../tclcl-1.0b13
checking for libtclcl... -L../tclcl-1.0b13 -ltclcl
checking for tcl2c++... ../tclcl-1.0b13
checking for X11 header files
checking for X11 library archive
checking for XOpenDisplay in -lX11... (cached) yes
checking for XShmAttach in -lXext... (cached) yes
checking for libtcldbg... no
checking dmalloc... not requested with --with-dmalloc
checking for perl... /usr/bin
checking for ANSI C header files... (cached) yes
checking for bcopy... (cached) yes
checking for bzero... (cached) yes
checking for fesetprecision... (cached) no
checking for getrusage... (cached) yes
checking for sbrk... (cached) yes
checking for snprintf... (cached) yes
checking for arpa/inet.h... (cached) yes
checking for netinet/in.h... (cached) yes
checking for string.h... (cached) yes
checking for strings.h... (cached) yes
checking for time.h... (cached) yes
checking for unistd.h... (cached) yes
checking for net/ethernet.h... (cached) yes
checking return type of random... long
checking for int8_t... (cached) yes
checking for int16_t... (cached) yes
checking for int32_t... (cached) yes
checking for u_int8_t... (cached) yes
checking for u_int16_t... (cached) yes
checking for u_int32_t... (cached) yes
checking for u_char... (cached) yes
checking for u_int... (cached) yes
checking for strtoq... (cached) yes
checking for strtoll... (cached) yes
checking size of long... (cached) 4
checking for __int64_t... no
checking for long long... yes
checking for int64_t... (cached) yes
checking which kind of 64-bit int to use... int64_t
checking for struct ether_header... found
checking for struct ether_addr... found
checking for addr2ascii... (cached) no
checking for Linux compliant tcphdr... found
checking for BSD compliant tcphdr... not found
checking for socklen_t... (cached) yes
checking for main in -lpcap... (cached) no
checking to make nse... no
Explicitly disabling static compilation
checking for dlopen in -ldl... (cached) yes
checking for a BSD compatible install... (cached) /usr/bin/install -c
creating ./config.status
creating Makefile
creating tcl/lib/ns-autoconf.tcl
creating indep-utils/webtrace-conv/ucb/Makefile
creating ind

Re: [ns] [tcpsat] How to add ISL between LEO satellite and GEO satellite inNS2?

[L.Wood]

Create a LEO satellite of zero inclination orbit at GEO altitude.

<[EMAIL PROTECTED]>



-Original Message-
From: [EMAIL PROTECTED] on behalf of ?bluesky
Sent: Mon 2008-05-19 12:33
To: ns-users@ISI.EDU; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: [tcpsat] How to add ISL between LEO satellite and GEO satellite inNS2?
 
Hi,dear friend.There are methods for users to add ISL (intraplane, interplane 
and crossseam) or GSL between satellites and terminals, but I cannot find the 
references for me to add the ISL between the LEO satellites and the GEO 
satellites. How can I do to solve this problems?Thanks!Best Regards1Li-zheng 
Jiang 18.May 2008

[ns] Exp and Poisson Traffic

[FERLIN,Simone]

Hi ns'ers,
Does anybody know how to check the given values to burst and idle times in
ns?

tks,

[ns] Accessing Node by its ID ???

[Mubashir Rehmani]

Hi Everyone

I want to access the node by its id 

I know how to get the current id of node that is currently dealing by NS2 by
using the command
Node::nodeid();
Basically the problem is that NS2 treats node by node and the above command
return the nodeid which is in treatment by NS. And I want to access a
particular node irrespective of NS treatment of node.


And i also know that how to get the total number of Nodes by using the
command
God::instance()->nodes();

What i want is very simple. I need to call a particular function by calling
node by its id. For instance if NS2 is treating Node 2 and I want to call a
function of Node5 then i want things like that
Node5.id() ==> This command should return me the node id i.e. 5
Node5.particularfucntion(). ==> This command should call a function for node
5.

Is their any way to do this?

Thanks in advance.

Regards

-- 
Mubashir Husain Rehmani

M2R Réseaux et Télécommunications
L2S Supélec
Université de Paris Sud XI

Mobile France: 00 33 (0)6 32 00 89 35

[ns] One week left: CFP for Workshop on ns-2 (WNS2)

[Lloyd Wood]

Only one week more to submit your full papers to this conference!

WNS2, the Workshop on ns2 (and -3) that is the ns event of the year, is this 
October in Athens, Greece, home of the Acropolis and Parthenon, but not of the 
Elgin marbles.
http://www.wns2.org/
http://www.wns2.org/docs/wns2-2008-call-for-papers.pdf

WNS2 part of Valuetools 2008, and is taking place in Athens the same week as 
the Internet Measurement Conference.
http://www.imconf.net/imc-2008/cfp.html

WNS2 is in association with ACM, and papers will be archived in the ACM library.

Do submit your papers! You have until 25 May to upload a full paper via 
http://www.cocus.info (Cocus - a Greek Titan.)

L.

for the WNS2 co-chairs.

<[EMAIL PROTECTED]>

SCOPE

ns, the free open-source network simulator, is the de-facto standard for 
research over a wide variety of networking areas. ns version 2 is widely used 
across both academia and industry as a way of designing, testing and evaluating 
new and existing protocols and architectures, and has also proven a very useful 
tool for teaching purposes. ns version 3 is under active development.

The Workshop on ns-2 (WNS2) is a two-day event held in conjunction with 
VALUETOOLS 2008, the Third International Conference on Performance Evaluation 
Methodologies and Tools (http://www.valuetools.org/), during the week of 20-24 
October 2008 in Athens, Greece. WNS2 2008 follows the success of the first WNS2 
workshop in 2006. A tutorial day on Thursday 23 October is followed by 
presentation of reviewed papers on Friday 24 October 2008.

The main goals of this second WNS2 workshop are to bring together networking 
researchers from both academia and industry, to discuss recent advances, to 
identify future directions in network simulation, and to foster 
interdisciplinary collaborative research in this area. The workshop aims to 
emphasise the future evolution of ns-2, now that ns-3 is under active 
development, and its extension in novel research areas and networking 
technologies and scenarios.

TOPICS

This workshop focuses on the ns simulator in itself, and in improving 
simulation. We seek original contributions that go beyond the use of ns-2 "as 
is" for networking scenarios, and which try to make ns do something new and 
different. Topics of interest for the Workshop include, but are not limited to:

Structural developments/enhancements to the NS-2 simulator itself:

* Presentation/evaluation of new features/architectures under development 
for ns-3.
* Dynamic management of libraries / ns-Modules.
* Large-scale network simulation and model-based simulation approaches.
* Development of parallel and distributed versions of ns. Use of 
virtualization with ns.
* Integration of simulation and emulation.
* Post-processing tools, including GUIs for statistical analysis and 
visualization of simulation results.

Simulator use and validation of simulation accuracy:

* Validation of ns behaviour with experimentation and real data from 
implementations.
* Comparative studies of ns and other network simulation tools, both 
commercial and freely available.
* Environments and methodologies: the best practices, third-party code, 
helper scripts, and frameworks that serious users of ns recommend to get things 
done

New simulation models and features:

* Wireless channel modelling.
* Frameworks for cross-layer support.
* Mobile and wireless networks, 3G/4G networks, WLANs, WPANs, WiMAX, Mesh 
networks...
* Delay-tolerant networking.
* Congestion-control and transport-layer issues in long-fat networks.
* Mobility: network mobility (NEMO), physical node mobility (e.g., group 
mobility models).
* Sensor and actuator networks (wireless, underwater, underground).
* Peer-to-peer systems.
* Network coding: data dissemination, encoding/decoding suites.
* Grid computing.

Important Dates
Full Papers due: May 25, 2008
Notification of Acceptance: July 1, 2008
Camera-ready Manuscripts due: August 1, 2008
Conference Dates: October 23-24, 2008