[ndnSIM] LongestPrefixMatch FIB problem

[Hisham Farahat]

Hi Alex,
No problem i've managed to solve the problem. I was using a string as the
name of the data to lookup the cache, but the original data stored in the
cache was named as two components (prefix and Seq).

Regards,

On Fri, Sep 4, 2015 at 5:08 AM, Alex Afanasyev <aa at cs.ucla.edu> wrote:

> Sorry for the delayed reply.  It doesn't look normal.  Can you send us a
> simple scenario that shows the problem?
>
> --
> Alex
>
> > On Aug 18, 2015, at 2:45 PM, Hisham Farahat <hishamfarahat at gmail.com>
> wrote:
> >
> > Hi,
> > LongestPrefixMatch when used with FIB gives wrong results. (I'm using
> ndnSIM 1.0.)
> >
> > The FIB of a node contains:
> > ############
> > Node
> >   Dest prefix      Interfaces(Costs)
> > +-------------+--------------------------------------+
> > /prefix_3     dev=net(0)(1,g,1)
> > /prefix_3/153 dev=net(1)(1,y,1)
> > #############
> >
> > The LongestPrefixMatch for interest "/prefix_3/153" is returning the
> first entry : "/prefix_3 dev=net(0)(1,g,1)"
> >
> > Is this normal?
> >
> > Regards,
>
>


-- 
Hisham Farahat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20150904/0e627a45/attachment.html>