[ns] Classfier::no-slot{} default handler (tcl/lib/ns-lib.tcl)
WINDFISH
u0083900 at cc.ncu.edu.tw
Sat Apr 16 02:10:34 PDT 2005
Dear all:
Sorry for the same letter again.=20
I found the topologies showed in the website are different from what I =
typed, and that could cause some misunderstanding. So, I sent the same =
letter again and added an annotation to the second typo. I hope this =
would help.
I encountered with the same problem - "Classfier::no-slot{} default =
handler (tcl/lib/ns-lib.tcl)." My original topology is as follows:
(1.0.1) (0.0.0)
w0 n1
\ /
(1.0.0) BS ______ n4 (0.3.0)
/ \
n2 n3
(0.1.0) (0.2.0)
The link between w0 and BS(base station) is a wireless link(802.11). The =
others link are all wired. I created a TCP connection between w0 and n3. =
Then I sent a tcp packet from w0 to n3, the problem, =
Classfier::no-slot{} default handler (tcl/lib/ns-lib.tcl), occurred. And =
the trace file showed that package arrived at n2.
However, I found the suggestion here from Xie Sheng, so I changed my =
topology as follows:
n1 (0.0.0)
(1.0.1) (1.0.0) (0.3.0) /
w0 ______ BS _______ n4 _____ n2 (0.1.0)
\
n3 (0.2.0)
(annotation: n1, n2, n3 all attach to n4)
Unfortunately, the problem still happened. The packet arrived at n1. I =
tried to exchange the addresses between n4 and n1, then the packet =
arrived at n4. In other words, the packet would arrive at 0.0.0 no =
matter what the destination of the packet is.
I also tried to use manual routing, but it occurred another problem in =
BS.
Could someone help me? Please tell me how to solve this problem. Is =
there any trouble in my second topology?
Thank you,
Charlene Hung
More information about the Ns-users
mailing list