Re: [ns] Classfier::no-slot{} default handler (tcl/lib/ns-lib.tcl) help me ??

2015-05-28 Thread knudfl
> @yang The error »»- Classfier::no-slot{} default handler (tcl/lib/ns-lib.tcl) ---«« is a generic error. Can happen for several reasons : Faulty simulation scripts. ( file.tcl, etc.) By using the wrong OS / the wrong architecture for an added protocol. A failed build of ns2 ( + some added pro

[ns] Classfier::no-slot{} default handler (tcl/lib/ns-lib.tcl)

2012-08-09 Thread sujana1
http://old.nabble.com/file/p34275794/mytopo1.png My tcl script gets compiled,but the trace and nam files are empty.i get the following message.. --- Classfier::no-slot{} default handler (tcl/lib/ns-lib.tcl) --- _o20: no target for slot 3 _o20 type: Classifier/Addr content dump:

[ns] -- Classfier::no-slot{} default handler (tcl/lib/ns-lib.tcl) --- error

2010-04-20 Thread Emma Ch
Hi every body; I have to simulate a scenario, every thing is well, but i have a problem on: SORTING LISTS ...DONE! --- Classfier::no-slot{} default handler (tcl/lib/ns-lib.tcl) ---     _o30: no target for slot 7     _o30 type: Classifier/Port content dump: classifier _o30     0 offset     0 shif

[ns] --- Classfier::no-slot{} default handler (tcl/lib/ns-lib.tcl) ---

2010-04-16 Thread sahib
Dear All Does anybody has any idea to resolve the following error pleae::-( --- Classfier::no-slot{} default handler (tcl/lib/ns-lib.tcl) --- _o76: no target for slot -1 _o76 type: Classifier/Hash/Dest content dump: classifier _o76 0 offset 0 shift

[ns] Classfier::no-slot{} default handler (tcl/lib/ns-lib.tcl) with wired-cum-wireless scenario script

2007-11-17 Thread Ghada Al-Mashaqbeh
Dear all, I am running a wired-cum-wireless scenario to simulate the topology of Wireless Mesh Networks, I have 6 wired hosts, every two are belong to the same domain with a router for each domain, I have 60 mobile nodes, and 30 static wireless nodes, among the static nodes I have three b

[ns] Classfier::no-slot{} default handler (tcl/lib/ns-lib.tcl)

2007-03-08 Thread Pusik Park
Hi all, When I run a ring-topology protocol script,I get an error listed below. Would you please tell me how to deal with it? Thanks I saw the response of a similar question, he commented "make sure it is fully connected". My topology is n0 ---> n1 > n2 ---> n0 Isn't it fully connected