Project

General

Profile

Actions

Bug #1448

closed

nfd crash when trying to ping a multiple faces prefix using broadcast strategy.

Added by Hila Ben Abraham about 10 years ago. Updated about 10 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
Forwarding
Target version:
Start date:
04/07/2014
Due date:
% Done:

100%

Estimated time:

Description

The way to reproduce:

(start nfd on nodes A & B)

$ build/bin/nfdc create udp://192.168.1.2
$ build/bin/nfdc create tcp://192.168.1.2
$ build/bin/nfdc add-nexthop ndn:/test-nfdc 7  10
$ build/bin/nfdc add-nexthop ndn:/test-nfdc 13 10
$ build/bin/nfdc set-strategy ndn:/ ndn:/localhost/nfd/strategy/broadcast
$ /ndn-tlv-ping/build/ndnping ndn:/test-nfdc -c 20

nfd: ../daemon/table/strategy-choice.cpp:172: nfd::fw::Strategy& nfd::StrategyChoice::findEffectiveStrategy(const nfd::pit::Entry&) const: Assertion `static_cast<bool>(nameTreeEntry)' failed.

IMPORTANT:
Doesn't happen when the prefix points to a single face (only a tcp4 face or a udp4 face). I was able to reproduce this bug only when I had more than one face attached to the prefix.


Related issues 1 (0 open1 closed)

Has duplicate NFD - Bug #1449: NFD crashes on broadcast strategy test scenarioClosed

Actions
Actions #1

Updated by Alex Afanasyev about 10 years ago

  • Category set to Tables
  • Priority changed from Normal to High
  • Target version set to v0.1
Actions #2

Updated by Junxiao Shi about 10 years ago

  • Has duplicate Bug #1449: NFD crashes on broadcast strategy test scenario added
Actions #3

Updated by Junxiao Shi about 10 years ago

  • Category changed from Tables to Forwarding
  • Status changed from New to In Progress
  • Assignee set to Junxiao Shi
  • % Done changed from 0 to 20

Confirmed.

Forwarder::onInterestUnsatisfied is invoked twice for the same PIT entry, because it's scheduled twice.

Actions #4

Updated by Junxiao Shi about 10 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 20 to 100
Actions #5

Updated by Hila Ben Abraham about 10 years ago

  • Status changed from Resolved to Closed

Verified.

Actions

Also available in: Atom PDF