alexander.afanasyev at ucla.edu
Thu Dec 19 12:56:12 PST 2013
Unless I have misunderstood you, the policy that you describing is actually ns3::ndn::pit::Persistent. Under this policy, when limit has been reached, no new items will be accepted.
On Dec 18, 2013, at 10:10 PM, sajjad zarei <sajjadzarei67 at gmail.com> wrote:
> Tnx for your reply.
> I used class below in order to limit PIT size and set maxsize=50
> ndnHelper.SetPit ("ns3::ndn::pit::...",
> "MaxSize", 50);
> It uses 'reject policy'.but I dont want this policy.I am looking for a policy that if PIT is full then new interests will drop.
> would you please help me with suggesting an appropriate solution to the issue above?
> On Wed, Dec 18, 2013 at 1:20 PM, Alex Afanasyev <alexander.afanasyev at ucla.edu> wrote:
> If you set MaxSize 0, it means that PIT is not limited. You have to set some limit that is not 0.
> On Dec 17, 2013, at 8:36 AM, sajjad zarei <sajjadzarei67 at gmail.com> wrote:
> > hi.
> > I am intending to simulate flooding DDoS attack against PIT in NDN.
> > I need to use class below in order to limit PIT size!
> > ndnHelper.SetPit ("ns3::ndn::pit::...",
> > "MaxSize", "0");
> > when I used "persistent".I didn't see customer DDoS and no new interest was dropped.
> > I am looking for a policy such that if PIT is full, new interests are dropped.
> > would you please help me with suggesting an appropriate solution to the issue above.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ndnSIM