Fun with MIL3 Opnet
MIL3's Opnet 16.0 was installed on a local network today, so I thought I'd try it out.
> opnet & [1] 28779 > ******************************************************** NOTE: Use of 'opnet' as the program name is deprecated, and will not be supported in future releases. Please use the actual program name to run the software. ********************************************************
Right, I should have invoked it by typing
modeler
, with
the US spelling. Rather than 'modeller,' as it's spelt in
the rest of the world. That was followed by a bunch of
warnings indicating that maintenance had expired, i.e. under
the educational license (which expires next month and will
need to be renewed) I'm on my own.
I tried building a test scenario, including a few things I thought I'd need. IP, Cisco stuff, TDMA... nothing fancy. I've spent the last six hours staring at a 'Please Wait' dialogue (sorry, dialog) alternating between 'Validating Demand Self-Description Database' and 'Validating Node Self-Description Database' while beeping. Eventually, I figured out how to disable the beep in the parent terminal.
Somehow, I don't think I'll be using Opnet Modeler for anything much, much less using Opnet Modeler for anything useful. So it's back to open-source ns; better the devil you know.
Update: It finally died after seven or so hours:
<<< Program Fault >>>
* Time: 17:58:16 Wed Jun 9 2010 * Product: modeler (32-bit) * Function: mmi_msg_tip_show_handler * Error: program abort -- segmentation violation
That's nice.
Update 2: Turns out the modeler binaries don't get along with Ubuntu 9, but are better behaved on Fedora Core. Shame we're switching to Ubuntu, really. The clue was that MIL3 supports Red Hat. Linux binary compatibility? Ha.