Frequently Asked Questions about NUTSS:

1. Q: What happened to [J]STUNT?
   A: JSTUNT was an initial proof of concept implementation that we are no longer supporting. Instead, you should use libnutss, which we are supporting, and which is intended to be production-useable.

2. Q: Who's using libnutss?
   A: A number of groups, both academic and industry, are evaluating NUTSS. A number have successfully compiled and ran it. We do not yet have any production users.

3. Q: What sort of machine do I need to do to use libnutss?
   A: You should be using a windows box, or linux. We haven't tested on other Unix systems, but it should work with minor modification. Macintosh support is likely in the future.

4. Q: Does NUTSS support UDP?
   A: Not yet. Currently, NUTSS is TCP-only. If you need UDP, you're out of luck for at least a few months. It's a fair bit of work, although we do intend to support UDP.

5. Q: Why does the Java version tell me "Exception in thread "main" java.lang.UnsatisfiedLinkError: jni_setProxy"?
   A: Libnutss isn't pure java. That error means it isn't finding the native libnutss.dll (or .so) that it needs to link against. There's a whole stack of DLLs that need to be somewhere on the library search path. (application's working dir is the best bet) They're in windows_libs.zip on the gforge download page.

   Also, be sure that if you build the library from source on Linux, you specify --enable-java during the configure stage.

6. Q: What do I need to build on Windows?
   A: You need Visual Studio 2005; you should be able to build with VC2003 if you create new project files.

7. Q: What does it mean when visual studio says something like "missing fatal error LNK1104: can not open libcharset.lib"?
   A: You need the dependencies; there's a stack of them, see next question. Headers, .lib import libraries, and the dlls are all in the windows_compat cvs module.

8. Q: What are the dependencies and their license terms?
   A: There's a bunch of them. Here's the list:

   • osip: LGPL [meaning you can use it in commercial software, but must include source to osip with your product]
   • exosip: GPL -- see this page for alternative license terms.
   • OpenSSL: apachelike, commercial use ok
   • Libxml: MIT license [can use in commercial software]
   • Libevent: BSD license, can use in commercial sw
   • Libcharset: LGPL
   • Pthreads: LGPL
   • Zlib: BSDish, can use in commercial sw

9. Q: Where do I go for help?
   A: Contact Ari Rabkin at asrabkin@gmail.com