The mailing is is now subscriber only---please see the FAQ entry on "How do I post to the mailing list? Why was my post rejected?" for details.
Please see "where to start" on the building ns web page: http://www.isi.edu/nsnam/ns/ns-build.html#start.
This question is answered in detail at http://www.isi.edu/nsnam/ns/ns-problems.html#downloading.
All documentation is linked from the main ns web page http://www.isi.edu/nsnam/ns/. Documentation includes a tutorial (originally from Marc Greis) and a reference manual (ns notes and documentation).
Many sample scripts can be found in the ns distribution in ~ns-2/tcl/ex and ~ns-2/tcl/test.
A lot! Almost all variants of TCP, several forms of multicast, wired networking, several ad hoc routing protocols and propagation models (but not cellular phones), data diffusion, satellite, and other stuff. See the documentation (described above) for details, or download ns and look.
Ns has validation tests that cover many protocols, see http://www.isi.edu/nsnam/ns/ns-tests.html. However, ultimately users are responsible for verifying that ns is accurate for their purposes---since we cannot foresee all the ways ns may be used, we cannot test all cases with all inputs.
Yes, please see the contributed code web page http://www.isi.edu/nsnam/ns/ns-contributed.html. The mailing list archives can also be helpful (see below).
We recommend that you look through the tutorial (see documentation, above), then start with an example program that is most similar to yours (in the tutorial, or in tcl/ex or tcl/test in the distribution), and then start changing things.
go to ns directory and run "make" or "make depend; make"
As of June 2004 the ns-users lists allow posts from subscriber only. If you're not a subscriber, your posts to the list will be rejected. (This is unfortunately necessary to dispose efficiently of spam; manual filtering is too expensive.) We realize that the list is high traffic, so if you wish to post to the list without receiving messages on it, please subscribe and select the no-mail option for your subscription.
For details about the mailing list including mailing-list specific FAQ (for example, what if you're subscribed but still can't post), please see http://www.isi.edu/nsnam/ns/ns-lists.html.
See the http://www.isi.edu/nsnam/ns/ns-lists.html web page for help debugging mailing list problems.
If you've checked the installation problems and bug fixes web page (http://www.isi.edu/nsnam/ns/ns-problems.html) and there's no answer to your question, you may want to file a bug report or post a question to the ns-user's mailing list.
First, you should check the archive of the list at http://www.isi.edu/nsnam/ns/ns-lists.html. Your question may already be answered there.
If not, you can post a bug report using the web form at http://www.isi.edu/cgi-bin/nsnam/reportbug.cgi.
If your question is NOT about ns implementation bugs, you may wish to post to the list. First you should subscribe. Subscription instructions are at http://www.isi.edu/nsnam/ns/ns-lists.html.
Please note that mail sent to the list is publicly distributed and archived. If you have concerns about your message being made public (spam harvesting of your address), please consider that before posting. We cannot remove messages from reciepient's mailboxes or the public archive after they're posted.
When posting bug reports, please always include information including at least (the bug report form includes spaces for these):
Soo-Hyun Choi observed from posts to the list: Sometimes, I see this list is filled with the questions with: 1) asked many times before 2) hardly understandable what this guy is asking 3) too easy to find an answer over a few clicks over the Internet 4) soliciting to do their homework in a simple way by asking in this list 5) easily seekable an answer by contributing a couple of hours of reading the ns-manual 6) etc, etc.
As many of us in this list are doing an advanced degree, it would be suggested to read the following article in order to raise a useful/meaningful question in a smart way. http://www.catb.org/~esr/faqs/smart-questions.html
This is very good advice, since asking the Right Question is very likely to get a good/helpful answer, while asking a question poorly. For example, think about how you would answer these two questions: "Ns doesn't work for me, it crashes. Help." as compared to "I get a segmentation fault when running test script test-suite-webcache on Mandrake 10 Linux. The backtrace is on my web page at www.someu.edu/~someone. It looks like it passes in the on-line test suites, but it fails for me. Am I doing something wrong?
A reminder about mailing list etiquette: