[ee122] Getting MNL to transmit ACK's...

Lisa Fowler fowler at eecs.berkeley.edu
Sun Dec 9 22:26:04 PST 2007

On Dec 9, 2007 8:12 PM, Richard Schmidt <huntingtonsurfca at gmail.com> wrote:
> Additionally, the MNLDaemon can only process outgoing packets, thus you will
> have to build support for MNL on both your sender and receiver. This means
> that your sender and receiver and their corresponding MNLDaemons need to be
> executed in different paths (e.g. in different folders, on different
> computers, etc.) -- Wednesday Dec 5 12:44pm"
> Are those e.g.'s all required or are some optional?
> Different paths could mean different folders, or different computers...

You'll have to use different MNLDaemons for each given config file
since you can only specify one config per running MNLDaemon.
Additionally, way that MNLDaemon works is that it will save its
listening port number to a file (MNLDaemon.sock) -- even if you
renamed MNLDaemon to something else, it still saves it in the local
directory as MNLDaemon.sock .  (Maybe a note for a future release of

Since you can't trace on loopback, you'll have to generate the data
running MNLDaemon on different computers -- and even if you're using
the same directory replicated across different systems, you'll have to
use a different directory.


More information about the ee122 mailing list