Contents

1. Is this FAQ list in progress?
2. What is the difference between Emulab's control network and my experiment's network?
3. Why is my experiment's network traffic going over Emulab's control network?
4. Why can't my program find its shared libraries when I run it via sudo?

1. Is this FAQ list in progress?

Yes. It's not very useful yet, and the answers are terse. Think of this page as a FAQ outline.

2. What is the difference between Emulab's control network and my experiment's network?

See the answer to this question in the Emulab FAQ.

3. Why is my experiment's network traffic going over Emulab's control network?

All Emulab hosts have multiple network inetrface cards --- i.e., they are multi-homed. One of these interfaces is attached to the Emulab control network; this is the interface that provides access to your nodes from the outside world (ssh, NFS, DNS, etc.).

The fully qualified name of a host in your experiment refers to the network interface that goes to the Emulab control network. So, if you use the fully qualified name to configure a program that sends network packets, that program is almost certainly going to send packets via the control network. E.g., `ping host.exp.pces.emulab.net'.

The usual solution is to use abbreviated host names, or to use numeric IP addresses.

Issues with TAO's AV service.

4. Why can't my program find its shared libraries when I run it via sudo?

sudo removes LD_LIBRARY_PATH from the environment before running the program. The solution is to either (1) run your program via a script that sets LD_LIBRARY_PATH, or (2) run a shell via sudo, set LD_LIBRARY_PATH the way you like, and then run your program.

Last modified: Thu Jun 26 2003 09:47:35 MDT