notes

在Linux下做的QuadTree的程序

 ./ns cmu/scripts/run.tcl -rp cmu/dsr/dsr.tcl -x 500 -y 500 -cp \
scen/cbr-50-20-8-2 -sc scen-500x500-0-10-1 -stop 30

 ./ns cmu/scripts/run.tcl -rp cmu/dsr/dsr.tcl -x 1500 -y 300 -cp \
scen/cbr-50-20-4-1 -sc scen/scen-1500x300-50-900-1-1 -stop 300

 ./ns cmu/scripts/run.tcl -rp cmu/dsr/dsr.tcl -x 1500 -y 300 -cp \
scen/1-conn -sc scen/scen-1500x300-50-0-2 -stop 900 -tr tr2

 ./ns cmu/scripts/dave.tcl -rp cmu/dsr/dsr.tcl -x 1500 -y 300 -cp \
scen/cbr-50-20-8-2 -sc  scen/scen-1500x300-50-0-2 -stop 100 -tr tr2

./ns cmu/scripts/run.tcl -rp cmu/dsdv/dsdv.tcl -x 1500 -y 300 -cp \
scen/cbr-50-30-4-2 -sc  scen/scen-1500x300-50-900-1-1 -stop 100

 ./ns cmu/scripts/run.tcl -rp cmu/dsdv/dsdv.tcl -x 1500 -y 300 -cp \
scen/cbr-50-30-4-2 -sc  scen/scen-1500x300-50-120-1-1 -stop 900


 ./ns cmu/scripts/run.tcl -rp cmu/dsdv/dsdv.tcl -x 1500 -y 300 -cp \
scen/cbr-50-10-4-2 -sc  scen/scen-1500x300-50-60-1-5 -stop 90

 ./ns cmu/scripts/run.tcl -rp cmu/dsr/dsr.tcl -x 1500 -y 300 -cp \
scen/cbr-50-20-4-2 -sc scen/scen-1500x300-50-900-1-4 -stop 170

 ./ns cmu/scripts/run.tcl -rp cmu/dsr/dsr.tcl -x 1500 -y 300 -cp \
cbr-50-20-4-768 -sc scen-1500x300-50-900-1-5 -stop 500

 ./ns cmu/scripts/run.tcl -rp cmu/dsr/dsr.tcl -x 1500 -y 300 -cp \
scen/cbr-50-20-4-1 -sc scen/scen-1500x300-50-0-1-1 -stop 100

 ./ns cmu/scripts/run.tcl -rp cmu/dsr/dsr.tcl -x 670 -y 670 -cp \
scen/cbr-50-20-4-1 -sc scen/scen-670x670-50-0-20-1 -stop 100

# to turn an out.tr into a list of source routes used to orginate
#   packets
perl -ne 'print "$1 $2\n" if /^SO.*\[\((\d+)\) (.*)\]/;' \
out.tr > src-rts

# to get unique sort routes
uniq src-rts usrc-rts
sort -n usrc-rts > susrc-rts
uniq susrc-rts usrc-rts
rm -f susrc-rts



5/13/98 0049 -dam I see reasonable numbers of route replies being
salvaged.  this seems potentially dumb, since if the reply is bad
(which it probably is, since we're reversing routes to return replies)
we should just dump it.  I've seen at least once this reply make to
the host and be used succesfully, so maybe congestion is triggering
fake 802.11 detects again?


heuristic: if a node has a route to a dest that is really long, and a
route to a dest that is much shorter, one of them is probably wrong.

Eg:


r 140.536753307 _42_ RTR  --- 5928 DSR 24 [20 0 ffffffff 6 800] ------- [6:255 3:255 32 0] 1 [1] [0 0 0] [0 0 0 0->0]
SRR 140.53675 _42_ cache-reply-sent 42 -> 6 (len 3) [(6) 42 3 ]
SO 140.53675 _42_ originating [(42) 6 ]

SRR 140.53809 _6_ reply-received from 42 -> 6 3
SO 140.53809 _6_ originating [(6) 42 3 ]

r 140.541748841 _42_ RTR  --- 5927 DSR 128 [20 a2 2a 6 800] ------- [6:255 3:255 255 42] 3 [0] [0 0 0] [1 1 3 6->5]
SRR 140.54175 _42_ dead-link 6 -> 5
SF 140.54175 _42_ [6 -> 3] via 0x3 [6 |42 3 ]

SSendFailure 140.56776 _42_ (5927) [6 |42 3 ]
S$hit 140.56776 _42_ salvaging 6 -> 3 (5927) with [(42) 6 43 13 44 28 3 ]
SIFQ 140.56776 _42_ len 0
SO 140.56776 _42_ originating [(42) 6 ]
SIFQ 140.56776 _42_ len 0
f 140.567764764 _42_ RTR  --- 5927 DSR 164 [20 a2 3 2a 800] ------- [6:255 3:255 255 6] 7 [0] [0 0 0] [1 1 3 6->5]
s 140.567764764 _42_ RTR  --- 5941 DSR 44 [20 a2 3 2a 800] ------- [42:255 6:255 255 6] 2 [0] [0 0 0] [1 2 6 42->3]
s 140.568093386 _6_ RTR  --- 5927 DSR 76 [20 a2 6 2b 800] ------- [6:255 3:255 255 42] 3 [0] [0 0 0] [1 1 3 6->5]

42's salvage route is correct; it's original cached reply is insane.  6
actually got lots of cached replies from neighbors who thought 3 was
nearby

egrep 'DSR .*---.*] .* \[0 .* \[0 .* \[0 .*' out.tr | more

------------------------
verifying the cache tracing stuff

check for any replies with tested links

 egrep 'adding .* \[1' xxx | more

check for replies from cache

 egrep 'adding .* \[1 .*\[2' xxx | more

looking for replies being caught by the tap

 egrep 'adding .* \[2 .* \[1' xxx | more