Account Policy: Due to spam problems, we have disabled the ability to create new accounts and to edit/move pages without moderator approval; our experience on the ns-2 wiki with Mediawiki captchas has been ineffective. If you would like to edit this wiki, please email firstname.lastname@example.org with your username and we will enable it for write privileges. Note: ns-2 has a separate wiki, at http://nsnam.isi.edu/nsnam/
- A new feature release, ns-3.21, is scheduled for September 5. Our most recent (ns-3.20) release can be downloaded here.
- 17 June 2014: A new feature release, ns-3.20, was released.
- 8-9 May 2014: Developer meetings and ns-3 Consortium annual plenary, Atlanta GA. Meeting notes will be posted shortly.
- 7 May 2014: The sixth annual Workshop on ns-3 was held in Atlanta, GA.
- 5-6 May 2014: The ns-3 Consortium offered two days of user training in Atlanta, preceding the Workshop on ns-3.
- 20 December 2013: A new feature release, ns-3.19, was released.
- 7-8 December 2013: NITK, Surathkal WiNG’s TEQIP-II Sponsored Workshop on Network Simulation using ns-3
- 3 December 2013: ns-allinone-3.18.2 was released to fix a regression in the DCE build system.
- 15 November 2013: ns-3.18.1, a maintenance release of ns-3.18 (previously released in August), was released.
- 15 November 2013: A documentation sprint was held.
- 4 November: The 16th Annual ACM International Conference on Modeling, Analysis, and Simulation of Wireless and Mobile Systems (MSWiM), Barcelona Spain, featured a demonstration of Direct Code Execution (DCE), featuring two typical use cases of DCE: information-centric networking over mobile ad hoc network using the PARC CCNx code, and a seamless handoff experiment based on a Linux Multipath TCP (MP-TCP) implementation.
- September through December: Dizhi Zhou has worked on an European Space Agency Summer of Code in Space (SOCIS) project, to implement the DTN Bundle Protocol.
- September: ns-3 Google Summer of Code final reviews for our two GSoC students:
Current ns-3-dev Build and Test Results
We use the Jenkins continuous integration (CI) tool to regularly test our development tree.
See our community portal.