Your e-mail messages will be slightly edited before being posted here :-) Ljiljana. Messages will be posted in a reverse chronological order (last message listed first) and grouped by the subject matter. ****************************************************************************** ****************************************************************************** From mtisdall@cs.sfu.ca Thu Feb 27 22:36:27 2003 Date: Thu, 27 Feb 2003 22:36:11 -0800 (PST) From: Dylan Tisdall To: Ljiljana Trajkovic UTP-x is what is I have known in the "IT world" as "Category x" cable. Thus, most ethernet runs over UTP-5 which any home-networker will buy as "cat five" when they walk into a computer store.... I don't mean to ask finicky IT questions in class, but occasionally implementation curiosity gets the better of me. Thanks, Dylan ****************************************************************************** From andthebrain@shaw.ca Thu Feb 13 22:24:32 2003 Date: Thu, 13 Feb 2003 22:20:45 -0800 From: Brian Fraser Subject: Compiling NS2 under GCC3.2 To: ljilja@cs.sfu.ca Hi Ljiljana, As we discussed in class today, here is the link to article that discusses how to compile NS2 under GCC 3.2. http://www.isi.edu/nsnam/ns/ns-problems.html#ns-allinone-2.1b9 There is a link to a patched version of the all-in-one file that does compile correctly. Brian. ****************************************************************************** From hzhange@cs.sfu.ca Wed Jan 29 21:50:51 2003 From: Hui Zhang Subject: ns-2 gurus: question. To: ljilja@cs.sfu.ca Cc: cnl-ensc2003@sfu.ca Dear Professor Ljiljana: This is Grace. When I ran the demo: ns tg.tcl, the nam did not show anything. I checked the ns2.1b8 in local2, and found the nam version in it is: nam-1.0a10. I checked the website: http://www.isi.edu/nsnam/nam/ The Binary Releases for nam is listed below: Nam 1.0a11a Windows (32-bit) (tested on Windows NT 4.0 and Windows XP, but may also work on Windows 95/98/ME/2000) Nam 1.0a11-prelease FreeBSD i386 Linux i386 Windows(32-bit) Nam 1.0a10 Binary Releases for: Windows(32-bit) Nam 1.0a9 Binary Releases for: i386 Linux Nam 1.0a8 Binary Releases for: FreeBSD 3.x Solaris 2.5 I wonder that this version may not work well in our workstation. And also I searched the problems that have been reported on line about the "nam-1.0a10". Many other users have met the very similar problem: it didn't show anything when running the sample simulation. However, if we delete the self-defined simulation topology (the commands with "orient"), the nam can work. For example in tg.tcl, if we delete the following few lines: "#$ns duplex-link-op $n0 $n1 orient right #$ns duplex-link-op $n0 $n2 orient left-up #$ns duplex-link-op $n0 $n3 orient left #$ns duplex-link-op $n0 $n4 orient left-down #$ns duplex-link-op $n0 $n5 orient down" the nam can work! In addition, here is the link for discussing the problems and tips of using ns2: http://www.isi.edu/cgi-bin/nsnam/htsearch. Thanks for reading this, and I'm sorry if this message bothers you. Wish you have a good night! Grace ------------- Begin Forwarded Message ------------- From: Ljiljana Trajkovic Date: Thu, 23 Jan 2003 20:57:57 -0800 (PST) To: cnl-ensc2003@sfu.ca Subject: ns-2 gurus: question. Cc: ljilja@cs.sfu.ca Folks, ns2.1b8 info: http://www.ensc.sfu.ca/people/faculty/ljilja/ENSC833/Tools/ns_info.html calls for a little demo: ns tg.tcl. Stundets in ENSC833/CMPT885 noticed that it does not work. It used to nicely work in ns2.1b6, but shows nothing in the NAM window when running ns2.1b8. Can anyone figure out why? Note that ns2.1b8 works fine with /ensc/dept1/ljilja/ns-2/example.tcl (except for some syntax warnings). Many thanks, Ljiljana ****************************************************************************** From ekchen@rm-rstar.sfu.ca Tue Jan 14 21:47:35 2003 To: eykeung@sfu.ca Cc: ljilja@cs.sfu.ca From: ekchen@sfu.ca Subject: Re: Problems launching OPNET / Tutorial problem Date: Tue, 14 Jan 2003 21:47:31 PST Hi Eric, I have problem getting the software required to launch OPNET remotely. In the section: Using SSH and TTSSH with Cygin/Xfree86, I couldn't obtain Cyginwin/Xfree86 from the web. It seems that the like the link ftp://mirrors.rcn.net/pub/sourceware/cygwin/xfree/xc-4-binaries/4.1.0/ is not available. I tried access this site from the top down but reached only: ftp://mirrors.rcn.net/pub/sourceware/cygwin/xfree/ . At that point, I couldn't find the xc-4-binaries directory. Thanks for your attention. Edward From hchenj@sfu.ca Thu Jan 16 08:57:24 2003 From: "Johnson Chen" To: Cc: , "Ljiljana Trajkovic" Subject: RE: Problems launching OPNET / Tutorial problem Date: Thu, 16 Jan 2003 09:04:29 -0800 Hi Edward, In the same webpage where you obtain Cygwin, http://sources.redhat.com/cygwin/, on the left side, you should see a subsection called "XFree86", follow the link and you could get the needed software. I havent tried that software in the new link yet, well it looks pretty much workable as Xfree86 is a very active GNU project. It is usual for the change of mirrored sites from time to time, but generally you are able to get the latest or stable version of software from its "offical" site. One rule of thumb, a search engine will do a fairly good job for you in similar case. Enjoy, Johnson ****************************************************************************** From owner-ensc833-g1@rm-rstar.sfu.ca Tue Jan 14 11:07:04 2003 Date: Tue, 14 Jan 2003 11:06:20 -0800 To: ensc833-g1@sfu.ca From: Eric Keung Subject: Re: Problems launching OPNET / Tutorial problem Hi all, The problem with launching OPNET from the Aquarium (Ensc Grad Computer Lab) is fixed. You may now launch OPNET directly from those local machines. If you are still encounter any problem, please e-mail me. Regarding the CS grad lab access for OPNET, it turns out that you can only access OPNET remotely through payette. And for those who tried running the tutorials for OPNET, you might encounter some problems. Specifically, the Small Internetworks tutorial. In that tutorial, it ask for a specific switch (3C_SSII_3300_2s_ae24_ge). That model for some reason is not supported by v9.0.A. Therefore, for the mean time, you'll have to access that switch through the v8.0.C library. Here is how this can be done. Close OPNET and modify 2 lines in your env_db9.0 file. The file reside in the op_admin directory. The lines you need to modify is under the section "mod_dirs". mod_dirs : /ensc/local2/opnet/9.0.A/sys/lib, ... .. . /ensc/local2/opnet/9.0.A/models/vendor_models/Xylan, >>>>> /ensc/local2/opnet/8.0.C/models/vendor_models/Cisco_Systems, /ensc/local2/opnet/9.0.A/models/vendor_models/Newbridge, /ensc/local2/opnet/9.0.A/models/vendor_models/Ascend, >>>>> /ensc/local2/opnet/8.0.C/models/vendor_models/3Com, ... .. . After that relaunch OPNET and open your files, try to follow the instructions and find the switch again. Hope this helps. Eric From saviol@sfu.ca Tue Jan 14 14:51:21 2003 Date: Tue, 14 Jan 2003 14:51:14 -0800 From: Savio Lau To: Catherine Crosbie Cc: ljilja@cs.sfu.ca, eykeung@sfu.ca, ensc-help@fornax.cs.sfu.ca Subject: Re: OPNET models problem After a little bit more of investigation I can report that the problem is more widespread than I initially suspected. Ex. The Sm_Int_Model tutorial's palette list is dated Year 2000 in OPNET 9.0.A whereas the equivalent one in 8.0.C is dated for 2001 (in directory models/std/tutorial_req/modeler) I tried to get around the 3Com problem by temporarly using the OPNET 8 render model libaries but I discover that a lot of the other files (such as the external C files oms_pkt_analyzer) are missing also, making the same tutorial refuse to compile. (in directory models/std/utilities/packet_analyzer) I am suspecting that we are missing a large number of model library files in the current version. Savio To: crosbie@sfu.ca From: OPNET Technical Support Subject: (TSC 101711) X-Spam-Level: Spam-Level SS Resent-Date: Tue, 14 Jan 2003 14:58:16 -0800 Resent-To: ensc-help@sfu.ca Dear Catherine Crosbie, I looked in the tutorial for "Small Internetworks" and it ask you to use node model named as "3C_SSII_1100_3300_4s_ae52_e48_ge3". I checked for this node model and this model is part of the standard model library and can be found in "3com" palette. Your configuration information at OPNET states that you have documentation dated 2002-09-29 which doesn't require node model named "3C_SSII_3300_2s_ae24_ge". Please make sure that you have 2002-09-29 documentation, you can verify by going to "Help->About This Application" and look for "OPNET Modeler Documentation". If you don't have the latest documentation then please get the latest documentation from OPNET FTP site. Thanks Varun L. Technical Support OPNET Technologies, Inc. ------ Register for OPNET's Online Technology Workshops (http://www.opnet.com/TechWorkshops/) ------ From saviol@sfu.ca Tue Jan 14 15:37:12 2003 Date: Tue, 14 Jan 2003 15:37:05 -0800 From: Savio Lau To: Catherine Crosbie Cc: ljilja@cs.sfu.ca, ensc-help@fornax.cs.sfu.ca, eykeung@sfu.ca Subject: Re: OPNET models problem It's correct that for that particular tutorial the 3C_SSII_1100_3300_4s_ae52_e48_ge3 should be used instead of the 3C_SSII_2s_ae24_ge. Regardless, the 3C_SSII_1100_3300_4s_ae52_e48_ge3 can be found in the 8.0.C model/vendor_models/3Com directory but not in the 9.0.A equivalent directory. I have checked further and even some of the modeler tutorial fails. The "simple source", one of the most used node model has problems linking the different packet formats. I discovered this while trying to run through the "Packet Switching I" tutorial. I have verified this model source problem in my own thesis project also. I suspect that most if not all of the models' libraries are missing files. Savio From saviol@sfu.ca Thu Jan 16 15:35:47 2003 Date: Thu, 16 Jan 2003 15:35:11 -0800 From: Savio Lau To: Catherine Crosbie Cc: ljilja@cs.sfu.ca, eykeung@sfu.ca, ensc-help@fornax.cs.sfu.ca Subject: Re: OPNET 9 re-install completed I have just ran through the whole Small Internetworks Tutorial. That works as described now. I have also manually checked for the missing files that I have noticed from last time. Now they are all there. So in general I can conclude that the previously mentioned problems are solved. Thank you Catherine for all the work. Savio ****************************************************************************** From owner-ensc833-g1@rm-rstar.sfu.ca Tue Jan 14 10:24:47 2003 Date: Tue, 14 Jan 2003 10:24:34 -0800 To: ensc833-g1@sfu.ca From: Eric Keung Subject: Running OPNET under Linux / X Instructions Cc: Savio Lau Hi all, For those that have Linux at home or are operating in the Linux environment, please refer to the following instructions for accessing OPNET remotely. These instruction are provided courtesy to Savio Lau, my colleague at CNL. Eric >Date: Mon, 13 Jan 2003 13:08:13 -0800 >From: Savio Lau >To: Eric Keung >Subject: OPNET Linux / X Instructions > >Any *NIX (UNIX, Linux) machine with a graphical desktop would have their >own X-server running. > >So this is the instruction of running OPNET from a Linux machine running X >Windows. If a machine has KDE or Gnome desktop, then it has X-windows. > >1. If the local machine have a firewall, expose TCP ports 6000-6009. Those >ports are needed for the Remote X-link. This is not necessary if it's run >from most UNIX stations in SFU. >2. open a terminal window. >3. run the following command (not necessary in SFU ENSC machines): >"xhost payette.ensc.sfu.ca" - this assumes that Payette is the OPNET >server. This indicates that incoming X connections from >payette.ensc.sfu.ca is trusted. >4. ssh to payette.ensc.sfu.ca >5. export the X display connection to the local machine by entering >command: >"setenv DISPLAY 111.111.111.111:0.0" where 111.111.111.111 is the local >machine's IP address. >6. Run OPNET through command "opnet &" > >-- >Savio Lau >SFU Engineering Science >Computer Engineering Option >5th year >Email: saviol@sfu.ca >ICQ UIN 8585945 ******************************************************************************