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 email@example.com with your preferred username (different from your email address; see these guidelines) and we will create the account and enable it for write privileges.
- A new feature release, ns-3.25, is planned for January 2016.
- None posted for the moment.
- 30 September 2015: The ns-3.24 release was updated to ns-3.24.1 to fix some build issues.
- 15 September 2015: A new feature release, ns-3.24, was published.
- 28 August 2015: Four students successfully completed the 2015 Google Summer of Code.
- 14-15 May: The ns-3 Consortium annual meeting, and developer meetings, were held following WNS3.
- 14 May 2015: A new feature release, ns-3.23, was published.
- 13-14 May: The seventh annual Workshop on ns-3 was held in Barcelona, Spain.
- 11-12 May: ns-3 training sessions (two days) was held in Barcelona, Spain.
- 11-12 April 2015: Vimal Jyothi Engineering College, Chemperi held a Two Days National Workshop on “Network Simulator-3“.
- 27 March, 2015: Coding sprint on IRC
- 5 February 2015: A new feature release, ns-3.22, was published.
- 12 December 2014: ns-3 documentation sprint (online)
- 3 October 2014: ns-3 documentation sprint (online)
- 17 September 2014: A new feature release, ns-3.21, was published.
- September 2014: ns-3 Summer of Code in Space final reviews for our SOCIS student
- August 2014: ns-3 Google Summer of Code final reviews for our four GSoC students
- 17 June 2014: A new feature release, ns-3.20, was published.
- 8-9 May 2014: Developer meetings and ns-3 Consortium annual plenary, Atlanta GA. Meeting notes.
- 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.
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.